Search Results dbms_offline_snapshot_internal




Overview
Explore in AI Chat

Overview

SYS.DBMS_OFFLINE_SNAPSHOT_INTERNAL is an Oracle-supplied, SYS-owned PL/SQL package that functions as the internal implementation layer for offline instantiation of materialized views (snapshots) in a distributed replication environment. In the context of Oracle E-Business Suite 12.1.1 and 12.2.2, this package is part of the Oracle database kernel infrastructure shipped with the RDBMS rather than an EBS application-tier object. It is present in the EBS database because EBS deployments rely on Advanced Replication and materialized view technology for distributed configurations, read-only reporting instances, and data propagation between tiered environments. The package is registered in ETRM with a status of VALID and an API classification of OTHER, confirming it is documented as system infrastructure rather than a callable public EBS API.

The package exposes no documented public procedures or functions in the ETRM metadata (0 total). Its role is strictly internal: it supports the user-facing DBMS_OFFLINE_SNAPSHOT package by encapsulating the low-level operations required to instantiate a snapshot at a remote site without requiring a direct network connection to the master site at creation time.

Key Procedures and Functions

ETRM documents zero public procedures or functions for DBMS_OFFLINE_SNAPSHOT_INTERNAL. This is consistent with its designation as an internal helper package. The documented metadata shows only the package specification and package body entries, with no individually listed callable units. Accordingly, no parameter lists are documented and none should be assumed.

The package's behavior is inferred from its dependency graph and naming. It is referenced directly by SYS.DBMS_OFFLINE_SNAPSHOT, meaning the public offline snapshot routines delegate their internal processing to this package. It also references itself, indicating internal recursive or helper call patterns within the package body. The absence of published entry points reinforces that the package is not intended for direct invocation by EBS developers, concurrent programs, or forms.

Tables Accessed

The ETRM metadata records no tables referenced via APPS synonyms for this package. This is expected, since the package operates entirely within the SYS schema and works against Oracle replication data dictionary objects — such as the SYS-owned snapshot and replication catalog tables that track materialized view definitions, refresh groups, and instantiation state — rather than against EBS application tables in the APPS schema. Because no APPS-synonym table access is documented, the package has no direct impact on EBS business data or transactional tables. Any data movement it performs relates to replication metadata and the physical creation of snapshot segments at the target site.

Usage Notes

DBMS_OFFLINE_SNAPSHOT_INTERNAL is not invoked directly. It is reached only indirectly when the public DBMS_OFFLINE_SNAPSHOT package executes its offline instantiation routines, which in turn are used to create and populate snapshots from an offline image. In EBS environments, this functionality may be exercised during the setup or cloning of distributed reporting instances, during disaster-recovery or data-propagation configurations, and during database-level replication maintenance windows.

The documented dependency list — DBMS_DB_VERSION, STANDARD, and SYS_STUB_FOR_PURITY_ANALYSIS — confirms standard Oracle kernel dependencies: version-awareness, core PL/SQL runtime support, and purity-analysis stubbing for wrapped system code. Because the package is SYS-owned and Oracle Proprietary, it must never be modified, and EBS developers should treat any reference to it as read-only diagnostic information. It is referenced by exactly one other package, DBMS_OFFLINE_SNAPSHOT, confirming a narrow, single-consumer design. For EBS 12.1.1 and 12.2.2 alike, the object remains a VALID kernel component whose relevance is limited to replication and snapshot administration performed at the database layer, outside the scope of standard EBS application customization.