Storage Foundation for Oracle® RAC 7.4.1 Configuration and Upgrade Guide - Solaris
- Section I. Configuring SF Oracle RAC
- Preparing to configure SF Oracle RAC
- Configuring SF Oracle RAC using the script-based installer
- Configuring the SF Oracle RAC components using the script-based installer
- Configuring the SF Oracle RAC cluster
- Configuring SF Oracle RAC in secure mode
- Configuring a secure cluster node by node
- Configuring the SF Oracle RAC cluster
- Setting up disk-based I/O fencing using installer
- Setting up server-based I/O fencing using installer
- Configuring the SF Oracle RAC components using the script-based installer
- Performing an automated SF Oracle RAC configuration
- Section II. Post-installation and configuration tasks
- Verifying the installation
- Performing additional post-installation and configuration tasks
- Section III. Upgrade of SF Oracle RAC
- Planning to upgrade SF Oracle RAC
- Performing a full upgrade of SF Oracle RAC using the product installer
- Performing an automated full upgrade of SF Oracle RAC using response files
- Performing a phased upgrade of SF Oracle RAC
- Performing a phased upgrade of SF Oracle RAC from version 6.2.1 and later release
- Performing a rolling upgrade of SF Oracle RAC
- Upgrading SF Oracle RAC using Live Upgrade or Boot Environment upgrade
- Performing post-upgrade tasks
- Section IV. Installation and upgrade of Oracle RAC
- Before installing Oracle RAC
- Preparing to install Oracle RAC using the SF Oracle RAC installer or manually
- Creating users and groups for Oracle RAC
- Creating storage for OCR and voting disk
- Configuring private IP addresses for Oracle RAC 11.2.0.1
- Configuring private IP addresses for Oracle RAC 11.2.0.2 and later versions
- Installing Oracle RAC
- Performing an automated Oracle RAC installation
- Performing Oracle RAC post-installation tasks
- Configuring the CSSD resource
- Relinking the SF Oracle RAC libraries with Oracle RAC
- Configuring VCS service groups for Oracle RAC
- Upgrading Oracle RAC
- Before installing Oracle RAC
- Section V. Adding and removing nodes
- Adding a node to SF Oracle RAC clusters
- Adding a node to a cluster using the Veritas InfoScale installer
- Adding the node to a cluster manually
- Setting up the node to run in secure mode
- Configuring server-based fencing on the new node
- Preparing the new node manually for installing Oracle RAC
- Adding a node to the cluster using the SF Oracle RAC response file
- Configuring private IP addresses for Oracle RAC 11.2.0.2 and later versions on the new node
- Removing a node from SF Oracle RAC clusters
- Adding a node to SF Oracle RAC clusters
- Section VI. Configuration of disaster recovery environments
- Configuring disaster recovery environments
- Configuring disaster recovery environments
- Section VII. Installation reference
- Appendix A. Installation scripts
- Appendix B. Tunable files for installation
- Appendix C. Sample installation and configuration values
- SF Oracle RAC worksheet
- Appendix D. Configuration files
- Sample configuration files
- Sample configuration files for CP server
- Appendix E. Configuring the secure shell or the remote shell for communications
- Appendix F. Automatic Storage Management
- Appendix G. Creating a test database
- Appendix H. High availability agent information
- About agents
- CVMCluster agent
- CVMVxconfigd agent
- CVMVolDg agent
- CFSMount agent
- CFSfsckd agent
- PrivNIC agent
- MultiPrivNIC agent
- CSSD agent
- VCS agents for Oracle
- Oracle agent functions
- Resource type definition for the Oracle agent
- Resource type definition for the Netlsnr agent
- Resource type definition for the ASMDG agent
- Oracle agent functions
- CRSResource agent
- Appendix I. SF Oracle RAC deployment scenarios
- Configuration diagrams for setting up server-based I/O fencing
Configuring disk-based I/O fencing using installer
Note:
The installer stops and starts SF Oracle RAC to complete I/O fencing configuration. Make sure to unfreeze any frozen VCS service groups in the cluster for the installer to successfully stop SF Oracle RAC.
To set up disk-based I/O fencing using the installer
- Start the installer with -fencing option.
# /opt/VRTS/install/installer -fencing
The installer starts with a copyright message and verifies the cluster information.
Note the location of log files which you can access in the event of any problem with the configuration process.
- Enter the host name of one of the systems in the cluster.
- Confirm that you want to proceed with the I/O fencing configuration at the prompt.
The program checks that the local node running the script can communicate with remote nodes and checks whether SF Oracle RAC 7.4.1 is configured properly.
Review the I/O fencing configuration options that the program presents. Type 2 to configure disk-based I/O fencing.
1. Configure Coordination Point client based fencing 2. Configure disk based fencing 3. Configure fencing in disabled mode Select the fencing mechanism to be configured in this Application Cluster [1-3,q.?] 2
- Review the output as the configuration program checks whether VxVM is already started and is running.
If the check fails, configure and enable VxVM before you repeat this procedure.
If the check passes, then the program prompts you for the coordinator disk group information.
- Choose whether to use an existing disk group or create a new disk group to configure as the coordinator disk group.
The program lists the available disk group names and provides an option to create a new disk group. Perform one of the following:
To use an existing disk group, enter the number corresponding to the disk group at the prompt.
The program verifies whether the disk group you chose has an odd number of disks and that the disk group has a minimum of three disks.
To create a new disk group, perform the following steps:
Enter the number corresponding to the Create a new disk group option.
The program lists the available disks that are in the CDS disk format in the cluster and asks you to choose an odd number of disks with at least three disks to be used as coordinator disks.
Veritas recommends that you use three disks as coordination points for disk-based I/O fencing.
If the available VxVM CDS disks are less than the required, installer asks whether you want to initialize more disks as VxVM disks. Choose the disks you want to initialize as VxVM disks and then use them to create new disk group.
Enter the numbers corresponding to the disks that you want to use as coordinator disks.
Enter the disk group name.
- Verify that the coordinator disks you chose meet the I/O fencing requirements.
You must verify that the disks are SCSI-3 PR compatible using the vxfentsthdw utility and then return to this configuration program.
- After you confirm the requirements, the program creates the coordinator disk group with the information you provided.
- Verify and confirm the I/O fencing configuration information that the installer summarizes.
Review the output as the configuration program does the following:
Stops VCS and I/O fencing on each node.
Configures disk-based I/O fencing and starts the I/O fencing process.
Updates the VCS configuration file main.cf if necessary.
Copies the /etc/vxfenmode file to a date and time suffixed file /etc/vxfenmode-date-time. This backup file is useful if any future fencing configuration fails.
Updates the I/O fencing configuration file /etc/vxfenmode.
Starts VCS on each node to make sure that the SF Oracle RAC is cleanly configured to use the I/O fencing feature.
- Review the output as the configuration program displays the location of the log files, the summary files, and the response files.
- Configure the Coordination Point Agent.
Do you want to configure Coordination Point Agent on the client cluster? [y,n,q] (y)
- Enter a name for the service group for the Coordination Point Agent.
Enter a non-existing name for the service group for Coordination Point Agent: [b] (vxfen) vxfen
- Set the level two monitor frequency.
Do you want to set LevelTwoMonitorFreq? [y,n,q] (y)
- Decide the value of the level two monitor frequency.
Enter the value of the LevelTwoMonitorFreq attribute: [b,q,?] (5)
Installer adds Coordination Point Agent and updates the main configuration file.
- Enable auto refresh of coordination points.
Do you want to enable auto refresh of coordination points if registration keys are missing on any of them? [y,n,q,b,?] (n)