RE: oradebug dump processstate 10

  • From: Muqthar Ahmed <Muqthar.Ahmed@xxxxxxxxxxxxxxxxx>
  • To: 'Egor Starostin' <egorst@xxxxxxxxx>
  • Date: Thu, 9 Jun 2005 13:58:47 -0400

Thanks Egor....I am reading Metalink Note:215858.1


-----Original Message-----
From: Egor Starostin [mailto:egorst@xxxxxxxxx] 
Sent: Thursday, June 09, 2005 1:19 PM
To: Muqthar.Ahmed@xxxxxxxxxxxxxxxxx
Cc: oracle-l@xxxxxxxxxxxxx
Subject: Re: oradebug dump processstate 10

> I have a function called GET_UTL_DIR and currently it is locked in the 
> database.  When I try to re-compile it I get the following error:
> ORA-04021: timeout occurred while waiting to lock object GET_UTL_DIR
> I have verified in v$lock but no user is locking.
Such locks (when someone is executing function and you are trying to
recompile it) are not displayed in v$lock.
>  Therefore, I have used oradebug command to get more info:
I'd say that 'oradebug dump processstate 10'' is some kind of overkill
in such situation.
You can easily find locker (not only for your case but for every
locking situation) issuing either "oradebug hanganalyze 2" or just 
"alter session set events 'immediate trace name hanganalyze level
2';". You will quickly get easily readable and small trace file with
tree(s) of blockers/waiters.

Read Metalink Note:215858.1 (Interpreting HANGANALYZE trace files to
diagnose hanging and performance problems) for further info about
hanganalyze event.

Free Oracle Session Resource Profiler

* * * * * * * * *

The information contained in this E-mail message is privileged, confidential, 
and may be protected from disclosure; please be aware that any other use, 
printing, copying, disclosure or dissemination 
of this communication may be subject to legal restriction or sanction. If you 
think that you have received this E-mail message in error, please reply to the 
sender and delete it from your computer. T
hank you.

Other related posts: