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 Mark Gury, of MGA based in Australia, spends countless hours optimizing PeopleSoft systems. He has personally told me on nurmous occasions that using the force option has returned a different row set. The lesson here is to always thoroughy test when using cursor sharing before you make the change in production.
4 Remember that a shared pool flush is not a true flush. Pinned cursors and objects (think packages) will not be flushed.
5 In case you're wondering, you can set both (although this is not recommended). If you set both, Oracle will probably respect the direct setting via shared_pool_reserved_size.
©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.
|