Re: hacmp fall over problem, db2 slow start
- From: "Andreas Schulze" <b79xan@xxxxxx>
- Date: 30 Mar 2007 01:58:14 -0700
On 29 Mrz., 18:20, "Hardy" <wyh...@xxxxxxxxx> wrote:
Hi,
DB2 HA on two AIX server A and B, HACMP take over test is OK.
but when we issue"halt -q" on on server A, B can take over all the
resource of A but it is very slow when it come to "db2start", 16nodes
start cost 30 minutes। but when started, it works well.
some problems about networking is reported:
1. the service ip of B is moved to another interface. also the service
ip of A is moved to the same interface.
2। "Interface 192.168.7.3 has failed on node PDBA","Interface
192.168.7.3 is now available on node PDBA". 7.3 is bootip of B.
for 1, why service ip for B is moved? is it normal?
for 2, the reason? what it is doing?
Thank you.
Hallo Hardy
Too little information for indepth analysis. Some thoughts:
Depending on HACMP release service IP might move if the cluster
detects network down on the originating adapter (resulting from
halting node A? How many interfaces are reachable on this particular
network?). This would explain that the service IP from A is placed on
the other adapter also.
Depending on vg type starting the DB might take considerably longer
after a halt -q because of fsck and/or replaying logs (both
filesystems and DB logs)?
As to your 2nd problem: that looks like some sort of misconfiguration
(works as designed). Check AIX and HACMP configuration on both nodes
for information about 192.168.7.3.
hth
andreas
.
- Follow-Ups:
- Re: hacmp fall over problem, db2 slow start
- From: Hardy
- Re: hacmp fall over problem, db2 slow start
- References:
- hacmp fall over problem, db2 slow start
- From: Hardy
- hacmp fall over problem, db2 slow start
- Prev by Date: Re: LPAR without HMC
- Next by Date: Re: hacmp fall over problem, db2 slow start
- Previous by thread: hacmp fall over problem, db2 slow start
- Next by thread: Re: hacmp fall over problem, db2 slow start
- Index(es):
Relevant Pages
|
|
