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

DELETE FROM pr_sys_locks causing DB Blockage

SA-52264

Summary



Database response is slow in production and it is generating alerts.

The Database connection pool is getting closed repeatedly,


Error Messages



The below message can be seen in the alert logs.
DELETE FROM pr_sys_locks WHERE PXEXPIREDATETIME < :1 AND PXOBJCLASS = :"SYS_B_0"


Steps to Reproduce



Not Applicable


Root Cause




The delete query on PR_SYS_LOCKS was generating PEGA0005 alert.

The volume of entry in the same table was high and the system performance was degraded.



Resolution


Perform the following steps:

1. Take the backup of the same table and delete few rows manually running the delete query on this table.
2. Also set the below DSS setting to defragment this table periodically.

syslocks/defragIntervalType - value of this settings should be "DAILY" .

3. Restart the system after configuring this DSS setting.

If this DSS settings doesn't help you can create an agent and run an activity which can have connect-SQL to delete entries from the PR_SYS_LOCKS table.


Published May 11, 2018 - 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?

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