Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

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.

Troubleshooting: Out-of-the-box triggers reference pr_sys_locks table impacting PRPC performance (HFix-4229, HFix-4349)

Updated on September 25, 2019

Summary

Certain out-of-the-box (OOTB) triggers for MS SQL and IBM DB2 UDB contain a SELECT query which references the pr_sys_locks table. When this query is executed against the pr_sys_locks table, a table scan is performed, which causes unintended performance issues.

HFix-4229 for PRPC 6.2 and HFix-4349 for PRPC 6.1 SP2 provide updated MS SQL and IBM DB2 UDB triggers that remove an unnecessary reference to the pr_sys_locks table which caused the unintended performance issues.

Suggested Approach

This issue was fixed in PRPC 6.2 SP2 and later releases. If you are running PRPC 6.2 or PRPC 6.1 SP2, refer to the steps below to request the appropriate Hotfix.

  1. Contact Pegasystems Global Customer Support (GCS) and request HFix-4229.zip for PRPC 6.2 or HFix-4349.zip for PRPC 6.1 SP2.
  2. Follow the instructions in the ReadMe.txt file.

You must contact Pega GCS to obtain the HFix-4229.zip for PRPC 6.2 or HFix-4349.zip for PRPC 6.1 SP2, because the nature of this update precludes it from being installed with the Update Manager.

  • Previous topic Troubleshooting: Microsoft SQL Server rounds datetime to nearest 1/3 of a hundredth of a second
  • Next topic Troubleshooting: PEGA0026 alerts indicate connection pool settings too low

Have a question? Get answers now.

Visit the Support 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.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us