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.
-------------------------------
3 As I'll detail in the Chapter 4, there are occasions where Oracle records that a session is consuming CPU when actually the session is waiting in the CPU run queue.
Oracle controls serial access to memory using latches and mutexes. When a serialization issue develops, Oracle DBAs feel it in their gut, because they know they will need to go deep-sometimes very deep-into Oracle internals.
Even the most seasoned Oracle performance specialists shudder at the thought of dealing with Oracle latch contention. I have heard some of the most respected Oracle performance specialists say that once you get latch contention, there really isn't a whole lot you can do about it. As you will learn, this is absolutely wrong!
©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.
|