InfoScale™ 9.0 Storage Foundation for Oracle® RAC Configuration and Upgrade Guide - Linux
- 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 7.3.1 and later release
- Performing a rolling upgrade of SF Oracle RAC
- Upgrading SF Oracle RAC using YUM
- Upgrading Volume Replicator
- Performing post-upgrade tasks
- Section IV. Installation 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
- 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 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
- 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
- Appendix J. Configuring LLT over UDP
- Using the UDP layer for LLT
- Manually configuring LLT over UDP using IPv4
- Using the UDP layer of IPv6 for LLT
- Manually configuring LLT over UDP using IPv6
- About configuring LLT over UDP multiport
- Appendix K. Using LLT over RDMA
- Configuring LLT over RDMA
- Configuring RDMA over an Ethernet network
- Configuring RDMA over an InfiniBand network
- Tuning system performance
- Manually configuring LLT over RDMA
- Troubleshooting LLT over RDMA
About SF Oracle RAC upgrade support using YUM
SF Oracle RAC version 9.0 introduces support for a new upgrade method using the Yellow-Dog Updater Modified (YUM) tool. This method is designed to work along with the operating system (OS) minor version upgrades and application upgrades. The YUM upgrade method uses a single node reboot to complete the upgrade process, with no application downtime or a need to evacuate the Cluster Server (VCS) resource, if applicable.
The YUM upgrade method is an additional way to upgrade SF Oracle RAC. This method does not require the use of the SF Oracle RAC installer. The other upgrade methods, for example with the Common Product Installer (CPI), continue to be supported.
Consider the following requirements and limitations before you use YUM to upgrade SF Oracle RAC:
YUM support for SF Oracle RAC upgrade is available on the RHEL platform only.
Upgrades are supported for SF Oracle RAC version 8.x to 9.x only.
Upgrades for older SF Oracle RAC versions (7.4.x onward) are not supported using the YUM tool.
Rollback (yum history rollback and yum history undo) is not supported.
Rolling or full upgrades are supported with this method.
The Dandified YUM (DNF) is a successor to YUM and uses a similar command structure. The upgrade process that is described here works with both YUM and the DNF commands.
In a pre-reboot phase where you have run the yum update command but have not yet rebooted the node, SF Oracle RAC continues to work as the previous version. New features and functionality of the upgraded SF Oracle RAC version are not available.
The pre-reboot phase may also enforce other restrictions. For example, you cannot update the VxVM tunables.
If the following services are not running before you run the yum update command, then ensure that you do not restart these services before a node reboot (during the pre-reboot phase):
vxfs service
vxodm service
vxgms service
vxglm service
veki service
All Secure File System (SecureFS) and VFR scheduled jobs are skipped for the time duration that it takes for the yum update command to complete. After the update process is complete, the jobs resume and run as per the configured schedule.