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.
-------------------------------
3 decode(a.type,'PACKAGE','PKG','PACKAGE BODY','PBDY','FUNCTION','FNC','PROCEDURE','PRC') typex,
Figure 7-10. Shown is output the OSM script dboc.sql followed by the actual SQL. This report was run immediately after the instance was cycled. Production Oracle systems will produce thousands of rows, and therefore the threshold parameters will need to be adjusted.
When forcing objects to be kept in the shared pool, keep in mind that we are, in effect, gaming Oracle's least recently used (LRU)-based shared pool memory management algorithm. We are saying that we know better than Oracle does. This could actually be the case, since most DBAs know their applications very well. But until you do, stuffing your shared pool full of packages like a Christmas stocking can actually increase the likelihood of "out of memory" errors, because little room is left for all the hundreds-if not thousands-of other shared pool objects. So, think carefully before using this procedure.
©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.
|