Global Enqueue Services Deadlock Detected In Table CS_INCIDENTS_ALL_B
(Doc ID 1321111.1)
Last updated on FEBRUARY 20, 2019
Applies to:
Oracle Teleservice - Version 12.1.1 and laterInformation in this document applies to any platform.
Symptoms
DBA finds that there are deadlocks on the node and they 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/udump/xxprd1_ora_123.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: 1234567890
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=123 serial=10001 audsid=987654321 user: 456/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=150150150150
Current SQL Statement:
UPDATE CS_INCIDENTS_ALL_B SET INCIDENT_ATTRIBUTE_15 = :B1 WHERE INCIDENT_ID=:B2 AND INCIDENT_ATTRIBUTE_15 IS NULL
In the examples above, user details / company name / address / IDs, etc. represent a fictitious sample (based upon made up data used in the Oracle Demo Vision instance).
Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.
Steps to Reproduce
Unknown
Business Impact
Due to this issue, Oracle Applications hangs and users cannot query or update service requests.
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 |
| Community Discussions |
| References |