Troubleshooting performance issues with archiving
When you observe performance issues with the archiving process, follow the appropriate logging and troubleshooting steps to either resolve a problem or create a BMC Support case.
Symptoms
Archiving Operation is taking too long to process the records.
Scope
- Individual Archive Operations are taking longer time than past runs.
- The total archiving process takes longer time.
Resolution
The following table describes the tasks performed to ensure that the Archiving process is running correctly:
Step | Task | Description | ||||||
---|---|---|---|---|---|---|---|---|
1 | Review the number of records being archived and the number of threads used to archive records. | Cause: When there are more records to process than before, the Archiving process takes a longer time to complete. As a company becomes more mature in the ITSM process, they create more records and have more assets and relationships between their data. As a result, more records get archived over time. To check whether the archiving process is taking longer time because of large number of records, perform the following steps:
Resolution: Add additional threads to your Archiving Operation. Configure the threads by setting the following component in CCS:
| ||||||
2 | Review the Individual SQL Queries. | Cause: When the Archiving Operation evaluates records to ensure they meet the archive qualification, the SQL statements used to evaluate the records can take a long time on some databases during certain scenarios. Enable the Archiving and SQL logs to check whether the archiving is taking longer time because of the SQL queries. Run the SQL logs through the AR Log Analyzer to identify poor running SQL queries. Resolution: The administrator must engage a Database administrator (DBA) to ensure that the database is healthy and help troubleshoot and tune the SQL query. The DBA should ensure that:
| ||||||
3 | Review the system resources. | Cause: While archiving records, the available system resources (CPU and Memory) can become very low. Occasionally, it might not be noticeable that a significant reduction in archiving performance has occurred. Additionally, you might notice that this adversely affects other operations the system might be trying to process. Resolution:
|