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
Environment variables to start and stop VCS modules
The start and stop environment variables for AMF, LLT, GAB, VxFEN, and VCS engine define the default VCS behavior to start these modules during system restart or stop these modules during system shutdown.
Note:
The startup and shutdown of AMF, LLT, GAB, VxFEN, and VCS engine are inter-dependent. For a clean startup or shutdown of SF Oracle RAC, you must either enable or disable the startup and shutdown modes for all these modules.
Table: Start and stop environment variables for VCS
Environment variable | Definition and default value |
|---|---|
AMF_START | Startup mode for the AMF driver. By default, the AMF driver is enabled to start up after a system reboot. This environment variable is defined in the following file:
Default: 1 |
AMF_STOP | Shutdown mode for the AMF driver. By default, the AMF driver is enabled to stop during a system shutdown. This environment variable is defined in the following file:
Default: 1 |
LLT_START | Startup mode for LLT. By default, LLT is enabled to start up after a system reboot. This environment variable is defined in the following file:
Default: 1 |
LLT_STOP | Shutdown mode for LLT. By default, LLT is enabled to stop during a system shutdown. This environment variable is defined in the following file:
Default: 1 |
GAB_START | Startup mode for GAB. By default, GAB is enabled to start up after a system reboot. This environment variable is defined in the following file:
Default: 1 |
GAB_STOP | Shutdown mode for GAB. By default, GAB is enabled to stop during a system shutdown. This environment variable is defined in the following file:
Default: 1 |
VXFEN_START | Startup mode for VxFEN. By default, VxFEN is enabled to start up after a system reboot. This environment variable is defined in the following file:
Default: 1 |
VXFEN_STOP | Shutdown mode for VxFEN. By default, VxFEN is enabled to stop during a system shutdown. This environment variable is defined in the following file:
Default: 1 |
VCS_START | Startup mode for VCS engine. By default, VCS engine is enabled to start up after a system reboot. This environment variable is defined in the following file:
Default: 1 |
VCS_STOP | Shutdown mode for VCS engine. By default, VCS engine is enabled to stop during a system shutdown. This environment variable is defined in the following file:
Default: 1 |
VCS_STOP_TIMEOUT | Time-out value in seconds for the stop operation of the VCS service. VCS uses this value during a system shutdown or restart operation to determine how long to wait for its stop operation to complete. After this duration has elapsed, VCS forcefully stops itself. If this value is set to 0 seconds, the stop operation does not time out. If an issue occurs when the resources are taken offline, HAD continues to be in the LEAVING state, thereby blocking the system shutdown or restart operation. Administrative intervention might be required to address such situations. Set this value to a positive integer to eliminate the need for manual intervention in case an operation is hung. After the duration specified that is in this variable has elapsed, VCS stops itself forcefully (hastop -local -force) and releases control of the application that is configured for HA. The operating system can then take the necessary action on the application components and continue with the shutdown or the restart operation. Note: If this value is set to anything other than a positive integer, VCS uses the default value (0, which indicates no time-out) instead. In This environment variable is defined in the Note: Veritas recommends that you do not change the TimeoutStopSec attribute of the VCS service. If you want to configure a time-out value for the stop operation, use the VCS_STOP_TIMEOUT variable in the Warning: Specifying a time-out value other than the default may have some adverse effects on the applications managed by VCS. For example, during a shutdown or a restart operation on a cluster node: Scenario 1, which may result in some unexpected behavior: If the value of VCS_STOP_TIMEOUT is too less, the VCS service stop operation times out before it can stop all the resources. This time-out may occur even when there is no issue with the cluster. Such an event may cause application-level issues in the cluster, because the application processes are no longer under the control of VCS. Scenario 2, which may result in some unexpected behavior: If a VCS agent fails to stop an application that it monitors, administrative intervention might be required. The VCS service stop operation times out and the necessary administrative intervention is not carried out. Default value: 0 seconds (indicates no time-out) |