Last updated on JUNE 27, 2017
Applies to:JDBC - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
When trying to use JDBC 18.104.22.168 with WLS 12.1.3, encountered the error 'maximum cursor limit exceeded'.
Based on this forum thread reporting a similar issue, <Patch 19632480> - ORACLEDATABASEMETADATA.GETTABLES CURSOR CONNECTION LEAK was applied, but the ORA-01000: maximum open cursors exceeded error persists.
This forces JDBC 11g to be used with WebLogic 12.1.3 application datasources, with which the error does not occur.
ORA-01000: maximum open cursors exceeded
The issue can be reproduced at will with the following steps:
1. Apply patch 20741228 on top of WebLogic 12.1.3 for production version of JDBC 22.214.171.124.
2. Apply patch 19632480 to fix the issue in bug: 19632480 - ORACLEDATABASEMETADATA.GETTABLES CURSOR CONNECTION LEAK.
3. Run the application. The ORA-1000 error will be reported in the WebLogic logs.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms