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

pr_sys_lock insert malfunction cause DB to slowdown and crash



Application server hang due to the pr_sys_locks table on the database.

Error Messages

Not Applicable

Steps to Reproduce

Not Applicable

Root Cause

Database table pr_sys_locks not responding due to this issue happened.


Here’s the explanation for the reported behaviour:

Recommended the following steps 
  1. Contact DBA: ensure that table pr_sys_locks does have the index enabled on this table. Ensure that the index has not been disabled or otherwise damaged. 
  2. The pr_sys_locks table is a high update table. This means that this table is constantly updated during the normal operations of PRPC.
  3. There is a possibility that the table INDEX has become severely fragmented, and therefore, the database access times have become exceptionally long. Contact your DBA, and perform a FULL COMPUTE STATISTICS on this table. 

Published October 28, 2016 - Updated October 8, 2020

Was this useful?

100% 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