Use this procedure to determine the specific subscription and columns that are failing to replicate. This procedure also checks to see if the primary and destination data servers and primary or destination Replication Server are running.
Identifying data that is failing to replicate
To find out which data in a suspect subscription is failing to replicate, use isql to log in to the primary or destination Replication Server and run rs_subcmp.
rs_subcmp logs in to the primary and destination data servers and compares the subscription’s data in the primary and destination tables. rs_subcmp can compare tables at Adaptive Server data servers only. To compare tables at a non-Adaptive Server data server, you can use a program equivalent to bcp out on the non-Adaptive Server data server and bcp out on the Adaptive Server data servers, and compare the output using the UNIX diff command
If rs_subcmp successfully displays inconsistent rows, note the columns and rows that are not being replicated.
If no data exists for subscribed columns, then the subscription has not materialized. Go to “Materialization”.
If you cannot log in to a Replication Server, then that Replication Server is down. Go to “Replication Server is down”.
If rs_subcmp fails, then one or both of the data servers are down:
If the primary data server is down, the Adaptive Server log may be corrupt or full. The data server may also have an operating system or hardware error. See Chapter 9, “Adaptive Server Log Problems”, for more information about troubleshooting these problems.
If the destination data server is down, then the data server may have a DSI problem, or an operating system or hardware error. See Chapter 8, “Data Server Interface Problems”.
Use rs_subcmp to check if other subscriptions on the same data server are replicating:
If no other subscriptions are replicating, it is likely that a problem exists with that data server and not with a particular subscription.
If all other subscriptions are replicating, then a problem may exist with that particular subscription.
Use rs_subcmp to check if other subscriptions on databases controlled by the same destination Replication Server are replicating. If replication is working for other databases controlled by the destination Replication Server, then the problem is a specific database, database connection, or RepAgent. Take the following actions:
Look for orphaned transactions in the primary Replication Server inbound queue for the database. See Chapter 9, “Adaptive Server Log Problems”.
Troubleshoot RepAgents. See Chapter 7, “RepAgent Problems”.
Troubleshoot database connections. See Chapter 8, “Data Server Interface Problems”.
Once you have identified the data that is failing to replicate, go to the next procedure.
