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.
-------------------------------
While there are hundreds of objects in the shared pool, as performance specialists, we must have a solid understanding of the following key objects (or areas):
* SQL (cursors): These statements contain the essence of the shared pool. In this chapter, I will provide details about cursors, but for now, think of a cursor as a chunk of memory connected to many other memory chunks containing information key to the proper functioning of the SQL statement.
* PL/SQL (cursors): These programmatic structures-such as functions, procedures, and packages-are also cached and therefore require shared pool memory. PL/SQL structures can consume a tremendous amount of shared pool memory.
©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.
|