Experiencing a single table / single row Transactional Replication burp (processes & source/target DB's are in sync and operational)
Details
- under our Rep Monitor Agents / Distribution Agent I see:
{CALL sp_MSins_tblMbrAssignments (2668927, 546264, 1, N'546264', 2004-12-21 00:00:00.000, 2005-12-31 00:00:00.000, 1, NULL)}
Transaction sequence number and command ID of last execution batch are 0x00008B3D00000697000100000000 and 1.
Replication is choking trying to INSERT a row into target table although this row does not exist on the source table. Where Replication is sourcing this row from I haven't a clue! There is also no data in the snapshot folder. (it can't be failing on a DUP INSERT because the row does not exist anywhere - except buried in Repl somewhere.
Otherwise, we're OK. The job is actually perpetually executing now (though the Dist Agent "RUN" step is failing w/ iterative RETRY's) All other objects across Replicated DB's are in sync & currnet.
Details
- under our Rep Monitor Agents / Distribution Agent I see:
{CALL sp_MSins_tblMbrAssignments (2668927, 546264, 1, N'546264', 2004-12-21 00:00:00.000, 2005-12-31 00:00:00.000, 1, NULL)}
Transaction sequence number and command ID of last execution batch are 0x00008B3D00000697000100000000 and 1.
Replication is choking trying to INSERT a row into target table although this row does not exist on the source table. Where Replication is sourcing this row from I haven't a clue! There is also no data in the snapshot folder. (it can't be failing on a DUP INSERT because the row does not exist anywhere - except buried in Repl somewhere.
Otherwise, we're OK. The job is actually perpetually executing now (though the Dist Agent "RUN" step is failing w/ iterative RETRY's) All other objects across Replicated DB's are in sync & currnet.