OraFAQ Forum: Server Administration » open cursor parameter exceeds but no alarm have been raised

Home » RDBMS Server » Server Administration » open cursor parameter exceeds but no alarm have been raised (oracle 11g)

Show: Today's Messages :: Polls :: Message Navigator
E-mail to friend

open cursor parameter exceeds but no alarm have been raised [message #680154]

Sat, 25 April 2020 06:10

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

Report message to a moderator

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

Michel Cadot
Messages: 68348
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

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 945 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

Michel Cadot
Messages: 68348
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.

Report message to a moderator

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

Michel Cadot
Messages: 68348
Registered: March 2007
Location: Nanterre, France, http://...

Senior Member
Account Moderator

Any feedback?

Report message to a moderator

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

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Sat Feb 04 08:56:01 CST 2023