A reader, July 06, 2017 - 9:48 am UTC
Hi,
Using X$ views are safer to execute in production environment and also on version 12c ??
A reader, July 06, 2017 - 9:49 am UTC
Hi,
Using X$ views are safer to execute in production environment and also on version 12c ??
July 07, 2017 - 2:17 am UTC
Any access to the X$ views in *any* evironment should be done with caution.
krishna, October 12, 2018 - 12:03 am UTC
Hi Connor ,
I have understand how library cache lock works but their are some scenarios where finding cause of occuring becomes difficult .
can you sahre some light how to trouble shoot how to find cause when their is no blocking session and mostly query waiting on this event are of select ,where no procedure is involved
October 12, 2018 - 3:19 am UTC
library cache locks normally indicate a higher level root cause issue. The most common I see are:
- High frequency SQL not using bind variables
- Shared pool too small (less common nowadays)
- Excessive DDL (people dropping/creating objects like they would in other database platforms)
So they are the things I look for (and tackle) when I see library cache issues in my database.
There are various means to find the session details involved. MOS Note 122793.1 covers them nicely.