Search Results dbms_repcat_mig_internal




Overview
Explore in AI Chat

Overview

SYS.DBMS_REPCAT_MIG_INTERNAL is an Oracle-supplied PL/SQL package body that forms part of the internal migration infrastructure of the Oracle Advanced Replication facility. Within Oracle E-Business Suite 12.1.1 and 12.2.2, this package supports the process by which replication metadata, deferred transaction queues, and multi-master object definitions are converted or upgraded between replication catalog versions. It is a private, undocumented companion to the public DBMS_REPCAT API, exposed in the SYS schema and marked VALID in the documented environment.

The package is not an application-facing API. It is invoked internally during replication catalog upgrades, territorial migration, and the transformation of legacy replication groups into their current catalog representation. Its presence in the ETRM dependency inventory confirms that the object is a permanent component of the shipped database tier, not a customer artifact, and that any EBS database at the documented release level will contain it.

Key Procedures and Functions

The documented metadata for this package body records no publicly listed procedures or functions. The package is classified under the generic API category OTHER, meaning Oracle does not publish a supported call interface, parameter list, or return specification for it. This is consistent with the INTERNAL suffix, which by Oracle naming convention designates implementation-only code that may change without notice between patch sets and database releases.

From its dependency footprint, the package operates as a coordination layer rather than a service endpoint. It relies on DBMS_REPCAT, DBMS_REPCAT_UTL, DBMS_REPCAT_UTL3, DBMS_REPCAT_DECL, and DBMS_REPCAT_FLA_UTL for catalog manipulation and flavor handling; on DBMS_DEFER_SYS and DBMS_DEFER_INTERNAL_SYS for deferred transaction queue management; on DBMS_REPUTIL and DBMS_SNAPSHOT for replication state and snapshot administration; and on DBMS_SQL, DBMS_ASSERT, UTL_RAW, and DBMS_SYSTEM for dynamic SQL, identifier validation, raw data conversion, and session control. These dependencies indicate a migration utility that reads catalog state, constructs dynamic DDL/DML, and writes the converted result back into the replication dictionary.

Tables Accessed

The package reads and writes the core replication dictionary tables: REPCAT$_REPCAT, REPCAT$_REPOBJECT, REPCAT$_REPCOLUMN, REPCAT$_REPGROUP_PRIVS, REPCAT$_REPPROP, REPCAT$_REPPROP_KEY, REPCAT$_REPSCHEMA, REPCAT$_GENERATED, REPCAT$_GROUPED_COLUMN, and REPCAT$_PARAMETER_COLUMN. These hold replication groups, replicated objects, column-level definitions, propagation attributes, and generated objects, and constitute the primary data the migration must transform.

It also references the deferred queue objects DEF$_DESTINATION, DEF$_PROPAGATOR, and HIST_HEAD$, along with MLOG$ materialized view logs, SNAP$ and SNAP-related snapshot metadata, and the core data dictionary views DBA_CONSTRAINTS, DBA_INDEXES, DBA_OBJECTS, and DBA_CONSTRAINTS-adjacent dictionary bases such as COL$, COLTYPE$, OBJ$, TAB$, USER$, and DUAL. These are consulted to validate object state, resolve column and constraint definitions, and confirm that replicated objects remain consistent after the migration transformations are applied.

Usage Notes

DBMS_REPCAT_MIG_INTERNAL is not invoked from Oracle EBS forms, concurrent programs, or documented public APIs. It executes as a nested dependency of higher-level replication administration and upgrade routines, particularly during patch application and database upgrade operations that touch the replication catalog. EBS administrators do not call it directly, and it exposes no supported signature for custom code.

Because the package is owned by SYS and marked as internal, it must be treated as read-only infrastructure. Granting EXECUTE on it, modifying it, or relying on its behavior from custom PL/SQL is unsupported and can break subsequent patch cycles that expect the shipped definition. It is not referenced by any other database object in the documented metadata, though the dependent package inventory lists one package that references it, confirming it sits at the leaves of the replication code hierarchy. Any error raised from this package during an upgrade should be diagnosed against the replication catalog and the dependent DBMS_REPCAT family, not against the internal body itself.