Troubleshooting the Archiving process
When the archiving process is running slower or records are not moved to archive, verify that the correct flag is set for the records, the required archiving policies are enabled, and the table indexing is complete.
Records are not being moved to the archive
Issue scope
When the archiving process is run.
Issue symptom
The records that otherwise meet the archiving criteria are not picked up by the process.
Resolution
Check the following points:
- Is the Do Not Archive flag set on the record? If the Do Not Archive flag is incorrectly set, clear the flag.
- Do the archiving logs show that there is an AR System error code against the record? The archiving process will not archive records that have AR System errors. If the logs indicate an error code, when you remove the cause of the error code, the archiving process will move the record to the archive the next time that it runs. You can turn on the Archiving Log from the AR System server.
- Refer to the Managing the Archiving process policies for the status of archiving policies in the AR System Archive Manager console.
Archive process is running very slowly
Issue scope
When the archiving process is run.
Issue symptom
For a single-thread process, the archiving process is running slower than you would expect.
Resolution
This might occur because of a problem with table indexing as the SQL queries run much slower on non-indexed tables. To check table indexing, turn on SQL logging. Before turning on logging, make sure that you configure the logging filter to pick up only SQL that was initiated by the AR_ARCHIVER user. Check the log for SQL queries that are taking the longest and then cross reference those queries with the tables that they are running against. Make sure that those tables are indexed.
To learn more about single thread execution, see AR System server architecture and scalability.