The number of maintenance operations or unmarked table references that can be skipped before requesting a new truncation point from the primary Replication Server.
1000
An integer in the range of 1 to 10000.
The lr_update_trunc_point configuration parameter is provided to allow logged operations that are not replicated (maintenance user operations and references to unmarked tables) to be truncated from the transaction log.
The value of the lr_update_trunc_point parameter is the number of maintenance operations or unmarked table references that the Log Reader component can process before the Replication Agent instance requests a new truncation point (LTM Locator) from the primary Replication Server.
If the value of the truncation_type parameter is locator_update, setting the value of the lr_update_trunc_point parameter to a lower number will cause automatic log truncation to occur more frequently.
If the value of the lr_update_trunc_point parameter is 0 (zero), Replication Agent does not request a new truncation point when processing maintenance operations or unmarked table references.
When Replication Agent processes transactions for replication, it automatically requests a new truncation point from the primary Replication Server based on the value of the lti_update_trunc_point parameter.
When Replication Agent processes maintenance operations or unmarked table references, and the value of the filter_maint_userid parameter is true, Replication Agent does not send LTL to the primary Replication Server for those operations, and the automatic request for a new truncation point based on the value of the lti_update_trunc_point parameter never takes place.
The lr_update_trunc_point parameter allows Replication Agent to periodically request a new truncation point from the primary Replication Server, even when no LTL output is sent. This provides faster recovery by ensuring that Replication Agent has a current value for the LTM Locator.
