Oracle Distributed Systems

DBMS_REPCAT_AUTH: Setting Up More Administrative Accounts

DBMS_REPCAT_AUTH grants and revokes privileges to a user ID that is designated at each master site to perform replication activities on behalf of other remote masters. In effect, the existence of such a user ID eliminates the need for SYS-owned database links between master sites.

How the Package Is Used

The replication administration account and/or a DBA account uses the two procedures in DBMS_REPCAT_AUTH to grant or revoke the specified privileges.

Installation and Access

The DBMS_REPCAT_AUTH package iscreated when the Oracle database is installed. The dbmsrepc.sql script (found in the built-in packages source directory) contains the source code for this package’s specification. This script is called by catrep.sql, which must be run to install the advanced replication packages. The wrapped SQL script prvtrepc.sqlcreates the public synonym DBMS_REPCAT_AUTH. No EXECUTE privileges are granted on DBMS_REPCAT_AUTH; only the owner (SYS) and those with the EXECUTE ANY PROCEDURE system privilege may execute the package.

DBMS_REPCAT_AUTH Procedures

Procedure Name	Description
GRANT_SURROGATE_REPCAT	Grants required privileges to a specified user
REVOKE_SURROGATE_REPCAT	Revokes required privileges from a specified user

DBMS_REPCAT_AUTH Exceptions

The DBMS_REPCAT_AUTH package may raise exception ORA-01917 if the specified user does not exist.