Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

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.

Error Messages

Not Applicable.

Steps to Reproduce

Not Applicable.

Root Cause

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.

Published June 24, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us