truncation

Warning! For UDB, Replication Agent silently deletes the UDB primary database log files. For Oracle, Replication Agent deletes the archived log files that it no longer needs. For more information, see the Replication Agent Primary Database Guide.

Default

locator_update

Values

command – 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.

interval – Replication Agent automatically truncates the transaction log when determined by a configurable interval of time.

locator_update – Replication Agent automatically truncates the transaction log 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 is automatically truncated when Replication Agent receives a new LTM Locator from the primary Replication Server.

Comments

Note: For Oracle and UDB, truncation of the archive log files that Replication Agent no longer needs from the pdb_archive_path directory is performed only if the pdb_archive_remove parameter is true.

Regardless of the value of the truncation_type parameter, you can truncate the Replication Agent transaction log 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.
Replication Agent receives a new LTM Locator based on the values of the lti_update_trunc_point parameter.