Troubleshooting cursor: mutex X Due to High Version Count on the Insert Statements with Binds using JDBC
(Doc ID 1469726.1)
Last updated on MARCH 08, 2022
Applies to:Oracle Database Exadata Express Cloud Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database - Enterprise Edition - Version 126.96.36.199 to 188.8.131.52 [Release 11.1 to 11.2]
Oracle Database Cloud Schema Service - Version N/A and later
Information in this document applies to any platform.
The following symptoms were encountered:
- Database slowness.
- The performance of the database was severely impacted with the 'cursor: mutex X' wait event.
- AWR report for the problematic period shows a couple of inserts statements with several binds, having very high version count.
- The version count report for those insert statements shows the cursor sharing failure reason as "bind mismatch".
There were no changes made to the database, nor any changes made to the insert statements.
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