Pinning (keeping) Packaged Procedures in the Shared Pool

After referencing information from the oraclemag home page
(http://165.121.1.161/columns/burleson.html) regarding memory management
for stored procedures, I have several questions:

1. Does the procedure for "pinning" a Package in memory
   (dbms_shared_pool.keep) work on the 7.0.16 version of the database? The
   dbms_shared_pool package is included with this version and appears to work, but I have heard that the ability to "pin" objects in memory is available only on 7.1 and above.
2. Assuming dbms_shared_pool.keep works on my 7.0.16 database, what is the best way to determine the Packages/Procedures that are frequently swapped in and out of memory. These objects would be the ones that I would most likely want to "pin".
3. The article from oraclemag referenced above shows a "memory.sql" script that shows info from v$db_object_cache. When I run this query, the same Package owned by different schemas will show different memory usages. I am not sure why. It appears that when a Package is installed in a schema, the entire contents of the Package are loaded into memory, but I am unsure as to why other schemas would show a radically different amout of memory used by the same Package.

Any insight would be appreciated. Received on Thu Aug 08 1996 - 00:00:00 CEST