My DB was slow for about a week.
Batches reached into daytime.
Applications were also slow especially with batches still running.
Management demanded root cause & fix.
I was focusing on batch (and the slowed down SQL within),
others engaged external experts for help… we were sweating bullets!
AWR report to the rescue…
We created AWR reports for 24 hour periods for both normal and slow days:
awr_0418_dbsidxxx.html
awr_0427_dbsidxxx.html
awrdiff_0418_0427_dbsidxxx.html
AWR reports can be overwhelming, too much data to swift through.
It is way too easy to go sideways and waste time on something unrelated.
To have a feel on the big picture I like to look at the sections for load profile, top events, and time model statistics.
What do you think the problem was?
Before you read the next post you may want to check the reports.
Zoltan Nyiri 