Search Results dbms_irefresh




Overview
Explore in AI Chat

Overview

SYS.DBMS_IREFRESH is an Oracle-supplied internal package that forms part of the materialized view refresh infrastructure in the Oracle database kernel. In the context of Oracle E-Business Suite 12.1.1 and 12.2.2, this package performs the low-level coordination work required to refresh internal snapshots (materialized views) that support EBS data propagation, distributed deployments, and multi-tier synchronization. As its name suggests, DBMS_IREFRESH ("internal refresh") is the private, unadvertised counterpart to the publicly documented DBMS_REFRESH and DBMS_MVIEW packages. EBS administrators encounter it indirectly whenever refresh groups are executed, since the higher-level refresh APIs delegate much of their execution logic to this package.

The package resides in the SYS schema and is reported with a status of VALID in the ETRM repository for release 12.2.2. It is classified as an OTHER-type API, indicating that it is not part of any documented, supported EBS extension interface. Oracle marks the object as proprietary and confidential, and it should be treated strictly as internal database plumbing rather than a callable application programming interface.

Key Procedures and Functions

The ETRM metadata documents no public procedures or functions for SYS.DBMS_IREFRESH. The package specification and body are recorded in the repository, but no individually named entry points are published, and no parameter lists are captured. This is consistent with an internal package whose routines are invoked only by other SYS-owned refresh components. No signature or purpose should be assumed from external sources, because the internal callable surface is undocumented and subject to change without notice across database patch levels.

Tables Accessed

No tables referenced through APPS synonyms are documented for this package. This is expected behavior: DBMS_IREFRESH operates on dictionary and temporary structures owned by SYS rather than on EBS application tables. The actual data manipulation is performed through the underlying materialized view definitions that the caller passes into the refresh engine, not through direct APPS-schema access by this package.

Usage Notes

DBMS_IREFRESH is not invoked from Oracle EBS forms, concurrent programs, or supported customization code. It is reached only through internal delegation from the documented refresh packages. The dependency metadata confirms this relationship precisely: DBMS_IREFRESH references SYS.DBMS_UTILITY and the SQL STANDARD package, and it is itself referenced by six other SYS packages — DBMS_IREFRESH (its own package body), DBMS_ISNAPSHOT, DBMS_REFRESH, DBMS_REFRESH_EXP_LWM, DBMS_REFRESH_EXP_SITES, DBMS_SNAPSHOT, and DBMS_SYNC_REFRESH. This dependency chain demonstrates that all refresh operations in the stack funnel through this internal layer.

For EBS 12.1.1 and 12.2.2 environments, the practical guidance is straightforward. Custom code should always call DBMS_REFRESH, DBMS_SNAPSHOT, or DBMS_MVIEW — never DBMS_IREFRESH. The object should be left untouched during cloning, patching, and upgrade operations, and any invalid status observed in the data dictionary should be remediated through standard database utilities such as utlrp.sql rather than manual recompilation. Because it is proprietary and undocumented, its behavior may differ between database versions certified for 12.1.1 and 12.2.2, and it carries no EBS support commitment beyond its internal role.