* Performance Summary: In a single sentence, summarize each subsystem's situation and comment on their relationships. Then clearly and forcefully establish the relationships among the three subsystems. In each subsystem's Performance Analysis section, I focus primarily on that circle's area. But in this Performance Summary section, my goal is to clearly demonstrate that their activity is strongly correlated. If I can establish these links, my recommendations will not only attack the actual problem, but will also be better received by others. I also summarize my recommendations in this section, showing how they address the problems directly.

* Oracle Performance Analysis: Start this section with a one- or two-sentence summary of the Oracle performance analysis. Then focusing on Oracle, not the application or the operating system, perform a detailed Oracle response-time analysis (you'll learn more about how to do this later in this chapter and in Chapter 5). This section is very detailed and includes actual script output and screen shots.

* Application Performance Analysis: Start this section with a one- or two-sentence summary of the application performance analysis. Then focus on the application, not Oracle or the operating system. Based on your Oracle performance analysis, identify the most resource-consuming SQL, programs, processes, users, and applications. I also look at application-specific features. For example, with the Oracle E-Business Suite, the batch manager (called the Concurrent Manager) can have a dramatic performance impact. For a comprehensive analysis, the Concurrent Manager must be addressed. As with the Oracle Performance Analysis section, the contents are typically very detailed and include actual script output and screen shots.