The Top Five Events
Dan AJun 2 2008 — edited Jun 3 2008Today was our payroll day so the database was busy. And here are three different snaps - in the morning around midday and early afternoon.
CPU time figures in all of them, and in the first report there is an elapsed time of 51.45 from the SQL*Net more data from dblink metric. None of our users complain of long wait times and I dont see anything here to drill down to as I read that CPU time often appears in the Top 5. The only issue I can see here maybe is the SQL*Net metric.
Event Waits Time(s) Ela Time
-------------------------------------------- ------------ ----------- --------
SQL*Net more data from dblink 209 167 51.45
CPU time 69 21.20
db file sequential read 33,174 43 13.14
SQL*Net message from dblink 115 35 10.88
db file scattered read 6,775 6 1.73
Event Waits Time(s) Ela Time
CPU time 307 52.15
db file sequential read 493,485 173 29.49
SQL*Net message from dblink 154,908 40 6.75
latch free 996 25 4.33
db file scattered read 47,175 25 4.32
Event Waits Time(s) Ela Time
CPU time 87 63.80
db file sequential read 71,643 26 19.02
db file scattered read 18,309 14 10.53
control file parallel write 321 4 2.87
log file sequential read 16 2 1.18
null