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>* 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><p>* Multiple solutions naturally result. At least three different solutions will naturally result, and probably many more! When solutions are being devised, I focus on each subsystem and ask myself how I can alter the situation to improve response time. For example, when focusing on the Oracle circle, I ask myself, "How can I alter the Oracle instance to reduce response time?" The answer may be as simple as increasing the buffer cache, but the focus is clearly on changing Oracle. It is common to develop multiple solutions for each subsystem. The realities of availability and change control mean that some changes are not immediately possible, need to be scheduled, or are simply not an option. Multiple solutions will be attacking the same problem, which obviously increases the chances of a significant performance improvement.
p><p>* A story develops organically. Your analysis will naturally develop a story. Yes, I said a story. If you can turn a raging technical catastrophe into a plausible story that both technical and nontechnical people can understand, you have a very good chance of people believing you and therefore embracing your recommendations. Why? Because it makes sense to them, and people are much more willing to believe in someone they understand. Don't underestimate the power of a simple story. Throughout history, stories have repeatedly demonstrated the ability to change entire cultures and countries. Your technical analysis may be staggeringly accurate, but if you can't convince others, they will not accept your recommendations. A simply story can transform a very complex problem into a tangible and understandable situation. The beauty of the 3-circle analysis method is that the technical analysis naturally creates the story for you. I'll show you how this works after we look at some case studies of 3-circle analysis.
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!
|
