BC remote Oracle DBA - Call (800) 766-1884  
Oracle Consulting Oracle Training Development

Remote DBA

Remote DBA Plans  

Remote DBA Service

Remote DBA RAC

Remote DBA Oracle Home
Remote DBA Oracle Training
Remote DBA SQL Tuning Consulting
Remote DBA Oracle Tuning Consulting
Remote DBA Data Warehouse Consulting
Remote DBA Oracle Project Management
Remote DBA Oracle Security Assessment
Remote DBA Unix Consulting
Burleson Books
Burleson Articles
Burleson Web Courses
Burleson Qualifications
Oracle Links
Remote DBA Oracle Monitoring
Remote DBA Support Benefits
Remote DBA Plans & Prices
Our Automation Strategy
What We Monitor
Oracle Apps Support
Print Our Brochure
Contact Us (e-mail)
Oracle Job Opportunities
Oracle Consulting Prices





Remote DBA services

Remote DBA Support

Remote DBA RAC

Remote DBA Reasons

Remote Oracle Tuning

Remote DBA Links

Oracle DBA Support

Oracle DBA Forum

Oracle Disaster

Oracle Training

Oracle Tuning

Oracle Training

 Remote DBA SQL Server

Remote MSSQL Consulting

Oracle DBA Hosting

Oracle License Negotiation








Automating Oracle

Oracle Tips by Mike Ault

Reset Of Kept Packages

Many times, for one reason or another, databases are periodically shutdown and restarted. The shutdown of a database releases the kept objects and this kept object information is not retained. Thus, upon restart, the objects must be re-kept. For those not sure what this process entails, let me explain. Each PL/SQL object, whether it be a procedure, function, package or trigger, is stored in the shared pool library caches after it is used. If the objects in the shared pool aren’t re-used, then they are eventually aged out by means of a modified least recently used (LRU) algorithm. Sometimes, objects that shouldn’t get aged out do, resulting in a performance hit when they must be recalled from disk. In order to prevent aging of objects out of the shared pool Oracle has provided a package called DBMS_SHARED_POOL that contains a procedure KEEP that is used to flag an object as KEPT preventing it from being aged out of the pool.

By creating a table that holds the names of kept objects, we can create a PL/SQL procedure that periodically wakes up and if required, re-issues the command to keep various objects in the shared pool. Figure 4 shows the structure of an example table.


For more information on this topic, I recommend Don Burleson's latest book "Oracle Tuning: The Definitive Reference". 

You can buy it direct from the publisher for 50%-off and get instant access to the code depot of Oracle tuning scripts:


Expert Remote DBA

BC is America's oldest and largest Remote DBA Oracle support provider.  Get real Remote DBA experts, call
BC Remote DBA today.



Remote DBA Service

Oracle Tuning Book


Advance SQL Tuning Book 

BC Oracle support

Oracle books by Rampant

Oracle monitoring software







BC Remote Oracle Support

Remote DBA

Remote DBA Services

Copyright © 1996 -  2013 by Burleson. All rights reserved.

Oracle® is the registered trademark of Oracle Corporation.

Hit Counter