Oracle Transactional Replication Settings

Enable Transactional Replication wizard or the Manage Transactional Log Settings dialog

The information below explains how to configure the transactional replication settings for Oraclein the Enable Transactional Replication wizard or the Manage Transactional Log Settings dialog available from the Transactional Setup > Manage option on the connection in the Metadata Explorer.

When replicating from Oracle using mirroring or synchronization, three transactional modes are available: Log Reader, Log Server Agent and Triggers.

Log Reader Settings

Log Settings

The Log Settings field displays the Oracle data source where the log is stored. This field is read-only and by default matches the data source specified in the source connection. If you are using the multitenant database architecture introduced in Oracle 12, and connecting to a pluggable database, you may need to modify the log location to match the Oracle root, or container, database. To modify the log location, click the [...] button.

Click [...] to open the Change Log Settings dialog to:

Change the Oracle server where the log is stored (for Oracle 12 multitenant database installations).
Set a path to an Oracle dictionary file (primarily for Oracle versions up to 9)
Change the archived log settings

Supplemental Log Minimal Level/Supplemental Log Database Level

These fields are inactive until you have clicked Verify to check what type of supplemental logging is currently set for your Oracle source connection. For transactional replications where Oracle is a source database, Syniti DR requires supplemental logging to be enabled at least at the minimal level (and later at the table level) to record sufficient information about changes to the data in the table.

Click Verify to determine which type of logging is currently set. If you want to make changes to the current setting:

Choose Minimal Level to establish minimal supplemental logging at the database level, then, during replication setup, add logging for the specific table(s) involved in the replication.

Choose Database Level to establish supplemental logging for the entire database, including primary key and index information for all tables. If you have a large number of tables in your database, and they are not involved in Syniti DR replications, you should be aware that supplemental logging can add unnecessary processing time/log information.

Click Install to make changes to the supplemental log settings.

Verify (appears only in the Transactional Log Settings dialog)

Click Verify to see if supplemental logging has been set up either at the database level or at the minimal level. Syniti DR requires supplemental logging to be set at minimum at the table level for the table(s) involved in replication.

If supplemental logging has not been established, or you wish to make changes, select the type of logging then click Install to set it. To later remove the log settings from the server, use the Disable Transactional Replication wizard available from the Transactional Setup > Disable option on the connection in the Metadata Explorer.

Oracle-Specific Log Server Agent Settings

Use Log Container

If your data source is an Oracle version 12 pluggable non-root database, you also need to complete the root database connection information:

Server, User, Password

The connection string for the root database. This is required because Oracle 12 does not keep redo log records for the entire database instance separately.

Use Remote LSA

This option is available for environments where it is preferable to read the Oracle log directly and involves the installation and configuration of an additional component on the Oracle server. Contact the support team via the Help Center for additional information.