We have a PeopleSoft system (Finanacials) that is just moving into production. Some of the conversion and data entry stuff was running slowly so I peaked at our system and session wait events (as well as looking at some recent history with statspack). There was a huge amount of time_waited for 'library cache load lock'. Never came across this one before. According to the Docs, it is a lock used to load an object into the library cache (you don't want the same object loaded more than once). I am trying to find more information so I can debug this. Of course the problem isn't there today (other modules are being worked on. Maybe that is why).
Just trying to be ready when/if this happens again. I'm thinking a 10046 trace might give me some object information about what is being loaded/locked. Metalink suggests taking a systemstate dump (though they seem to mix up 'library cache lock' with 'library cache load lock'. Don't know if the same tracking techniques work on both.). Anybody else see this before? Suggestions on what to do if it shows up again? Thanks. Henry -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: Henry Poras INET: [EMAIL PROTECTED] Fat City Network Services -- 858-538-5051 http://www.fatcity.com San Diego, California -- Mailing list and web hosting services --------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
