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>* 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><p>* Avoid finger-pointing; breed cooperation. Unless there is a gross misconfiguration, everyone involved can contribute to the solution. Since everyone has something to contribute, finger-pointing stops. It also helps put pressure on vendors or groups who state there is nothing for them to do, because essentially they are saying that there is nothing they can do to help. No one wants to say they don't want to help. For one group to place the blame entirely on another subsystem is usually not appropriate, demonstrates ill will, and will result in a suboptimal solution. When discussing solutions, look for every circle's group to contribute significantly. There must be a very good reason why a circle's group does not wish to participate in solving the problem.
</p><p>* Any performance tools will help. Any respectable tool kit will provide the information you need to perform a solid 3-circle analysis. Basic operating system tools such as vmstat and sar, and Oracle tools such as Statspack are enough to perform a strong analysis. These tools make it easier to get the information you need. Your analysis can go deeper, and you have a higher trust level in the raw data. When this occurs, both your productivity and analysis confidence increase. Regardless of your tools, because you're performing a 3-circle analysis, its built-in multiperspective analysis safeguards you from making a mistake.
</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!
|
