Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

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.

Troubleshooting "Too many open cursors" (Oracle)

Updated on September 13, 2021

Summary

For an Oracle database, the OPEN_CURSORS parameter is an initialization parameter which defines the maximum number of cursors per user.  As a best practice, set this parameter to at least 300.


 

Suggested Approach

The OPEN_CURSORS parameter is an initialization parameter which defines the maximum number of cursors per user.  There are two types of cursors, Implicit and Explicit.  Implicit cursors are defined by the Oracle system as Process Commander requires them; they are out of the control of the executing application.  Explicit cursors are specifically defined by the application when constructing SQL Statements that will return more than a single row.

By default, Oracle assigns a value of 50 to this parameter.  This number is too low to run Process Commander, and will produce Oracle errors stating "Too Many Open Cursors."

It is possible to use the sample init.ora file to set runtime parameters for an Oracle database; in this file, OPEN_CURSORS is set to 300.

Per Oracle's documentation:

 "It is important to set the value of OPEN_CURSORS high enough to prevent your application from running out of open cursors.  The number will vary from one application to another.  Assuming that a session does not open the number of cursors specified by OPEN_CURSORS, there is no added overhead to setting this value higher than actually needed."

Based on the above information, as a best practice, set this parameter to at least 300.  (The above Oracle quote is from the Oracle 8i Initialization Parameters documentation for the parameter OPEN_CURSORS.)

  • Previous topic Troubleshooting "ORA-00942 table or view does not exist" (Oracle COMPATIBLE parameter supports system pulse)
  • Next topic Troubleshooting: ORA-01460 and ORA-01461 errors for database operations with Oracle 10.2.0.3

Have a question? Get answers now.

Visit the Support 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.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us