Using Serviceguard Extension for RAC, 2nd Edition, February 2005 Update

Maintenance and Troubleshooting
Managing the Shared Storage
Chapter 3 87
Make a copy of /etc/lvmpvg in /tmp/lvmpvg, then copy the file to
/tmp/lvmpvg on node 2. Copy the file /tmp/vg_ops.map to node 2.
10. Use the following command to make the volume group shareable by
the entire cluster again:
# vgchange -S y -c y /dev/vg_ops
11. On node 2, issue the following command:
# mkdir /dev/vg_ops
12. Create a control file named group in the directory /dev/vg_ops, as
in the following:
# mknod /dev/vg_ops/group c 64 0xhh0000
The major number is always 64, and the hexadecimal minor number
has the form
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 -v -m /tmp/vg_ops.map /dev/vg_ops
/dev/dsk/c0t2d0/dev/dsk/c1t2d0
14. Activate the volume group in shared mode by issuing the following
command on both nodes:
# vgchange -a s -p /dev/vg_ops
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.
Adding Additional Shared LVM Volume Groups
To add capacity or to organize your disk resources for ease of
management, you may wish to create additional shared volume groups
for your Oracle RAC databases. If you decide to use additional shared
volume groups, they must conform to the following rules: