Truncating the log of the primary database may lead to these types of inconsistencies:
Orphaned transactions can cause the stable queues to fill.
Inbound queue requires more disk space.
Parts of transactions, or entire transactions, may be missing, causing inconsistent data at replicate sites. See Chapter 19, “Replication System Recovery,” in the Replication Server Administration Guide for more information.
Subscription commands may be lost, disrupting the materialization or dematerialization protocol and requiring manual cleanup.
If a log is truncated while a route is being created, subscription commands against the RSSD may be lost. As a result, the route cannot be created. If this occurs, drop and re-create the route.
For more information about how to recover lost transactions, see Chapter 19, “Replication System Recovery,” in the Replication Server Administration Guide.
