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

ORA-01000: Maximum number of open cursors exceeded



After the upgrade to Pega 7.2, user gets many errors on DB level, related to the open cursors.
The SQL showing the highest number of open cursors (500-up) is:

select pzInsKey as "pzInsKey" , pxLockhandle as "pxLockHandle" from RULES.pr_sys_locks where pxOwnerID = ?

Error Messages

ORA-01000: maximum open cursors exceeded

Steps to Reproduce

Not applicable

Root Cause

Below two defects in PRPC caused cursor leaks: 
  • Cursor leaks are observed in LockManagerImpl code where prepared statement in not being closed and cursors are being held. 
  • Stored procedure SPPR_SYS_RESERVEQUEUEITEM_B does not close the cursors.


Apply HFix-29955to avoid the error message.


Published November 15, 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