Determining the Reason the Inbound Queue is Not Being Updated

Learn to determine the reason for unupdated inbound queue.

1. Verify the Replication Server connection Replication Agent User thread status.
   You can issue an admin who command in the primary Replication Server to review the status of the Replication Agent User thread for the Replication Server database connection in question.

   • If there is no Replication Agent User thread for the connection, the connection was not created with the with log transfer on clause. You can alter the Replication Server database connection to turn log transfer processing on, if needed.

   • If the Replication Agent User thread status is down, the Replication Agent is not actively connected to the Replication Server. A down status is typical for Replication Agents that connect to Replication Server only when there is work to be sent, and then disconnect after a period of inactivity.

2. Verify that the expected Replication Agent is executing.

   Verify that the expected Replication Agent is active, and that the values of the Replication Agent rs_source_ds and rs_source_db configuration parameters match the desired Replication Server connection name.

   Refer to the appropriate Replication Agent documentation for other tests to validate that the Replication Agent is executing.

3. Verify that the expected table or procedure is marked for replication.

   Replication Agent documentation describes the Replication Agent commands you can use to check replication status.

   Replication Agent provides for separate enabling of replication, in addition to marking. In this case, make sure the marked object is also enabled for replication.

4. Verify that the Replication Agent is scanning new records.

   If the database object is marked for replication, the log scanning process of the Replication Agent should record that additional information is being scanned.

   To verify that new records are being scanned:

   • Start tracing in the Replication Agent.

   • Update or execute a primary database object that has been marked for replication.

   • Verify that scanning occurs.

   Refer to the appropriate Replication Agent documentation to determine the trace flags you can use to validate the scanning process.