Please enter search query.
Search <book_title>...
Storage Foundation for Oracle® RAC 7.3.1 Administrator's Guide - Linux
Last Published:
2018-01-16
Product(s):
InfoScale & Storage Foundation (7.3.1)
- 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
Node is unable to join cluster while another node is being ejected
A cluster that is currently fencing out (ejecting) a node from the cluster prevents a new node from joining the cluster until the fencing operation is completed. The following are example messages that appear on the console for the new node:
...VxFEN ERROR V-11-1-25 ... Unable to join running cluster since cluster is currently fencing a node out of the cluster.
If you see these messages when the new node is booting, the vxfen startup script on the node makes up to five attempts to join the cluster.
To manually join the node to the cluster when I/O fencing attempts fail
- If the vxfen script fails in the attempts to allow the node to join the cluster, restart vxfen driver with the command:
For RHEL 7, SLES 12, and supported RHEL distributions:
# systemctl stop vxfen # systemctl start vxfen
For earlier versions of RHEL, SLES, and supported RHEL distributions:
# /etc/init.d/vxfen stop # /etc/init.d/vxfen start
If the command fails, restart the new node.