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 the cluster name
- Configuring private heartbeat links
- Configuring the virtual IP of the cluster
- Configuring SF Oracle RAC in secure mode
- Configuring a secure cluster node by node
- Adding VCS users
- Configuring SMTP email notification
- Configuring SNMP trap notification
- Configuring global clusters
- Creation of SF Oracle RAC configuration files
- Stopping and starting SF Oracle RAC processes
- 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 SFDB
- Configuring the SF Oracle RAC components using the script-based installer
- Performing an automated SF Oracle RAC configuration
- Configuring SF Oracle RAC using response files
- Response file variables to configure SF Oracle RAC
- Sample response file for configuring SF Oracle RAC
- Configuring I/O fencing using response files
- Response file variables to configure disk-based I/O fencing
- Sample response file for configuring disk-based I/O fencing
- Configuring CP server using response files
- Response file variables to configure CP server
- Sample response file for configuring the CP server on SFHA cluster
- Response file variables to configure server-based I/O fencing
- Sample response file for configuring server-based I/O fencing
- 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
- About phased upgrade
- Performing a phased upgrade of SF Oracle RAC from version 6.2.1 and later release
- Step 1: Performing pre-upgrade tasks on the first half of the cluster
- Step 2: Upgrading the first half of the cluster
- Step 3: Performing pre-upgrade tasks on the second half of the cluster
- Step 4: Performing post-upgrade tasks on the first half of the cluster
- Step 5: Upgrading the second half of the cluster
- Step 6: Performing post-upgrade tasks on the second half of the cluster
- Performing a rolling upgrade of SF Oracle RAC
- Upgrading SF Oracle RAC using Live Upgrade or Boot Environment upgrade
- Performing post-upgrade tasks
- Relinking Oracle RAC libraries with the SF Oracle RAC libraries
- Setting or changing the product license level
- Resetting DAS disk names to include host name in FSS environments
- Upgrading disk layout versions
- CVM master node needs to assume the logowner role for VCS managed VVR resources
- Switching on Quotas
- Upgrading the disk group version
- Section IV. Installation and upgrade of Oracle RAC
- Before installing Oracle RAC
- Important preinstallation information for Oracle RAC
- About preparing to install Oracle RAC
- Preparing to install Oracle RAC using the SF Oracle RAC installer or manually
- Identifying the public virtual IP addresses for use by Oracle
- Setting the kernel parameters
- Verifying that packages and patches required by Oracle are installed
- Verifying the user nobody exists
- Launching the SF Oracle RAC installer
- 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
- Verifying that multicast is functional on all private network interfaces
- Creating Oracle Clusterware/Grid Infrastructure and Oracle database home directories manually
- Setting up user equivalence
- Verifying whether the Veritas Membership library is linked to Oracle libraries
- Installing Oracle RAC
- Performing an automated Oracle RAC installation
- Performing Oracle RAC post-installation tasks
- Adding Oracle RAC patches or patchsets
- Configuring the CSSD resource
- Preventing automatic startup of Oracle Clusterware/Grid Infrastructure
- Relinking the SF Oracle RAC libraries with Oracle RAC
- Creating the Oracle RAC database
- Configuring VCS service groups for Oracle RAC
- Preventing automatic database startup
- Removing existing PrivNIC or MultiPrivNIC resources
- Removing permissions for communication
- Upgrading Oracle RAC
- Before installing Oracle RAC
- Section V. Adding and removing nodes
- Adding a node to SF Oracle RAC clusters
- About adding a node to a cluster
- Before adding a node to a cluster
- Adding a node to a cluster using the Veritas InfoScale installer
- Adding the node to a cluster manually
- Starting Veritas Volume Manager (VxVM) on the new node
- Configuring cluster processes on the new node
- Setting up the node to run in secure mode
- Starting fencing on the new node
- After adding the new node
- Configuring server-based fencing on the new node
- Configuring Cluster Volume Manager (CVM) and Cluster File System (CFS) on the new node
- Configuring the ClusterService group for 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
- Adding the new node to Oracle RAC
- Adding nodes to a cluster that is using authentication for SFDB tools
- Updating the Storage Foundation for Databases (SFDB) repository after adding a node
- Sample configuration file for adding a node to the cluster
- Removing a node from SF Oracle RAC clusters
- About removing a node from a cluster
- Removing a node from a cluster
- Modifying the VCS configuration files on existing nodes
- Modifying the Cluster Volume Manager (CVM) configuration on the existing nodes to remove references to the deleted node
- Removing the node configuration from the CP server
- Removing security credentials from the leaving node
- Updating the Storage Foundation for Databases (SFDB) repository after removing a node
- Sample configuration file for removing a node from the cluster
- Adding a node to SF Oracle RAC clusters
- Section VI. Configuration of disaster recovery environments
- Configuring disaster recovery environments
- Disaster recovery options for SF Oracle RAC
- Hardware requirements for campus cluster
- Supported replication technologies for global clusters
- About setting up a campus cluster for disaster recovery
- About setting up a global cluster environment for SF Oracle RAC
- About configuring a parallel global cluster using Volume Replicator (VVR) for replication
- Configuring disaster recovery environments
- Section VII. Installation reference
- Appendix A. Installation scripts
- Appendix B. Tunable files for installation
- About setting tunable parameters using the installer or a response file
- Setting tunables for an installation, configuration, or upgrade
- Setting tunables with no other installer-related operations
- Setting tunables with an un-integrated response file
- Preparing the tunables file
- Setting parameters for the tunables file
- Tunables value parameter definitions
- Appendix C. Sample installation and configuration values
- About the installation and configuration worksheets
- SF Oracle RAC worksheet
- Oracle RAC worksheet
- Replicated cluster using VVR worksheet
- Replicated cluster using SRDF worksheet
- Required installation information for Oracle Clusterware/Grid Infrastructure
- Required installation information for Oracle database
- Appendix D. Configuration files
- About VCS configuration file
- About the LLT and GAB configuration files
- About I/O fencing configuration files
- Packaging related SMF services on Solaris 11
- Sample configuration files
- sfrac02_main.cf file
- sfrac03_main.cf file
- sfrac04_main.cf file
- sfrac05_main.cf file
- sfrac06_main.cf file
- sfrac07_main.cf and sfrac08_main.cf files
- sfrac09_main.cf and sfrac10_main.cf files
- sfrac11_main.cf file
- sfrac12_main.cf and sfrac13_main.cf files
- sfrac14_main.cf file
- sfrac15_main.cf and sfrac16_main.cf files
- sfrac17_main.cf file
- Sample configuration files for CP server
- Appendix E. Configuring the secure shell or the remote shell for communications
- About configuring secure shell or remote shell communication modes before installing products
- Manually configuring passwordless ssh
- Setting up ssh and rsh connection using the installer -comsetup command
- Setting up ssh and rsh connection using the pwdutil.pl utility
- Restarting the ssh session
- Enabling and disabling rsh for Solaris
- 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
- Managing high availability of private interconnects
- Functions of the MultiPrivNIC agent
- Required attributes of the MultiPrivNIC agent
- States of the MultiPrivNIC agent
- Sample service group configuration with the MultiPrivNIC agent
- Type definition of the MultiPrivNIC resource
- Sample configuration of the MultiPrivNIC resource
- CSSD agent
- VCS agents for Oracle
- Oracle agent functions
- Startup and shutdown options for the pluggable database (PDB)
- Recommended startup modes for pluggable database (PDB) based on container database (CDB) startup modes
- Monitor options for the Oracle agent in traditional database and container database
- Monitor for the pluggable database
- Info entry point for Cluster Server agent for Oracle
- Action entry point for Cluster Server agent for Oracle
- Resource type definition for the Oracle agent
- Netlsnr agent functions
- Resource type definition for the Netlsnr agent
- ASMDG agent functions
- Resource type definition for the ASMDG agent
- Oracle agent functions
- CRSResource agent
- Appendix I. SF Oracle RAC deployment scenarios
- SF Oracle RAC cluster with UDP IPC and PrivNIC agent
- SF Oracle RAC cluster for multiple databases with UDP IPC and MultiPrivNIC agent
- SF Oracle RAC cluster with isolated Oracle traffic and MultiPrivNIC agent
- SF Oracle RAC cluster with NIC bonding, UDP IPC, and PrivNIC agent
- Configuration diagrams for setting up server-based I/O fencing
Using Install Bundles to simultaneously install or upgrade full releases (base, maintenance, rolling patch), and individual patches
Beginning with version 6.2.1, you can easily install or upgrade your systems directly to a base, maintenance, patch level or a combination of multiple patches and packages together in one step using Install Bundles. With Install Bundles, the installer has the ability to merge so that customers can install or upgrade directly to maintenance or patch levels in one execution. The various scripts, packages, and patch components are merged, and multiple releases are installed together as if they are one combined release. You do not have to perform two or more install actions to install or upgrade systems to maintenance levels or patch levels.
Releases are divided into the following categories:
Table: Release Levels
Level | Content | Form factor | Applies to | Release types | Download location |
|---|---|---|---|---|---|
Base | Features | packages | All products | Major, minor, Service Pack (SP), Platform Release (PR) | FileConnect |
Maintenance | Fixes, new features | packages | All products | Maintenance Release (MR), Rolling Patch (RP) | Veritas Services and Operations Readiness Tools (SORT) |
Patch | Fixes | packages | Single product | P-Patch, Private Patch, Public patch | SORT, Support site |
When you install or upgrade using Install Bundles:
Veritas InfoScale products are discovered and assigned as a single version to the maintenance level. Each system can also have one or more patches applied.
Base releases are accessible from FileConnect that requires customer serial numbers. Maintenance and patch releases can be automatically downloaded from SORT.
Patches can be installed using automated installers from the 6.2.1 version or later.
Patches can now be detected to prevent upgrade conflict. Patch releases are not offered as a combined release. They are only available from Veritas Technical Support on a need basis.
You can use the -base_path and -patch_path options to import installation code from multiple releases. You can find packages and patches from different media paths, and merge package and patch definitions for multiple releases. You can use these options to use new task and phase functionality to correctly perform required operations for each release component. You can install the packages and patches in defined phases using these options, which helps you when you want to perform a single start or stop process and perform pre and post operations for all level in a single operation.
Four possible methods of integration exist. All commands must be executed from the highest base or maintenance level install script.
In the example below:
7.4.1 is the base version
7.4.1.1 is the maintenance version
7.4.1.1.100 is the patch version for 7.4.1.1
7.4.1.0.100 is the patch version for 7.4.1
Base + maintenance:
This integration method can be used when you install or upgrade from a lower version to 7.4.1.1.
Enter the following command:
# installmr -base_path <path_to_base>
Base + patch:
This integration method can be used when you install or upgrade from a lower version to 7.4.1.0.100.
Enter the following command:
# installer -patch_path <path_to_patch>
Maintenance + patch:
This integration method can be used when you upgrade from version 7.4.1 to 7.4.1.1.100.
Enter the following command:
# installmr -patch_path <path_to_patch>
Base + maintenance + patch:
This integration method can be used when you install or upgrade from a lower version to 7.4.1.1.100.
Enter the following command:
# installmr -base_path <path_to_base> -patch_path <path_to_patch>
Note:
From the 6.1 or later release, you can add a maximum of five patches using -patch_path <path_to_patch> -patch2_path <path_to_patch> ... -patch5_path <path_to_patch>