Replication Agent supports both automatic and manual log truncation.
To configure Replication Agent log truncation, observe these guidelines:
All DB2 transaction logs are maintained through the data server. You can configure Replication Agent for UDB to truncate transaction logs from either the active or the archive log directory. When you have enabled DB2 archiving with LOGARCHMETH1, you can also configure a second archive location by setting the LOGARCHMETH2 DB2 configuration parameter. DB2 then archives logs into the two directories. You can then configure Replication Agent to automatically truncate the processed archives from one of these directories.
Set pdb_archive_path to point to the location specified by either LOGARCHMETH1 or LOGARCHMETH2.
Set pdb_archive_remove to true if you want Replication Agent to delete archives that are no longer necessary.
To enable automatic truncation, set truncation_type to interval, and set truncation_interval to a value greater than 0 (zero), which deletes log files at the designated interval. Alternately, set truncation_type to locator_update, which causes truncation to occur each time Replication Agent receives a new LTM locator value from the primary Replication Server.
You can truncate the Replication Agent transaction log manually, at any time, by invoking pdb_truncate_xlog at the Replication Agent administration port.
When DB2 truncate runs, the oldest LSN for which Replication Agent has not processed a commit/rollback (oldest active LSN) is obtained and the archive log file that contains the LSN is determined. All archive log files up to but not including the file with the oldest active LSN are deleted.
For more information on these properties, see the Replication Agent Reference Manual. For a more detailed description of truncating, see "Administering Replication Agent” in the Replication Agent Administration Guide.