HDR problem ..Plase help...
Niraj Sinha reported an HDR secondary going into an incompatible state after heavy batch work. Informix advised stopping replication around batches; then it stayed out of sync with about 90 logs to send. Barry Lloyd and Rudy Fernandes noted the restart command should be onmode -d primary with the secondary name. Rudy suggested more log space. Smooth1 asked about version. Unresolved.
Auto-generated by Claude from the posts below — may be imperfect; read the full thread.
Does any one use HDR at their place, or know any client who uses HDR.
We have set up HDR and having problems. Spoke to Informix but till now
no luck.
Our HDR pair use to come in "incompatible " state (secondary) whenever
we did heavy batch process. Saw that incompatible state came only when
the prmary server hade checkpoint duration of 400-500, some how.
Informix told us to stop replication before batch job and restart after
it has finished. As we have batch jobs running every morning and
evening, we stop replication every evening, and restart next morning.
It
worked fine for a few days. And today morning, whle HDR seems to be up,
but it never became operational. we had around 90 logs to be sent over,
and primary just sent 1 log and is out of sync.
This is what I did :
Started HDR pair initially.
Then every day :
stop replcation : On primary server : onmode -d standard
start replication : On promary server : onmode -d secondary "primary
name"
thx,
niraj
niraj@bondbook.com
Which Online version? Hopefully either 7.31.UC4 or 7.31.UC7 Sinha, Niraj wrote in message <900pa3$aob$1@news.xmission.com>... >
We use HDR, but we don't do any Batch updates. My only question is the
command to restart replication. On the Primary shouldn't the command
be onmode -d primary "secondary name".
"Sinha, Niraj" wrote:
>
> Does any one use HDR at their place, or know any client who uses HDR.
> We have set up HDR and having problems. Spoke to Informix but till now
> no luck.
> Our HDR pair use to come in "incompatible " state (secondary) whenever
> we did heavy batch process. Saw that incompatible state came only when
> the prmary server hade checkpoint duration of 400-500, some how.
> Informix told us to stop replication before batch job and restart after
> it has finished. As we have batch jobs running every morning and
> evening, we stop replication every evening, and restart next morning.
> It
> worked fine for a few days. And today morning, whle HDR seems to be up,
> but it never became operational. we had around 90 logs to be sent over,
> and primary just sent 1 log and is out of sync.
> This is what I did :
> Started HDR pair initially.
> Then every day :
> stop replcation : On primary server : onmode -d standard
> start replication : On promary server : onmode -d secondary "primary
> name"
>
> thx,
> niraj
> niraj@bondbook.com
Presumably, your "start replication" command is a typo. To restart
replication, the correct command to be run on the primary server is "onmode
-d primary <secondary name>".
Do you have enough log space? You could try increasing log space to more
than twice the 90 logs that usually have to be sent over.
All the best.
Rudy
"Sinha, Niraj" wrote:
> Does any one use HDR at their place, or know any client who uses HDR.
> We have set up HDR and having problems. Spoke to Informix but till now
> no luck.
> Our HDR pair use to come in "incompatible " state (secondary) whenever
> we did heavy batch process. Saw that incompatible state came only when
> the prmary server hade checkpoint duration of 400-500, some how.
> Informix told us to stop replication before batch job and restart after
> it has finished. As we have batch jobs running every morning and
> evening, we stop replication every evening, and restart next morning.
> It
> worked fine for a few days. And today morning, whle HDR seems to be up,
> but it never became operational. we had around 90 logs to be sent over,
> and primary just sent 1 log and is out of sync.
> This is what I did :
> Started HDR pair initially.
> Then every day :
> stop replcation : On primary server : onmode -d standard
> start replication : On promary server : onmode -d secondary "primary
> name"
>
> thx,
> niraj
> niraj@bondbook.com