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
Step 2: Upgrading the first half of the cluster
Perform the following steps to upgrade the first half of the cluster.
To upgrade the first half of the cluster
- If you plan to upgrade the operating system, rename the
/etc/llttab
file to prevent LLT from starting automatically when the node starts:# mv /etc/llttab /etc/llttab.save
- Upgrade the operating system, if required.
For instructions, see the operating system documentation.
- If you upgraded the operating system, restart the nodes if required:
# shutdown -g0 -y -i6
You may see some errors in the system log file when the nodes restart. This is because LLT is disabled. Ignore these messages.
svc.startd[7]: [ID 652011 daemon.warning] svc:/system/llt:default: Method "/lib/svc/method/llt start" failed with exit status 2. gab: [ID 438192 kern.notice] GAB WARNING V-15-1-20115 Port d registration failed, GAB not configured
- After you finish upgrading the operating system, change the LLT configuration to its original configuration.
# mv /etc/llttab.save /etc/llttab
- Make sure that you can run secure shell or remote shell from the node where you launched the installer to the nodes in the second subcluster without requests for a password.
- Upgrade SF Oracle RAC using the product installer. Navigate to the product directory on the installation media. When you invoke the installer, select the Full Upgrade option. The installer automatically detects the phased upgrade though you select the Full Upgrade option.
# cd product image folder
# cd /dvd_mount/
Using the product installer:
# ./installer -upgrade sys1 sys2
At this point, you may see the following installer prompt:
1) Relink Oracle Database Binary 2) Exit SF Oracle RAC Configuration
It is recommended that you choose to exit the configuration.
For Solaris Zone environments: Additionally, perform the following steps if Oracle RAC is installed in a non-global zone:
Take the zone service groups in the subcluster offline:
# hagrp -offline zone_group -sys sys_name
Update the zone configuration.
For instructions, see the topic "Preparing to install non-global zones" in the document Storage Foundation and High Availability Solutions Virtualization Guide.
From the global zone, run the following command for each non-global zone in the subcluster:
# zoneadm -z zone_name attach -u
Note:
After you complete the upgrade of the first half of the cluster, no GAB ports will be shown in the output when you run the gabconfig -a command.
- Change the
/etc/default/llt
file to prevent LLT from starting automatically after reboot by setting the LLT_START attribute to 0:LLT_START=0
- Restart the nodes:
# shutdown -g0 -y -i6
You may see some errors in the system log file when the nodes restart. This is because LLT is disabled. Ignore these messages.
svc.startd[7]: [ID 652011 daemon.warning] svc:/system/llt:default: Method "/lib/svc/method/llt start" failed with exit status 2. gab: [ID 438192 kern.notice] GAB WARNING V-15-1-20115 Port d registration failed, GAB not configured