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

Poor Performance - Numerous PEGA0029 alerts



  • Overall performance of the system is poor
  • An ALERT log is increasing in size. There is a large number of PEGA0029 alerts.

Error Messages

Not Applicable

Steps to Reproduce

No specific steps were found that would trigger the poor performance. Performance seems poor immediately after user logins.

Root Cause

Database is responding poorly to PRPC SQL. Specifically, the PEGA0005 alerts indicate that a specific SQL is causing the most mayhem. The source of the SQL has been traced back to standard Report Definition: <DATA-RULE-SUMMARY> PZWARNINGINTRODUCED. This standard stored procedure is called by each User Requestor Instance after user login, and is called repeatedly as the user updates rule instances.


To stop the imposition of this SQL statement, perform the following:

1.    Save the following section to the user's ruleset:


2.    Update this newly saved section and remove the reference to the report definition "pzWarningsIntroduced".  Save the updated section.

3.    Shutdown Process Commander.

4.    For each PRPC node, delete the PegaRULES_Extract_Marker.txt file located in the PRPC Explicit Temp directory.

5.    Restart Process Commander and Re-test.

Published January 31, 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