How Error Modes Affect Server Behavior
Server behavior differs for each propagation error mode.
Note: In the following descriptions, the “current replication transaction” is in the context of the Replicator Server, which can disagree with the original user transaction if the latter updated more than one CDDS.
Error modes and how they affect server behavior are described here:
• Skip Transaction
(Default) The Replicator Server:
– Rolls back the current replication transaction
– Processes the next transaction
– Retries the transaction in error during the next processing of the distribution queue
• Skip Row
The Replicator Server continues from the error with no rollback performed. The record in error is skipped and processing proceeds to the next record. The record in error is removed from the queue.
Note: This setting disables transaction consistency, therefore data integrity needs to be maintained manually.
• Quiet CDDS
The Replicator Server rolls back the current replication transaction. After the rollback of the transaction in error, the Replicator Server quiets the CDDS on the database where the transaction error occurred. (In this context, quiets means disabling propagation from the local database to the target database where the error occurred.)
The Replicator Server continues processing the remaining replicated transactions for the same CDDS on other databases, and for other CDDSs.
For information on reactivating the CDD, see chapter “Using the Replicator Server.”
• Quiet Database
The Replicator Server rolls back the current replication transaction. After the rollback of the transaction in error, the Replicator Server quiets all CDDSs in the database where the transaction error occurred. (In this context, quiets means disabling propagation from the local database to the target database where the error occurred.)
The Replicator Server continues processing the remaining replicated transactions for other databases.
For information on reactivating the database, see chapter “Using the Replicator Server.”
• Quiet Server
The Replicator Server:
– Rolls back the current replication transaction
– Stops processing of the remaining batch of replicated transactions
– Changes its status from active to quiet mode