Search Results dbms_streams_rpc




Overview
Explore in AI Chat

Overview

SYS.DBMS_STREAMS_RPC is a wrapped Oracle-supplied PL/SQL package body that forms part of the Oracle Streams Replication infrastructure. In the context of Oracle E-Business Suite 12.1.1 and 12.2.2, this package serves as the remote procedure call (RPC) layer that allows an Oracle Streams capture process, propagation job, or apply process to invoke Streams administrative operations on a remote database through a database link. Rather than executing Streams management logic directly against the local instance, the local Streams components call DBMS_STREAMS_RPC entries, which forward the request to the corresponding entry point in DBMS_STREAMS_ADM (or related packages such as DBMS_CAPTURE_ADM, DBMS_PROPAGATION_ADM, and DBMS_APPLY_ADM) on the target database.

The ETRM record classifies this object under owner SYS with an API classification of OTHER, confirming that it is not an EBS application-owned API but rather a core database component that EBS inherits from the underlying RDBMS release. Its wrapped (obfuscated) body, indicated by the wrapped declaration and the encoded token block in the source, is consistent with Oracle's standard practice of protecting internal replication logic from modification.

Key Procedures and Functions

The ETRM metadata for this object lists zero documented procedures or functions, and the package body is shipped wrapped, so individual subprogram signatures are not exposed through standard EBS documentation. What is known from the object's role is that its entry points mirror the remote-enabled operations of the Streams administrative packages. Each subprogram is designed to be executed when the local session is connected to one database while the actual Streams object being administered resides on another, reached via a database link.

  • Capture-related RPC entries that support creation, alteration, and management of capture processes on a remote instance.
  • Propagation-related RPC entries that manage propagation jobs and queue-to-queue forwarding between databases.
  • Apply-related RPC entries that administer apply processes and their associated rules and handlers on a remote target.
  • Rule and rule-set RPC entries that create or modify Streams rules used for subsetting and transformation.

Because the body is wrapped and the ETRM record documents no callable interface, no parameter lists are asserted here. Consumers should treat the package as an internal implementation dependency rather than a directly coded API.

Tables Accessed

The ETRM metadata does not enumerate any tables referenced through APPS synonyms for this package, which is expected given that it operates in the SYS schema and against Streams data dictionary views rather than EBS application tables. In normal operation the package interacts with Streams metadata structures such as DBA_CAPTURE, DBA_PROPAGATION, DBA_APPLY, DBA_STREAMS_RULES, and the underlying SYS-owned queue and rule tables. In an EBS deployment these objects support the replication topology used for reporting databases, data guard-style distribution, or custom information-sharing integrations rather than the core transactional schema.

Usage Notes

DBMS_STREAMS_RPC is invoked indirectly. Application users, EBS forms, and concurrent programs do not call it directly; instead, Streams background processes and the higher-level administrative packages invoke it automatically whenever a Streams operation must cross a database link. In EBS 12.1.1 and 12.2.2 environments, this occurs only when Streams-based replication has been configured, which is not part of the standard EBS installation. The ETRM record notes that the package is referenced by eight other packages, reflecting its role as a shared dependency for the Streams component stack.

From an EBS administration perspective, the practical implications are limited. The package should not be modified, and any error surfaced from it during patching or cloning typically indicates a mismatch or corruption in the underlying SYS-owned Streams objects rather than an EBS application defect. Remediation normally consists of re-running the appropriate catproc or component scripts for the database release, or reinstalling the Streams option, rather than altering the wrapped body. Because the object is owned by SYS and is not part of the APPS schema, it falls outside the standard EBS customization and extension boundaries.