CDRTIME column with NULL value

Hi, We are using Informix ER replication in a 2 node setup. We need to periodically check if a replicated table is in sync. We do this by verifying that the count(*) and max(cdrtime) for the table matches between the 2 nodes when there is no (insert/update/delete) activity on the table. We normally expect (and observe) that the CDRTIME for a row to be the time when the row was updated/inserted. However, we are seeing that CDRTIME column is NULL in some scenarios one of which is as follows. When a row is inserted into node 1 when replication is down and then replication is setup followed by a synchronization of the rows using cdr check & repair, Informix propagates the row to node 2 but the CDRTIME for this row is NULL in node 2. Also, the CDRTIME on node 1 for this row gets updated to the time when cdr check and repair took place. Is this behavior of CDRTIME becoming NULL expected ? Is there any other efficient and accurate way of determining that a replicated table is in sync? (The Informix version used is below (output of onstat -version) Build Version: 11.50.UC5XA Build Number: N104 Build Host: ku Build OS: Linux kernel-2.6.9-34.ELsmp glibc-2.3.4-2.19 compat-glibc-2.3.2-95.30 Build Date: Wed Feb 24 19:33:04 CST 2010 GLS Version: glslib-4.50.UC6) Thanks Sridhar

This problem(cdrtime null after synchronizing data with 'cdr sync/check -R' command) is fixed in 11.50xC8. Thanks & Regards, Nagaraju From: "SRIDHAR CHANDRASEKHARAN" <sridhcha@cisco.com> To: ids@iiug.org Date: 09/09/2011 02:05 PM Subject: CDRTIME column with NULL value [24885] Hi, We are using Informix ER replication in a 2 node setup. We need to periodically check if a replicated table is in sync. We do this by verifying that the count(*) and max(cdrtime) for the table matches between the 2 nodes when there is no (insert/update/delete) activity on the table. We normally expect (and observe) that the CDRTIME for a row to be the time when the row was updated/inserted. However, we are seeing that CDRTIME column is NULL in some scenarios one of which is as follows. When a row is inserted into node 1 when replication is down and then replication is setup followed by a synchronization of the rows using cdr check & repair, Informix propagates the row to node 2 but the CDRTIME for this row is NULL in node 2. Also, the CDRTIME on node 1 for this row gets updated to the time when cdr check and repair took place. Is this behavior of CDRTIME becoming NULL expected ? Is there any other efficient and accurate way of determining that a replicated table is in sync? (The Informix version used is below (output of onstat -version) Build Version: 11.50.UC5XA Build Number: N104 Build Host: ku Build OS: Linux kernel-2.6.9-34.ELsmp glibc-2.3.4-2.19 compat-glibc-2.3.2-95.30 Build Date: Wed Feb 24 19:33:04 CST 2010 GLS Version: glslib-4.50.UC6) Thanks Sridhar ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum.