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.
Replication Server error messages may contain references to Adaptive Server errors. By examining the causes of the Adaptive Server error, you will be able to solve the problem.
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.
Reading a Replication Server error log
Look for the most recent Replication Server error by scanning from the end to the beginning of the error log. 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. Find the first Replication Server error message in the error block.
If you see an Open Server/Client error such
as “no more threads,” fix that error first. An
Open Server error “no more threads” message means
that you have run out of an Open Server resource (and Replication Server
might have terminated)
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).
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.
