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

Performance issue: PEGA0037 and PEGA0001 occurrences observed

SA-9480

Summary



Multiple application developers in a Pega 7.1.7 environment report general performance problems and slowness.

No specific steps were isolated or identified as a cause for the performance issue; users logging into the environment after a restart immediately reported problems.

Error Messages



Not Applicable

Steps to Reproduce



Unknown

Root Cause



Analysis of the Pega ALERT log file indicated that database performance was significantly affecting the user experience. Examination of the SQL statements reported in the PEGA0005 alerts suggested that database performance was the root cause of the PEGA0037 alerts, leading to the long browser wait times (PEGA0001 alerts).

Additional analysis revealed that the standard report definition <DATA-RULE-SUMMARY>pzWarningsIntroduced (Pega-Desktop:07-10-13)was incurring a 400+ line SQL statement. This caused performance delays in excess of 10 seconds.


Resolution


To resolve this issue, perform the following two-part local-change:
  1. Define additional INDEXes on the designated tables and properties. Details below.
  2. Isolate and disable the standard report defintion. Details below.
Define additional INDEXes on the following tables and properties:
TABLE: PR_INDEX_REFERENCE
PROPERTIES: PXINSINDEXEDKEY, PXRULEOBJCLASS, PYRULENAME, PXINDEXPURPOSE, PXREFERENCINGRULESETNAME, PXINSINDEXEDKEY

TABLE: PR4_RULE_VW
PROPERTIES: PZINSKEY, PYRULEAVAILABLE

TABLE: PC_HISTORY_WORK
PROPERTIES: PYHISTORYTYPE, PYWORKCLASS, PXOBJCLASS

TABLE: PC_WORK
PROPERTIES: PZINSKEY, PYID, PXOBJCLASS

To disable the standard report definition <DATA-RULE-SUMMARY>pzWarningsIntroduced (Pega-Desktop:07-10-13), complete the following steps:
  1. Save this section to the user's ruleset: <RULE-HTML-SECTION>@baseclass.RuleFormHeaderMessagesInner
  2. Update this newly saved section and remove the reference to the report definition <DATA-RULE-SUMMARY>pzWarningsIntroduced (Pega-Desktop:07-10-13).
  3. Save the updated section.
  4. Shut down Process Commander.
  5. For each PRPC node, delete the PegaRULES_Extract_Marker.txt file located in the PRPC Explicit Temp directory.
  6. Restart Process Commander.
Suggest Edit

Published June 14, 2017 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

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