SystemCleaner is not always purging pr_perf_stats table (DB2)
SystemCleaner Agent that calls SystemCleaner Activity occasionally causes the database transaction log to fill up as it tries to purge a large number of 30 million rows from the pr_perf_stats table.
This leads to the Pega application system crashing. To move past this, the table needs to be purged manually at regular intervals. The problem occurs when the Pega database application is DB2.
Steps to Reproduce
A defect in Pegasystems’ code or rules causes this issue. The stored procedure that attempts to purge the pr_perf_stats is configured to turn the database transaction logging off.
However, if user has modified the stored procedure (SPPR_PURGE_TABLE_NO_LOGGING) and kept the database transaction logging enabled, this issue may arise if the dynamic system setting (DSS) usage or usagetrackingenabled or its associated prconfig.xml setting were set to False.
Ensure that the usage or usagetrackingenabled DSS is set to True in the user environment and that none of the prconfig.xml files in use have this set to False.
This also includes BIX command line processes that use an external prconfig.xml file.
0% found this useful