My Oracle Support Banner

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 9.0.4.1 to 9.0.4.8
Information in this document applies to any platform.
***Checked for relevance on 04-Nov-2014***

Symptoms

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.

Cause

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
Symptoms
Cause
Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.