Search Results add_message_rule

Overview

SYS.DBMS_STREAMS_ADM is the principal administrative package of Oracle Streams, Oracle's built-in information-sharing infrastructure for capturing, propagating, and applying database changes. In the Oracle E-Business Suite 12.1.1 and 12.2.2 environments, this package is a SYS-owned, VALID dictionary object that provides the procedural interface for building and maintaining Streams configurations. Its business role is to allow administrators and infrastructure components to define capture processes, propagation jobs, and apply processes without manually manipulating the underlying dictionary tables. The package is primarily invoked through internal EBS plumbing rather than directly by end users, but its configuration determines data movement for replication, data warehouse feeds, and the Advanced Queuing topology used by several EBS components.

Key Procedures and Functions

The documented 57 subprograms cover the full lifecycle of Streams configuration. At the top level, SET_UP_QUEUE creates the AnyData queue used as the staging point for captured changes, while REMOVE_QUEUE tears it down. Rule management is handled by ADD_TABLE_RULES, ADD_SCHEMA_RULES, ADD_GLOBAL_RULES, ADD_SUBSET_RULES, and ADD_MESSAGE_RULE, which associate capture, propagation, or apply rules with specific objects. Propagation is configured through ADD_TABLE_PROPAGATION_RULES, ADD_SCHEMA_PROPAGATION_RULES, ADD_GLOBAL_PROPAGATION_RULES, ADD_SUBSET_PROPAGATION_RULES, and ADD_MESSAGE_PROPAGATION_RULE. Rule maintenance is supported by REMOVE_RULE and SET_RULE_TRANSFORM_FUNCTION, the latter allowing column mapping or data transformation during apply. Streams splitting and merging operations are provided by SPLIT_STREAMS, MERGE_STREAMS, and MERGE_STREAMS_JOB, which redistribute capture load or consolidate configurations. Notification and cleanup are handled by SET_MESSAGE_NOTIFICATION and PURGE_SOURCE_CATALOG, while REMOVE_STREAMS_CONFIGURATION deconstructs an entire Streams setup.

Tables Accessed

The ETRM metadata records no direct table references via APPS synonyms; all persistent state is managed through the SYS-owned Streams dictionary tables (such as ALL_CAPTURE, ALL_PROPAGATION, ALL_APPLY, ALL_RULES, and the rule-set tables). These tables store capture process definitions, propagation schedules, apply handlers, and rule evaluation order. Because the package is owned by SYS and is not exposed through EBS synonym layers, direct SQL access from the APPS schema is not part of its supported interface; all interaction occurs through the package API and its internal dependencies.

Usage Notes

In EBS 12.1.1 and 12.2.2, DBMS_STREAMS_ADM is generally invoked by DBA scripts, upgrade or patching routines, and advanced configuration utilities rather than by Oracle Forms or concurrent programs directly. The package is referenced by 28 other packages, including DBMS_CAPTURE_ADM, DBMS_STREAMS, DBMS_XSTREAM_ADM, DBMS_COMPARISON, and DBMS_STREAMS_DATAPUMP, which use it as a building block. When custom replication or data-sharing code is required in an EBS instance, the Streams administrator connects as a privileged user (typically SYSDBA or a user granted DBMS_STREAMS_AUTH privileges) and calls the appropriate subprogram to define queues, rules, and propagation. Direct invocation should be treated as a privileged DBA activity, and any configuration created through this package should be validated against the EBS support matrix before production use.