Customise Consent Preferences

We use cookies to help you navigate efficiently and perform certain functions. You will find detailed information about all cookies under each consent category below.

The cookies that are categorised as "Necessary" are stored on your browser as they are essential for enabling the basic functionalities of the site. ... 

Always Active

Necessary cookies are required to enable the basic features of this site, such as providing secure log-in or adjusting your consent preferences. These cookies do not store any personally identifiable data.

No cookies to display.

Functional cookies help perform certain functionalities like sharing the content of the website on social media platforms, collecting feedback, and other third-party features.

No cookies to display.

Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics such as the number of visitors, bounce rate, traffic source, etc.

No cookies to display.

Performance cookies are used to understand and analyse the key performance indexes of the website which helps in delivering a better user experience for the visitors.

No cookies to display.

Advertisement cookies are used to provide visitors with customised advertisements based on the pages you visited previously and to analyse the effectiveness of the ad campaigns.

No cookies to display.

ORA-01000: Maximum Open Cursors Exceeded

Breadcrumb Abstract Shape
Breadcrumb Abstract Shape
Breadcrumb Abstract Shape
Breadcrumb Abstract Shape
Breadcrumb Abstract Shape
Breadcrumb Abstract Shape
  • User AvatarKiran Dalvi
  • 06 Dec, 2023
  • 0 Comments
  • 58 Secs Read

ORA-01000: Maximum Open Cursors Exceeded

This ORA-01000 error occurs when current open_cursors exceeds the defined open_cursor parameter database.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
SELECT max(a.value) as highest_open_cur, p.value as max_open_cur FROM v$sesstat a,
v$statname b, v$parameter p WHERE a.statistic# = b.statistic# and b.name = 'opened cursors current'
and p.name= 'open_cursors' group by p.value;
 
HIGHEST_OPEN_CUR MAX_OPEN_CUR
---------------- -----------------------
320 300
 
 
 
SQL> show parameter open_cursor
 
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
open_cursors integer 300
Here we can see the highest_open_curosor is more than max_open_cursor. So to avoid this, increase the open_cursor values in spfile.
1
2
3
SQL> alter system set open_cursors=1000;
 
System altered.
Now check again. To get more information you can use the below query to find what session was causing the issue.
1
2
3
4
5
6
7
select a.value, s.username, s.sid, s.serial# from v$sesstat a, v$statname b,
v$session s where a.statistic# = b.statistic# and s.sid=a.sid and
b.name = 'opened cursors current' and s.username is not null;
 
VALUE USERNAME SID SERIAL#
---------- ------------------------------ ---------- ----------
2 SYS 12 61990

Hope it Helps!