Replication Agent Failure

Troubleshoot Replication Agent failure.

• Verifying that a Primary Database Object Is Marked for Replication
  In a Sybase transaction replication system, both Replication Agent and Replication Server allow you to select the objects that you want to replicate. You do not need to replicate all objects or all data-changing operations in the primary database.
• Checking the Current Replication Agent Status
  The status of the Replication Agent instance indicates whether it is in Replicating state or in Admin state.
• Primary Database Log Access
  Replication Agent may fail if it cannot read the primary database log.
• Replication Agent Logs
  The Replication Agent system log files contain warning and error messages, as well as information about the Replication Agent connections to the primary database and the primary Replication Server.
• Using ra_statistics to Check Replication Agent Operations and Performance
  The ra_statistics command returns activity-related statistics that you can use to evaluate Replication Agent operations and performance.
• Available Memory
  Diagnose and troubleshoot memory shortages.
• Debugging LTL
  LTL (Log Transfer Language) is the syntax used to communicate or distribute replication data to Replication Server.
• Skipped DDL Commands
  If you move the truncation point to the end of the primary database transaction log with the ra_locator move_truncpt command, you have skipped over DDL commands that may have been read by Replication Agent to keep the RASD synchronized with the primary database.
• JVM Thread Dump
  A thread dump contains information about active threads in the Replication Agent JVM and can therefore be useful in troubleshooting a Replication Agent deadlock or performance issue.