CDR27 warning message in a transaction for a 2 way replication table
Posted on behalf of a customer:
When we DELETE/INSERT a record with the same PK in a transaction for a 2 way
replication table we always get a CDR27 warning message, while this never
happens for 1 way replication tables.
Please can any Informix Replication guru kindly advise me how to be able to
stop this CDR27 message generated.
The 2 way replication table is defined as follows:
cdr define repl -iFTAR -C timestamp -S row r_rtmdcone \\
"P regress4@crtr4_grp:informix.rtmdcone" \\
"select * from rtmdcone" \\
"P v4uat@webuat_grp:informix.rtmdcone" \\
"select * from rtmdcone"
In the program the transaction is written as:
BEGIN WORK;
delete from rtmdcone where .... PK = X;
insert into rtmdcone (PK, ... ) values (X, ....);COMMIT WORK
This will generate the CDR27 message after the transaction is done.
This technique is used in far too many places to replace. Is it possible to
silence this message using some configuration or perhaps a conflict
resolution procedure?
Could we get the actual error message that they are seeing. I don't know
what CDR27 is.
Thanks
M.P.
"Andrew Hamm" <ahamm@mail.com> wrote in message
news:bunngb$juusi$1@ID-79573.news.uni-berlin.de...
> Posted on behalf of a customer:
>
> When we DELETE/INSERT a record with the same PK in a transaction for a 2
way
> replication table we always get a CDR27 warning message, while this never
> happens for 1 way replication tables.
>
> Please can any Informix Replication guru kindly advise me how to be able
to
> stop this CDR27 message generated.
>
> The 2 way replication table is defined as follows:
>
> cdr define repl -iFTAR -C timestamp -S row r_rtmdcone \\
> "P regress4@crtr4_grp:informix.rtmdcone" \\
> "select * from rtmdcone" \\
> "P v4uat@webuat_grp:informix.rtmdcone" \\
> "select * from rtmdcone"
>
> In the program the transaction is written as:
>
> BEGIN WORK;
> delete from rtmdcone where .... PK = X;
> insert into rtmdcone (PK, ... ) values (X, ....);> COMMIT WORK
>
> This will generate the CDR27 message after the transaction is done.
>
> This technique is used in far too many places to replace. Is it possible
to
> silence this message using some configuration or perhaps a conflict
> resolution procedure?
>
>