Storage Foundation for Oracle® RAC 7.3.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
- How SF Oracle RAC works (high-level perspective)
- Component products and processes of SF Oracle RAC
- Periodic health evaluation of SF Oracle RAC clusters
- About Virtual Business Services
- About Veritas InfoScale Operations Manager
- About Veritas Services and Operations Readiness Tools (SORT)
- Administering SF Oracle RAC and its components
- Administering SF Oracle RAC
- Setting the environment variables for SF Oracle RAC
- Starting or stopping SF Oracle RAC on each node
- Applying Oracle patches on SF Oracle RAC nodes
- Migrating Pluggable Databases (PDB) between Container Databases (CDB)
- Installing Veritas Volume Manager, Veritas File System, or ODM patches on SF Oracle RAC nodes
- Applying operating system updates on SF Oracle RAC nodes
- Adding storage to an SF Oracle RAC cluster
- Recovering from storage failure
- Backing up and restoring Oracle database using Veritas NetBackup
- Enhancing the performance of SF Oracle RAC clusters
- Administering SmartIO
- Creating snapshots for offhost processing
- Managing database storage efficiently using SmartTier
- Optimizing database storage using Thin Provisioning and SmartMove
- Scheduling periodic health checks for your SF Oracle RAC cluster
- Using environment variables to start and stop VCSMM modules
- Verifying the nodes in an SF Oracle RAC cluster
- Administering VCS
- About managing VCS modules
- Viewing available Veritas device drivers
- Starting and stopping VCS
- Environment variables to start and stop VCS modules
- Adding and removing LLT links
- Configuring aggregated interfaces under LLT
- Displaying the cluster details and LLT version for LLT links
- Configuring destination-based load balancing for LLT
- Enabling and disabling intelligent resource monitoring for agents manually
- Administering the AMF kernel driver
- Administering I/O fencing
- About administering I/O fencing
- About the vxfentsthdw utility
- General guidelines for using the vxfentsthdw utility
- About the vxfentsthdw command options
- Testing the coordinator disk group using the -c option of vxfentsthdw
- Performing non-destructive testing on the disks using the -r option
- Testing the shared disks using the vxfentsthdw -m option
- Testing the shared disks listed in a file using the vxfentsthdw -f option
- Testing all the disks in a disk group using the vxfentsthdw -g option
- Testing a disk with existing keys
- About the vxfenadm utility
- About the vxfenclearpre utility
- About the vxfenswap utility
- Enabling or disabling the preferred fencing policy
- About I/O fencing log files
- Migrating from disk-based fencing to server-based fencing using the installer
- Migrating from server-based fencing to disk-based fencing using the installer
- Administering the CP server
- Administering CFS
- Administering CVM
- Listing all the CVM shared disks
- Establishing CVM cluster membership manually
- Changing the CVM master manually
- Importing a shared disk group manually
- Deporting a shared disk group manually
- Starting shared volumes manually
- Verifying if CVM is running in an SF Oracle RAC cluster
- Verifying CVM membership state
- Verifying the state of CVM shared disk groups
- Verifying the activation mode
- Administering Flexible Storage Sharing
- About Flexible Storage Sharing disk support
- About the volume layout for Flexible Storage Sharing disk groups
- Setting the host prefix
- Exporting a disk for Flexible Storage Sharing
- Setting the Flexible Storage Sharing attribute on a disk group
- Using the host disk class and allocating storage
- Administering mirrored volumes using vxassist
- Displaying exported disks and network shared disk groups
- Tuning LLT for memory and performance in FSS environments
- 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
- Restarting the installer after a failed network connection
- Installer cannot create UUID for the cluster
- Troubleshooting SF Oracle RAC pre-installation check failures
- Troubleshooting LLT health check warning messages
- Troubleshooting I/O fencing
- SCSI reservation errors during bootup
- The vxfentsthdw utility fails when SCSI TEST UNIT READY command fails
- Node is unable to join cluster while another node is being ejected
- System panics to prevent potential data corruption
- Cluster ID on the I/O fencing key of coordinator disk does not match the local cluster's ID
- Fencing startup reports preexisting split-brain
- Registered keys are lost on the coordinator disks
- Replacing defective disks when the cluster is offline
- Troubleshooting I/O fencing health check warning messages
- 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
- Restoring communication between host and disks after cable disconnection
- Shared disk group cannot be imported in SF Oracle RAC cluster
- Error importing shared disk groups in SF Oracle RAC cluster
- Unable to start CVM in SF Oracle RAC cluster
- CVM group is not online after adding a node to the SF Oracle RAC cluster
- CVMVolDg not online even though CVMCluster is online in SF Oracle RAC cluster
- Shared disks not visible in SF Oracle RAC cluster
- Troubleshooting CFS
- Troubleshooting interconnects
- Troubleshooting Oracle
- Error when starting an Oracle instance in SF Oracle RAC
- Clearing Oracle group faults
- Oracle log files show shutdown called even when not shutdown manually
- DBCA fails while creating an Oracle RAC database
- Oracle's clusterware processes fail to start
- Oracle Clusterware fails after restart
- Troubleshooting the Virtual IP (VIP) configuration in an SF Oracle RAC cluster
- Troubleshooting Oracle Clusterware health check warning messages in SF Oracle RAC clusters
- Troubleshooting ODM in SF Oracle RAC clusters
- Troubleshooting Flex ASM in SF Oracle RAC clusters
- Prevention and recovery strategies
- Tunable parameters
- Troubleshooting SF Oracle RAC
- Section III. Reference
Displaying the I/O fencing registration keys
You can display the keys that are currently assigned to the disks using the vxfenadm command.
The variables such as disk_7, disk_8, and disk_9 in the following procedure represent the disk names in your setup.
To display the I/O fencing registration keys
- To display the key for the disks, run the following command:
# vxfenadm -s disk_name
For example:
To display the key for the coordinator disk
/dev/sdxfrom the system with node ID 1, enter the following command:# vxfenadm -s /dev/sdx key[1]: [Numeric Format]: 86,70,68,69,69,68,48,48 [Character Format]: VFDEED00 * [Node Format]: Cluster ID: 57069 Node ID: 0 Node Name: sys1
The -s option of vxfenadm displays all eight bytes of a key value in three formats. In the numeric format,
The first two bytes, represent the identifier VF, contains the ASCII value 86, 70.
The next four bytes contain the ASCII value of the cluster ID 57069 encoded in hex (0xDEED) which are 68, 69, 69, 68.
The remaining bytes contain the ASCII value of the node ID 0 (0x00) which are 48, 48. Node ID 1 would be 01 and node ID 10 would be 0A.
An asterisk before the Node Format indicates that the vxfenadm command is run from the node of a cluster where LLT is configured and is running.
To display the keys on a CVM parallel disk group:
# vxfenadm -s /dev/vx/rdmp/disk_7 Reading SCSI Registration Keys... Device Name: /dev/vx/rdmp/disk_7 Total Number Of Keys: 1 key[0]: [Numeric Format]: 66,80,71,82,48,48,48,49 [Character Format]: BPGR0001 [Node Format]: Cluster ID: unknown Node ID: 1 Node Name: sys2
To display the keys on a Cluster Server (VCS) failover disk group:
# vxfenadm -s /dev/vx/rdmp/disk_8 Reading SCSI Registration Keys... Device Name: /dev/vx/rdmp/disk_8 Total Number Of Keys: 1 key[0]: [Numeric Format]: 65,86,67,83,0,0,0,0 [Character Format]: AVCS [Node Format]: Cluster ID: unknown Node ID: 0 Node Name: sys1
- To display the keys that are registered in all the disks specified in a disk file:
# vxfenadm -s all -f disk_filename
For example:
To display all the keys on coordinator disks:
# vxfenadm -s all -f /etc/vxfentab Device Name: /dev/vx/rdmp/disk_9 Total Number Of Keys: 2 key[0]: [Numeric Format]: 86,70,70,68,57,52,48,49 [Character Format]: VFFD9401 * [Node Format]: Cluster ID: 64916 Node ID: 1 Node Name: sys2 key[1]: [Numeric Format]: 86,70,70,68,57,52,48,48 [Character Format]: VFFD9400 * [Node Format]: Cluster ID: 64916 Node ID: 0 Node Name: sys1
You can verify the cluster ID using the lltstat -C command, and the node ID using the lltstat -N command. For example:
# lltstat -C 57069
If the disk has keys that do not belong to a specific cluster, then the vxfenadm command cannot look up the node name for the node ID, and hence prints the node name as unknown. For example:
Device Name: /dev/vx/rdmp/disk_7 Total Number Of Keys: 1 key[0]: [Numeric Format]: 86,70,45,45,45,45,48,49 [Character Format]: VF----01 [Node Format]: Cluster ID: unknown Node ID: 1 Node Name: sys2
For disks with arbitrary format of keys, the vxfenadm command prints all the fields as unknown. For example:
[Numeric Format]: 65,66,67,68,49,50,51,45 [Character Format]: ABCD123- [Node Format]: Cluster ID: unknown Node ID: unknown Node Name: unknown