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.
-------------------------------
As you can see, understanding how Oracle latches and mutexes work is just the beginning. But it is where you must start to resolve the most notorious of all Oracle performance problems, so it's worth spending your time to dig deep into the details.
Oracle systems have many protection needs. Besides the obvious security requirements, there are control requirements as well. Two broad categories of control are relational structures and memory structures. Latches and mutexes are firmly aligned with memory control.
Another name for relational control is lock management. For example, when the command lock table employee exclusive is issued, that's relational control.
©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.
|