My Oracle Support Banner

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 11.5.10.2 to 12.1.3 [Release 11.5 to 12.1]
Information in this document applies to any platform.

Symptoms

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:

Select Oracle_Process_Id, Queue_Application_Id, Concurrent_Queue_Id, 
Os_Process_Id, Lk_Handle, Node_Name, Db_Instance, Process_Context, 
Gsm_Internal_Status 
From 
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 ; 

Changes

Large numbers of Concurrent Managers defined to support more end users.

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
References


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