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.

This report was first used to understand how the application set some of the various session identification columns. I always hope no action will be required to further identify a session(s) or a user(s). Logon triggers are just plain scary. You mess them up, and the entire Oracle application can halt. In this case, I felt it was necessary and implemented the logon trigger that is shown back in Figure 5-20.