To improve secondary truncation point management in a multipath replication environment, set the frequency of truncation point request intervals for Adaptive Server RepAgent.
In a multipath replication environment with a single scanner, the distribution of data in the primary Adaptive Server database log might be uneven, because some replication paths may not receive data as frequently as other paths. Therefore, truncation point requests are infrequent if RepAgent bases the requests on specifying the maximum number of log records to send to Replication Server in each batch. As a result, the secondary truncation point is moved only as often as the replication path with the least transaction volume. No matter how many commands are replicated on the first path, truncation does not occur until the minimum number of commands has also been processed by the second path. If the truncation point moves slowly, or not at all, the Adaptive Server transaction log grows until the log can be truncated.
See Secondary Truncation Point Management in the Replication Server Administration Guide Volume 1.