Search Results dbms_repcat_rpc




Overview
Explore in AI Chat

Overview

SYS.DBMS_REPCAT_RPC is an Oracle-supplied PL/SQL package body owned by the SYS schema. It forms part of Oracle's symmetric replication infrastructure, specifically the advanced replication management API commonly known as DBMS_REPCAT. In the context of Oracle E-Business Suite 12.1.1 and 12.2.2, this package supports the internal remote procedure call (RPC) mechanism by which replication administration commands are transported and executed across participating master and materialized view sites.

Advanced replication allows a multi-site EBS deployment to keep designated schema objects synchronized across databases. Administrative operations such as adding master groups, generating replication support, refreshing snapshots, and quiescing replication activity are issued at one site and must be applied consistently at others. DBMS_REPCAT_RPC provides the internal plumbing that directs these operations between nodes, complementing the user-facing entry points exposed through DBMS_REPCAT and its subordinate packages.

The object carries a status of VALID in the ETRM documentation, indicating that it is successfully compiled and available within the database. Its classification as OTHER in the EBS API taxonomy reflects that it is an internal support package rather than a documented, customer-callable interface.

Key Procedures and Functions

The ETRM documentation records no publicly documented procedures or functions for DBMS_REPCAT_RPC. This is consistent with its role as an internal package body whose subprograms are invoked indirectly by higher-level replication APIs rather than directly by developers or administrators. The absence of a published signature list means that no parameter-level detail is available or endorsed for external use.

Functionally, the package is understood to dispatch replication administration requests to remote sites and to coordinate the execution of those requests through the DBMS_REPCAT family of packages. Because these entry points are undocumented and subject to change between releases, they should be treated as internal implementation elements and not as supported integration points.

Tables Accessed

The dependency listing identifies REPCAT$_REPSCHEMA as a referenced object. REPCAT$_REPSCHEMA is a core replication dictionary table that records the schemas participating in a replication group. Access to this table enables DBMS_REPCAT_RPC to resolve which schemas and sites are involved when propagating replication administrative activity.

The package additionally depends on the SYSTEM schema and on a broad set of sibling packages, including DBMS_REPCAT, DBMS_REPCAT_UTL, DBMS_REPCAT_UTL2, DBMS_REPCAT_UTL3, DBMS_REPCAT_UTL4, DBMS_REPCAT_ADD_MASTER, DBMS_REPCAT_MAS, DBMS_REPCAT_DECL, DBMS_REPCAT_OBJ_UTL, DBMS_REPCAT_RPC_UTL, DBMS_REPCAT_FLA_UTL, and DBMS_REPCAT_VALIDATE. Supporting dependencies include DBMS_ASSERT, DBMS_LOB, DBMS_SQL, DBMS_DEFER_SYS_PART1, DBMS_LOGREP_UTIL, DBMS_STREAMS_ADM_UTL, DBMS_SYS_ERROR, DBMS_SYS_SQL, and STANDARD. These references confirm that the package participates in deferred transaction handling, LOB manipulation, dynamic SQL generation, and Streams-based replication utilities.

Usage Notes

DBMS_REPCAT_RPC is not intended for direct invocation by EBS developers or administrators. It is called internally during replication configuration and maintenance operations, typically triggered when DBMS_REPCAT procedures execute at a master or materialized view site. The documentation states that the package is not referenced by any database object while simultaneously being referenced by seven other packages, underscoring its role as a callee within the replication stack.

In EBS environments, replication activity is generally limited and controlled, since EBS relies primarily on a single primary database with optional read-only reporting or disaster recovery configurations. Where Advanced Replication is deployed, administrators should use the documented DBMS_REPCAT interfaces rather than call DBMS_REPCAT_RPC directly. Customizations that reference internal packages of this kind risk breakage during patching or upgrade between 12.1.1 and 12.2.2, because internal signatures are neither published nor guaranteed to remain stable.

For troubleshooting, DBMS_REPCAT_RPC appears in dependency chains rather than in explicit calls. When replication does not behave as expected, validation should focus on the documented DBMS_REPCAT entry points, the replication dictionary objects such as REPCAT$_REPSCHEMA, and the deferred transaction queue, treating this package as supporting infrastructure rather than a configurable component.