Search Results dbms_repcat_fla




Overview
Explore in AI Chat

Overview

SYS.DBMS_REPCAT_FLA is an Oracle-supplied PL/SQL package that forms part of the internal replication infrastructure underlying Oracle Advanced Replication, which is embedded within the E-Business Suite database tier. In Oracle EBS 12.1.1 and 12.2.2, the DBMS_REPCAT family of packages supports multi-master and materialized-view replication of application data across distributed database nodes, most notably in deployments that use Multi-Org architectures spanning multiple instances or data centers. DBMS_REPCAT_FLA is not a public, externally documented API; it is an internal helper package whose name reflects the "FLA" (flavor/parallel propagation support) layer of the replication catalog management subsystem. Within EBS, its role is to assist the higher-level replication administration packages in managing the metadata that describes replicated objects, their propagation settings, and the associated deferred transaction queues. The package is owned by SYS and is marked VALID in the ETRM repository for both 12.1.1 and 12.2.2, confirming that it is present, compiled, and usable in a standard installation.

Key Procedures and Functions

The ETRM documentation for this object lists no publicly documented procedures or functions. The package is classified as OTHER, indicating that it is an internal implementation package rather than a supported application programming interface. No callable signatures are exposed in the metadata, and Oracle does not publish a parameter list for DBMS_REPCAT_FLA.

Functionally, DBMS_REPCAT_FLA operates as an internal service layer consumed by the broader replication administration packages. Its documented dependencies show that it references SYS.DBMS_REPCAT_DECL and the STANDARD package, and that it is referenced by a substantial set of sibling packages, including DBMS_REPCAT_DEFINER, DBMS_REPCAT_FLA_MAS, DBMS_REPCAT_MAS, DBMS_REPCAT_RQ, DBMS_REPCAT_SNA_INTERNAL, DBMS_REPCAT_SNA_UTL, DBMS_REPCAT_UTL, DBMS_REPCAT_UTL3, and DBMS_REPCAT_UTL4. This dependency graph places DBMS_REPCAT_FLA among the lower-level utility packages that support replication catalog maintenance, deferred remote procedure call handling, and snapshot administration. Practically, its routines are invoked indirectly when replication groups, replicated objects, or propagation configurations are created, altered, or refreshed by administrative procedures in the parent packages.

Tables Accessed

The ETRM metadata records no tables accessed via APPS synonyms, which is expected for a SYS-owned replication utility. Packages of this type work against the Oracle replication catalog views and tables owned by SYS, such as those underlying DBA_REPCAT, DBA_REPCAT_OBJECT, DBA_REPCAT_REFRESH_TEMPLATES, and the deferred transaction queue tables that support asynchronous propagation. In the EBS context, these catalogs describe which application objects—typically base tables and their triggers, indexes, and supporting sequences—participate in a replication group, how changes are propagated between masters, and how conflicts are resolved. DBMS_REPCAT_FLA reads and maintains this metadata on behalf of the parent replication packages rather than touching business data directly. Because no APPS-synonym tables are referenced, the package does not intersect with the Oracle EBS application schema objects recorded in ETRM.

Usage Notes

DBMS_REPCAT_FLA is an internal package and is not intended for direct invocation from Oracle EBS forms, concurrent programs, or custom code. No Oracle EBS form or concurrent program documented in ETRM references it as a called API. It is executed implicitly when an administrator or a scheduled job invokes higher-level replication procedures such as those in DBMS_REPCAT, DBMS_REPCAT_ADMIN, or DBMS_REPCAT_INSTANTIATE. Customizations and third-party tools should always target the documented public replication APIs rather than DBMS_REPCAT_FLA, since Oracle may change internal package behavior between releases and patches without notice. Support and troubleshooting of this package fall under standard database replication administration rather than EBS application support. Its presence and VALID status in both 12.1.1 and 12.2.2 confirm that the replication infrastructure remains a standard component of the EBS database tier, though many modern deployments no longer rely on Advanced Replication and instead use Data Guard or third-party replication technologies.