At this point, you may have prepared a trace file for analysis, as well as possibly performance statistics. Now it's your turn to take this information and perform a session-level response-time analysis.

Using DBMS_MONITOR the first few times can be confusing. There is a lot involved to achieve the final reports. To help in this transition, I have included a real-life example here. To get the most from this example, remember the steps outlined in the previous section. You will see the spooled output follows these steps precisely. I have divided the key steps and made comments following each snippet.

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.