Note
Using Log Server Agent for Oracle is Optional.
Overview
The Log Server Agent option is available in situations when the standard Log Reader replication can not be applicable.
This alternative creates a Windows service on the system running the Server Agent that makes only a single connection to the database to read the binary log for all replications in a source connection. The service autonomously reads the native database transaction log and writes all changes from the tables being replicated into intermediate binary log files (a Syniti proprietary format) in a specified folder. The Replication Agent reads the changes from the intermediate binary log files.
As mentioned in the How Syniti Replicate uses the Redo Logs in Oracle article, Syniti recommends to keep the log retention for a minimum of 72hrs. In situations when the retention time must be less than 72hrs, the Log Server Agent could be an option.
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.
Log Files Folder
An existing folder where all the intermediate binary logs files are written. The folder is also used to contain trace files.
Prefix
A prefix for all files created in the folder. This provides easy identification and management of files associated with your connection. The primary purpose for the prefix is to support the case when you configure more than one connection to use the same folder. In general, however, it is advisable to use different folders for different connections.
Log File Size
The maximum size of each binary log file in megabytes.
Keep Max Files
The maximum number of binary log files to keep. Combined with the log file size, this number needs to be large enough to make sure that all the files are read by Syniti Replicate before they get deleted.
Trace
Unchecked by default. When checked, enables tracing for diagnostics and problem reporting. Trace files are saved in the Log Server folder.
Windows Service Name
Prefix:
This value is provided and cannot be changed It allows you to easily identify the service in the Microsoft Windows Services tool.
Name:
Specify a unique name for the Windows service. Each connection runs its own instance of the Syniti Replicate Log Server as a Windows service.
Start service after completing the wizard: When checked, starts the service automatically after you click Finish to complete the wizard.
Start, Stop, Reset (appears only when managing the service via the Manage Transactional Log Settings dialog)
The Service can be started and stopped here or in the Windows Services tool. If stopped and then re-started, the Log Server resumes reading the database’s binary log from the point where it was stopped.
If the database or binary log is reset, or if the Log Server has been stopped for too long and the database’s binary logs are no longer available, first stop the service, then click Reset to reset the binary log position to where the Log Server can read again. The log position is reset to the current position in the database. Also reset the last transaction ID for all replications, or run a refresh replication to make sure they are up to date.