Global Enqueue Services Deadlock Detected In The Table Cs_incidents_all_b (Doc ID 1321111.1)

Last updated on FEBRUARY 03, 2019

Applies to:

Symptoms

DBA finds that there are deadloscks on the node.
Deadlocks refer to UPDATE CS_INCIDENTS_ALL_B, the following error occurs in the trace file.

Error

Alert_xx.log
Global Enqueue Services Deadlock detected. More info in file
/dbtop/db_rac/tech_st/10.2.0/admin/xxPRD1_sec33-e/udump/xxprd1_ora_3739.trc.
Tue Apr 12 12:27:06 2011
Trace dumping is performing id=[cdmp_20110412122702]
Tue Apr 12 12:27:33 2011
Beginning log switch checkpoint up to RBA [0x6f09.2.10], SCN: 9936709670703
Tue Apr 12 12:27:33 2011
Thread 1 advanced to log sequence 28425 (LGWR switch)
Current log# 2 seq# 28425 mem# 0: +WFDATA/wfprd/onlinelog/redo2a.log
Current log# 2 seq# 28425 mem# 1: +WFDATA/wfprd/onlinelog/redo2b.log
...
Tracelog.trc
user session for deadlock lock 781e28148
pid=715 serial=10860 audsid=1244029618 user: 173/APPS
O/S info: user: xxxxxxx, term: unknown, ospid: 11111, machine: sec32-xxxx.com.xa
program: JDBC Thin Client
client info: 0 0
action name: 29653;CSF_JAVA, hash value=1507095192
Current SQL Statement:
UPDATE CS_INCIDENTS_ALL_B SET INCIDENT_ATTRIBUTE_15 = :B1 WHERE INCIDENT_ID=:B2 AND INCIDENT_ATTRIBUTE_15 IS NULL

Expected Behavior
Deadlocks are not expected.

Steps to Reproduce
Unknown

Business Impact
Due to this issue, Oracle Applications hangs and users cannot query or update service requests.

Cause

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