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.
-------------------------------
Resolving the most common mutex issues is detailed in their respective Oracle internals chapter. For now, you are fully prepared to detect if mutex contention exists, if it is significant, and specifically which mutex is being requested.
Figure 3-18. An example of mutex contention. This situation was created by having a few sessions opening and closing a very simple cursor in a tight PL/SQL loop.
Figure 3-19. An example of mutex contention. This situation was created in the same way as the one reflected in Figure 3-18, except the instance parameter session_cached_cursors was set to zero. This ensures exclusive library cache mutex acquisition requests.
©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.
|