Search Results set_heat_map_start

Overview

SYS.DBMS_ILM_ADMIN is a server-side PL/SQL package owned by the SYS schema and shipped as part of the Oracle Database kernel, not as an Oracle E-Business Suite product component. Within an EBS 12.1.1 or 12.2.2 environment it is exposed to the application tier because the APPS schema holds the standard DBMS_ILM_ADMIN synonym and the underlying package is granted to PUBLIC. The package provides the administrative front end for Information Lifecycle Management (ILM), the database facility that evaluates data against user-defined policies and moves or deletes rows once they fall outside a retention window. In practice, DBMS_ILM_ADMIN is the configuration layer that supports Automatic Data Optimization: it lets an administrator enable or disable ILM processing, define and clear Heat Map collection, and tune the heat map windows that determine which EBS segments qualify as hot, warm, or cold. Because ILM decisions in EBS are frequently applied to high-volume transactional tables such as audit, interface, and temporary staging tables, the package is relevant to any purge or archiving strategy implemented on top of the 12.1.1 or 12.2.2 dataset.

Key Procedures and Functions

The ETRM catalogue records eight documented entry points, all configured as administration procedures:

• ENABLE_ILM — turns on ILM processing at the database level so that defined policies become eligible for execution.
• DISABLE_ILM — turns off ILM processing, suspending policy evaluation without dropping policy definitions.
• SET_HEAT_MAP_START — establishes the starting point or schedule from which Heat Map data collection begins.
• SET_HEAT_MAP_ALL — enables Heat Map tracking across all eligible segments for full-database heat tracking.
• CLEAR_HEAT_MAP_ALL — removes all collected Heat Map data, typically before re-baselining.
• SET_HEAT_MAP_TABLE — scopes Heat Map tracking to a specific table rather than the whole database.
• CLEAR_HEAT_MAP_TABLE — removes Heat Map data for a single table.
• CUSTOMIZE_ILM — applies non-default ILM settings, allowing the tuning of attributes and window characteristics used by the scheduler.

The package body is implemented on top of the private package PRVT_ILM, which appears in the dependency listing as the internal worker supporting the public API. The external consumer known to reference DBMS_ILM_ADMIN is that same private ILM infrastructure, confirming that the public package functions as the supported interface while PRVT_ILM performs the underlying work.

Tables Accessed

The ETRM dependency extract documents no application tables referenced through APPS synonyms for this package. Its dependencies resolve only against SYS, STANDARD, and the internal ILM implementation objects. Heat Map and ILM metadata are persisted in Oracle-owned dictionary and work area structures rather than in EBS product tables, which means no EBS application data is read or written directly by DBMS_ILM_ADMIN. Administrators should therefore treat the recorded table list as empty by contract, and any effect on EBS data occurs indirectly through policies evaluated against EBS segments.

Usage Notes

DBMS_ILM_ADMIN is not invoked by EBS forms, concurrent programs, or standard application flows. It is called manually from SQL*Plus or another privileged client using the APPS synonym, normally after DBMS_ILM policy creation has been completed. Typical usage is a one-time setup sequence: enable ILM, start and scope the Heat Map, allow a representative collection window to elapse, then review heat data and adjust with CUSTOMIZE_ILM. Because the package is owned by SYS and requires elevated privileges, changes should be coordinated with the DBA team and documented in the EBS change-management process. When troubleshooting, note that the object is internal to the database, so issues are more likely to reflect database version, licensing of the Advanced Compression or ILM option, or Heat Map configuration than EBS application code.