Figure 9-34. Shown is the essential application SQL information. Because of the index addition, the targeted high logical IO SQL statements no longer appear on the top SQL report! In addition, the top logical IO SQL statements now consume 8.4M and 4.1M logical IOs, compared to the earlier case where the top two statements consumed 22.6M and 10.3M logical IOs, respectively (Figure 9-29). The status column index has had a profound impact on the most resource-consuming SQL.

It is also very encouraging that as result of the additional index, the top two logical IO statements consumed a combined 12.5M logical IOs (Figure 9-34), whereas before the index addition, the top two consumed 32.9M logical IOs (Figure 9-29). So, by aligning our ORTA with the application analysis, we correctly targeted the high-impact SQL statements.

The beauty of this is the drop in logical IO consumption occurred in conjunction with an increase in the number of SQL statement executions. For example, Figure 9-30 shows Oracle processed 134M logical IOs and 48.7K SQL statement executions. But with the additional index, Figure 9-35 shows Oracle processed only 37M logical IOs while executing over 53.1K SQL statements! And this all occurred with a reduced CPU utilization.