ORA-1000 "maximum number of cursors exceeded" with Toplink Statement Caching and External Connection Pool
(Doc ID 337529.1)
Last updated on NOVEMBER 15, 2019
Applies to:Oracle TopLink - Version 22.214.171.124 to 126.96.36.199
Information in this document applies to any platform.
***Checked for relevance on 04-Nov-2014***
ORA-1000 "maximum number of cursors exceeded"
occurs after Toplink session configuration has been changed to use external connection pooling.
The problem can be verified by executing the follwing statement as SYSDBA:
select sid, sql_text, count(*) from v$open_cursor where username='<datasource user>' group by sid, sql_text;
This statement shows the the number of open cursors with the same syntax per session. This number should stay about 1.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document