Adaptive Server log corruption can cause failures anywhere along the replication path. The most common symptoms are:
RepAgent or LTM shuts down when it reads log data it cannot process.
The RepAgent or LTM shutting down is the most common symptom of a corrupt Adaptive Server log. In addition, the error log may reveal error messages that are inconsistent with the current operation; however, no specific log corruption error message is displayed.
Adaptive Server shuts down. The LTM logscan thread, which reads the Adaptive Server log, terminates when it reads corrupted log data.
A component of the Replication Server (such as the DSI) shuts down.
When the RepAgent or LTM passes incorrect data to the Replication Server, Replication Server components, such as the DSI, may shut down. For instance, if the DSI encounters a mismatched data type and fails to resolve the differences, it shuts down.
Replicated data appears out of sync.
The procedures for determining log corruption and where the corruption occurs is complex. It requires knowledge of the log format as well as Adaptive Server and Replication Server internal components.
If you suspect Adaptive Server log corruption, contact
Sybase Technical Support to help you diagnose and resolve the issue.
