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.
-------------------------------
As the following code snippet shows, flushing the shared pool is very simple, yet the effect is indeed significant.
One of the easiest, most powerful, and most appropriate shared pool latching solutions is to simply add subpools, which will also add shared pool latches. The process is detailed in the earlier "From Hashing to Subpools" section.
This particular solution is very clean in that it requires minimal effort and we are not gaming Oracle's shared pool LRU algorithm. However, keep in mind that more subpools may require more shared pool memory, an instance restart is required for the instance parameter change to take affect, and Oracle reserves the right to not respect your recommendation.
©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.
|