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

System cleaner is not cleaning up perf stats table



System cleaner is not cleaning up perf stats table. Exceptions are found in Pega Logs.

Error Messages

2016-12-14 00:00:10,423 [ PegaRULES-Batch-2] [ STANDARD] [ ] [ PegaRULES:07.10] (l.access.ConnectionManagerImpl) ERROR - Not returning connection 1 for database "pegadata" to the pool as it previously encountered the following error
User ID: System
Last SQL: {call PEGA_WORK.sppr_purge_table (?,?,?)} Transaction (Process ID 185) was deadlocked on lock | communication buffer resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
at org.apache.tomcat.dbcp.dbcp.DelegatingPreparedStatement.execute(
at org.apache.tomcat.dbcp.dbcp.DelegatingPreparedStatement.execute(
at com.pegarules.generated.activity.ra_action_pzsystemstatuspurge_5b2e9e10ae5b0e174dfcd127853ce2ee.step2_circum0(
at com.pegarules.generated.activity.ra_action_pzsystemstatuspurge_5b2e9e10ae5b0e174dfcd127853ce2ee.perform(
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(
at com.pega.pegarules.session.internal.mgmt.Executable.invokeActivity(
at com.pegarules.generated.activity.ra_action_systemcleaner_086584e6b8a1ac0ea644fcb3ea53969f.step16_circum0(
Same error is seen for pr_log_reportstats and pr_sys_statusdetails tables.

Steps to Reproduce

Not Applicable

Root Cause

A defect or configuration issue in the operating environment.

System Cleaner is unable to delete records from
pr_perf_stats table as there are more than 2 million records that have accumulated in this table.

The database is configured with more than 20 live JVMs. Every Requestor, Agent, CTI from each JVM writes performance data to this table every hour and upon termination/signoff.


Make the following change to the operating environment:

Delete rows from these tables to bring the size down to thousands records so that the Pega stored proc can execute subsequent deletes without taking too long.

Also perform the following local-change:

Set this prconfig and the other two DSS after deleting records from these tables (pr_log_reportstats, pr_perf_stats, pr_sys_statusdetails) that are older than say 7 days.

<env name="usage/retentionperiod" value="7" />

Owning Ruleset: Pega-RulesEngine
Purpose: management/systemdetails/maxdays
Value: 7

Owning Ruleset: Pega-RulesEngine
Purpose: reporting/reportstatistics/minimumDaysToPurgeFromDatabase
Value: 7

This should bring the tables to manageable sizes and also allow System Cleaner to maintain it.

Published January 30, 2017 - 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