A correctly configured Replication Server® system is designed to be fault-tolerant. However, in the event of a serious failure, you may need to intervene and manually fix the problem.
Identifying recent tasks or events that might have adversely affected the replication system. A user may have performed a task that caused a replication failure or reduced the performance of the replication system. Many things can happen when a number of people are working on the same replication system.
An event such as a temporary network outage may also have caused a replication system problem.
Analyzing error logs.
Determining the general problem category (configuration, subscription, replication, recovery).
Using diagnostic tools, such as Replication Server programs or stored procedures, or isql, to analyze the replication system.
If you see an error message in a Replication Server error log, you can identify the problem by reading the error log. If there is no error message, use diagnostic tools to further analyze the replication system.
Replication Manager (RM) and the Embedded Replication Server System Database (ERSSD) problems are not included in the Replication Server Troubleshooting Guide. RM uses the Sybase Central™ message logging feature to provide a log of all commands sent by the RM to any server. It also has a view queue data feature that helps you troubleshoot transactions in a queue. See the online help for the Replication Manager plug-in and the Replication Server Administration Guide Volume 1 for more information on how to use these features. See also the Replication Server Administration Guide Volume 1 for more information on ERSSD recovery procedure.
The Replication Server Troubleshooting Guide may be able to help you to identify hardware, network, and operating system problems, but solving these problems is beyond the scope of the guide. Any time a server or a network connection is down, you should also check for hardware, network, or operating system problems.
On Windows, you can usually see a hardware or operating system problem when stack traces randomly or frequently occur at the same time you get errors in the Replication Server error log.
Check the operating system error log for errors that indicate hardware or operating system problems. Such failures might only partially resolve the effects on the replication system. You may still need to resynchronize data between the primary and destination databases.