Re: CDR Conflict Resolution
Posted in 1999
Topics: High Availability & Replication, Versions, Editions & End-of-Life
Katja, Since my last reply I have done a test trying to add a replicate with conflict=timestamp without adding crcols. The answers to your problems will be: 1) Add crcols - ALTER TABLE tablename ADD CRCOLS; 2) Here is a sample definition: cdr define replicate \\ --conflict=timestamp \\ --scope=row \\ --ats --ris r_scmtest \\ "alm@grp2:quanta.scmtest" "select \\ Regards, Stephen C Manga Email: Stephen.Manga@dbgroup.co.nz Stephen@quanta.co.nz On Tue, 3 Aug 1999 heikkka4@my-deja.com wrote: > Hello again! > > I have been setting up Enterprise Replication with CDR APIs > (IDS 7.24) and finally got it work OK (thanks to the kind > assistance of Mr. Pruet). > > Now I would like to change my conflict resolution rule > to "timestamp" and that's where the problem arises. > Our system is simple primary-target. > > To define replicates I used sample programs "define_repl" > and "participate_repl" as follows: > > 1) define_repl -c myserver1 myrepl -C "ignore" -S row -R > "P mydb@myserver1:informix.mytable" "select * from informix.mytable" > > 2) participate_repl -c myserver1 myrepl -a "R > mydb@myserver2:informix.mytable" "select * from informix.mytable" > > This works perfect as long as the conflict resolution rule is set to > "ignore". But when I change it to "timestamp" happens following: > "define_repl" command goes OK, but "participate_repl" causes error > message "CDRERR 69 Conflict mode for replicate not ignore". > (CRCOLS have been created.) > > Is it OK to use "timestamp" with primary-target configuration? > Could anybody give a hint where to start debugging? > > I would GREATLY appreciate your comment. > > Recards > > Katja Heikkinen > Abacus Solutions Inc, > Finland > > > > > > Sent via Deja.com http://www.deja.com/ > Share what you know. Learn what you don't. > >
Thank you, Steve, very much for aswering. This works perfectly after I removed references to primary-target from my replicate definition. IDS 7.24 does not seem to allow any error resolution rules ,exept "ingore", when the replication system is set to primary-target ("one-way" replication). Mr. Roach kindly told me that he had noticed the same. I wanted to set conflict resolution to "timestamp" due to the behaviour of "cascading deletes"... But it seems I just have to live with this limitation. Best recards, Katja Heikkinen, Finland In article <7oldj9$e27$1@news.xmission.com>, Stephen Manga <steve@quack16.quanta.co.nz> wrote: > > Katja, > > Since my last reply I have done a test trying to add a replicate with > conflict=timestamp without adding crcols. > > The answers to your problems will be: > > 1) Add crcols - ALTER TABLE tablename ADD CRCOLS; > 2) Here is a sample definition: > cdr define replicate \\ > --conflict=timestamp \\ > --scope=row \\ > --ats --ris r_scmtest \\ > "alm@grp2:quanta.scmtest" "select \\ > > Regards, > > Stephen C Manga > Email: Stephen.Manga@dbgroup.co.nz > Stephen@quanta.co.nz > > On Tue, 3 Aug 1999 heikkka4@my-deja.com wrote: > > > Hello again! > > > > I have been setting up Enterprise Replication with CDR APIs > > (IDS 7.24) and finally got it work OK (thanks to the kind > > assistance of Mr. Pruet). > > > > Now I would like to change my conflict resolution rule > > to "timestamp" and that's where the problem arises. > > Our system is simple primary-target. > > > > To define replicates I used sample programs "define_repl" > > and "participate_repl" as follows: > > > > 1) define_repl -c myserver1 myrepl -C "ignore" -S row -R > > "P mydb@myserver1:informix.mytable" "select * from informix.mytable" > > > > 2) participate_repl -c myserver1 myrepl -a "R > > mydb@myserver2:informix.mytable" "select * from informix.mytable" > > > > This works perfect as long as the conflict resolution rule is set to > > "ignore". But when I change it to "timestamp" happens following: > > "define_repl" command goes OK, but "participate_repl" causes error > > message "CDRERR 69 Conflict mode for replicate not ignore". > > (CRCOLS have been created.) > > > > Is it OK to use "timestamp" with primary-target configuration? > > Could anybody give a hint where to start debugging? > > > > I would GREATLY appreciate your comment. > > > > Recards > > > > Katja Heikkinen > > Abacus Solutions Inc, > > Finland > > > > > > > > > > > > Sent via Deja.com http://www.deja.com/ > > Share what you know. Learn what you don't. > > > > > > Sent via Deja.com http://www.deja.com/ Share what you know. Learn what you don't.