Storage Foundation for Oracle® RAC 8.0.2 Administrator's Guide - Solaris
- Section I. SF Oracle RAC concepts and administration
- Overview of 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
- About the vxfenadm 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
- 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 VCSIPC
- Troubleshooting Oracle
- Troubleshooting ODM in SF Oracle RAC clusters
- Prevention and recovery strategies
- Tunable parameters
- Troubleshooting SF Oracle RAC
- Section III. Reference
Shared disks not visible in SF Oracle RAC cluster
If the shared disks in /dev/rdsk are not visible, perform the following tasks:
Make sure that all shared LUNs are discovered by the HBA and SCSI layer. This can be verified by running the ls -ltr command on any of the disks under /dev/rdsk/*.
For example:
# ls -ltr /dev/rdsk/disk_name lrwxrwxrwx 1 root root 81 Aug 18 11:58 c2t5006016141E02D28d4s2 -> ../../devices/pci@7c0/pci@0/pci@8/SUNW,qlc@0/fp@0, 0/ssd@w5006016141e02d28,4:c,raw lrwxrwxrwx 1 root root 81 Aug 18 11:58 c2t5006016141E02D28d3s2 -> ../../devices/pci@7c0/pci@0/pci@8/SUNW,qlc@0/fp@0, 0/ssd@w5006016141e02d28,3:c,raw lrwxrwxrwx 1 root root 81 Aug 18 11:58 c2t5006016141E02D28d2s2 -> ../../devices/pci@7c0/pci@0/pci@8/SUNW,qlc@0/fp@0, 0/ssd@w5006016141e02d28,2:c,raw lrwxrwxrwx 1 root root 81 Aug 18 11:58 c2t5006016141E02D28d1s2 -> ../../devices/pci@7c0/pci@0/pci@8/SUNW,qlc@0/fp@0, 0/ssd@w5006016141e02d28,1:c,raw
If all LUNs are not discovered by SCSI, the problem might be corrected by specifying dev_flags or default_dev_flags and max_luns parameters for the SCSI driver.
If the LUNs are not visible in /dev/rdsk/* files, it may indicate a problem with SAN configuration or zoning.
Perform the following additional steps:
Check the file
/kernel/drv/sd.conf
to see if the new LUNs were added.Check the format to see if the LUNs have been labeled in the server.
Check to see is the disk is seen, using the following command:
# prtvtoc /dev/rdsk/disk_name