EM13c：Started BLACKOUT on all RAC nodes at the same time, failed With "Start Failed". (Doc ID 3057818.1)

Last updated on NOVEMBER 11, 2024

Applies to:

Symptoms

 Started BLACKOUT on all RAC nodes at the same time, failed With "Start Failed".

For example:
./emcli create_blackout -name="${BLACKOUT_NAME}" -add_targets="${BLACKOUT_TARGET}" -propagate_targets -reason="${BLACKOUT_NAME}" -schedule="duration:-1"

In the mgmt_system_error_log of the EM repository DB, the following error output is found:

Exception while updating blackout start on agent for blackout during edit: targetxxx E82112FE212F6C3D0249BE6E104 emd_url: https://xxx:3872/emd/main/ Error:
ORA -00060: deadlock detected while waiting for resource Trace:
ORA-06512: at "SYSMAN.EM_TARGET_AP", line 338
ORA-06512: at "SYSMAN.EM_TARGET_AP", line 737
ORA-06512: at "SYSMAN.EM_TARGET_AP", line 1062
ORA-06512: at "SYSMAN.EM_TARGET_AP", line 1081
ORA-06512: at "SYSMAN.EM_TARGET_AP", line 940
ORA-06512: at "SYSMAN.EM_SEV ERITY", line 3386
ORA-06512: at "SYSMAN.EM_SEVERITY", line 3737
ORA-06512: at "S YSMAN.EM_VIOLATION_CHECKS", line 1755
ORA-06512: at "SYSMAN.MGMT_BLACKOUT_ENGINE _NG", line 1095
ORA-06512: at "SYSMAN.MGMT_BLACKOUT_ENGINE_NG", line 1295
ORA-06 512: at "SYSMAN.MGMT_BLACKOUT_ENGINE_NG", line 4215
ORA-06512: at "SYSMAN.MGMT_B LACKOUT_ENGINE_NG", line 4303

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.