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

Deadlocks due to IBM DB2 utilites executing against Pega DB



Admin wishes to run third party utilities but cannot find a suitable time when there is no contention.

DB2 Reorg:
• Reorganizing a table compresses the data file that contains the table by physically reclaiming unusable space create by deletes and updates. Each Online Reorg requires a few second of lock on the respective table to go through a step referred to as a ‘Switch step’ through which a shadow copy of the table is renamed and becomes active. Due to high transaction volumes with some of the Pega tables such as PR_Sys_Locks and Clipboard cache the jobs have not successfully executed at times for these tables.

DB2 Quiesce:
This utility takes a quiet point from all the WSP tables on daily basis to be used in case a Recovery of the DB is required. Quiesce may not need an outage for most of the applications and it does not cause an outage since quiesce only waits for the next commit point. Problem is when there are long running threads without commits or too many active threads then quiesce can cause an outage.

Error Messages

Error Message
[7/22/14 18:45:51:782 MST] 00043cbc PRBootstrap E com.pega.pegarules.internal.bootstrap.PRBootstrap Problem during method invocation (unlock)
javax.ejb.EJBException: nested exception is: Problem executing quick lock delete: DB2 SQL Error: SQLCODE=-913, SQLSTATE=57033, SQLERRMC=00C900BA;00002008;PSYSLOCK.00000000, DRIVER=3.64.133: code: -913 SQLState: 57033 Message: DB2 SQL Error: SQLCODE=-913, SQLSTATE=57033, SQLERRMC=00C900BA;00002008;PSYSLOCK.00000000, DRIVER=3.64.133

Steps to Reproduce

Execute the IBM DB2 reorg and Quiesce utilities

Root Cause

The root cause of this problem is in a third-party product integrated with PRPC. 


Here are some details on the pr_sys_locks table that is involved in one of the deadlock issues.

While the system is up 24 x 7 if there are times when the system is not as heavily used that is the time that these type of utilities should be run. They should never be run during high volume times as they will hinder performance.  Also if possible it may be better if you can configure these tools to not run against certain tables, such as the system tables that you are running into issues with.

Published June 12, 2015 - 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