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

Unable to access database for System-Locks class



User creates a data page and maps it to the out-of-the-box System-Locks class. Later, an error occurs in all the Dev nodes which are connected to the Dev cluster. The user removes all the compiled classes and restarts the cluster. However, the PegaRULES initialization failed error occurs. The entire Dev cluster is down since the restart fails.

Error Messages

ERROR - lock provider could not be created Database-General unable to access database for Class: System-Locks
at ~[prprivate.jar:?]
at ~[prprivate.jar:?]
at ~[prprivate.jar:?]
at ~[prprivate.jar:?]
at ~[prprivate.jar:?]
at ~[prprivate.jar:?]
at ~[prprivate.jar:?]
at$ ~[prprivate.jar:?]

Steps to Reproduce

  1. Create a data page 
  2. Map the data page to the System-Locks class
  3. Restart the node

Root Cause

A defect or configuration issue in the operating environment. A query was run in the database to verify the SYSTEM-LOCKS entries in pr4_base. The Rule-Obj-Class instance for the System-Locks class is not present in Dev.


Perform the following local-change:
  1. Copy the record which is not present, from the TST environment
  2. Import the record to the DEV database


Published March 18, 2020 - 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