You can tell that the Replication Server inbound queue for a primary database is not being updated if you issue the Replication Server admin who,sqm command at the primary Replication Server and the results indicate the following:
The number of blocks being written in the Replication Server inbound queue for the connection in question is not changing.
The number of duplicate messages being detected is not increasing.
To determine the reason the inbound queue is not
being updated
Verify the Replication Server connection Rep Agent User thread status.
You can issue an admin who command in the primary Replication Server to review the status of the Rep Agent User thread for the Replication Server database connection in question.
If there is no Rep 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 Rep 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 only connect to Replication Server when there is work to be sent, and then disconnect after a period of inactivity.
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.
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.
Sybase 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.
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.
Verify that logging occurs for the primary object.
For Replication Agents that use the primary database transaction or recovery log, this check is not required.
For Replication Agents that use a trigger-based transaction log (Sybase Replication Agent for Informix and Microsoft SQL Server), validate that the log is being populated.
You can use the following procedure to validate that the Sybase Replication Agent trigger-based log is being updated:
Shut down (suspend) the Replication Agent log scanning process.
Verify that there is no other activity against marked objects.
To get a count of the current records in the transaction log, issue the following statement:
select count(*) from ra_tran_log_
where ra_ is the value of the Replication Agent pdb_xlog_prefix configuration parameter.
Update or execute a primary database object that has been marked for replication.
Issue the same select count(*) statement.
If the row count does not change, the transaction was not logged. If the row count increases, logging is occurring.
If the row count decreases, a log truncation process is executing, and you must retry the test after the truncation process is complete.
Verify that the transactions to be replicated are not being executed by the Replication Server Maintenance User.
Transactions being processed by the Maintenance User defined in the Replication Server connection for this database are typically bypassed by the Replication Agent. For some Replication Agents, bypassing Maintenance User transactions is optional.
Refer to the appropriate Replication Agent Administration Guide for details.
