Mirror Replication Agent for Oracle uses the pds_username to connect to Oracle and must have the following Oracle permissions:
create session – required to connect to Oracle.
select_catalog_role – required to select from the DBA_* views.
alter system – required to perform redo log archive operations.
execute on DBMS_FLASHBACK – required to execute DBMS_FLASHBACK.get_system_change_number.
alter any procedure – required to manage procedures for replication.
create table – required to create tables in the primary database.
create procedure – required to create rs_marker and rs_dump proc procedures.
create public synonym – required to create synonyms for created tables in the primary database.
create sequence – required to support replication.
drop public synonym – required to drop created synonyms.
select on SYS.OBJ$ – required to process procedure DDL commands.
select on SYS.LOB$ – required to support LOB replication.
select on SYS.COLLECTION$ – required to support table replication.
select on SYS.COL$ – required to support table replication.
select on SYS.COLTYPE$ – required to support table replication.
select on SYS.CON$ – required to support table replication.
select on SYS.CDEF$ – required to support replication.
select on SYS.IND$ – required to support index identification.
select on SYS.USER$ – required to support replication.
select on SYS.SEQ$ – required to support sequence replication.
In addition, the user who starts Mirror Replication Agent for Oracle instance must have read access to mirror copies of the Oracle redo log files and the archive directory that contains the archive log files to be accessed for replication. If Mirror Replication Agent is configured to remove old archive files, the user must have update authority to the directory and the archive log files. If the redo logs or archived redo logs are stored within Automatic Storage Management (ASM), the user who starts Mirror Replication Agent for Oracle must have read access to the ASM disk devices that contain the redo log data.
