Always maintain open windows for all error logs, including:
Replication Server error logs (including a window for Replication Server standard error output (stderr))
Replication Agent logs (such as Replication Agent for DB2)
Any data server error logs (such as Adaptive Server)
Any gateway error logs (such as DirectConnect™ or OmniConnect™)
Usually an error message will be displayed in one of these logs. Before checking for failures throughout your replication system, check for error messages in the error logs.
Checking for error messages in the error logs
Scan the Replication Agent, data server, and gateway error logs to see if you can immediately find an error message that describes the cause of the error. If you find an error, see the documentation for the Replication Agent, data server or gateway to solve the problem.
Check for error messages in the rs_init, Replication Server error logs following the instructions in Chapter 2, “How to Read Error Log Files.”
RepAgent error messages are displayed in the Adaptive
Server error log.
Find the error message in Chapter 3, “Common Errors.”
Apply the corresponding repair procedure.
If you cannot find the error message in Chapter 1, “Identifying the Problem”, look in one of the other chapters that corresponds to the symptoms of your problem or in one of the following error message text files in the $SYBASE/$SYBASE_REP/doc directory on UNIX platforms or the %SYBASE%\%SYBASE_REP%\doc directory on Windows. These text files contain the text of the error message, a brief description of the error, its cause, and, sometimes, how to fix it.
For Windows:
errmsg.rs for Replication Server error messages
errmsg.sub for rs_subcmp error messages
For UNIX:
error_messages_rs for Replication Server error messages
error_messages_subcmp for rs_subcmp error messages
