High Waits for 'library cache lock' and 'library cache: mutex X' Due to Parse Failures When Using JDBC ResultSet.TYPE_SCROLL_SENSITIVE
(Doc ID 1566018.1)
Last updated on MAY 12, 2022
Applies to:
Oracle Database Cloud Exadata Service - Version N/A and laterOracle Database Cloud Service - Version N/A and later
Oracle Database - Enterprise Edition - Version 11.2.0.3 and later
Oracle Database Cloud Schema Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Information in this document applies to any platform.
Symptoms
- You are using JDBC in the application and the "ResultSet.TYPE_SCROLL_SENSITIVE" feature that permits scrolling of the result set returned from the database.
Other symptoms may vary, but may include:
- high "library cache lock" and "library cache: mutex X" waits
- Disproportionately high "failed parse elapsed time" under the "Time Model Statistics" section of AWR:
- A high number or "parse count (failures)" under "Instance Activity Stats"
.
.
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 |
| Cause |
| Solution |
| References |