Oracle-focused solutions will zero in on reducing both service time and queue time. CBC latch contention indicates a high level of buffer activity, which consumes CPU. So you start thinking of creative Oracle-centric ways to reduce the amount of buffer cache activity. You also expect, and will be looking for, high buffer get (that is, logical IO) SQL during your application analysis. From an Oracle queue time perspective, a possible solution is to increase the number of CBC latches. (Many other solutions will be presented in Chapter 6, which covers Oracle buffer cache internals.) The key is to focus on reducing the response time, not just the service time or the wait time.

From an application perspective, look for the high buffer get SQL. From an operating system perspective, look for ways to give Oracle more CPU power. Of course, this could mean additional and/or faster CPUs, but it also implies looking for any processes consuming a lot of the CPU that could possibly run at other times or not be run at all.

This example demonstrates that a relatively simple ORTA, combined with a quick 3-circle analysis, results in a spot-on diagnosis, a number of solution possibilities, and graphics to help everyone understand the situation.