John,
I would tend to disagree with that comment. If there are no wait events being recorded, and the process is consuming CPU, then my usual experience is that something brutal and inefficient is happening - such as extreme PL/SQL, or massive scanning and pinning (perhaps through bitmap indexes) with vast amounts of logical I/O. I've seen 'create index' take 30 minutes of CPU with no wait events (after the db file waits for the initial tablescan were over).
I may have come very late to this thread, so someone has probably said already that wait_time=-1 means less than 1 hundredth of a second for 8i, and less than 50 milliseconds for later versions of 9.
Regards
Jonathan Lewis
http://www.jlcomp.demon.co.uk/faq/ind_faq.html The Co-operative Oracle Users' FAQ
http://www.jlcomp.demon.co.uk/cbo_book/ind_book.html Cost Based Oracle: Fundamentals
http://www.jlcomp.demon.co.uk/appearances.html Public Appearances - schedule updated 4th Nov 2005
Ray,
What does WAIT_TIME = -1 indicate?
Regards, John Kanagaraj <>< DB Soft Inc Phone: 408-970-7002 (W)
Co-Author: Oracle Database 10g Insider Solutions http://www.samspublishing.com/title/0672327910
** The opinions and facts contained in this message are entirely mine and do not reflect those of my employer or customers **
-- //www.freelists.org/webpage/oracle-l
-- //www.freelists.org/webpage/oracle-l