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.
-------------------------------
If you are not sure what the key business transactions are, then ask your manager. Even better, set up a meeting with the user representatives and ask their priorities. Keep it limited to just a handful of transactions. Let everyone know that initially your team must focus on the absolute business-critical transactions and nothing else. Reassure them that after these transactions are running well, you will move on to another tier of performance analysis.
After selecting the transactions, take multiple samples. It is best to have users run the transactions and have them watch you write down the timing result. This will increase their trust, which at this point is probably at an all-time low. You don't need to take 30 samples-3 to 5 will be enough to give you a good idea of the situation.3 Then write these down and perhaps post them so everyone knows the baseline.
Regardless of which tools you use, you will need interactive and historically focused tools. Each has a distinct focus, and most vendor-supplied tools naturally fall into one of these categories.
©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.
|