Session-level ORTA is useful when a very specific business-centric problem has been reported, and the underlying database interaction can be identified. Keep in mind that Oracle and operating systems are designed and built to share resources. This implies that any singularly transactional-focused report is the result of both the transaction under investigation and all the other activity. No Oracle session operates untouched by other Oracle sessions, because Oracle is built to share resources. Don't be fooled into thinking your session-level profile output is the result of only the processes run by the session being profiled.

There are times when a user's session can be uniquely identified by its session identifier and serial number. When this is possible, it is usually very easy to profile that session based solely on Oracle's performance views.

Figure 2-18 shows the result of profiling a session based on its session identifier, which is the sid column from the v$session view. This report is run with careful user coordination, as follows: