Skip Log Reader Errors

You may need to prevent log reader errors from stopping replication in systems that cannot afford down time during periods of high volume and high demand. You can then address skipped errors at a more convenient time.

Use the skip_lr_errors parameter to skip log record processing errors and log warning messages to the Replication Agent system log without stopping replication.

Note:

This parameter is available only for Oracle.

Default

false

Value

true – enables Replication Agent to skip log record processing errors and continue replication.

false – disables Replication Agent from skipping log record processing errors.

Comments

If you configure skip_lr_errors to true, Replication Agent logs the log record processing error encountered and also logs a warning that the error has been skipped. If the transaction ID, operation ID and locator of the log record are available at the time of the error, these are also logged. Replication Agent continues processing transaction log records.
If you configure skip_lr_errors to false, Replication Agent throws an exception, stops all replication processing, and transitions to the Replication Down state.
skip_lr_errors is intended only for troubleshooting with assistance from Sybase® Technical Support.
You can change skip_lr_errors only when Replication Agent is in the Admin or Replication Down state.

Warning! Use of this parameter does not guarantee that there will be no transaction loss, nor does it guarantee that the RASD is synchronized with the primary database when log record processing errors are skipped.