September 4, 2008 at 11:10 pm
A subscription is failing validation (checksum).
I deleted and recreated publication.
Recreated the subscriptions with initialization.
Still it is failing validation.
What could be the reason? How to resolve it?
Any help in this matter will be highly appreciated.
Note: Replication is working. New rows are being replicated to the subscriber.
There are other replications between the same publisher and subscriber. They are passing validation.
October 6, 2008 at 10:36 pm
This is telling you that some data within tables is failing validation, meaning that at least one table has data in it which is different between the Publisher and Subscriber. This could be due to a conflict, and this is the first place I would look
The results of the validation exercise should tell you which table(s) this is occuring in, so step 1 is to check this against any possible conflicts, and resolve these conflicts where necessary, and then re-validate the subscription
If it is not a conflict, and if it is a only a small number of tables affected, you can use tablediff to create a script file that will essentially contain all of the updates, which should be the differences between one table and the other. You can then view this script file to see what and how many of those changes there are
The tablediff utility, to my knowledge, can only be run on a single table at a time though so if there are a lot of tables affected, you probably need a different solution
October 7, 2008 at 2:33 am
Thanks Adrian for replying.
This issue has been resolved. It was happening due to difference in the UDDTs in the publisher and subscriber.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply