- Overview
- Requirements
- Installation
- Q&A: Deployment templates
- Configuring the machines
- Configuring the external objectstore
- Configuring an external Docker registry
- Configuring the load balancer
- Configuring the DNS
- Configuring Microsoft SQL Server
- Configuring the certificates
- Online multi-node HA-ready production installation
- Offline multi-node HA-ready production installation
- Disaster recovery - Installing the secondary cluster
- Downloading the installation packages
- install-uipath.sh parameters
- Enabling Redis High Availability Add-On for the cluster
- Document Understanding configuration file
- Adding a dedicated agent node with GPU support
- Adding a dedicated agent Node for Task Mining
- Connecting Task Mining application
- Adding a Dedicated Agent Node for Automation Suite Robots
- Post-installation
- Cluster administration
- Monitoring and alerting
- Migration and upgrade
- Migration options
- Step 1: Moving the Identity organization data from standalone to Automation Suite
- Step 2: Restoring the standalone product database
- Step 3: Backing up the platform database in Automation Suite
- Step 4: Merging organizations in Automation Suite
- Step 5: Updating the migrated product connection strings
- Step 6: Migrating standalone Insights
- Step 7: Deleting the default tenant
- B) Single tenant migration
- Product-specific configuration
- Out-of-sync Task Mining
- Cleaning up the Task Mining database
- Best practices and maintenance
- Troubleshooting
- How to troubleshoot services during installation
- How to uninstall the cluster
- How to clean up offline artifacts to improve disk space
- How to clear Redis data
- How to enable Istio logging
- How to manually clean up logs
- How to clean up old logs stored in the sf-logs bundle
- How to disable streaming logs for AI Center
- How to debug failed Automation Suite installations
- How to delete images from the old installer after upgrade
- How to automatically clean up Longhorn snapshots
- How to disable TX checksum offloading
- How to manually set the ArgoCD log level to Info
- How to generate the encoded pull_secret_value for external registries
- How to address weak ciphers in TLS 1.2
- Unable to run an offline installation on RHEL 8.4 OS
- Error in downloading the bundle
- Offline installation fails because of missing binary
- Certificate issue in offline installation
- First installation fails during Longhorn setup
- SQL connection string validation error
- Prerequisite check for selinux iscsid module fails
- Azure disk not marked as SSD
- Failure after certificate update
- Antivirus causes installation issues
- Automation Suite not working after OS upgrade
- Automation Suite requires backlog_wait_time to be set to 0
- GPU node affected by resource unavailability
- Volume unable to mount due to not being ready for workloads
- Failure to upload or download data in objectstore
- PVC resize does not heal Ceph
- Failure to resize PVC
- Failure to resize objectstore PVC
- Rook Ceph or Looker pod stuck in Init state
- StatefulSet volume attachment error
- Failure to create persistent volumes
- Storage reclamation patch
- Backup failed due to TooManySnapshots error
- All Longhorn replicas are faulted
- Setting a timeout interval for the management portals
- Update the underlying directory connections
- Authentication not working after migration
- Kinit: Cannot find KDC for realm <AD Domain> while getting initial credentials
- Kinit: Keytab contains no suitable keys for *** while getting initial credentials
- GSSAPI operation failed due to invalid status code
- Alarm received for failed Kerberos-tgt-update job
- SSPI provider: Server not found in Kerberos database
- Login failed for AD user due to disabled account
- ArgoCD login failed
- Failure to get the sandbox image
- Pods not showing in ArgoCD UI
- Redis probe failure
- RKE2 server fails to start
- Secret not found in UiPath namespace
- ArgoCD goes into progressing state after first installation
- Issues accessing the ArgoCD read-only account
- MongoDB pods in CrashLoopBackOff or pending PVC provisioning after deletion
- Unhealthy services after cluster restore or rollback
- Pods stuck in Init:0/X
- Prometheus in CrashloopBackoff state with out-of-memory (OOM) error
- Missing Ceph-rook metrics from monitoring dashboards
- Running High Availability with Process Mining
- Process Mining ingestion failed when logged in using Kerberos
- Unable to connect to AutomationSuite_ProcessMining_Warehouse database using a pyodbc format connection string
- Airflow installation fails with sqlalchemy.exc.ArgumentError: Could not parse rfc1738 URL from string ''
- How to add an IP table rule to use SQL Server port 1433
- Using the Automation Suite Diagnostics Tool
- Using the Automation Suite Support Bundle Tool
- Exploring Logs
Cleaning up the Task Mining database
This page describes the necessary maintenance tasks for the Task Mining databases.
[AutomationSuite_Task_Mining]
, uses a single schema [tddiscovery]
for data storage. Primarily, Task Mining stores data in the object store, reducing the need of frequent database maintenance.
If required, you can use the Remove_Active_History.sql
database maintenance script to periodically clean up the following database table:
-
[AutomationSuite_Task_Mining].[tddiscovery].[ActivityHistory]
[AutomationSuite_Task_Mining]
before executing any scripts.
The following prerequisites are assumed:
-
You have access to the
[AutomationSuite_Task_Mining]
database with the required permissions.
CREATE PROCEDURE [tddiscovery].[Delete_TaskMining_ActivityHistory]
@CutoffTimeStamp datetime2,
@BatchSize INT = 10000
AS
BEGIN
DECLARE @total_deleted_items BIGINT = 0;
SET NOCOUNT ON;
-- delete ActivityHistoryItems
DECLARE @Deleted_Rows_ActivityHistoryItems INT = @BatchSize;
WHILE(@Deleted_Rows_ActivityHistoryItems = @BatchSize)
BEGIN
DELETE TOP(@BatchSize) FROM [tddiscovery].[ActivityHistory] WHERE At <= @CutoffTimeStamp;
SET @Deleted_Rows_ActivityHistoryItems = @@ROWCOUNT;
SET @total_deleted_items = @Deleted_Rows_ActivityHistoryItems + @total_deleted_items;
END;
PRINT('The script executed successfully!');
PRINT('Total deleted rows from [tddiscovery].[ActivityHistory]: ' + CONVERT(NVARCHAR, @total_deleted_items));
END;
GO
CREATE PROCEDURE [tddiscovery].[Delete_TaskMining_ActivityHistory]
@CutoffTimeStamp datetime2,
@BatchSize INT = 10000
AS
BEGIN
DECLARE @total_deleted_items BIGINT = 0;
SET NOCOUNT ON;
-- delete ActivityHistoryItems
DECLARE @Deleted_Rows_ActivityHistoryItems INT = @BatchSize;
WHILE(@Deleted_Rows_ActivityHistoryItems = @BatchSize)
BEGIN
DELETE TOP(@BatchSize) FROM [tddiscovery].[ActivityHistory] WHERE At <= @CutoffTimeStamp;
SET @Deleted_Rows_ActivityHistoryItems = @@ROWCOUNT;
SET @total_deleted_items = @Deleted_Rows_ActivityHistoryItems + @total_deleted_items;
END;
PRINT('The script executed successfully!');
PRINT('Total deleted rows from [tddiscovery].[ActivityHistory]: ' + CONVERT(NVARCHAR, @total_deleted_items));
END;
GO
-
Run the
Remove_Active_History.sql
database maintenance script to create theDelete_TaskMining_ActivityHistory
Stored Procedure.Note:Always use the most recent version of the Stored Procedure.
If it already exists, drop the existing Stored Procedure and recreate it using the provided script. Alternatively, you can changeCREATE
toALTER
and then execute the script to update the stored procedure. -
Execute the
Delete_TaskMining_ActivityHistory
Stored Procedure. This deletes all data related to Activity History for a cut-off timestamp from the[AutomationSuite_Task_Mining].[tddiscovery].[ActivityHistory]
table.
PROCEDURE [tddiscovery].[Delete_TaskMining_ActivityHistory]
script, ensure that Task Mining usage is suspended.
Delete_TaskMining_ActivityHistory
SQL Stored Procedure.
Parameter |
Description |
Mandatory Y/N |
@CutoffTimeStamp
|
Delete all data before a specified timestamp (e.g., 2021-01-01 01:00:05). Note:
Do not provide a timestamp that leads to an empty table. |
Y |
@BatchSize INT = 10000
|
The number of rows to be deleted at a time. This enables you to delete the data batch by batch. The default is set to 10000.
|
N |
DECLARE @ProcessTime datetime2;
SET @ProcessTime = '2024-07-11 13:44:42.7856026';
EXEC [tddiscovery].[Delete_TaskMining_ActivityHistory] @CutoffTimeStamp = @ProcessTime;
DECLARE @ProcessTime datetime2;
SET @ProcessTime = '2024-07-11 13:44:42.7856026';
EXEC [tddiscovery].[Delete_TaskMining_ActivityHistory] @CutoffTimeStamp = @ProcessTime;
For more information, see the official Microsoft documentation on Stored procedures.