1.Ensure that the Oracle RAC database is not active on either node.
2.From node 2, use the vgchange command to deactivate the volume group:
#vgchange
3.From node 2, use the vgexport command to export the volume group:
#vgexport
This dissociates the volume group from node 2.
4.From node 1, use the vgchange command to deactivate the volume group:
#vgchange
5.Use the vgchange command to mark the volume group as unshareable:
#vgchange
6.Prior to making configuration changes, activate the volume group in normal
#vgchange
7.Use normal LVM commands to make the needed changes. Be sure to set the raw logical volume device file's owner to oracle and group to dba with a mode of 660.
8.Next, from node 1, deactivate the volume group:
#vgchange
9.Use the vgexport command with the options shown in the example to create a new map file:
#vgexport
Make a copy of /etc/lvmpvg in /tmp/lvmpvg, then copy the file to /tmp/lvmpvg on node 2. Copy the file /tmp/vg_rac.map to node 2.
10.Use the following command to make the volume group shareable by the entire cluster again:
#vgchange
11.On node 2, issue the following command:
#mkdir /dev/vg_rac
12.Create a control file named group in the directory /dev/vg_rac, as in the following:
#mknod /dev/vg_rac/group c 64 0xhh0000
The major number is always 64, and the hexadecimal minor number has the format:
0xhh0000
where hh must be unique to the volume group you are creating. Use the next hexadecimal number that is available on your system after the volume groups that are already configured.
13.Use the vgimport command, specifying the map file you copied from the configuration node. In the following example, the vgimport command is issued on the second node for the same volume group that was modified on the first node:
#vgimport
14.Activate the volume group in shared mode by issuing the following command on both nodes:
#vgchange
Skip this step if you use a package control script to activate and deactivate the shared volume group as a part of RAC startup and shutdown.
Managing the Shared Storage 129