If the apply was paused due to a conflict, or it is retrying in a loop the same SQL again and again, you can instruct it about what to do next using the command:
RESOLVE CONFLICT id AS resolution
The conflict id is the number shown in the status bar, the resolution can be:
- IGNORE: skip the transaction
- RETRY: try again
- ABORT: abort the apply process
- RESTART: rollback and restart the transaction
- ROLLBACK:rollbacks the transaction
- IGNOREALL:ignore all current conflicts
To see the SQL that is causing the conflict, logon to the apply (target database) as the Dbvisit Replicate schema owner (dbvrep) and query table:
DBRSAPPLY_CONFLICT_LOG
This lists all the conflicts encountered, including failing SQL.