The DSI applies transactions from a Replication Server stable queue to a data server, which can be an Adaptive Server or another data server with an interface to the Replication Server. Before a transaction is applied, Replication Server uses function strings to convert the commands to the format specified for the data server.
If the data server is not receiving updates, the DSI may be suspended or down. A down or suspended DSI can be caused by:
Incorrect login or permissions
A data server error
A Replication Server error
A suspended DSI always results in an error message being sent to the Replication Server error log. You can analyze this error message to solve the problem. After correcting the error, restart the DSI.
If the DSI is active, unique transactions might be incorrectly resolved as duplicates, or the transactions might be failing on the data server. You must manually resolve the data inconsistency between the primary and replicate databases or reapply the transactions.
To determine the exact cause of the problem, use a select command, admin who, and admin who, dsi.
These problems also apply to parallel DSI threads. For
more information specific to parallel DSI threads, see Replication
Server Administration Guide Volume 2.
