This is a short preview of a Knowledge Base article. The full article is available to logged-in Continuous Community members.
Summary
Explains where OpCon stores job history in its database and how to manage how long it is kept. It describes the history and archive tables, why the history tables can become the largest in a big environment, and how the Job History Purge job in the SMAUtility schedule controls retention. It covers reasons to adjust it, such as database size and performance or audit requirements.
Applies to
OpCon database · job history · SMAUtility schedule
Topics covered
- Where job history is stored
- History versus archive tables
- The Job History Purge job and its parameters
- Reasons to change retention
Keywords
job history, history retention, HISTORY table, HISTARC, HISTORY_AUX, Job History Purge, SMAUtility, database size, purge job, history archive, OpCon database performance
