98 DBMS_ILM_ADMIN
The DBMS_ILM_ADMIN
package provides an interface to customize Automatic Data Optimization (ADO) policy execution. In combination with partitioning and compression, ADO policies can be used to help implement an Information Lifecycle Management (ILM) strategy.
This chapter contains the following topics:
See Also:
-
Oracle Database VLDB and Partitioning Guide for information about managing Automatic Data Optimization (ADO) with this package
98.1 DBMS_ILM_ADMIN Overview
To implement your ILM strategy, you can use Heat Map in Oracle Database to track data access and modification. You can also use Automatic Data Optimization (ADO) to automate the compression and movement of data between different tiers of storage within the database.
98.2 DBMS_ILM_ADMIN Security Model
This package runs under definer's rights. The user requires DBA privileges.
98.3 DBMS_ILM_ADMIN Constants
The table in this topic describes constants used by the DBMS_ILM_ADMIN
package.
The value column refers to the numeric or character value that the constants resolve to.
Table 98-1 DBMS_ILM_ADMIN Constants
Constant | Value | Type | Description |
---|---|---|---|
|
|
|
Specifies the absolute number of concurrent ILM ADO jobs. |
|
|
|
Decides the degree of parallelism to be used for ADO jobs |
|
|
|
Provides a way to turn background ADO off or on |
|
1 |
|
Determines the frequency with which ADO background evaluation occurs. Specified in minutes. |
|
4 |
|
Controls whether ADO execution is online, offline. The
value for this parameter should either be
|
|
8 |
|
Index scan done |
|
1 |
|
Segment read done |
|
4 |
|
Full table scan done |
|
|
|
Segment write done |
|
|
|
Specifies the size (in megabytes) of the data that is processed by a single ILM ADO row level compression job. |
|
|
|
Controls the upper limit on number of ILM ADO jobs at
any time. The maximum number of concurrent ADO jobs is
|
|
11 |
|
Decides if ADO policies are treated as though they are
specified in seconds rather than days. Can take value
|
|
|
|
Controls the amount of time ADO history should be maintained. Specified in days. |
|
|
|
Decides the targeted tablespace storage through ADO actions as a percentage of tablespace quota. |
|
|
|
Decides when a tablespace is considered full. Specified as a percentage of tablespace quota. |
The DBMS_ILM_ADMIN
package uses the constants as parameter values shown in Table 98-2.
Table 98-2 DBMS_ILM_ADMIN Constants Used as Parameter Values
Constant | Value | Type | Description |
---|---|---|---|
|
|
|
Indicates whether automatic storage compression is enabled. |
|
|
|
The period of inactivity that will
determine that there are no modifications. This can be specified
using DBMS_ILM_ADMIN.CUSTOMIZE_ILM . The default
value is 1440 minutes, which is 1 day.
|
|
|
|
Indicates automatic ADO policy evaluation and execution is disabled |
|
1 |
|
Indicates automatic ADO policy evaluation and execution is enabled |
|
1 |
|
Specifies that the object may be offline while ADO action is performed. |
|
|
|
Specifies that the object should be online while ADO action is performed |
|
|
|
Indicates policy is specified in days. This is the default. |
|
|
|
Indicates policy unit is
changed from days to seconds. This could be used to test ADO
policy evaluation quickly instead of waiting for the policy
duration.
Note:
|
98.4 Summary of DBMS_ILM_ADMIN Subprograms
This table lists and briefly describes the DBMS_ILM_ADMIN
package subprograms.
Table 98-3 DBMS_ILM_ADMIN Package Subprograms
Subprogram | Description |
---|---|
Deletes all rows except the dummy row |
|
Clears all or some statistics for the heat map table, deleting rows for a given table or segment which match a given pattern, or all such rows |
|
Customizes environment for ILM execution by specifying the values for ILM execution related parameters |
|
Turns off all background ILM scheduling |
|
ENABLE_AUTO_OPTIMIZE Procedure | Enables Auto Compression for all Hybrid Columnar Compression objects in the PDB. |
Turns on all background ILM scheduling |
|
IGNORE_AUTO_OPTIMIZE_CRITERIA Procedure | Ignores the inactivity threshold so that uncompressed loads will be eligible for background auto optimization immediately. |
Updates or inserts heat map rows for all tables |
|
Sets the start date for collecting heat map data |
|
Updates or inserts a row for the specified table or segment |
98.4.1 CLEAR_HEAT_MAP_ALL Procedure
This procedure deletes all rows in HEAT_MAP_STAT$
except the dummy row.
Syntax
DBMS_ILM_ADMIN.CLEAR_HEAT_MAP_ALL;
98.4.2 CLEAR_HEAT_MAP_TABLE Procedure
This procedure clears all or some statistics for the heat map table, deleting rows for a given table or segment which match a given pattern, or all such rows.
Syntax
DBMS_ILM_ADMIN.CLEAR_HEAT_MAP_TABLE ( owner IN VARCHAR2, tablename IN VARCHAR2, partition IN VARCHAR2 default '', access_date IN DATE DEFAULT NULL, segment_access_summary IN NUMBER DEFAULT NULL);
Parameters
Table 98-4 CLEAR_HEAT_MAP_TABLE Procedure Parameters
Parameter | Description |
---|---|
|
Table owner |
|
Table name |
|
Name of the subobject, defaults to |
|
Date for the entry in |
|
Summary of segment access constants indicating access operations performed on the segment |
98.4.3 CUSTOMIZE_ILM Procedure
This procedure customizes environment for ILM execution by specifying the values for ILM execution related parameters. These values take effect for the next background scheduling.
Syntax
DBMS_ILM_ADMIN.CUSTOMIZE_ILM ( parameter IN NUMBER, value IN NUMBER);
Parameters
Table 98-5 CUSTOMIZE_ILM Procedure Parameters
Parameter | Description |
---|---|
|
One of the parameter constants defined in |
|
Value of parameter |
98.4.4 DISABLE_AUTO_OPTIMIZE Procedure
Disables Auto Compression for all Hybrid Columnar Compression objects in the PDB.
Syntax
After you issue enable_auto_optimize, auto compression will be enabled. New direct loads will be in an uncompressed format and the data will be compressed gradually in the background. For example, after five direct loads the user issues disable_auto_optimize. If the background auto compression task was only able to compress three of them (because of autotask time constraints, data not yet cold, etc.), the remaining two will be in an uncompressed format. The data from these two uncompressed loads will be compressed in the background even after the user issues disable_auto_optimize, but new direct loads will now be compressed.
DBMS_ILM_ADMIN.DISABLE_AUTO_OPTIMIZE;
98.4.5 DISABLE_ILM Procedure
This procedure turns off all background ILM scheduling.
Syntax
DBMS_ILM_ADMIN.DISABLE_ILM;
98.4.6 ENABLE_AUTO_OPTIMIZE Procedure
Enables Auto Compression for all Hybrid Columnar Compression objects in the PDB.
Syntax
When Auto Compression is enabled, direct loads into a Hybrid Columnar Compression (HCC) object would use the uncompressed format to achieve faster loads. The system will then wait until there are no modifications to the newly loaded data, for the duration of the specified inactivity threshold. At that point, the data from the uncompressed direct load will be gradually HCC compressed using a background Auto Compression task.
DBMS_ILM_ADMIN.ENABLE_AUTO_OPTIMIZE;
98.4.7 ENABLE_ILM Procedure
This procedure turns on all background ILM scheduling.
Syntax
DBMS_ILM_ADMIN.ENABLE_ILM;
98.4.8 IGNORE_AUTO_OPTIMIZE_CRITERIA Procedure
Ignores the inactivity threshold so that uncompressed loads will be eligible for background auto optimization immediately.
Syntax
DBMS_ILM_ADMIN.IGNORE_AUTO_OPTIMIZE_CRITERIA;
98.4.9 SET_HEAT_MAP_ALL Procedure
This procedure sets an HTTP request header. The request header is sent to the Web server as soon as it is set.
Syntax
DBMS_ILM_ADMIN.SET_HEAT_MAP_ALL ( access_date IN DATE, segment_access_summary IN NUMBER);
Parameters
Table 98-6 SET_HEAT_MAP_ALL Procedure Parameters
Parameter | Description |
---|---|
|
Date for the entry in |
|
Summary of segment access constants indicating access operations performed on the segment |
98.4.10 SET_HEAT_MAP_START Procedure
This procedure sets the start date for collecting heat map data.
Syntax
DBMS_ILM_ADMIN.SET_HEAT_MAP_START ( start_date IN DATE);
Parameters
Table 98-7 SET_HEAT_MAP_START Procedure Parameters
Parameter | Description |
---|---|
|
Indicates the new date from which all statistics are valid |
98.4.11 SET_HEAT_MAP_TABLE Procedure
This procedure updates or inserts a row for the specified table or segment.
Syntax
DBMS_ILM_ADMIN.SET_HEAT_MAP_TABLE ( owner IN VARCHAR2, tablename IN VARCHAR2, partition IN VARCHAR2 DEFAULT '', access_date IN DATE DEFAULT NULL, segment_access_summary IN NUMBER DEFAULT NULL);
Parameters
Table 98-8 SET_HEAT_MAP_TABLE Procedure Parameters
Parameter | Description |
---|---|
|
Table owner |
|
Table name |
|
Name of the subobject, defaults to |
|
Date for the entry in |
|
Summary of segment access constants indicating access operations performed on the segment |