My Oracle Support Banner

Deadlock Error During Concurrent Request Termination (Doc ID 1060736.1)

Last updated on NOVEMBER 19, 2017

Applies to:

Oracle Concurrent Processing - Version 11.5.10.2 to 12.1.3 [Release 11.5 to 12.1]
Information in this document applies to any platform.
Checked for relevance on 7-OCT-2016

Symptoms

Deadlock happens during concurrent request termination (or) timeout. The error below is flashed in the alert log whenever post processing request is being terminated. This might cause concurrent processing to hang.

ERROR (alert.log)

Global Enqueue Services Deadlock detected. More info in file
(OR)
ORA-00060: Deadlock detected. More info in file

Trace File

DEADLOCK DETECTED ORA-00060 (deadlock_detected).
[Transaction Deadlock]
Current SQL statement for this session:
UPDATE FND_CONCURRENT_REQUESTS
SET PP_END_DATE = SYSDATE, POST_REQUEST_STATUS = 'E'
WHERE
REQUEST_ID = :B1
----- PL/SQL Call Stack -----
object line object
handle number name
3fda81b78 67 package body APPS.FND_CP_OPP_CMD
3fec758a0 1 anonymous block

fnd_cp_opp_cmd.terminate_opp_request()

The following deadlock is not an ORACLE error. It is a
deadlock due to user error in the design of an application
or from issuing incorrect ad-hoc SQL. The following
information may aid in determining the deadlock:

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

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