The depth is one (dep=1), which means Oracle considers this application SQL, recursive SQL. Therefore, all its related CPU time will be recorded as both recursive SQL and server process SQL (statistics CPU used by this session), plus there will be some related parse time CPU consumption. So, as you can see, we cannot simply subdivide total Oracle CPU consumption into the three exclusive categories of parsing, recursive SQL, and everything else. This also provides an answer to why recursive CPU consumption can seem strangely high!

Figure 5-3 shows a simple script to gather CPU consumption, including recursive SQL CPU consumption, and parsing-related CPU consumption, over a 120-second period. Figure 5-4 takes the raw values and produces the service time details we need for our ORTA.

Figure 5-3. This code snippet details the collection of values for service time classification based on v$sysstat.