BLOG UPDATE 2015.01.20: Please Note! This patch has been deprecated. Please go to kevinclosson.net/slob to get the latest SLOB kit with the latest awr_info.sh.
BLOG UPDATE 2014.09.11: Please note: the following is a link to a more recent update of the awr_info.sh script. This version adds DB Time, DB CPU and Logical I/O: click here. The MD5 sum for this version of awr_info.sh is: a28a38b11040bb94f08a8f817792c75c
The SLOB kit comes with a little script that extracts interesting information from the awr.txt file produced at the end of a SLOB test. This is just a quick blog entry to point folks to a patched version of awr_info.sh that works properly with all Oracle Database 11g releases as well as Oracle Database 12c.
Oracle changed AWR format in the 18.104.22.168 and 12c releases so the old awr_info.sh script (in the publicly available SLOB kit) has been faulty for some time now.
I have a release of SLOB in the works that will include this awr_info.sh as well as improved data loader and improvements to the driver script (runit.sh) that includes optional, tunable think time between iterations of the SLOB work loop in slob.sql. For the time being please get a copy of the patched version of awr_info.sh.
New awr_info.sh Output
This version of awr_info.sh also gleans and outputs logical read (SGA buffer pool cached block accesses) data.
The following screen shot shows the patched awr_info.sh generating proper output for awr.txt files collected by SLOB databases running out of the 22.214.171.124, 126.96.36.199 and 12c releases.
The following picture is what Microsoft Excel looks like when I cut and paste the output of awr_info.sh. I’ve highlighted the new column for logical reads.
Exadata Cell Single Block Physical Reads?
Yes, the above picture does show AWR output from a run where the top wait event was cell single block physical read. Exadata? Yes! That’s because SLOB users often share their testing results from the Exadata platform. However, I do not get enough Exadata AWR reports to work through all of the awr_info.sh issues related to Exadata. To that end, latency information is not calculated and presented as is the case with db file sequential read. For what it’s worth this particular AWR report shows Exadata single block reads serviced with average latencies of 507 microseconds ( 7233/14256602).
Where To Get The Patch?
BLOG UPDATE 2014.12.09: Please Note! The following awr_info.sh readme and script supercede all prior versions mentioned in this blog: