1002603 wrote:in EVERY TOP 5 list one item will reside in the top spot.
I'm wondering why OEM/ASH shows the main wait events as CPU and CPU Wait:
Event Event Class % Event Avg Active Sessions
CPU + Wait for CPU CPU 72.60 16.69
1002603 wrote:what evidence do you have that IO Waits should/would be reported in this section of the report?
Right, I understand that. Let me try to re-state my question. OEM is telling me that the largest wait is for CPU/CPU Wait, yet I can see from top that there are plenty of free CPU cycles. I can see from iostat that the disk subsystem is completely saturated. My question is...why is OEM reporting that CPU is the worst wait offender when there are plenty of free CPU cycles available and the disk subsystem is saturated? Why isn't OEM reporting pysical io waits as the worst wait offender?