High Waits for 'library cache lock' and 'library cache: mutex X' Due to Parse Failures When Using JDBC ResultSet.TYPE_SCROLL_SENSITIVE

Last updated on SEPTEMBER 19, 2016

Applies to:

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