Finding Failed Replication Component

To determine the component on which replication has stopped, turn on traces and examine the output of sysadmin dump_queue.

  1. Specify trace flags when you run the diagnostic versions of the Replication Server (repserver.diag).
  2. Run sysadmin dump_queue and examine its output.
    If replication stopped in one of the components, determine the cause of failure and rectify the problem.

    Component

    Troubleshooting Reference

    Primary data server

    • Replication Server Troubleshooting Guide > Data Server Interface Problems
    • Replication Server Troubleshooting Guide > Adaptive Server Log Problems

    RepAgent

    Replication Server Troubleshooting Guide > RepAgent Problems

    Primary data server

    • Replication Server Troubleshooting Guide > Data Server Interface Problems
    • Replication Server Troubleshooting Guide > Adaptive Server Log Problems

    Outbound queue

    • Replication Server Troubleshooting Guide > Route Problems
    • Replication Server Troubleshooting Guide > Data Server Interface Problems

    Data Server Interface (DSI) thread

    Replication Server Troubleshooting Guide > Data Server Interface Problems

    Custom function-string class or customized function strings

    • Replication Server Troubleshooting Guide > Data Server Interface Problems
    • Replication Server Troubleshooting Guide > Stable Queues > Using Traces to Print Commands
Related concepts
Data Server Interface Problems
Adaptive Server Log Problems
RepAgent Problems
Related tasks
Using Traces to Print Commands
Related reference
Route Problems