You could skip the error (enter the error number in the -SkipErrors section
of the distribution agent's profile) but is that really wise? I'd try to find
out why this has occurred. The dataon the subscriber is treated as read only,
and this has somehow been violated. Perhaps this is only one of several
instances like this, and you'll end up with a corrupt view of data at the
subscriber if you skip the error. In your instance I'd skil the error then
use DataCompare from Redgate to try to reconcile the data. It might turn out
easier to reinitialize, but the Redgate tool will give you an idea of the
size of the problem.
HTH,
Paul Ibison (www.replicationanswers.com)
"Iter" wrote:
> In addition, I found there is issue in subscription, that is The row was not
> found at the Subscriber when applying the replicated command. (Source:
> MSSQLServer, Error number: 20598), how to get rid of this error? thanks
>
>
> "Iter" wrote:
>
> > Hi ,
> > I checked replication in replication monitor, and there 700 command waiting
> > for transfering to subscriber in distributor, how to check which command
> > waiting for transfering to subscriber in distributor? thanks >> Stay informed about: how to check which command waiting for transfering to subs..