Craig Shallahamer's Blog
|
You were brought to this page based on an internet search
and as a free service to Oracle DBAs.
The text below is an except from the book,
Oracle Performance Firefighting, written by
Craig Shallahamer of
OraPub, Inc.
Figures and tables are not included on this page, only their reference.
To order the book in either print or PDF form, click
here.
©2009, 2010 by Craig Shallahamer. This is copyrighted material.
Please—Out of respect for those involved in the creation of the book and also for
their familes, we ask you to respect the copyright both in intent and deed. Thank you.
-------------------------------
<p>The benefits of the 3-circle analysis method are many and should quickly become obvious. As you read about the following benefits, consider how they would have helped you in previous firefighting situations.
</p><p>* Different perspectives reduce risk. An ancient proverb says, "Plans fail for lack of counsel, but with many advisers they succeed."7 When your analysis is based on three connected yet distinct perspectives, your chances of making a mistake are greatly diminished. In addition, I cannot overstate the power of analyzing the operating system bottleneck from an operating system perspective, or finding the problem SQL based on what both Oracle and the operating system are telling you. If your operating system and Oracle analysis do not support each other, then you are missing something. Once you have confirmed your analysis from multiple perspectives, the risk of a misdiagnosis is greatly reduced.
</p><p>* Different perspectives strengthen analysis. Establishing and understanding the links or relationships among the three subsystems not only reduces the risk of a misdiagnosis, but also increases the strength of the analysis. You will have anticipated questions others will ask and can address how one subsystem is affecting the other. People inherently seem to understand that your analysis vets inconsistencies and errors. You'll find that your analysis is naturally comfortable for people from both an operating system and a "it's always the SQL" perspective. This helps build a cohesive and unified approach to solving the problems. Many DBAs make the mistake of diagnosing only from one or perhaps two perspectives. Then when they present their analysis, they are shocked to find that, for example, the operating system team does not agree with or is offended by their analysis. If they had analyzed the situation from all three perspectives, their analysis would have been much stronger and received a better reception.
</p>
©2009, 2010 by Craig Shallahamer. This is copyrighted material.
Please—Out of respect for those involved in the creation of the book and also for
their familes, we ask you to respect the copyright both in intent and deed. Thank you.
|
|
Know what's important before it's too late!
OraPub's
Performance Training
is like no other...
More Class Pics...
Get student testimonials!
|
