Storage Foundation for Oracle® RAC 7.4.1 Administrator's Guide - Linux
- Section I. SF Oracle RAC concepts and administration
- Overview of Storage Foundation for Oracle RAC
- About Storage Foundation for Oracle RAC
- Component products and processes of SF Oracle RAC
- About Virtual Business Services
- Administering SF Oracle RAC and its components
- Administering SF Oracle RAC
- Starting or stopping SF Oracle RAC on each node
- Administering VCS
- Administering I/O fencing
- About the vxfentsthdw utility
- Testing the coordinator disk group using the -c option of vxfentsthdw
- About the vxfenadm utility
- About the vxfenclearpre utility
- About the vxfenswap utility
- Administering the CP server
- Administering CFS
- Administering CVM
- Changing the CVM master manually
- Administering Flexible Storage Sharing
- Backing up and restoring disk group configuration data
- Administering SF Oracle RAC global clusters
- Administering SF Oracle RAC
- Overview of Storage Foundation for Oracle RAC
- Section II. Performance and troubleshooting
- Troubleshooting SF Oracle RAC
- About troubleshooting SF Oracle RAC
- Troubleshooting I/O fencing
- Fencing startup reports preexisting split-brain
- Troubleshooting CP server
- Troubleshooting server-based fencing on the SF Oracle RAC cluster nodes
- Issues during online migration of coordination points
- Troubleshooting Cluster Volume Manager in SF Oracle RAC clusters
- Troubleshooting CFS
- Troubleshooting interconnects
- Troubleshooting Oracle
- Troubleshooting ODM in SF Oracle RAC clusters
- Prevention and recovery strategies
- Tunable parameters
- Troubleshooting SF Oracle RAC
- Section III. Reference
Replacing coordination points for server-based fencing in an online cluster
Use the following procedure to perform a planned replacement of customized coordination points (CP servers or SCSI-3 disks) without incurring application downtime on an online SF Oracle RAC cluster.
Note:
If multiple clusters share the same CP server, you must perform this replacement procedure in each cluster.
You can use the vxfenswap utility to replace coordination points when fencing is running in customized mode in an online cluster, with vxfen_mechanism=cps. The utility also supports migration from server-based fencing (vxfen_mode=customized) to disk-based fencing (vxfen_mode=scsi3) and vice versa in an online cluster.
However, if the SF Oracle RAC cluster has fencing disabled (vxfen_mode=disabled), then you must take the cluster offline to configure disk-based or server-based fencing.
You can cancel the coordination point replacement operation at any time using the vxfenswap -a cancel command.
See About the vxfenswap utility.
To replace coordination points for an online cluster
- Ensure that the SF Oracle RAC cluster nodes and users have been added to the new CP server(s). Run the following commands:
# cpsadm -s cpserver -a list_nodes # cpsadm -s cpserver -a list_users
If the SF Oracle RAC cluster nodes are not present here, prepare the new CP server(s) for use by the SF Oracle RAC cluster.
See the Storage Foundation for Oracle RAC Configuration and Upgrade Guide for instructions.
- Ensure that fencing is running on the cluster using the old set of coordination points and in customized mode.
For example, enter the following command:
# vxfenadm -d
The command returns:
I/O Fencing Cluster Information: ================================ Fencing Protocol Version: <version> Fencing Mode: Customized Cluster Members: * 0 (sys1) 1 (sys2) RFSM State Information: node 0 in state 8 (running) node 1 in state 8 (running)
- 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.Review and if necessary, update the vxfenmode parameters for security, the coordination points, and if applicable to your configuration, vxfendg.
Refer to the text information within the
vxfenmode
file for additional information about these parameters and their new possible values. - From one of the nodes of the cluster, run the vxfenswap utility.
The vxfenswap utility requires secure ssh connection to all the cluster nodes. Use - n to use rsh instead of default ssh. Use - p <protocol>, where <protocol> can be ssh, rsh, or hacli.
# vxfenswap [-n | -p <protocol>]
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
The vxfenswap utility rolls back the migration operation.
If you want to commit the new fencing configuration changes, answer y at the prompt.
Do you wish to commit this change? [y/n] (default: n) y
If the utility successfully completes the operation, the utility moves the
/etc/vxfenmode.test
file to the/etc/vxfenmode
file.
- Confirm the successful execution of the vxfenswap utility by checking the coordination points currently used by the vxfen driver.
For example, run the following command:
# vxfenconfig -l