We have a simple 2 node ER deployment (IDS 11.5). One node is active
and
the other is standby. Data is correctly replicated from active to
standby node.

But we noticed that commands like

cdr view profile
cdr check repl

are properly executed only on active server displaying data from both
nodes, while on standby they display correct data only for that node,
or
reporting messages like this:
--------------
Connection to server g_server1 failed
Can not connect to g_server1
------------
Where g_server1 is the group of active server.

Documentation says that all cdr commands can be used on each node.

Is it possible to solve this situation?

On 12/11/2010 18:02, Cveja wrote:

Can you on the standby server do dbaccess / connect / "Standy instance"
using any of the DBSERVERNAME / DBSERVERALIAS / group name (obviously
TCP connections only)

You state "ER out of sync" - is there actually data queuing up on the
active? What does cdr list server show?

On 12 нов, 19:51, "Jonny... (AT) Usenet-News (DOT) net" <Jonny...@Usenet-
News.net> wrote:
Yes.

We didn't try that. I can't check whether it works at the moment, but
I
certainly will on Monday.

No, replication is OK, but we are testing failover scenario.
Actually, we need a way to know in the case of failover, using standby
node, whether the tables in replication are out of sync with the
active
server. We need to know whether it is safe to promote standby server
to
active. We thought we could use consistency check (cdr check repl)
from
standby node. And that's when this problem showed up.

-->> server. We need to know whether it is safe to promote standby
server
-->> to
-->> active. We thought we could use consistency check (cdr check
repl)


Do not get me wrong here ER is great however when i read above
is it not easyer to use HDR instead of ER in your situation???

(unless of course you have byte and text data in oldfashion
blobspaces..)

Superboer




On 13 nov, 01:06, Cveja <niko... (AT) gmail (DOT) com> wrote:

On Nov 15, 8:26*am, Superboer <superbo... (AT) t-online (DOT) de> wrote:
I'm afraid it's not possible to change the replication deployment at
this
point.

On Nov 12, 7:51*pm, "Jonny... (AT) Usenet-News (DOT) net" wrote:
It was possible to connect using dbaccess, and
that was the clue that lead us to the solution.
Thanks.

I must admit it was kind of a beginner's mistake.
We didn't use -c option for connection to the other node
explicitly, and the wrong user was invoking the commands.



On a related topic, regarding usage of cdr check repl, when the
tables
have large number of rows, the processing obviously takes significant
amount
of time. We tested table with 180k records and cdr check took 4
minutes
to finish.

Does this command make significant impact on IDS when executed on
large
tables? We're planning to make a script that invokes cdr check repl
which
cron job would call in defined intervals, so our concern is how the
IDS will
handle that.

informix-list-bounces (AT) iiug (DOT) org wrote on 11/15/2010 06:46:33 AM:

Definitely there will be some impact as cdr check repl has to read all the
rows from the
table on source and target to identify inconsistent rows. You could improve
the
performance of cdr check repl by using ifx_replcheck shadow column. Create
the shadow
column and then define unique index using primary key and ifx_replcheck
column.
cdr check repl will use this index to perform speedy consistency check.
More details --
http://publib.boulder.ibm.com/infoce...ds_erp_526.htm

On Nov 16, 8:19*pm, Nilesh Ozarkar <nile... (AT) us (DOT) ibm.com> wrote:
Also, you can include a 'where' clause or 'since' clause in the check
to reduce the number of rows which have to be compared.

On Nov 17, 10:38*am, mpruet <mpru... (AT) verizon (DOT) net> wrote:
On Nov 17, 10:38 am, mpruet <mpru... (AT) verizon (DOT) net> wrote:
I have a question concerning the use of 'since' clause.
Let's say I have a script that will call cdr check repl every ten
minutes. Each time it uses the last check time for 'since' clause.
As I understand it should report the inconsistencies in given time
interval.

Let's say there are two consecutive reads and in the first
one there are problems (some rows are mismatch) and the
next one ten minutes later shows no problems.

How will the DBA know upon reading the last report
that there were some inconsistencies?
Is the last read the right one?