|
Hello, I am not sure if anybody had this kind of situation before. Last week, for no reason, our Sql Server went down. And from then on, the replication process( which was working fine before) is totally messed up. I do replication from Sql Server to IBM As400. Now during the replication process, I get a duplicate record error. This is my view after checking all the possibilities, Let say in the replication process, there was change in the existing record. The replication does the following steps. a.) delete the existing record in the As400. b.) commit. c.) insert the new record to as400. d.) commit. The only way i can get a dupicate record error if step b is being skipped. I don't know if this is bug in sql server or am i missing something. Please advice. Thanks. Gade. +--- | This is the RPG/400 Mailing List! | To submit a new message, send your mail to RPG400-L@midrange.com. | To subscribe to this list send email to RPG400-L-SUB@midrange.com. | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.