High Version Count With PURGED_CURSOR Mismatch Causes Database Hang Due 'cursor: mutex S' Contention From 12.2.0.1
(Doc ID 2542011.1)
Last updated on JULY 20, 2024
Applies to:
Oracle Database - Enterprise Edition - Version 12.2.0.1 and later
Information in this document applies to any platform.
Symptoms
- Database hang due to high number of waits on 'cursor: mutex S' or 'cursor: mutex X'.
- Flushing the shared pool brings performance back to normal and mutex waits got alleviated.
- Mutex waits again resurface after some time and causing the database slow or hang situation.
- Version count of some SQL statements are very high > 1024.
- V$SQL_SHARED_CURSOR shows lot of child cursors created with PURGED_CURSOR mismatch with reason "Marked for Purge(5)".
Changes
Database Upgraded to 12.2.0.1.
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
My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.