"Cursor: Pin S Wait On X" Contention Mutex Sleep Reason Primarily ' kkslce [KKSCHLPIN2]'
(Doc ID 1268724.1)
Last updated on JULY 15, 2022
Applies to:
Oracle Database - Enterprise Edition - Version 10.2.0.4 to 10.2.0.4 [Release 10.2]Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
- Sessions waiting on 'latch:library cache' and 'cursor pin S wait on X' mutexes
- Application changes were made prior to the issue. Application changes involve changes to NLS_LENGTH_SEMANTICS although this is unlikely to be apparent initially, for example, whilst the length of PLSQL datatypes is fixed at compile time, anonymous PLSQL blocks have their variables defined at run time .
- Database is not hung just contending as more and more sessions start waiting for the "cursor: pin S wait on X" event.
- main mutex sleeps by volume were :
kkslce [KKSCHLPIN2] and kksfbc [KKSPRTLOC1]
using:
Changes
Application changes were made prior to the issue
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 |