Oracle Change Log Settings Dialog

The Oracle Change Log Settings dialog can be used 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

  • Set up a remote log server

Server

Specifies the Oracle data source where the log is stored. If you are using the multitenant database architecture introduced in Oracle 12, and connecting to a pluggable database, you need to modify the log location to match the Oracle root, or container, database.

User

User ID for the Oracle data source where the log is stored.

Password

Password for the Oracle data source where the log is stored.

Use Log Server for Remote Mining

Check this option to

Dictionary

Dictionary File

If the log is stored as a dictionary file (typically only for Oracle versions up to 9), type the path and file name for an Oracle dictionary file. The Oracle dictionary file should already be defined in your Oracle environment. See Setup for Different Oracle Versions for more information.

 Read Archived Logs

When checked, Syniti Replicate accesses Oracle archived redo logs for transactions in addition to the online redo logs. Check with your Oracle system administrator to see if your database is configured to use ARCHIVELOG mode. If it is, you can check the Read Archived Logs option to ensure that all transactions between mirroring intervals are identified by Syniti Replicate. For example, if your mirroring interval is set for 90 seconds, but within that time the online logs fill with transactions, the online logs are archived as needed to accommodate additional transactions. If you check the Read Archived Logs option, Syniti Replicate will be able to locate the last transaction ID from the archived log. Note that the Read Archived Logs option is not useful when using the default setting on Oracle databases, NOARCHIVELOG mode.

Use CONTINUOUS_MINE Option
When ReadArchivedLogs is checked, the Use CONTINUOUS_MINE Option is checked by default. The CONTINUOUS_MINE option instructs the Oracle log reader to load archived log files continuously as they get created, instead of loading a batch of files statically when the log reader is initially instantiated. Syniti Replicate can therefore replicate transactions as they are backed up. however, Oracle recommends that the CONTINUOUS_MINE option should not be used in a RAC (Real Application Cluster) environment where RAC nodes are continuously enabled/disabled.

Destination ID
This option allows you to set the location from which Syniti Replicate will pick up Oracle archived logs for replication. When the value is set to the default, 0, Syniti Replicate searches for Oracle archived logs in the standard destination, ('FLASH RECOVERY AREA (FRA)'). A value between 1 and 31 specifies an alternative location to retrieve archived logs. Oracle users can retrieve a list of all archive locations by running the query: SELECT * FROM V$ARCHIVE_DEST.

This feature is useful when your environment includes a customized archive setup and you want to instruct Syniti Replicate to use a specific location for archived logs.

Opening the Change Log Settings Dialog

From the Manage Transactional Log Settings dialog, click ... to the right of the Log Settings field.