Re: CDR27 warning message in a transaction for a 2 way replication table
There's a CDR:27 buried in here...
Source server is 7.31.FD1A, and the target is 7.31.UC6
TXH Source ID:0 / Name:*UNKNOWN* / CommitTime:
TXH Target ID:8 / Name:webuat_grp / ReceiveTime:04-01-19 12:13:15
----------
RRH Row:1 / Collection Id: 524371 / Replicate Id: 524371 / Table:
v4uat@informix.rtmdcond / DbOp:Delete
RRH CDR:27 (Warning: Local delete row has been reinserted on local server) /
SQL:0 / ISAM:0
LRS 8 (webuat_grp)|1074474794 (04/01/19 12:13:14)
LRD 1|Partners|913606|Tomcat 1.8kg Blox||1.8000000000000000|KG|PL|25.96|Y|
RRS 8 (webuat_grp)|1074474794 (04/01/19 12:13:14)
RRD 1|Partners|913606|Tomcat 1.8kg Blox||1.8000000000000000|KG|PL|25.96|Y|
==========
TXH Transaction committed
TXH Total number of rows in transaction:1
replicant (once again) is:
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"
and the program is doing
begin work;
delete from rtmdcone where PK = X;
insert into rtmdcone (PK, ...) values (X, ....); commit work;
which is unavoidable, so they'd prefer to silence this warning without
losing all other warnings (ie by just blocking the RIS file)
I have a vague feeling this was touched upon in the course and the doco, but
I've not used ER for over two years so I'm not going to remember in a
hurry....
thanks in advance
ok -
These are not errors, but warnings. It is indicating that a row that has
been deleted has been re-inserted.
When this type of transaction occurs, we can not map the prior image of the
row with the after image because it does not have the same rowid. So even
though the delete and insert happens within the same transaction, we can not
record it as an update.
We've recently made a minor change to allow these types of warnings to not
be issued. Check out bug #164187 for more information about this.
(This is not really a bug, but a feature request since it is requesting a
change in the documented behavior. However, we track these types of
requests as though it is a bug.)
M.P.
"Andrew Hamm" <ahamm@mail.com> wrote in message
news:bups19$l0s9p$1@ID-79573.news.uni-berlin.de...
> There's a CDR:27 buried in here...
>
> Source server is 7.31.FD1A, and the target is 7.31.UC6
>
> TXH Source ID:0 / Name:*UNKNOWN* / CommitTime:
> TXH Target ID:8 / Name:webuat_grp / ReceiveTime:04-01-19 12:13:15
> ----------
> RRH Row:1 / Collection Id: 524371 / Replicate Id: 524371 / Table:
> v4uat@informix.rtmdcond / DbOp:Delete
> RRH CDR:27 (Warning: Local delete row has been reinserted on local server)
/
> SQL:0 / ISAM:0
> LRS 8 (webuat_grp)|1074474794 (04/01/19 12:13:14)
> LRD 1|Partners|913606|Tomcat 1.8kg Blox||1.8000000000000000|KG|PL|25.96|Y|
> RRS 8 (webuat_grp)|1074474794 (04/01/19 12:13:14)
> RRD 1|Partners|913606|Tomcat 1.8kg Blox||1.8000000000000000|KG|PL|25.96|Y|
> ==========
> TXH Transaction committed
> TXH Total number of rows in transaction:1
>
> replicant (once again) is:
>
> 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"
>
> and the program is doing
>
> begin work;
> delete from rtmdcone where PK = X;
> insert into rtmdcone (PK, ...) values (X, ....);> commit work;
>
> which is unavoidable, so they'd prefer to silence this warning without
> losing all other warnings (ie by just blocking the RIS file)
>
> I have a vague feeling this was touched upon in the course and the doco,
but
> I've not used ER for over two years so I'm not going to remember in a
> hurry....
>
> thanks in advance
>
>