Deadlock Occurred While Running Posting in Parallel (Doc ID 839847.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle General Ledger - Version 11.5.10.2 to 11.5.10.2 [Release 11.5.10]
Information in this document applies to any platform.
Checked relevance on 18-Oct-12
This problem can occur on any platform.
GLPPOS

Symptoms

While running GLPPOS (posting) in parallel, deadlock occurred. This problem occurs if multiple posting programs are submitted for the same set of book. Problem can be avoided by setting up incompatibilities with the posting program itself. However, where users require multiple posting programs to run parallely, this issue will be faced.

The deadlock message is as follows.

[ERROR MESSAGE]
DEADLOCK DETECTED ( ORA-60 )
[Transaction Deadlock]
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.

application name: GLPPOS,
action name: Concurrent Request,
Current SQL Statement:
lock table GL_CONCURRENCY_CONTROL in exclusive mode
End of information on OTHER waiting sessions.
Current SQL statement for this session:
lock table GL_CONCURRENCY_CONTROL in exclusive mode

Changes

None

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms