The Art of Interpreting An AWR
The Art of Interpreting An AWR
The Art of Interpreting An AWR
Report
Important Sections
Top Wait Events
Load Profile
Instance Efficiency Percentages
SQL Statistics
Wait Event Histogram
Tablespace I/O stats section
Segment Statistics
Latch Sleep Breakdown
v$system_Wait_class;
Wait_class :- Application, Configuration, Concurrency,
Commit
Time_Waited :- Amount of time (in hundredths of a
second)
Total_Waits :- Number of times waited
Execute to parse %
# of times a statement was executed v/s # of
times it was parsed
% Non-Parse CPU
Shows the percentage of how much CPU resources were
spent on the actual SQL execution
If ratios is very high that means Oracle utilizes the CPU
mostly for statement execution but not for parsing
Scenarios
CASE 1
Free Buffer Waits is the common wait event
Environment EXADATA X3-2 Machine
How to resolve it ?
CASE 1 Findings
DBAs finding in AWR top wait event section (Free Buffer
Waits)
ASH report suggests few high load inserts
This only happens during massive inserts
Case 1 Solution
Configuring write back flash cache
This brought down the response time from 1 hour to just
10 mins
Case 2
Suddenly the complete database is hung
Every thing is stuck
What can be the issue ?
Case 2 Outcome
Storage issue (Dell Compellent)
/var/log/messages report multipath issue
Case 3
Suddenly the database is slow
Load Factor more than 3 times the #CPUs
What could be the problem ?
CASE 3 Solution
dbms_shared_pool.markhot
dbms_shared_pool.markhot('SYS','DBMS_APPLICATION_I
NFO',1);
number of CPU Cores hot objects copies
_kgl_hot_object_copies parameter
WAITEVENT: "library cache: mutex X" (Doc ID 727400.1)
Conclusion
Do not forget to use ASH where needed
It is important to check ADDM report
Consider using SQL Plan Management
Compare the numbers over time
Reduce long full table scans in OLTP
Minimize locking usage
Do not forget to do maintenance
Do not forget to use Real time ADDM
THANK YOU