If the status is "waited known time" then you are no longer waiting, and have been burning CPU since the completion of the last wait. The "seconds_in_wait" will then be a fair indicator of how long you've been burning CPU, given that it would have reset to zero as the last wait started and been counting roughly every 3 seconds since. The last wait was a "db file sequential read", so the actual time_waited will be in the order of 1/100 of a second and ignorable compared to seconds_in_wait (probably). The title "seconds_in_wait" is very misleading, it should be "seconds_since_the_start_of_the_last_wait_but_only_ accurate_to_about_the_nearest_three_seconds". But the limit on a column name is only 32 characters. Your correlated delete needs fixing to stop it burning CPU. Regards Jonathan Lewis http://www.jlcomp.demon.co.uk The Co-operative Oracle Users' FAQ http://www.jlcomp.demon.co.uk/faq/ind_faq.html April 2004 Iceland http://www.index.is/oracleday.php June 2004 UK - Optimising Oracle Seminar ----- Original Message ----- From: "Stefan Jahnke" <Stefan.Jahnke@xxxxxx> To: <oracle-l@xxxxxxxxxxxxx> Sent: Wednesday, March 31, 2004 7:26 PM Subject: AW: Urgent: db file sequential read - wait I actually got waited known time as a status. And the seconds where still counted up. So I guess the session was still waiting on this event. Stefan -----Ursprüngliche Nachricht----- Von: Mladen Gogala [mailto:mladen@xxxxxxxxxxxxxxx] Gesendet: Wednesday, March 31, 2004 8:10 PM An: oracle-l@xxxxxxxxxxxxx Betreff: Re: Urgent: db file sequential read - wait ---------------------------------------------------------------- Please see the official ORACLE-L FAQ: http://www.orafaq.com ---------------------------------------------------------------- To unsubscribe send email to: oracle-l-request@xxxxxxxxxxxxx put 'unsubscribe' in the subject line. -- Archives are at //www.freelists.org/archives/oracle-l/ FAQ is at //www.freelists.org/help/fom-serve/cache/1.html -----------------------------------------------------------------