The session identification criteria are the same as the logon trigger shown in Figure 5-20. In fact, the results are based on setting the client identifier using that specific logon trigger. The group of activity I am interested in has the session's client identifier set to WLC_1. Multiple sessions do meet the criteria, and Oracle is setup in a multithreaded architecture. This ensured multiple trace files would be produced, which makes for a more interesting (and trust-building) example.

The preceding code snippet ensures both tracing and statistics collection are turned off. Turning off statistics collection effectively empties the views of all rows. This is why it is also important to query the statistics before turning off statistics collection!

This particular DBMS_MONITOR session was run on Oracle Database 10g Release 1. If you are using Oracle Database 11g, the trace file directory structure is about a gazillion9 levels down. As you'll see in a few snippets later, I reset the trace file directory to /tmp. To make my job even easier, before I started having trace files placed in this directory, I removed all the trace files.