High Waits for 'library cache lock' Event when Using Table Partitioned by Interval
(Doc ID 1530075.1)
Last updated on FEBRUARY 18, 2019
Applies to:Oracle Database - Enterprise Edition - Version 126.96.36.199 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database 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.
- high percentage of waits on 'library cache lock'
- high percentage of parse time on queries against tables that are partitioned by interval
- skip_unusable_indexes is TRUE
- Large gaps exist in the values stored in the partitioning key, causing the table to be "sparsely partitioned."
For example, given a partitioning column of calendar quarter, there are, perhaps, partitions for all four quarters of 2008 and 2013, but none for any quarters in the years 2009–2012.
There are no changes to the environment, although you may not have used interval partitioning in the past.
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