July 14, 2009 at 3:13 pm
We have set up a transactional replication of 3 servers: Primary, Distribution and Subscribers.
Sometimes, we find that the distributor agent fails while trying to insert the records to some of the tables and throws error msg as follows:
" Primary key vaiolation error. Unable to insert the record in the table..."
I typically noticed that it happens when there is a delay from distributor to Subscriber happens and this thing happens..
Can anyone who faces the similar issue can suggest some ways to handle this type of issues towards resolution?
How much helpful the "Trace Token" here?
Regards
Sourav
Thanks.
July 15, 2009 at 6:54 am
Are users entering data into the destination database? If so are they using the same PK (eg. identity column)?
July 15, 2009 at 2:07 pm
No, no updated are happening at Distributor end!
Thanks.
July 15, 2009 at 2:20 pm
Sourav (7/15/2009)
No, no updated are happening at Distributor end!
I think LeeM was asking about the Subscriber (destination DB).
Are the data in the replicated tables onthe subscriber side updated ONLY from your replication?
If users/apps could update the tables in your subscriber side, it may cause this PK violation error (esp. as pointed by LeeM, when the PK is an identity column).
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply