What should I do if hacmp fails to start after AIX is powered off?

AIX is a UNIX-like operating system, and hacmp is a control application for AIX systems. When AIX suddenly loses power, hacmp will not start. The following small series will introduce you to the next. The solution that hacmp can't start after AIX is powered off.

because of problems caused ups and minicomputer database storage, power off, hacmp not start,

found that hard to identify a problem on jzpt1, the original hard drive from hdisk0 - hdisk11, Now hdisk2 to hdisk9 is gone, there are a lot of hard disks from hdisk12, through rmdev -Rdl

hdisk2 to all the last hard disk, cfgmgr -v re-identification, but error in importvg,

0516-082 lqueryvg: Unable to access a special device file.

Execute redefinevg and synclvodm to build correct environment.

0516-082 lqueryvg: Unable to access a special device file.

Execute redefinevg and synclvodm to build correct environment.

0516-1140 importvg: Unable to read the volume group descriptor area

on specified physical volume.

The newly recognized hard disk has no pvid

by the following command:

chdev -l hdisk2 -a pv=yes, error:

Method error (/usr/lib/methods /chgdisk)

0514-047 Cannot access a device.

Use the following method to solve the problem:

rmdev -Rdl hdisk2

rmdev -Rdl hdisk3

. . . .

rmdev -Rdl hdisk11

Delete all disks

rmdev -Rdl fcs0

. . . .

rmdev -Rdl fcs3

cfgmgr -v

Found pvid

for all pvs but found

hdisk2 on jzpt1 The order of pv on -hdisk8 and jzpt2 is the same, but hdisk9 (on jzpt2) which also belongs to datavg is hdisk10 on jzpt1. The order of the two hard disks has been inconsistent,

and both are datavg. It seems that in the future, when doing shared vg, try not to use multiple small luns, but use a small amount of large-capacity lun, in order to reduce the inconsistency of this hdisk order.

Last resort, datavg varyon on jzpt2, then smitty reducevg, but prompted to destroy the raw device content on datavg.

The smitty migratepv command was used to move the contents of hdisk9 to hdisk2. After transferring lspv -p datavg, it is found that there is no more content on hdisk9, and the content on hdisk2 is more than the contents of hdisk3

.

lsvg -p datavg

datavg:

PV_NAME PV STATE TOTAL PPs FREE PPs FREE DISTRIBUTION

hdisk2 active 1599 811 62..00..109 ..320..320

hdisk3 active 1599 1155 192..04..319..320..320

hdisk4 active 1599 1155 192..04..319..320. .320

hdisk5 active 1599 1087 64..64..319..320..320

hdisk6 active 1599 1087 64..64..319..320..320

hdisk7 active 1599 1135 112..64..319..320..320

hdisk8 active 1599 1215 192..64..319..320..320

Hdisk9 active 1599 1599 192..64..319..320..320

Then use smitty reducevg to remove hdisk9 from datavg. Thus the hdisk in datavg on jzpt1 and jzpt2 is consistent.

Execute smitty importvg on jzpt1

vg writes to datavg, pv writes to hdisk2. Datavg is imported. The bare device in datavg is given to the Oracle:dba user group.

Problem Solving

Later found that jcpt1's hacmp can be started, datavg can also be pulled up concurrently, but jzpt2's datavg can't get up, so all the storage disks on jzpt2 are deleted and deleted. Hba card, then re-

In fact, the root problem is caused by the operating system not installing storage multipathing software.

The above is the method that hacmp can't start after AIX is powered off. In order to avoid similar situations, it is better to install storage multipathing software in AIX system.