Replication Server passes messages to data servers and other Replication Servers while they are accessible and queues messages when connections are down. Using Sybase Central, you can monitor the status of the replication system and troubleshoot problems as they arise.
Normally, short-term failures of networks and data servers do not require special error handling or intervention. When the failure is corrected, replication system components resume their work automatically. Lengthier failures may require intervention if there is not enough disk space to queue up messages or if it is necessary to reconfigure the replication system to work around the failure.
Failures of some system components, such as Replication Server partitions or primary databases, also require user intervention. Refer to Chapter 7, “Replication System Recovery” for more information about recovery procedures.
A Replication Server response to errors depends on the kind of error, source of the error, and how the Replication Server is configured. Replication Server handles errors in these ways:
Logs errors in its error log file.
Responds to data server errors based on configuration settings.
If transactions fail to commit in a database, writes the transactions to the exceptions log for manual resolution.
Detects duplicate transactions after system restart.
