EM 13C: Metrics Collected by Agent Causing "ORA-01000: maximum open cursors exceeded" for 11.2.0.4 DB targets
(Doc ID 2542496.1)
Last updated on NOVEMBER 20, 2020
Applies to:
Enterprise Manager Base Platform - Version 13.3.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
Receiving ORA-01000 errors for 11.2.0.4 DB target's
Open Cursors is set to 2000
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
2 p.value;
HIGHEST_OPEN_CUR MAX_OPEN_CUR
309 2000
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
2 p.value;
HIGHEST_OPEN_CUR MAX_OPEN_CUR
309 2000
Observed the below errors in gcagent.log:
2019-02-22 17:35:43,230 129:GC.Executor.7 (oracle_database:<Target name>:dbjob_status) (oracle_database:<Target name>:dbjob_status:dbjob_status) ERROR - ORA-01000: maximum open cursors exceeded
java.sql.SQLException: ORA-01000: maximum open cursors exceeded
2019-02-22 17:35:43,240 83:GC.Executor.2 (oracle_database:<Target name>:problemTbspTemp_10i_Loc) (oracle_database:<Target name>:problemTbspTemp_10i_Loc:problemTbspTemp) ERROR - ORA-01000: maximum open cursors exceeded
java.sql.SQLException: ORA-01000: maximum open cursors exceeded
Changes
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 |
| Changes |
| Cause |
| Solution |
| References |