Replication failures may occur after subscriptions have successfully materialized. This section documents procedures you can use to isolate replication failures.
These procedures assume that the replication system has:
Been installed and configured correctly,
Successfully completed subscription materialization, and
Correctly replicated data previously
If you are having installation and configuration problems, see the Replication Server Configuration Guide for your platform. If you are having subscription problems, see “Troubleshooting subscription failures”.
Before you troubleshoot a replication failure, verify that data is not replicating:
Use isql to log in to the primary and replicate databases.
Execute select commands that select the replicate columns from the replicate table and the columns to be replicated from the primary table.
Compare the data from both tables to see if it is the same.
If the subscription has many columns that are replicated,
use rs_subcmp to compare data in the
primary and replicate databases. See “Identify the data that is failing to replicate”.
After you have verified that data is not replicating, use the procedures and diagnostic tools in the rest of this section to investigate and identify the exact cause of your problem. These procedures can be executed separately and in any order; however, they are listed in the order in which they are most likely to solve the problem:
When you think you have solved the problem, run the replication system. If replication is still not executing correctly:
Analyze errors (see “Analyzing error logs”), or
Complete any of this section’s procedures that you skipped.
