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 open cursors exceeded

SA-69426

Summary



The 'ORA-01000: maximum open cursors exceeded' error is generated continuously in the Business Intelligence Exchange (BIX) logs. As a result, the jobs fail in every run.


Error Messages



[PegaRULES-Batch-1] [ ] [pperEndUser:03.02.01] (internal.access.ExtractImpl) ERROR - SQL Exception: ORA-00604: error occurred at recursive SQL level 1
ORA-01000: maximum open cursors exceeded

[PegaRULES-Batch-1] [ ] [pperEndUser:03.02.01] (internal.access.ExtractImpl) ERROR - YOURTABLE: table doesn't exist in target Database: TARGETDATABASE


Steps to Reproduce



Rerun the BIX extract.


Root Cause



A defect or configuration issue in the operating environment.

The open_cursors limit on the target database is the default 300. The the source database, this limit is set to 1000. 

Oracle driver bug with a cursor leak exists in the getTables. However, this is an issue with the Oracle driver 12.1.0.2.0. 
Oracle driver 12.1.0.1.0 is used and should not cause any issue.


Resolution



Make the following change to the operating environment: 

Update the open_cursors count to 1000 on the target database.
Suggest Edit

Published January 4, 2019 - Updated December 2, 2021

Did you find this content helpful? Yes No

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.

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