EM 13c: Global Enqueue Services Deadlock Detected in Enterprise Manager 13c Cloud Control Repository Database
(Doc ID 2829995.1)
Last updated on DECEMBER 25, 2023
Applies to:
Enterprise Manager Base Platform - Version 13.4.1.0.0 and laterInformation in this document applies to any platform.
Symptoms
Enterprise Manager (EM) 13.4 Cloud Control, Global Enqueue Services Deadlock detected in EM Repository Database:
user session for deadlock lock 0xc3149fa30
sid: 1435 ser: 50827 audsid: 736906794 user: 34/SYSMAN
flags: (0x8000045) USR/- flags_idl: (0x1) BSY/-/-/-/-/-
flags2: (0x40009) -/-/INC
pid: 387 O/S info: user: grid, term: UNKNOWN, ospid: 27873
client details:
O/S info: user: <username>, term: unknown, ospid: 1234
machine: <host-name> program: OMS
client info: <host-name>:4889_Management_Service
application name: OEM.PbsDefaultPool, hash value=2164726901
action name: Job Step 486585353 Job Long-Syst, hash value=2805963363
current SQL:
UPDATE EM_CS_SCORE SET COMPLIANT_RULES = :B16 , CRITICAL_RULES = :B15 ,
WARN_RULES = :B14 , MWARN_RULES = :B13 , ERROR_RULES = :B12 , UNKNOWN_RULES =
:B11 , CRIT_VIOLATIONS = :B10 , WARN_VIOLATIONS = :B9 , MWARN_VIOLATIONS =
:B8 , COMPLIANCE_SCORE = :B7 , COMPLIANCE_SCORE_LEVEL = :B6 ,
LAST_EVALUATION_DATE = MGMT_GLOBAL.SYSDATE_UTC(), IS_SCORE_VALID = 1 WHERE
RQS_GUID = :B4 AND ROOT_CS_GUID = :B3 AND CS_GUID = :B2 AND ROOT_TARGET_GUID = :B5 AND TARGET_GUID = :B1
DUMP LOCAL BLOCKER: initiate state dump for DEADLOCK
possible owner[387.27873] on resource
Other SQL's causing deadlocks in Repository database:
UPDATE MGMT_USER_CONTEXT SET VALUE = :B4 , PREDICATE_CONSTANT = :B3 WHERE
CLIENT_IDENTIFIER = :B2 AND ATTRIBUTE = :B1
UPDATE MGMT_USER_CONTEXT SET VALUE = :B2 WHERE CLIENT_IDENTIFIER = :B1 AND
ATTRIBUTE IN ( SELECT COLUMN_VALUE FROM TABLE(CAST(:B3 AS
SYSMAN_TYPES.MGMT_SHORT_STRING_ARRAY)))
UPDATE MGMT_JOB_EXEC_CRED_INFO SET CREDENTIALS_SET=:B7 WHERE JOB_ID=:B6 AND
EXECUTION_ID=:B5 AND TASK_NAME=:B4 AND TARGET_GUID=:B3 AND
CONTAINER_LOCATION=:B2 AND CREDENTIAL_SET_NAME=:B1
BEGIN EM_JOB_CREDS.credset_assoc_cb(:1, :2); END;
UPDATE EM_TARGET_CREDS SET CRED_GUID = :B5 , UPDATED_BY =
MGMT_USER.GET_CURRENT_EM_USER, UPDATED_ON = SYSTIMESTAMP WHERE USER_NAME =
:B4 AND TARGET_GUID = :B3 AND SET_NAME = :B2 AND TARGET_TYPE = :B1
UPDATE MGMT_USER_CONTEXT SET VALUE = :B2 WHERE CLIENT_IDENTIFIER = :B1
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 |
Cause |
Solution |
References |