Performance Issue When Standard Managers Waiting for "enq: TX - row lock contention" Held By ICM
(Doc ID 1492893.1)
Last updated on APRIL 04, 2025
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.
Reviewed for Relevance 27 Jan 2019.
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:
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 |