Data server errors, such as permission violations or duplicate keys, are logged in the Replication Server error log.
If you cannot correct the data server error, restart the Data Server Interface (DSI) by requesting that the first transaction (the one causing the error) be skipped. Do this by executing the resume connection command with the skip transaction option.
If errors are caused by unique-key violations, you can use the set autocorrection command to turn automatic error correction on, before you resume the connection. These errors are likely to occur during nonatomic materialization. For more information about the set autocorrection command, see the Replication Server Reference Manual.
As a last resort, use the skip transaction option of the resume connection command. This option skips the materializing or dematerializing transaction altogether. If the problem occurred during subscription materialization, drop the subscription and create it again in a way that avoids the same problem.