Incorrect login or permissions, data server errors, or Replication Server errors can cause the Data Server Interface (DSI) to suspend or shut down.
If a subscription problem causes the DSI thread for the replicate database to terminate abnormally, you can restart the thread using the resume connection command. If possible, fix whatever condition caused the problem before resuming the connection. For example, if the maintenance user does not have update permission on the replicate table, first grant the user update permission, then resume the connection.
If you cannot fix the problem, resuming the connection causes the DSI thread to reexecute the command that failed, and suspends the DSI again. To prevent this cycle, assign a different action to the error returned to the DSI. You must assign error actions at the Replication Server where the error class is created. For information about error actions and classes, see Replication Server Administration Guide Volume 2.