See the tool configuration parameters link

Chapter 13 ■ traCe Files, trCaNlZr aNd ModiFyiNg sQlt behavior

The reason I mention the glossary of terms is because TRCANLZR needs to be interpreted correctly. There are many measures of time and each one needs to be understood for you to get the right picture of what is happening. For example the “response time” is the measure of time that the user perceives if they were sitting at a terminal running the SQL. That time is made up of actual work (Elapsed) and non-idle wait times. Idle wait times can be ignored as they are due the end user not responding (normally shown as SQL*Net message from client). Non-idle wait times are usually made up of activities that happen during steps in the SQL, for example fetching data from a disk. Once we have these definitions clear we can look at the “Response Time Summary”. Look at Figure 13-4, which shows an example response time summary for the SQL (this is for a simple SQL with no complications).

248

Chapter 13 ■ traCe Files, trCaNlZr aNd ModiFyiNg sQlt behavior

SQL> @sqltrcxtr.sql

You will be prompted for the same parameters as for TRCANLZR but after that ends you will be prompted for the parameters to run XTRACT.

Modifying SQLT Behavior

SQLT has many aspects to it and many tools that can be used. Despite this there are still situations where SQLT could do better or be modified to help with some situation. Luckily this is covered by the parameters which can be set to change SQLT’s behavior. If we look at the now familiar first page of the main report (see Figure 13-6), we see the “Tool Configuration Parameters” link.