Informational, warning, thread-terminated, fatal, and internal error messages from Replication Server are recorded in the Replication Server error log.
Messages are appended to the error log while Replication Server is operating. Error messages are appended to the end of the existing error log each time you restart Replication Server.
Informational messages report the current status of a component; for example, a process or command has completed or a component has been shut down. Warning, thread-terminated, fatal, and internal error messages are reported when a component abnormally terminates, a process or command cannot be completed, or a fatal internal error occurs in a component.
When Adaptive Server errors cause a Replication Server error, you find references to the Adaptive Server errors in the text of the Replication Server error message. In these cases, you may fix the Adaptive Server problem, which should eliminate the Replication Server error.
The Replication Server error log may also contain Open Client/Server™ error messages, since Replication Server is an Open Server program with Open Client components. Any Open Server errors in the error log constitute internal errors.
Replication Server error logs contain error messages generated during the execution of asynchronous commands, such as create subscription and create route. When you are executing asynchronous commands, pay special attention to the error logs for the Replication Servers affected by the asynchronous command.
Dedicate a terminal window to show the standard error output from a Replication Server. If the Replication Server error log is unavailable, error messages are sent to stderr. Error messages that are sent only to stderr are extremely serious, because the only action available to the Replication Server is to dump the stack and exit.
rs_name.logwhere rs_name is the Replication Server name.