ORA-00060 errors during blackout end for Enterprise Repository Database
(Doc ID 2314383.1)
Last updated on AUGUST 19, 2022
Applies to:
Enterprise Manager Base Platform - Version 12.1.0.5.0 to 13.2.0.0.0 [Release 12.1 to 13c]Information in this document applies to any platform.
Symptoms
From 12.1.0.5 Enterprise Manager, getting deadlock in repository database during black out end for targets. Alert log of repository database have following messages:
ORA-00060: Deadlock detected. See Note 60.1 at My Oracle Support for Troubleshooting ORA-60 Errors. More info in file <DIR>/trace/DBTEST_ora_4010.trc.
Mon Oct 11 01:16:30 2016
ORA-00060: Deadlock detected. See Note 60.1 at My Oracle Support for Troubleshooting ORA-60 Errors. More info in file <DIR>/trace/DBTEST_ora_4020.trc.
Following are the different types of error stack shown:
Stack 1:
current SQL:
BEGIN MGMT_BLACKOUT_ENGINE.host_change_callback(:1, :2, :3); END;
----- End of information for the OTHER waiting sessions -----
Information for THIS session:
----- Current SQL Statement for this session (sql_id=dy5cf88cnng5j) -----
SELECT TARGET_GUID FROM EM_CURRENT_AVAILABILITY WHERE TARGET_GUID = :B1 FOR UPDATE
----- PL/SQL Stack -----
----- PL/SQL Call Stack -----
object line object
handle number name
3da31cc90 61 package body SYSMAN.EM_SEVERITY
3e2f393e0 485 SYSMAN.EM_VIOLATION_CHECKS
3d31459e0 6 anonymous block
Stack 2:
current SQL:
SELECT TARGET_GUID FROM EM_CURRENT_AVAILABILITY WHERE TARGET_GUID = :B1 FOR UPDATE
----- End of information for the OTHER waiting sessions -----
Information for THIS session:
----- Current SQL Statement for this session (sql_id=3c2mghfx5v6zn) -----
BEGIN MGMT_BLACKOUT_ENGINE.host_change_callback(:1, :2, :3); END;
----- PL/SQL Stack -----
----- PL/SQL Call Stack -----
object line object
handle number name
3dca204e8 82 package body SYS.DBMS_LOCK
3dca204e8 98 package body SYS.DBMS_LOCK
3da7922b8 34 package body SYSMAN.MGMT_LOCK_UTIL
3da7922b8 66 package body SYSMAN.MGMT_LOCK_UTIL
3db3bc130 466 package body SYSMAN.MGMT_BLACKOUT_ENGINE
3db3bc130 2755 package body SYSMAN.MGMT_BLACKOUT_ENGINE
3db3bc130 5828 package body SYSMAN.MGMT_BLACKOUT_ENGINE
3d3bf8608 1 anonymous block
4d1d31ad0 405 package body SYSMAN.EM_ASSOC_NG
4d1d31ad0 467 package body SYSMAN.EM_ASSOC_NG
4d1d31ad0 2266 package body SYSMAN.EM_ASSOC_NG
4d1d31ad0 4275 package body SYSMAN.EM_ASSOC_NG
3dabd9e28 258 package body SYSMAN.EM_MASTER_AGENT
4569b1808 2 SYSMAN.MASTER_AGENT_CHANGE_TRIGGER
3dabd9e28 139 package body SYSMAN.EM_MASTER_AGENT
3dabd9e28 671 package body SYSMAN.EM_MASTER_AGENT
3dabd9e28 829 package body SYSMAN.EM_MASTER_AGENT
Stack 3:
current SQL:
SELECT TARGET_GUID FROM EM_CURRENT_AVAILABILITY WHERE TARGET_GUID = :B1 FOR UPDATE
----- End of information for the OTHER waiting sessions -----
Information for THIS session:
----- Current SQL Statement for this session (sql_id=49x6ufcmyxu36) -----
SELECT T.ENTITY_GUID TARGET_GUID, T.EMD_URL EMD_URL, T.ENTITY_NAME TARGET_NAME, T.ENTITY_TYPE TARGET_TYPE, T.MONITORING_MODE MONITORING_MODE FROM EM_MANAGEABLE_ENTITIES T WHERE T.ENTITY_GUID IN (SELECT TARGET_GUID FROM MGMT_TARGET_AGENT_ASSOC A WHERE A.AGENT_GUID = :B3 AND A.PROMOTE_STATUS >= :B2 ) AND T.MANAGE_STATUS = :B1 ORDER BY ENTITY_TYPE, ENTITY_NAME FOR UPDATE OF T.MANAGE_STATUS
----- PL/SQL Stack -----
----- PL/SQL Call Stack -----
object line object
handle number name
3dabd9e28 787 package body SYSMAN.EM_MASTER_AGENT
3da31cc90 3288 package body SYSMAN.EM_SEVERITY
3da31cc90 4717 package body SYSMAN.EM_SEVERITY
3e2f393e0 1491 SYSMAN.EM_VIOLATION_CHECKS
3ddb3ab88 300 package body SYSMAN.EM_PING
3ddb3ab88 648 package body SYSMAN.EM_PING
3ddb3ab88 1098 package body SYSMAN.EM_PING
3ddb3ab88 1273 package body SYSMAN.EM_PING
3ccb58650 1 anonymous block
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 |