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 manually, the truncation point is determined by the most recent LTM Locator received from the primary Replication Server. The Replication Agent truncates not only based on the truncation point, but also keeps at least the same number of archive files as there are log groups.

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

Enabling Automatic Log Truncation
Automatically truncate the transaction log.
Disabling Automatic Log Truncation
Disable automatic truncation.
Truncating the Replication Agent Transaction Log Manually
If automatic log truncation is disabled, you must periodically truncate the Replication Agent transaction log manually.

Parent topic: Replication Agent Management