What is the OEM open cursor method really reflect??
From: Chris King <"Chris>
Date: Tue, 5 Jul 2016 15:12:13 +0000 (UTC)
Message-ID: <1595098417.2043130.1467731533694.JavaMail.yahoo_at_mail.yahoo.com>
Date: Tue, 5 Jul 2016 15:12:13 +0000 (UTC)
Message-ID: <1595098417.2043130.1467731533694.JavaMail.yahoo_at_mail.yahoo.com>
Given that the open_cursor parameter reflects a per session maximum; andv$open_cursors reflect the number of cursors cached and not the number of open cursors; and It appears therefore there is no way to directly set the maximum number of cursors that can be opened in the database at one time, yet OEM reports on the number of cursors opened in the database at one time. Therefore the number OEM is reporting is not related to the open_cursor setting.
What is the use of this OEM metric? In the case where there are many applications connecting to the database at one time, I'm not sure it could be trusted to give an accurate picture of any cursor leak problems. Is there any other use for this metric?
-- http://www.freelists.org/webpage/oracle-lReceived on Tue Jul 05 2016 - 17:12:13 CEST