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.
-------------------------------
What a difference a few years can make, eh? The key difference is that John can tell the doctor where the pain is. This is just like Oracle's wait interface telling you where the pain is, where the contention is, and where too much time is being spent. Ratio analysis is like diagnosing Johnny, whereas wait-event analysis is like working with John-a much faster, more precise, and more confident diagnosis.
* First, the doctor must know John's language and be able to listen to him. This is just like a firefighter knowing how to listen to Oracle, through Oracle's wait interface. This book will teach you how to listen to Oracle. But this is just the start.
* Second, even with an amazing diagnosis, to solve John's problem, the doctor must have a deep understanding of the human body and specifically in this case, the elbow. This is just like a performance specialist knowing Oracle internals. Knowing Oracle is suffering from intense library cache contention is good, but to solve the problem, you must understand Oracle internals enough to influence the situation to reduce the contention.
©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.
|