Veritas Storage Foundation 5.1 SP1 for Oracle RAC Administrator"s Guide (5900-1512, April 2011)

4
Stop I/O fencing on each node:
# /sbin/init.d/vxfen stop
This removes any registration keys on the disks.
5
Import the coordinator disk group. The file /etc/vxfendg includes the name
of the disk group (typically, vxfencoorddg) that contains the coordinator
disks, so use the command:
# vxdg -tfC import ‘cat /etc/vxfendg‘
where:
-t specifies that the disk group is imported only until the node restarts.
-f specifies that the import is to be done forcibly, which is necessary if one
or more disks is not accessible.
-C specifies that any import locks are removed.
6
To remove disks from the disk group, use the VxVM disk administrator utility,
vxdiskadm.
You may also destroy the existing coordinator disk group. For example:
■ Verify whether the coordinator attribute is set to on.
# vxdg list vxfencoorddg | grep flags: | grep coordinator
■ Destroy the coordinator disk group.
# vxdg -o coordinator destroy vxfencoorddg
7
Add the new disk to the node and initialize it as a VxVM disk.
Then, add the new disk to the vxfencoorddg disk group:
■ If you destroyed the disk group in step 6, then create the disk group again
and add the new disk to it.
See the Veritas Storage Foundation for Oracle RAC Installation and
Configuration Guide for detailed instructions.
■ If the diskgroup already exists, then add the new disk to it.
# vxdg -g vxfencoorddg -o coordinator adddisk disk_name
8
Test the recreated disk group for SCSI-3 persistent reservations compliance.
See “Testing the coordinator disk group using vxfentsthdw -c option”
on page 109.
207Troubleshooting SF Oracle RAC
Troubleshooting I/O fencing