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.

Remember your school report card? It may have included your current term's grade point average and also an accumulated grade point average. Both statistics are important, yet based on a different data set. Oracle reports based on performance views can also yield current or single-term data (think interval) or accumulated data (think since instance start). For example, running a quick SQL statement referencing an Oracle performance view, such as v$sysstat, does not necessarily represent what is currently occurring, what just occurred, or what has recently occurred. It represents what has been occurring since the Oracle instance started! Therefore, unless you are careful, you can be deceived.