Error Actions for Data Server Errors

ignore

Assume that the command succeeded and that there is no error or warning condition to process. This action can be used for a return status that indicates successful execution.

warn

Log a warning message, but do not roll back the transaction or interrupt execution.

retry_log

Roll back the transaction and retry it. The number of retry attempts is set with the configure connection command. If the error continues after retrying, write the transaction into the exceptions log, and continue, executing the next transaction.

log

Roll back the current transaction and log it in the exceptions log; then continue, executing the next transaction.

retry_stop

Roll back the transaction and retry it. The number of retry attempts is set with the configure connection command. If the error recurs after retrying, suspend replication for the database.

stop_replication

Roll back the current transaction and suspend replication for the database. This is equivalent to using the suspend connection command. This action is the default.

Since this action stops all replication activity for the database, it is important to identify the data server errors that can be handled without shutting down the database connection, and assign them to another action.