January 20, 2007 at 11:57 pm
Hi ,
During some project implementation we kept log reader disabled and re-initialize the subscription and run the snapshot and all worked fine but when we enabled the log reader agent so all pending transaction flow down and distribution agent failed for error
The row was not found at the Subscriber when applying the replicated command
Replication monitor reflect that it is calling
CALL sp_MSdel_TBLHistoryDetail (4549254) ,Here TBLHistoryDetail is my table and 4549254 is TBLHistoryDetailid.
but there is no record in publisher also with this ID ,so what could be the issue and how it can be fixed the only solution i am thinking to re-sync but as data is too huge so any other suggetion will be highly appretiated.
Thanks
January 21, 2007 at 1:18 am
Some one deleted the data from subscriber directly... In one way transactional replication you have to delete the data at publisher...
In your case some one deleted the data at subscriber and then deleted the database at publisher...Delete at publisher deleted the data so that you don't see that at publisher and MS replication trying to delete the data at subscriber and it did not find the row...
To resolve the solution make sure no one is deleting the data at subscriber...
You have to reinsert the deleted data at subscriber...or
You have to reinitialize the publication ..or
if you don't want to reinitialize then you can use -SKIPERRORS parameter...
Use the "-SkipErrors" parameter in Distribution Agent cautiously
http://support.microsoft.com/kb/327817
MohammedU
Microsoft SQL Server MVP
January 22, 2007 at 9:39 am
Thanks much Mohammed Uddin it really helps.
January 22, 2007 at 9:45 am
Might also consider changing permissions on the subscriber so that users can't delete records there.
January 22, 2007 at 7:04 pm
I Agree Andy, better to change permissions...
MohammedU
Microsoft SQL Server MVP
Viewing 5 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply