Search Results dbms_streams_auth




Overview

SYS.DBMS_STREAMS_AUTH is a PL/SQL package owned by the SYS schema and shipped as part of the Oracle Database server kernel rather than as an E-Business Suite application object. Within the Oracle EBS 12.1.1 and 12.2.2 technical stack it serves a single, narrowly scoped administrative purpose: it manages the privileges that enable a database user to act as a Streams or XStream capture, propagation, or apply process. In an EBS environment this package is most closely associated with the configuration of Oracle Streams-based data replication, Advanced Queuing propagation between EBS instances, and the Oracle GoldenGate/XStream capture infrastructure that some EBS customers deploy for reporting or disaster-recovery replicas. The package does not contain any EBS business logic, does not operate on EBS application tables, and is not invoked by standard EBS concurrent programs or forms. Its presence in the ETRM dependency inventory reflects the fact that EBS technology-stack components (notably DBMS_XSTREAM_AUTH) depend on it, and therefore it appears in dependency reports generated against the EBS schema stack.

Key Procedures and Functions

The documented interface exposes four procedures. Each is an administrative grant/revoke operation and none should be called against an EBS schema owner such as APPS without deliberate planning.

  • GRANT_ADMIN_PRIVILEGE — Grants the Streams administrator role and the associated system and object privileges to a specified database user, enabling that user to create and manage capture, propagation, and apply processes.
  • REVOKE_ADMIN_PRIVILEGE — Revokes the Streams administrator privileges previously granted to a user, returning the account to a non-administrative state for replication purposes.
  • GRANT_REMOTE_ADMIN_ACCESS — Grants a user the ability to administer Streams components on a remote database from the local instance, supporting distributed replication topologies.
  • REVOKE_REMOTE_ADMIN_ACCESS — Removes the remote administration capability granted by the corresponding grant procedure.

The package also depends on the SYS.STANDARD package, and is in turn referenced by DBMS_XSTREAM_AUTH, which is the higher-level API normally used in modern EBS-adjacent replication setups.

Tables Accessed

The ETRM documentation records no table access for this package via APPS synonyms. This is expected: DBMS_STREAMS_AUTH operates almost entirely against data dictionary views and internal SYS-managed tables that track Streams administrator configuration and privileges. Because no EBS application tables are read or written, the package poses no risk to EBS data integrity or to the integrity of the APPS schema, although the privileges it grants can indirectly expose application data to a replication administrator.

Usage Notes

In EBS 12.1.1 and 12.2.2 this package is invoked from SQL*Plus or another privileged session by a DBA running as SYSDBA or as a user with the necessary SYS grants. It is not called from EBS Forms, OAF pages, or standard concurrent programs. Typical scenarios include initial setup of a Streams-based logical standby or reporting replica of an EBS database, configuration of Advanced Queuing propagation between two EBS instances, and preparation of a database user for XStream capture in support of GoldenGate-based replication. Because DBMS_STREAMS_AUTH is referenced by DBMS_XSTREAM_AUTH, DBAs using the newer XStream API will trigger this package indirectly. Any use in an EBS environment should be coordinated with the EBS patching and cloning strategy, since the grants and any replication processes created can interfere with AutoConfig, adclone, and the standard EBS backup/restore procedures. The package should remain VALID at all times; if it becomes INVALID, the standard remedy is to recompile it as SYS or to re-run the database catalog scripts.