Configures transaction log truncation behavior of the Sybase Replication Agent.
WARNING! For UDB, the Replication Agent deletes the UDB primary database log files that it no longer needs. For more information, see the Sybase Replication Agent Primary Database Guide.
interval (for Oracle: locator_update)
command – Sybase Replication Agent truncates the transaction log only when the pdb_truncate_xlog command is invoked.
When the value of the truncation_type parameter is command, the only way you can truncate the transaction log is by invoking the pdb_truncate_xlog command. No automatic truncation takes place when the value of the truncation_type parameter is command.
locator_update – Sybase Replication Agent truncates the transaction log automatically whenever it receives a new LTM Locator value from the primary Replication Server.
When the value of the truncation_type parameter is locator_update, the transaction log will be truncated automatically when Sybase Replication Agent receives a new LTM Locator from the primary Replication Server.
For Oracle, Truncation of the old archive log files
from the pdb archival path directory is performed only if the pdb_archive_remove property
is true.
Regardless of the value of the truncation_type parameter, the Sybase Replication Agent transaction log can be truncated manually at any time by invoking the pdb_truncate_xlog command.
If the value of the truncation_interval parameter is 0 (zero) and the value of the truncation_type parameter is interval (the default values for both parameters), automatic truncation is disabled.
Sybase Replication Agent receives a new LTM Locator based on the values of the lti_update_trunc_point property.
See the pdb_archive_path, pdb_archive_remove, and truncation_interval configuration properties.
