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.
-------------------------------
Based on my understanding of IMU, the experimental results, and understanding Oracle performance analysis, unless there are kernel issues with IMU (which there have been), I would always keep IMU enabled. With IMU enabled, you can expect Oracle to consume a significantly less amount of CPU.
IMU setup and monitoring is quite simple because Oracle automatically enables IMU by default. Only eight instance parameters directly affect IMU, and IMU activity is recorded just like any other Oracle internal activity.
If you want to make changes, carefully consider their effects, as all direct IMU instance parameters are currently hidden parameters. Eight instance parameters are used to control or affect IMU operations, as listed in Table 7-2.
©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.
|