Troubleshooting cursor: mutex X Due to High Version Count on the Insert Statements with Binds using JDBC
Last updated on SEPTEMBER 19, 2016
Applies to:Oracle Database - Enterprise Edition - Version 18.104.22.168 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.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms