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.
PleaseOut 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.
-------------------------------
When I first perform my analysis, while the overall structure is set, the document is essentially a scratch pad. Sure, it's full of report output and technical details, but it also contains comments, ideas, and offhand remarks. These are meant for my eyes only, as they contain undeveloped, untested, and miscellaneous ideas. I will never show this raw document to management. Only when I have a chance to back off a bit and rest, and then make a second pass will I allow anyone other than the DBAs to view my work.
Once I have completed my 3-circle analysis, I repeatedly go over each circle, and then work on clearly establishing each circle's relationship with the others. Detailed circle-specific solutions will naturally result. Eventually, the overall performance situation will become apparent and can be summarized in only one or two sentences. If I cannot quickly summarize the situation, then I know my analysis is somehow flawed or incomplete.
After repeated cleansing cycles and hopefully an "aha!" moment or two, the final document will begin to take shape. With the document completed, I am able to easily create a presentation or create email messages for a variety of audiences.
©2009, 2010 by Craig Shallahamer. This is copyrighted material.
PleaseOut 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.
|