PL/SQL (MOSC)

MOSC Banner

Library cache pin wait event on a pakage

in PL/SQL (MOSC) 1 commentAnswered

We have a 19.17 database and recently we saw a "library cache pin" wait event and the object related to that was a package body. The wait event got resolved by itself in 10 min or so but during those 10 minutes there was a huge spike in the concurrency wait and lots of sessions were waiting. The issue / contention started at 9 AM and was resolved by 9.10 AM

So we have 2 questions

  1. What could cause such a lock / wait event?Can it happen if multiple sessions are trying to EXECUTE that package? OR it can only happen if one session was trying to alter that package or modify it and only that will place that lock / pin on that object and all other sessions trying to execute that package will need to wait until session # 1 finish compiling it?

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center