The Data Server Interface (DSI) for the replicate database may have been suspended if changes made to a primary database do not reach the replicate database that has active subscriptions.
Use this procedure to find out the cause of the problem.
- Log in to the Replication Server that controls
the replicate database.
- Execute admin who, dsi.
This
returns one entry for each database with replicated data.
- If a database does not have an entry, check the
Replication Server error log to see if the DSI for the database
was not started or was suspended. These are samples of error messages that are reported
in the Replication Server error log as a result of a DSI that did
not start or was suspended:
The DSI thread for ’RDS.rdb2’ is not started, because
the connection to the database has been suspended or
the connection has not been completed.
The DSI thread for database ’RDS.rdb2’ is being
shutdown. DSI received data server error #1105 which
is mapped to STOP_REPLICATION. See logged data
server errors for more information. The data server
error was caused by RS output command #1 mapped from
input command #1 of the failed transaction.
The DSI thread for database ’RDS.rdb2’ is shutdown.
- If there is an entry for the database, but the
state is Awaiting Command, the DSI is waiting for a transaction
from the primary. Determine why updates are not reaching this Replication Server.
- If the state of the DSI thread is Active, then:
Unique transactions might
be incorrectly resolved as duplicates, or
Transactions might be failing on the data server
and written to the exceptions log.