Transaction Log Truncation

The Replication Agents for Oracle, Microsoft SQL Server, and UDB support both automatic and manual truncation of the transaction log.

You can enable or disable automatic log truncation at any time, and you can truncate the Replication Agent transaction log manually at any time, with automatic log truncation either enabled or disabled.

Note: Depending on the type of database and the Replication Agent configuration, Replication Agent truncates either the database online logs or archive logs. Sybase recommends that you configure Replication Agent to truncate the database archive logs. See the Replication Agent Primary Database Guide for details.

When the Replication Agent truncates its transaction log, either automatically or on demand (manually), the truncation point is determined by the most recent LTM Locator received from the primary Replication Server.

Automatic Truncation

You have two options for automatic transaction log truncation:

  • Automatic truncation each time the Replication Agent receives a new LTM Locator value from the primary Replication Server

  • Periodic truncation on a time interval you specify

When Replication Agent truncates its transaction log, either automatically or manually, the truncation point is determined by the most recent LTM Locator received from the primary Replication Server.

Parent topic: Replication Agent Management