Performance Issue When Standard Managers Waiting for "enq: TX - row lock contention" Held By ICM
(Doc ID 1492893.1)
Last updated on APRIL 09, 2018
Applies to:Oracle Concurrent Processing - Version 12.1.3 to 12.1.3 [Release 12.1]
Oracle Application Object Library - Version 22.214.171.124 to 12.1.3 [Release 11.5 to 12.1]
Information in this document applies to any platform.
Internal Concurrent Manager (ICM) holds TX lock on a lot of rows in FND_CONCURRENT_PROCESSES table. Many Standard Managers are waiting for "enq: TX - row lock contention" held by ICM.
Below SQL was being executed by ICM:
Os_Process_Id, Lk_Handle, Node_Name, Db_Instance, Process_Context,
Fnd_Concurrent_Processes Where Concurrent_Process_ID = :cpid And
Process_Status_Code in ('A', 'T', 'C', 'P') Order by Node_Name, Db_Instance
For Update Of Concurrent_Process_Id ;
Large numbers of Concurrent Managers defined to support more end users.
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