Best practices for archiving and purging Workload Automation DE (dSries) database for improved server performance.
The best practices for archiving and purging Workload Automation DE (dSries) database for improved server performance are;
CA Workload Automation DE 11.3 SP1 and higher:
Guidelines for Cleaning Up Old Generations from the Database
The ESP_APPLICATION,ESP_GENERIC_JOB table tends to grow over time and requires trimming or cleaning to create space. We recommend that you periodically clean the CA Workload Automation DE database. As jobs complete, the database continues to grow with records of completed jobs.
The server collects information about completed Applications and stores this information in the relational database. Over time, the history data can become huge. To create more disk space for the database and improve server performance, you can issue the MOVEHISTORYDATA command to move some of the history information in the database tables to stage tables.
Note: When the data has been moved, a message is added to the tracelog.txt file indicating the number of Applications and rows that were moved. For more information about the trace log, see Maintaining.
This command has the following format:
movehistorydata olderthan("olderthan")
olderthan("olderthan")
Moves history data older than the specified time to stage tables.
Note: The value must be a valid schedule criteria statement that resolves to a date and time. For more information about a valid schedule criteria statement, see Schedule Criteria.
Example: Move History Data Older than a Specified Date
The following example moves all the history data that is older than a month to stage tables:
movehistorydata olderthan("now less 1 month")
We recommend that you force complete Applications that have been active for a long time because of failed jobs or jobs with submission errors (suberror). Force completing old Application generations helps prevent the server from caching unwanted data.
We also recommend that you issue the PURGECOMPLETEDJOBS CLI command regularly to purge completed Application generations. You can schedule the PURGECOMPLETEDJOBS command to run once a day for Applications over seven days old. For certain Applications that run on a more frequent basis, you can schedule it to run every two hours.