RE: DBA_HIST_ACTIVE_SESS_HISTORY library cache pin waits

From: McPeak, Matt <>
Date: Wed, 26 Feb 2014 20:08:54 +0000
Message-ID: <>

More information...

There was a package (call it "P") re-installed at 4:29pm. There was a long-running (4hr) process ( call it "S1" ) running at that time that uses that package. Should that have prevented us from installing a new version of the package? It doesn't seem to have.

Then, other processes (call it "S2") - started after 4:29pm and that refer to "P" -- all seemed to start waiting indefinitely for the long-running process "S1".

Does that make sense?


From: [] On Behalf Of McPeak, Matt Sent: Wednesday, February 26, 2014 2:40 PM To: ORACLE-L
Subject: DBA_HIST_ACTIVE_SESS_HISTORY library cache pin waits


I have been asked what a process on Monday (2/24) timed out.

Going to DBA_HIST_ACTIVE_SESS_HISTORY, I can see that the process in question spent all its time waiting for a library cache pin.

I can see a lot written on how to get more information about current library cache pin waits. But does anyone know how to find out more about a library cache pin wait showing up only in ASH?

Thanks in advance!


Received on Wed Feb 26 2014 - 21:08:54 CET

Original text of this message