Mirror Replication Agent permissions

Mirror 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 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.

Mirror Replication Agent for Oracle requires the alter system privilege to issue the alter system archive log command. If Mirror Replication Agent is configured to access only online Oracle redo logs, Mirror 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, Mirror Replication Agent uses the alter system privilege to issue the alter system archive log current command when Mirror Replication Agent is instructed to move processing to the end of the Oracle log. By issuing the alter system archive log current command, Mirror Replication Agent insures that the current redo log file does not contain old data. Mirror 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. Mirror Replication Agent may also move processing to the end of the Oracle redo log during migration from one version of Mirror Replication Agent to another.