|
We seem to have switched email threads, but
the value from the VALUE column in the query on V$SESSTAT is centiseconds
of CPU consumed by the session. Although V$SESSTAT is not updated
continuously (but rather in "spurts"), you should see a clear trend in which
session is consuming the most CPU.
Whichever session is doing it, I would suggest
enabling SQL Trace (a.k.a. "the big hammer") on the session and running TKPROF
SORT=PRSELA,EXEELA,FCHELA against the raw ".trc" file produced...
...or use STATSPACK......or both...
|
Title: RE: 100% CPU utilization, urgent
- RE: Re: 100% CPU utilization, urgent Jeremiah Wilton
- RE: 100% CPU utilization, urgent Chris Stephens
- RE: 100% CPU utilization, urgent Broodbakker, Mario
- Re: 100% CPU utilization, urgent Thomas Day
- Re: 100% CPU utilization, urgent Tim Gorman
- RE: 100% CPU utilization, urgent Hussain Ahmed Qadri
- RE: 100% CPU utilization, urgent Koivu, Lisa
- RE: 100% CPU utilization, urgent Jeff Herrick
- RE: 100% CPU utilization, urgent Koivu, Lisa
- RE: 100% CPU utilization, urgent Rick_Cale
- RE: 100% CPU utilization, urgent Tim Gorman
- RE: 100% CPU utilization, urgent Thomas Day
- RE: 100% CPU utilization, urgent Thomas Day
- Re: 100% CPU utilization, urgent Thomas Day
- RE: 100% CPU utilization, urgent Koivu, Lisa
- Re: 100% CPU utilization, urgent Stephane Faroult
- Re: 100% CPU utilization, urgent Vladimir Begun
- Re: Re: 100% CPU utilization, urgent Jared Still
- RE: Re: 100% CPU utilization, urgent Stephane Faroult
- RE: Re: 100% CPU utilization, urgent Stephane Faroult
- RE: Re: 100% CPU utilization, urgent Jamadagni, Rajendra
