The DBMS_SHARED_POOL
package provides access to the shared pool, which is the shared memory area where cursors and PL/SQL objects are stored. DBMS_SHARED_POOL
enables you to display the sizes of objects in the shared pool, and mark them for keeping or not-keeping in order to reduce memory fragmentation.
This chapter contains the following topics:
Overview
Operational Notes
The procedures provided here may be useful when loading large PL/SQL objects. When large PL/SQL objects are loaded, users response time is affected because of the large number of smaller objects that need to be aged out from the shared pool to make room (due to memory fragmentation). In some cases, there may be insufficient memory to load the large objects.
DBMS_SHARED_POOL
is also useful for frequently executed triggers. You may want to keep compiled triggers on frequently used tables in the shared pool.
Additionally, DBMS_SHARED_POOL
supports sequences. Sequence numbers are lost when a sequence is aged out of the shared pool. DBMS_SHARED_POOL
is useful for keeping sequences in the shared pool and thus preventing the loss of sequence numbers.
Table 133-1 DBMS_SHARED_POOL Package Subprograms
Subprogram | Description |
---|---|
Sets the aborted request threshold for the shared pool |
|
Keeps an object in the shared pool |
|
Marks a library cache object as a hot object |
|
Purges the named object or specified heap(s) of the object |
|
Shows objects in the shared pool that are larger than the specified size |
|
Unkeeps the named object |
|
Unmarks a library cache object as a hot object |
This procedure sets the aborted request threshold for the shared pool.
Usually, if a request cannot be satisfied on the free list, then the RDBMS tries to reclaim memory by freeing objects from the LRU list and checking periodically to see if the request can be fulfilled. After finishing this step, the RDBMS has performed a near equivalent of an 'ALTER
SYSTEM
FLUSH
SHARED_POOL
'.
Because this impacts all users on the system, this procedure "localizes" the impact to the process failing to find a piece of shared pool memory of size greater than thresh_hold
size. This user gets the 'out of memory' error without attempting to search the LRU list.
This procedure keeps an object in the shared pool. Once an object has been kept in the shared pool, it is not subject to aging out of the pool. This may be useful for frequently used large objects. When large objects are brought into the shared pool, several objects may need to be aged out to create a contiguous area large enough.
Table 133-3 KEEP Procedure Parameters
Parameter | Description |
---|---|
|
Name of the object to keep. The value for this identifier is the concatenation of the address and Currently, |
|
(Optional) If this is not specified, then the package assumes that the first parameter is the name of a package/procedure/function and resolves the name. Set to Set to Set to Set to In case the first argument is a cursor address and hash-value, the parameter should be set to any character except |
There are two kinds of objects:
PL/SQL objects, triggers, sequences, and types which are specified by name
SQL cursor objects which are specified by a two-part number (indicating a location in the shared pool).
For example:
DBMS_SHARED_POOL.KEEP('scott.hispackage')
This keeps package HISPACKAGE
, owned by SCOTT
. The names for PL/SQL objects follow SQL rules for naming objects (for example, delimited identifiers and multibyte names are allowed). A cursor can be kept by DBMS_SHARED_POOL
.KEEP('0034CDFF, 20348871','C')
, 0034CDFF
being the ADDRESS
and 20348871
the HASH_VALUE
. Note that the complete hexadecimal address must be in the first 8 characters.
This procedure marks a library cache object as a hot object.
DBMS_SHARED_POOL.MARKHOT ( schema VARCHAR2, objname VARCHAR2, namespace NUMBER DEFAULT 1, global BOOLEAN DEFAULT TRUE); DBMS_SHARED_POOL.MARKHOT ( hash VARCHAR2, namespace NUMBER DEFAULT 1, global BOOLEAN DEFAULT TRUE);
Table 133-4 MARKHOT Procedure Parameters
Parameter | Description |
---|---|
|
User name or the schema to which the object belongs |
|
Name of the object |
|
Number indicating the library cache namespace in which the object is to be searched. Views such as |
|
If |
|
16-byte hash value for the object |
This procedure purges the named object or specified heap(s) of the object.
DBMS_SHARED_POOL.PURGE ( name VARCHAR2, flag CHAR DEFAULT 'P', heaps NUMBER DEFAULT 1); DBMS_SHARED_POOL.PURGE ( schema VARCHAR2, objname VARCHAR2, namespace NUMBER, heaps NUMBER); DBMS_SHARED_POOL.PURGE ( hash VARCHAR2, namespace NUMBER, heaps NUMBER);
Table 133-5 PURGE Procedure Parameters
Parameter | Description |
---|---|
|
Name of the object to purge. The value for this identifier is the concatenation of the address and Currently, |
|
(Optional) If this is not specified, then the package assumes that the first parameter is the name of a package/procedure/function and resolves the name. Set to 'P' or 'p' to fully specify that the input is the name of a package/procedure/function. Set to 'T' or 't' to specify that the input is the name of a type. Set to 'R' or 'r' to specify that the input is the name of a trigger. Set to 'Q' or 'q' to specify that the input is the name of a sequence. In case the first argument is a cursor address and hash-value, the parameter should be set to any character except 'P' or 'p' or 'Q' or 'q' or 'R' or 'r' or 'T' or 't'. |
|
Heaps to be purged. For example, if heap 0 and heap 6 are to be purged: 1<<0 | 1<<6 => hex 0x41 => decimal 65, so specify heaps =>65.Default is 1, that is, heap 0 which means the whole object would be purged |
|
User name or the schema to which the object belongs |
|
Name of the object to purge |
|
Parameter is a number indicating the library cache namespace in which the object is to be searched |
|
16-byte hash value for the object |
ORA-6570
: An exception is raised if the named object cannot be found
ORA-6570
: An object cannot be purged it marked as permanently kept
All objects supported by the KEEP Procedure are supported for PURGE
.
This procedure shows objects in the shared_pool
that are larger than the specified size. The name of the object is also given, which can be used as an argument to either the KEEP
or UNKEEP
calls.
This procedure unkeeps the named object.
DBMS_SHARED_POOL.UNKEEP ( name VARCHAR2, flag CHAR DEFAULT 'P');
Caution:
This procedure may not be supported in the future if automatic mechanisms are implemented to make this unnecessary.
This procedure unmarks a library cache object as a hot object.
DBMS_SHARED_POOL.UNMARKHOT ( schema VARCHAR2, objname VARCHAR2, namespace NUMBER DEFAULT 1, global BOOLEAN DEFAULT TRUE); DBMS_SHARED_POOL.UNMARKHOT ( hash VARCHAR2, namespace NUMBER DEFAULT 1, global BOOLEAN DEFAULT TRUE);
Table 133-8 UNMARKHOT Procedure Parameters
Parameter | Description |
---|---|
|
User name or the schema to which the object belongs |
|
Name of the object |
|
Number indicating the library cache namespace in which the object is to be searched |
|
If |
|
16-byte hash value for the object |