Thanks Venu. THis database got some issue and had to brought down and up . When the database brought down, it was taking so much time that we finally nedd to abort and this happen three time today and look like that this result in some recovery or other issue that is taking such lock. As the database backed up, all job queue process are taking all pending jobs and all are shown with this lock in v$session_wati and hanged there from last three hours. Hopefully it will be clreared by the end of the day and in the meantime will work on metalinK as well as oradebug command suggestion Thanks "Potluri, Venu (CT)" <venu_potluri@xxxxxx> wrote: I had this problem recently in our Oracle Applications database. Had a TAR open with Oracle Support and they proved to be useless, as it happens more often than not. I couldn?t get them to give me a sure fire way to identify the session causing the others to wait on this event. There is a doc on metalink that describes how to troubleshoot this. The name escapes me but search on something like ?how to troubleshoot library cache clock?. Everytime I saw this wait event, I took a system state dump and looked at the trace file which could help in identifying the offender. It was largely a futile exercise as I could never identify the offender in two weeks using what Oracle had given me. Good luck. -----Original Message----- From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Sanjay Mishra Sent: Wednesday, July 06, 2005 3:01 PM To: Jared Still Cc: oracle-l@xxxxxxxxxxxxx Subject: Re: library cache load lock Jared Thanks for quick reply. I had no record in both blockers and Waiters view. I had killed the session appeared in DBa_jobs_running and even killed the snp_process and now I am not getting any snp process started even the Job_queue_process are 8. ANy suggestions. Lock are still same for all sid appeared in Dba_jobs_runing and appeared in v$session_wait Thanks Sanjay Jared Still <jkstill@xxxxxxxxx> wrote: Have you examined dba_blockers/dba_waiters to see which session is causing the contention? Maybe it needs to be killed? We have a similar issue at times with a misbehaving app. The processes on the app server dies, leaving a lock on a table. TCP being what it is, the database never knows that the client process has died, and we ( meaning me) must go kill the process. Yes, I have a potential work-around for that, still waiting for user testing. Jared On 7/6/05, Sanjay Mishra <smishra_97@xxxxxxxxx> wrote: I have several of these shown in the v$session_wait. Any idea as what need to be done. SOme of the them are linked to mine Job QUeue process. So all 7 Job processa re hanged and each have is showing this lock TIA Sanjay __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- Jared Still Certifiable Oracle DBA and Part Time Perl Evangelist __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --------------------------------- If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ --------------------------------- --------------------------------- Sell on Yahoo! Auctions - No fees. Bid on great items.