Truncates the Replication Agent transaction log on demand.
Sybase Replication Agent does not support log truncation for DB2 Universal
Database.
pdb_truncate_xlog
When pdb_truncate_xlog is invoked, Replication Agent immediately truncates the transaction log based on the most recent truncation point received from the primary Replication Server. The truncation point is part of the information contained in the LTM Locator.
To update the LTM Locator from the primary Replication Server, use the ra_locator command.
The pdb_truncate_xlog command is asynchronous and it does not return success or failure (unless an immediate error occurs). You must examine the Replication Agent system log to determine success or failure of the pdb_truncate_xlog command.
You can use the ra_statistics command to view the “Number of transactions truncated,” both before and after you use the pdb_truncate_xlog command.
If the Replication Agent transaction log does not exist or if a connection failure occurs, the pdb_truncate_xlog command returns an error message.
You can use the ra_config command to specify the type of automatic truncation you want. You can use the pdb_truncate_xlog command to truncate the transaction log if automatic truncation is not sufficient to manage the size of the transaction log.
The pdb_truncate_xlog command is valid when the Replication Agent instance is in either Admin or Replicating state.
pdb_xlog, ra_config, ra_locator
