Primary Oracle Database Configuration for Replication

Configure the primary Oracle database for replication and to ensure that the Oracle redo log data is not overwritten before it is read by Replication Agent.

In addition to Oracle LogMiner, you can now alternatively configure the Replication Agent for Oracle Log Reader component to use Oracle XStream APIs to read from the transaction logs. The XStream APIs enable you to share data changes between Oracle and non-Oracle data sources, such as SAP Replication Server.

Note: You can configure the Replication Agent for Oracle Log Reader component to use XStream APIs from version 15.7.1 SP120 and later.

Verifying the Current Archive Setting of the Redo Logs
Verify that redo logging, which Oracle uses to maintain a log infrastructure, is turned on in the primary database.
Verifying the Supplemental Logging of Primary Key Data
By default, Oracle does not log primary keys and unique indexes. For successful replication of all table values, you must log these values.
Configuring Oracle LogMiner
Configure Oracle LogMiner on the primary Oracle database.
Setting Up an Oracle XStream JDBC Driver
To use the Replication Agent for Oracle with XStream APIs, use the setenv function to set or modify ORACLE_HOME, LD_LIBRARY_PATH, and CLASSPATH environment variables.
Creating Oracle User and Grant Permissions
Create an Oracle database user for use by Replication Agent when connected to the primary database.
Verifying the Oracle User Roles Created by the Replication Agent
Validate the required Oracle settings.

Parent topic: Configuring Replication Agent