Handling repositioning in the log

When the value of the LTM locator received from Replication Server and the LTM locator stored by Replication Agent are both zero (0), the Replication Agent positions the Log Reader component at the end of the DB2 Universal Database transaction log.

WARNING! In the event that both LTM locator values are zero, there is a remote possibility of data loss. Two specific conditions could cause this data loss:

Repositioning the Log Reader at the end of the transaction log may cause data loss if there are replicated transactions that have not been processed at the time the Log Reader is repositioned.
When the Replication Agent Log Reader component goes to the Replicating state, it does so asynchronously. When you receive a prompt after invoking the resume command, the Log Reader component may not be finished getting into the Replicating state and positioning itself at the end of the log. If you mark a table immediately after the prompt returns from the resume command, it is possible that the record containing the mark information will be written to the log before the Log Reader component has positioned itself. In that case, the Log Reader component will miss that record and not replicate any subsequent data for that table. To avoid this problem, you should wait a short time after invoking the resume command before marking a table for replication.

When the value of the LTM locator received from Replication Server and the LTM locator stored by Replication Agent are both not zero, Replication Agent uses the LTM locator value it received from Replication Server to determine the starting position of the oldest open transaction and positions the Log Reader component at that location in the DB2 Universal Database transaction log.

When the value of the LTM locator received from Replication Server is zero (0) and the value of the LTM locator stored by Replication Agent is not zero, Replication Agent uses the LTM locator value it has stored to determine the starting position of the oldest open transaction and positions the Log Reader component at that location in the DB2 Universal Database transaction log.