> > The issue we all forget is this: The "Wait Interface" records the last > _instrumented_ *wait* event. The process has then moved on to executing in > the CPU. However, since there is not "Waiting for CPU" event (and this is > not necessarily a "wait" event!!), what you need to do is to look at the > "SESSION_STATE" column, and you _will_ see "ON CPU" for this event. What Don't forget that Oracle doesn't really know if it is running or Not when it comes to precess state. For instance, if a session is marked "ON CPU" it can also be swapped out. Oracle is user mode code. -- //www.freelists.org/webpage/oracle-l