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
- 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
Managing SCSI-3 PR keys in SF Oracle RAC cluster
I/O Fencing places the SCSI-3 PR keys on coordinator LUNs. The format of the key follows the naming convention wherein ASCII "A" is prefixed to the LLT ID of the system that is followed by 7 dash characters.
For example:
node 0 uses A-------
node 1 uses B-------
In an SF Oracle RAC/SF CFS/SF HA environment, VxVM/CVM registers the keys on data disks, the format of which is ASCII "A" prefixed to the LLT ID of the system followed by the characters "PGRxxxx" where 'xxxx' = i such that the disk group is the ith shared group to be imported.
For example: node 0 uses APGR0001 (for the first imported shared group).
In addition to the registration keys, VCS/CVM also installs a reservation key on the data LUN. There is one reservation key per cluster as only one node can reserve the LUN.
The following command lists the keys on a data disk group:
# vxdg list |grep data
sys1_data1 enabled,shared,cds 1201715530.28.pushover
Select the data disk belonging to sys1_data1:
# vxdisk -o alldgs list |grep sys1_data1
The following command lists the PR keys:
# vxdisk -o listreserve list sdh
........
........
Alternatively, the PR keys can be listed using vxfenadm command:
#echo "/dev/vx/dmp/sdh" > /tmp/disk71
# vxfenadm -s all -f /tmp/disk71
Device Name: /dev/vx/dmp/sdh Total Number Of Keys: 2 key[0]: Key Value [Numeric Format]: 66,80,71,82,48,48,48,52 Key Value [Character Format]: BPGR0004 key[1]: Key Value [Numeric Format]: 65,80,71,82,48,48,48,52 Key Value [Character Format]: APGR0004