HADR disconnected status

[Brian]

We are having some problems administering HADR on a new installation.
Specifically, we are seeing that the connection status of the pair is
"disconnected". We have restarted, restored, and even rebooted to no
avail. In the diag log we are seeing lots of "External Comm Error".
The machines can see each other on the network, and in fact we can
start HADR on both machines from the primary (without specifying BY
FORCE). Once HADR is started, we have one PRIMARY and one STANDBY, but
the pair shows status disconnected. I'm not sure what else to try...
anyone have any ideas what could be causing this?

[Jean-Marc Blaise]

"Brian" <bv*******@yahoo.com> a écrit dans le message de
news:11**********************@o13g2000cwo.googlegr oups.com...

We are having some problems administering HADR on a new installation.
Specifically, we are seeing that the connection status of the pair is
"disconnected". We have restarted, restored, and even rebooted to no
avail. In the diag log we are seeing lots of "External Comm Error".
The machines can see each other on the network, and in fact we can
start HADR on both machines from the primary (without specifying BY
FORCE). Once HADR is started, we have one PRIMARY and one STANDBY, but
the pair shows status disconnected. I'm not sure what else to try...
anyone have any ideas what could be causing this?

Hi Brian,

I don't think the messages you get are related to HADR, but I wish IBM
change these "External Comm Error" that pollute the db2diag.log... Please,
why don't you make this in Information Level ?

Regards,

Jean-Marc

[Ian]

Brian wrote:

We are having some problems administering HADR on a new installation.
Specifically, we are seeing that the connection status of the pair is
"disconnected". We have restarted, restored, and even rebooted to no
avail. In the diag log we are seeing lots of "External Comm Error".
The machines can see each other on the network, and in fact we can
start HADR on both machines from the primary (without specifying BY
FORCE). Once HADR is started, we have one PRIMARY and one STANDBY, but
the pair shows status disconnected. I'm not sure what else to try...
anyone have any ideas what could be causing this?

Does the pair ever get to peer state?

[Brian]

No it never does make it to peer state. If we restore the secondary
from backup, it will show 'peer' for a brief moment, but then shows
disconnected within a few seconds. This leads me to believe that
there's some issue with transferring the logs, but I'm not sure how to
troubleshoot this issue more.

Thanks,
Brian

[Brian]

Ok, change in status. It seems one of our databases had a 'deactivate'
command issued against it. When we ran a 'db2 activate ...' command
from the command line, we got to peer state. But... the mode shows
'asynchronous', despite the fact that we configured both databases to
run in 'synchronous'. We have restarted both databases, but still
can't get to synchronous. If we do a "db2 get db cfg for testing1" on
the command line, we see that the mode show async for both databases.
I thought we could just change the mode through the gui, then restart
the database for changes to take effect. Is this true?
Thanks

[Steve Pearson (news only)]

I'm not very familiar with the GUI, but maybe some final "take action"
step was overlooked. Anyway, once the configuration change is made on
both systems, and both are recycled, there obviously should be no
drifting of configuration values. If you'd like an alternative to the
GUI, then you can change the configuration using CLP commands, for
example:

db2 update db cfg for <db-name> using HADR_SYNCMODE SYNC

Regards,
-Steve P.
--------------------------------------
Steve Pearson
DB2 UDB for LUW Development
Portland, OR, USA