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.
-------------------------------
There are a few ways to monitor IMU activity. (Detecting and resolving performance problems are covered in the next section.)
You cannot directly control the memory Oracle allocates to the IMU buffers. However, you can possibly indirectly influence Oracle's IMU memory allocation by altering the shared pool size by changing, for example, the shared_pool_size instance parameter. The current IMU memory allocation can be easily queried, as shown in the following code snippet:
Like many other Oracle statistics, IMU activity is recorded via the system statistics view, v$sysstat and v$sesstat. It's also interesting to watch the change between standard commits and IMU commits. If you see IMU commits increasing, you know IMU is active. The following is an example showing and comparing IMU and user commits.
©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.
|