查看AWR报告的10个技巧.pdfVIP

TEN TIPS FOR USING AWR TOP TEN TIPS Sometimes we just want to get a quick idea of how things look on a database. Reviewing an AWR report is one way to do that. Here are ten most-used methods. CHECK THE TOP-5 FOREGROUND EVENTS Almost always, a database will be waiting most often on disk reads--usually sequential reads for OLTP-type applications, or direct path read (or scattered read) for databases running batch jobs doing full scans. Very often, CPU time is the next event. Below is one such typical report. Top 5 Timed Foreground Events Event Waits Time(s) Avg wait (ms) % DB time Wait Class db file sequential read 7,202,983 54,532 8 37.40 User I/O db file scattered read 1,638,646 26,803 16 18.38 User I/O DB CPU 20,566 14.11 gc cr grant 2-way 2,096,011 5,021 2 3.44 Cluster gc current block 3-way 850,526 2,637 3 1.81 Cluster CHECK THE SEQUENTIAL READ RATE The sequential read rate is a great metric. You can compare that number across platforms, whereas the scattered read metric is not easily comparable. Disk latency should always be below 10 ms, or at least 100 reads/sec. Depending on how the SAN is caching data, the sequential read rate is sometimes as low as 2 ms. That indicates the SAN has already cached the data, not that the disk drives are really fast. In the excerpt above, you can see we have 8 ms latency. REVIEW TOP-SQL BY ELAPSED TIME This is a convenient, easy way to see the longest runtime for that period. Here is an example: SQL ordered by Elapsed Time TEN TIPS FOR USING AWR Elapsed Elapsed Time Executions %Total %CPU %IO SQL Id SQL Module SQL Text