High "enq: TX - Row Lock Contention" Wait Caused internal query on CUBE_INSTANCE
(Doc ID 2829468.1)
Last updated on AUGUST 16, 2024
Applies to:
Oracle SOA Suite - Version 12.2.1.4.0 and laterInformation in this document applies to any platform.
Symptoms
On : 12.2.1.4.0 version, Deployment
ACTUAL BEHAVIOR
---------------
High "enq: TX - row lock contention" wait caused by below SQL.
EM was not accessible to customer and instances where not being completed, customer DB team check the DB side found errors on te DB side ,
"ORA-32701: Possible hangs up to hang ID=5 detected" and for that the contacted Oracle Support DB team.
On further investigation by Oracle Support DB team they provided the query which they mention it caused the issue , that query is related to the SOA product/ application.
"Analyzing data for the period "25-Oct-21 12:00:41" to "25-Oct-21 13:00:58" we can see that the SQL 92d4tznvukncf landed into high "enq: TX - row lock contention" wait.
the query in question is
This SQL is having for update clause. As per Oracle Support DB team:
Having for update clause will have high risk of hitting "enq: TX - row lock contention" wait when there is one more session trying to update the same table while the first session is trying to update the table with for update clause and the first session will take an exclusive lock.
EXPECTED BEHAVIOR
-----------------------
a RCA is requested for why this query can be causing row lock contention
Changes
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 |