Use admin who_is_down to determine if the primary and destination Replication Server threads are up.
This command displays all the threads on this Replication Server that are down. If any threads are down, an error message should have been displayed in the Replication Server error log.
The Data Server Interface (DSI) is down,
The RepAgent is not connected to the Replication Server or Adaptive Server, and
The entire (or part of the) network went down and was restarted.
If the conditions exist, the keepalive value is set too low and the TCP connection was terminated and never restarted.
If a thread is down, determine the cause of the failure and correct the problem.
Thread That Failed |
Action |
---|---|
Distributor (DIST) |
Determine if the failure is due to Replication Server error 7035 or 13045, and correct the problem. |
DSI |
See Replication Server Troubleshooting Guide > Data Server Interface Problems. Possible problem is duplicate keys or permission failure. |
DSI EXEC |
See Replication Server Troubleshooting Guide > Data Server Interface Problems. |
RepAgent User |
See Replication Server Troubleshooting Guide > RepAgent Problems. |
Replication Server (RS) User |
See Replication Server Troubleshooting Guide > Subscriptions Problems. |
Replication Server Interface (RSI) and RSI User |
See Replication Server Troubleshooting Guide > Replication Server Interface Problems. |
Stable Queue Manager (SQM) |
The SQM should not go down. Restart the Replication Server; you cannot resume the SQM thread. |
Stable Queue Thread (SQT) |
Determine if the failure is due to Replication Server error 13045, and correct the problem. |
User |
This should have no effect on replication. |