Analyzing the Replication Server Error Log

Analyze the Replication Server error log to determine the cause of the replication system failure.

To analyze a Replication Server error log, you must understand how multiple error messages are related. Multiple error messages can be generated by the same problem and usually have identical, or very close, dates and times. Error messages that occur close together constitute an error block.

  1. Scan from the end of the error log to the beginning, looking for the most recent Replication Server error. To identify the problem, find the error block to which the error belongs. As Replication Server errors occur, Replication Server appends the error messages to the end of the error log. The most recent Replication Server error marks the end of the error block.
    Note: If you see an Open Server/Client error such as no more threads, fix that error first. This message means you have run out of an Open Server resource (and Replication Server might have terminated).
  2. Find and diagnose the last non-Replication Server error message that occurred after the first Replication Server error. If there are no non-Replication Server error messages after the first Replication Server error message, investigate the causes of the first Replication Server error message. In diagnosing non–Replication Server errors, you may need to use other troubleshooting or error message guides—such as those for Adaptive Server or Open Client (particularly with network communication or other client problems).
  3. In the error block, find any Replication Server error messages that tell you if a Replication Server component or thread has terminated. You must restart the component or thread that has terminated. Usually, subsequent Replication Server errors in the same error block were caused by the first Replication Server error.
Parent topic: Error Messages and Error Logs