Home » RDBMS Server » Server Administration » open cursor parameter exceeds but no alarm have been raised (oracle 11g)
open cursor parameter exceeds but no alarm have been raised [message #680154] Sat, 25 April 2020 06:10 Go to next message
nill
Messages: 2
Registered: April 2020
Junior Member
Hi
my open_cursor parameter value is 3000 . I had a watermark (7200) a few days ago, but no alarm has been raised.
why?
I thought number of open cursors per session can be greater than the value 3000 , but also i should have an alaram like "ORA-01000 maximum open cursors exceeded" , right?

let me know if you have any idea
thanks
NiLL
Re: open cursor parameter exceeds but no alarm have been raised [message #680155 is a reply to message #680154] Sat, 25 April 2020 07:23 Go to previous messageGo to next message
Michel Cadot
Messages: 67488
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator

"open_cursors" parameter gives the maximum number of cursors for a session.
It'd be better to show us how you get your watermark but I bet it was for all sessions of the instance.

[Updated on: Sat, 25 April 2020 07:24]

Report message to a moderator

Re: open cursor parameter exceeds but no alarm have been raised [message #680166 is a reply to message #680155] Sun, 26 April 2020 00:50 Go to previous messageGo to next message
nill
Messages: 2
Registered: April 2020
Junior Member
you mean 7409 is for all sessions?

and what about Collection Schedule? not set for this parameter
so when database checks the value and raises alert?
what does Server Evaluation Frequency mean? is it related to Collection Schedule?

BR
  • Attachment: 1.jpg
    (Size: 80.43KB, Downloaded 163 times)

[Updated on: Sun, 26 April 2020 01:27]

Report message to a moderator

Re: open cursor parameter exceeds but no alarm have been raised [message #680167 is a reply to message #680166] Sun, 26 April 2020 01:38 Go to previous messageGo to next message
Michel Cadot
Messages: 67488
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator

This is why you should NOT rely on GUI.
Use SQL*Plus, then you will know which query you execute and what it retrieves.

I do not use OEM, so can't answer you but I can move the topic to this forum if you want.

In short, "open_cursors" instance parameter gives a limit per session, "v$open_cursor" (if this what EM queries) gives information instance wide.

Re: open cursor parameter exceeds but no alarm have been raised [message #680228 is a reply to message #680166] Wed, 29 April 2020 07:37 Go to previous message
Michel Cadot
Messages: 67488
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator

Any feedback?

Previous Topic: Basic Partition compression while run DML statement
Next Topic: Oracle DB Upgrade Clarification
Goto Forum:
  


Current Time: Sat Oct 31 21:07:02 CDT 2020