How To Trace Overall Library Cache Objects Invalidation Happening At Particular Period
(Doc ID 2746493.1)
Last updated on MARCH 18, 2022
Applies to:Oracle Database - Enterprise Edition - Version 220.127.116.11 and later
Information in this document applies to any platform.
Goal of this document is to explain a method to trace all library cache objects' invalidation at particular point of time by different process(es). Invalidation caused by DDL statements leads to library cache wait events like "library cache lock", "library cache pin", "cursor: pin S wait on X", "library cache: mutex X" etc in an highly concurrent environment. If there are too many invalidation happening to library cache objects during particular period of time by different processes and if you want to identify what are those DDL statements causing invalidation to both the parent objects and the dependent objects like CURSORs etc and executed by which process(es) then the following method can be followed.
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