To help in analyzing the application, the report captures the SQL directly affecting the response times and shows its resource consumption. As Figure 2-16 shows, only the SQL identifier and key performance attributes appear in the report. For performance reasons, the actual SQL statement text is not collected.

During the reporting interval, every few seconds, the currently running SQL statement's identifier (SQL_ID) is captured from v$session. This part of rtsysx.sql provides the SQL statement's interval activity. For example, if SQL statement 123 were first captured and had already consumed 10,000 Oracle blocks, and during the last probe, it had consumed 15,000 blocks, this probe report would show the statement consuming 5,000 blocks during the report interval.

The SQL Activity Details During Probe section in Figure 2-16 captured a few statements. IO read queue time dominates this ORTA; therefore, locating physical IO SQL is extremely important to complete our analysis. The first two statements in this section have the largest number of physical reads! It is very common for this simple sampling method to quickly identify the key SQL statements that need special attention.