When a transaction submitted by Replication Server fails, Replication Server records the transaction in the exceptions log in the RSSD. The replication system administrator at the site must resolve the transactions in the exceptions log. See “Accessing the exceptions log”.
Transactions can fail due to errors such as duplicate keys, column value checks, and insufficient disk space. They may also be rejected for reasons such as insufficient permissions, version control conflicts, and invalid object references.
Because skipping a transaction causes inconsistency and can have an adverse affect on the system, you should review on a regular basis any transactions that have been recorded in the exceptions log and resolve them. The best resolution for a transaction may depend on the client application that originated it. For example, if a failed transaction corresponds to a real-world event, such as a cash withdrawal, the transaction must somehow be applied.
Refer to the Replication Server Troubleshooting Guide for more information on the implications of skipping a transaction.
