In vivid contrast with online activity, during batch processing, there is no think time and there can be significant client-processing time. As a result, for the total Oracle response time to equal batch process elapsed time, our response-time analysis must include client-processing time and also communication time between the client and server process. As presented in Chapter 5, this time component is captured by the SQL*Net message from client and SQL*Net more data from client wait events. If database links are involved, then don't forget to also include SQL*Net message from dblink and SQL*Net more data from dblink. When this normally useless and idle classified time is included, the batch process elapsed time will equal the total Oracle response time.

While including background process service and queue time is important and useful when analyzing an entire system, it can become less useful when focused on a single or a few sessions or processes. This normally does not present a problem, because session-focused collection will naturally include only time related to a specific session or group of sessions. So, what may seem like quite a technical challenge turns out to be not that big of a deal.

Depending on the Oracle release, Statspack and AWR reports may separate background process time. This makes our job even easier. But if the time is not separated, simply manually exclude any background process-related time.