Oracle large database systems on actual AIX / UNIX Explanation of focused 37 Wenping
A few readers in the implementation of their RAC after the restart HACMP concurrent volume group found that another node does not activate (lsvg -o), see PV found no activation (CONCURRENT ACTIVE).
May the following reasons (Oracle Release Notes):
To enable simultaneous access to a disk device from multiple nodes, you must set the appropriate Object Data Manager (ODM) attribute listed in the following table to the value shown, depending on the disk type:
Disk Type Attribute Value
SSA, FAStT, or non-MPIO-capable disks reserve_lock no
ESS, EMC, HDS, CLARiiON, or MPIO-capable disks
reserve_policy no_reserve
To determine whether the attribute has the correct value, enter a command similar to the following on all cluster nodes for each disk device that you want to use:
# /usr/sbin/lsattr -E -l hdiskn
If the required attribute is not set to the correct value on any node, then enter a command similar to one of the following on that node:
■ SSA and FAStT devices
# /usr/sbin/chdev -l hdiskn -a reserve_lock=no
■ ESS, EMC, HDS, CLARiiON, and MPIO-capable devices
# /usr/sbin/chdev -l hdiskn -a reserve_policy=no_reserve
Therefore, the need to close HACMP are performed on two nodes:
chdev -l hdisk2 -a reserve_lock=no
chdev -l hdisk3 -a reserve_lock=no
chdev -l hdisk4 -a reserve_lock=no
chdev -l hdisk5 -a reserve_lock=no
or:
chdev -l hdisk2 -a reserve_policy=no_reserve
chdev -l hdisk3 -a reserve_policy=no_reserve
chdev -l hdisk4 -a reserve_policy=no_reserve
chdev -l hdisk5 -a reserve_policy=no_reserve
Then restart the HACMP, it should be no problem.
Reproduced in: https: //www.cnblogs.com/dbserver/articles/1716889.html