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.
-------------------------------
* The critical production system is involved. This one is kind of obvious because, if the situation were not critical and a production system were not involved, then it wouldn't be classified as firefighting. But it's a common element.
* Technical promises are made by nontechnical people. When a performance situation escalates, it's common for management to get involved. While this can bring calm to the situation, if management desires peace at any price, it can lead to promises that are technically unfounded and put unnecessary stress on the technical team. You need to be diplomatic in these situations. Never agree to something you know is false and cannot be realistically accomplished. In the end, you could be held accountable simply for agreeing.
* The timing is unfortunate. How about Friday afternoon just before you are about to leave on a holiday-sound familiar? It has happened to everyone.
©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.
|