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.
-------------------------------
Figure 7-18. While 24 IMU latches have been created, at the time of this report, only 9 of them have been used, as evidenced by their gets activity.
Identifying IMU latch contention is no different than identifying any other type of latch contention. If you're not comfortable with this, please review Chapter 3.
If IMU is causing problems, on Oracle Database 10g and later systems, you will see the wait event latch: In-memory undo latch as your top wait event. Plus your database server CPUs are probably so hot due to server processes spinning trying to acquire one of the IMU latches that they are ready to explode. So pinpoint diagnosis is not the tricky part.
©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.
|