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

To migrate from disk-based fencing to server-based fencing

Make sure system-to-system communication is functioning properly.

Make sure that the SF Oracle RAC cluster is online and uses disk-based fencing.

# vxfenadm -d

For example, if SF Oracle RAC cluster uses disk-based fencing:

I/O Fencing Cluster Information:

================================

Fencing Protocol Version: 201

Fencing Mode: SCSI3

Fencing SCSI3 Disk Policy: dmp

Cluster Members:

* 0 (galaxy)

1 (nebula)

RFSM State Information:

node 0 in state 8 (running)

node 1 in state 8 (running)

Make sure that you performed the following tasks on the designated CP server:

■ Preparing to configure the new CP server.

■ Configuring the new CP server

■ Preparing the new CP server for use by the SF Oracle RAC cluster

See the Veritas Storage Foundation for Oracle RAC Installation and

Configuration Guide for the procedures.

Create a new /etc/vxfenmode.test file on each SF Oracle RAC cluster node

with the fencing configuration changes such as the CP server information.

Refer to the sample vxfenmode files in the /etc/vxfen.d folder.

From any node in the SF Oracle RAC cluster, start the vxfenswap utility:

# vxfenswap [-n]

Review the message that the utility displays and confirm whether you want

to commit the change.

■ If you do not want to commit the new fencing configuration changes, press

Enter or answer n at the prompt.

Do you wish to commit this change? [y/n] (default: n) n

Overview of Veritas Storage Foundation for Oracle RAC

About preventing data corruption with I/O fencing