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.

The tkprof utility was invoked, and the formatted file traceout.txt was created and does indeed exist!

The preceding trace file snippet is what we would expect, with one exception. It does contain the standard trace information about CPU consumption and block activity, and it also contains wait event data including the average wait times. As discussed previously, IO-related average wait times are very useful in understanding Oracle's interaction with the IO subsystem. What is missing though is bind variable details. The SQL statement clearly shows bind variables are being used (and they are system-generated), but notice there are no references to the actual bind variables. When multiple trace files are consolidated, don't expect to see the individual bind variables. To get this level of detail, you'll need to look at the trace file yourself or use another tool.