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
- 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
About GAB load-time or static tunable parameters
Table: GAB static tunable parameters lists the static tunable parameters in GAB that are used during module load time. Use the gabconfig -e command to list all such GAB tunable parameters.
You can modify these tunable parameters only by adding new values in the GAB configuration file. The changes take effect only on reboot or on reload of the GAB module.
Table: GAB static tunable parameters
GAB parameter | Description | Values (default and range) |
|---|---|---|
numnids | Maximum number of nodes in the cluster | Default: 128 Range: 1-128 |
numports | Maximum number of ports in the cluster | Default: 32 Range: 1-32 |
flowctrl | Number of pending messages in GAB queues (send or receive) before GAB hits flow control. This can be overwritten while cluster is up and running with the gabconfig -Q option. Use the gabconfig command to control value of this tunable. | Default: 128 Range: 1-1024 |
logbufsize | GAB internal log buffer size in bytes | Default: 48100 Range: 8100-65400 |
msglogsize | Maximum messages in internal message log | Default: 256 Range: 128-4096 |
isolate_time | Maximum time to wait for isolated client Can be overridden at runtime | Default: 120000 msec (2 minutes) Range: 160000-240000 (in msec) |
kill_ntries | Number of times to attempt to kill client Can be overridden at runtime | Default: 5 Range: 3-10 |
conn_wait | Maximum number of wait periods (as defined in the stable timeout parameter) before GAB disconnects the node from the cluster during cluster reconfiguration | Default: 12 Range: 1-256 |
ibuf_count | Determines whether the GAB logging daemon is enabled or disabled The GAB logging daemon is enabled by default. To disable, change the value of gab_ibuf_count to 0. The disable login to the gab daemon while cluster is up and running with the gabconfig -K option. Use the gabconfig command to control value of this tunable. | Default: 8 Range: 0-32 |
kstat_size | Number of system statistics to maintain in GAB | Default: 60 Range: 0 - 240 |