Therefore, when using a report similar to Figure 8-17, a Statspack, or an AWR report, you should look for the highest elapsed time DML SQL.

The report shown in Figure 8-17 is a stripped-down version of Oracle's OSM topdml.sql report. There are many other columns of useful information that could be added to help identify the offending SQL and locate its application source. Identifying where in the application the SQL occurs is the first step in determining if the SQL statement itself, its application area, or its execution rate can be altered to reduce redo creation.

Figure 8-17. Shown is a condensed version of OraPub's OSM script topdml.sql, which helps identify redo-generating SQL. Additional columns that can be useful are centered around locating where the SQL resides or its source, such as the action and service columns.