This report shows the activity during the collection interval only for the sessions of interest. Also note the use of the v$client_stats view, since we were collecting data based on the client identifier. We are provided with different types of statistics: DB CPU (service time), wait times (queue time) related to IO and RAC, workload statistics like db block changes, execute count, and user calls. This is a wonderful collection of statistics that can be used for firefighting, response-time analysis, and predictive analysis.

The preceding code snippet performs a variety of tasks. First, both statistics collection and tracing are disabled. Notice I used the proper client identifier. If you do make a mistake and attempt to turn off collection that is not currently enabled, Oracle will respond with an error.

I then wanted to know how many trace files were created during the 60-second interval. The 58 trace files were created and stored in the /tmp directory. All files with a suffix of .trc and SQL statements with an associated client identifier of WLC_1 were consolidated into a single trace file named WLC_1.trc. Specifying the client identifier was redundant, but I wanted to show the capability.