Support Article
max open cursors exceeded error after Upgrade
SA-4091
Summary
MaxOpen cursors exceeded Error on PRPC 7.1.5
Error Messages
ORA-01000: max open cursors exceeded
Root Cause
The root cause of this problem is in a third-party product integrated with PRPC.
Driver jar file ojdbc6.jar (11.2.0.3) is incompatible with Oracle Database version --11.2.0.2.
Tomcat container was not able to close the Resultsets and Statements.
Resolution
This issue is resolved by making the following change to the PRPC operating environment:
Oracle Database version --11.2.0.2
Downgraded ojdbc6.jar to
OJDBC6.jar version -- 11.2.0.2
Added below parameter to datasource tag.
jdbcInterceptors="org.apache.tomcat.jdbc.pool.interceptor.ConnectionState;
org.apache.tomcat.jdbc.pool.interceptor.StatementFinalizer;"
<Resource name="jdbc/PegaRULES"
auth="Container"
type="javax.sql.DataSource"
driverClassName="oracle.jdbc.OracleDriver"
url="jdbc:oracle:thin:@10.100.126.119:1697:PEAPPLD1"
username="XXX"
password="XXX"
maxActive="100"
maxIdle="30"
maxWait="10000"
jdbcInterceptors="org.apache.tomcat.jdbc.pool.interceptor.ConnectionState;
org.apache.tomcat.jdbc.pool.interceptor.StatementFinalizer;"
/>
org.apache.tomcat.jdbc.pool.interceptor.ConnectionState - keeps track of auto commit, read only, catalog and transaction isolation level.
org.apache.tomcat.jdbc.pool.interceptor.StatementFinalizer - keeps track of opened statements, and closes them when the connection is returned to the pool.
Published January 31, 2016 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.