Replication Agent permissions

Replication Agent for Oracle uses the pds_username to connect to Oracle and must have the following Oracle permissions:

NoteThe permissions for SYS.CON$ and SYS.CDEF$ are required to handle the constraint information in the CREATE and ALTER TABLE DDL operations.

In addition, the user who starts the Replication Agent for Oracle instance must have read access to the Oracle redo log files and the Oracle archive directory that contains the archive log files to be accessed for replication. If the Replication Agent is configured to remove old archive files, the user must have update authority to the directory and the archive log files. If Oracle redo logs or archived redo logs are stored within ASM, the user who starts Replication Agent for Oracle must have read access to the ASM disk devices that contain the redo log data.

Replication Agent for Oracle requires the alter system privilege to issue the alter system archive log command. If Replication Agent is configured to access only online Oracle redo logs, Replication Agent issues the alter system archive log sequence command when the online redo log is no longer needed for replication (as when all data from the log has been replicated). Regardless of online or archive log processing, Replication Agent uses the alter system privilege to issue the alter system archive log current command when Replication Agent is instructed to move processing to the end of the Oracle log. By issuing the alter system archive log current command, Replication Agent insures that the current redo log file does not contain old data. Replication Agent moves processing to the end of the Oracle redo log when requested by the move_truncpt options of the pdb_xlog init command. Replication Agent may also move processing to the end of the Oracle redo log during migration from one version of Replication Agent to another.