Professional Documents
Culture Documents
AWR Analysis
AWR Analysis
AWR Analysis
REPORT ANALYSIS
What Is AWR
A background process
A set of tables
A set of reports
Takes snapshots of statistics every hour
Takes snapshot of high-cost SQL every hour
Top-Down Approach
In above scenario " DB time " metric is higher than elapsed time .
which is not a concern.But if it is Reverse then session are waiting
for something.
Load Profile Section:
1.How many Hard Parse are happening
2.How much Redo is generated
3.How many Physical Reads are happening etc
4.How many Sorts are happening
Wait Classes :
No of CPU core=2.
Parse CPU to Parse Elapsd : parse cpu time /parse Elapsed time :
Here it is only 6.90 means more cpu time used for parsing.which is not
good.
Here low % indicate some bottleneck is there related to parsing.
Execute to Parse: When execute is more than parse, the
figure will be positive. The ratio goes down if there are
more parses than the execute. Some of the queries are
parsed, but less or never executed!
1. first of all check for wait class if wait class is User I/O , System I/O, Others etc this could be fine but if wait
class has value "Concurrency" then there could be some serious problem.
2.Next to look at is Time (s) which show how many times DB was waiting in this class and then Avg Wait (ms).
If Waits are high but Avg Wait (ms) is low then you can ignore this. If both are high or Avg Wait (ms) is high
then this has to further investigate.
In the above screen shot, most of the %DB time on Concurrency but Avg wait is 0.381min.So ignore it.
CPU and Memory
The values should not be very high (preferably less than 75%).
Time Model Statistics:
1.If Hard parse elapsed time took more %of DB time then we have to
find out incorrect use of Bindvariable
2.Here Sql execute elapsed time took 96% of DB time . So we can look
into Top SQL to Tune it.
Operating System Statistics
system is 63.99 and 73.44% idle at time of report taken, So, there is
no resource crunch at system level. But if, you found low idle % that
means System is waiting for Some Resource.
SQL Statistics
Analysis Period:
AWR snapshot range from 78950 to 78952.
Summary of Findings
-------------------
Description ActiveSessions Recommendations PercentofActivity
-------------------- -------- ----------- -----------
1 Top SQL Statements 36.58 | 93.81 2
2 Buffer Cache Latches 6.58 | 16.86 1
Findings and Recommendations
----------------------------
Miscellaneous Information
---------------------------------------
● Wait class "Application" was not consuming significant database time.
● Wait class "Commit" was not consuming significant database time.
● Wait class "Configuration" was not consuming significant database time.
● CPU was not a bottleneck for the instance.
● Wait class "Network" was not consuming significant database time.
● Wait class "User I/O" was not consuming significant database time.
● Session connect and disconnect calls were not consuming significant database time.
● Hard parsing of SQL statements was not consuming significant database time.
THANK YOU