Skip Navigation Links | |
Exit Print View | |
Oracle Solaris Cluster Data Service for Oracle Real Application Clusters Guide Oracle Solaris Cluster |
1. Installing Support for Oracle RAC
Overview of the Installation Process for Support for Oracle RAC
Preinstallation Considerations
Hardware and Software Requirements
Oracle Solaris Cluster Framework Requirements
Supported Topology Requirements
Patch Installation Requirements
Storage Management Requirements for Oracle Files
Overview of Storage Management Schemes for Oracle Files
Storage Management Requirements for Oracle Clusterware Disks
Storage Management Requirements for the Oracle Clusterware Binaries
Storage Management Requirements for the Oracle RAC Database
Using Local Disks for Oracle Binary Files and Oracle Configuration Files
Using a Shared File System for Oracle Binary Files and Oracle Configuration Files
Storage Management Schemes Supported by Zone Clusters
SPARC: Processor Architecture Requirements for Oracle Components
Preparing the Oracle Solaris Cluster Nodes
How to Bypass the NIS Name Service
How to Create the DBA Group and the DBA User Accounts
How to Configure Shared Memory for Oracle RAC Software in the Global Cluster
How to Configure Shared Memory for Oracle RAC Software in a Zone Cluster
How to Set the Necessary Privileges for Oracle RAC Software in a Zone Cluster
Installing the Support for Oracle RAC Packages
How to Install the Support for Oracle RAC Packages
SPARC: How to Install the UDLM
2. Configuring Storage for Oracle Files
3. Registering and Configuring the Resource Groups
4. Enabling Oracle RAC to Run in a Cluster
5. Administering Support for Oracle RAC
6. Troubleshooting Support for Oracle RAC
7. Modifying an Existing Configuration of Support for Oracle RAC
8. Upgrading Support for Oracle RAC
A. Sample Configurations of This Data Service
B. Preset Actions for DBMS Errors and Logged Alerts
Oracle Real Application Clusters (Oracle RAC) is an application that can run on more than one machine concurrently. Oracle RAC can run either in the global-cluster voting nodes of the global cluster or in a zone cluster. An Oracle RAC installation is entirely contained within one cluster, either a global cluster or a specific zone cluster. Keeping the Oracle RAC installation in one cluster ensures the support of multiple independent Oracle RAC installations concurrently, where each Oracle RAC installation can be of a different version or use different options, such as storage. Support for Oracle RAC enables you to run Oracle RAC on Oracle Solaris Cluster nodes and to manage Oracle RAC by using Oracle Solaris Cluster commands.
Configuring this data service involves configuring resources for the following components of an Oracle RAC installation with Oracle Solaris Cluster software:
The Oracle RAC framework. These resources enable Oracle RAC to run with Oracle Solaris Cluster software. The resources also enable reconfiguration parameters to be set by using Oracle Solaris Cluster commands. You must configure resources for the Oracle RAC framework. For more information, see Registering and Configuring the Oracle RAC Framework Resource Group.
Storage for Oracle files. These resources provide fault monitoring and automatic fault recovery for volume managers and file systems that store Oracle files. Configuring storage resources for Oracle files is optional. For more information, see Registering and Configuring Storage Resources for Oracle Files.
Oracle RAC database instances. The features that these resources provide depend on the version of Oracle that you are using:
Oracle 10g release 2, 11g, and 12c. These resource types enable Oracle Clusterware and Oracle Solaris Cluster software to interoperate. These resource types do not provide fault monitoring and automatic fault recovery for Oracle Solaris Cluster 10g release 2, 11g, or 12c. The Oracle Clusterware software provides this functionality. This statement is not applicable to Oracle 10g release 1.
Do not use Solaris project resource properties and resource-group properties with Oracle Solaris Cluster resource types for Oracle RAC 10g, 11g, or 12c. The proxy resource does not directly start the database instance. Instead, Oracle Clusterware starts the database instances, and Solaris Resource Manager abstractions do not work with these versions of Oracle RAC.
Note - Unless otherwise stated, instructions and information for Oracle 11g apply to both Oracle 11g release 1 and Oracle 11g release 2.
Oracle 9i. These resource types provide fault monitoring and automatic fault recovery for Oracle RAC. The automatic fault recovery that these resource types provide supplements the automatic fault recovery that the Oracle RAC software provides.
Use Solaris project resource properties and resource group properties only with Oracle Solaris Cluster resource types for Oracle 9i RAC. For Oracle 9i RAC, if you put the Oracle RAC server resource group under the control of a specific project, for example Oracle, all databases are started under the control of that project.
Configuring resources, which enable Oracle Solaris Cluster software to administer Oracle RAC database instances, is optional. For more information, see Configuring Resources for Oracle RAC Database Instances.
Note - When you use Oracle RAC in a zone cluster, ensure that the zone cluster is not configured with the /opt directory as an inherited read-only directory. For an Oracle RAC configuration in a zone cluster, the /opt file system must be writable and unique to each zone. If the zone cluster that you intended to use for Oracle RAC is configured with an inherit-pkg-dir resource for the /opt directory, destroy and recreate the zone cluster or create a new zone cluster to meet this requirement.
If your application deployment requires the zone cluster nodes to be accessible from the public network at their host names or to have concurrent outbound traffic from each node, you must have a fixed public network address for each zone cluster node. Examples of such deployments include running RAC in zone clusters or applications using the scalable services (the SharedAddress resource) in the zone clusters.
The following sections contain additional preinstallation information:
Before you begin the installation, note the hardware and software requirements in the subsections that follow.
Support for Oracle RAC requires a functioning cluster with the initial cluster framework already installed. See Oracle Solaris Cluster Software Installation Guide for details about initial installation of cluster software.
Verify that you have obtained and installed the appropriate licenses for your software. If you install your licenses incorrectly or incompletely, the nodes might fail to boot correctly.
For example, if you are using VxVM with the cluster feature, verify that you have installed a valid license for the Volume Manager cluster feature by running the vxlicrep command.
Check with a Sun Enterprise Services representative for the current supported topologies for Support for Oracle RAC, cluster interconnect, storage management scheme, and hardware configurations.
Ensure that you have installed all the applicable software patches for the Solaris OS, Oracle Solaris Cluster, Oracle, and volume manager software. If you need to install any Support for Oracle RAC patches, you must apply these patches after you install the data service packages.
This section provides the following information about storage management for Oracle RAC:
Storage Management Requirements for Oracle Clusterware Disks
Storage Management Requirements for the Oracle Clusterware Binaries
Support for Oracle RAC enables you to use the storage management schemes for Oracle files that are listed in the following table. The table summarizes the types of Oracle files that each storage management scheme can store. Ensure that you choose a combination of storage management schemes that can store all types of Oracle files.
The meaning of each symbol in the table is as follows:
Indicates that the storage management scheme can store the type of Oracle file.
Indicates that the storage management scheme cannot store the type of Oracle file.
Indicates that, starting with Oracle 11g release 2, the storage management scheme cannot store the type of Oracle file. However, for Oracle versions 11g release 1 and before, the storage management scheme can store the type of Oracle file.
Indicates that, starting with Oracle 12c, the storage management scheme can store the type of Oracle file. But for Oracle versions before 12c, the storage management scheme cannot store the type of Oracle file.
Table 1-2 Storage Management Schemes for Oracle Files
|
1The fast recovery area cannot reside on a cluster file system because this set of files includes online redo logs.
Note - Some types of files are not included in all releases of Oracle RAC. For information about which types of file are included in the release that you are using, see your Oracle documentation.
Oracle Clusterware disks such as Oracle cluster registry (OCR) and voting disks are supported on the following storage management schemes:
Solaris Volume Manager for Sun Cluster
Veritas Volume Manager (VxVM)
Note - VxVM is supported only on the SPARC platform.
Hardware redundant array of independent disks (RAID) support
Sun QFS shared file systems with hardware RAID support or with Solaris Volume Manager for Sun Cluster
Qualified network-attached storage (NAS) devices
You can use the following storage management schemes for the Oracle Clusterware binaries:
Solaris Volume Manager for Sun Cluster
Veritas Volume Manager (VxVM) with the cluster feature
Note - VxVM is supported only on the SPARC platform.
Hardware redundant array of independent disks (RAID) support
Sun QFS shared file system with hardware RAID support or with Solaris Volume Manager for Sun Cluster
Qualified network-attached storage (NAS) devices
Oracle Automatic Storage Management (Oracle ASM)
Note - For 11g release 2 and 12c, Oracle ASM is only supported with hardware RAID. The use of Oracle ASM disk groups on devices that are managed by volume managers is not supported with version 11g release 2 or 12c.
You can install the Oracle RAC database on one of the following locations.
The local disks of each cluster node. See Using Local Disks for Oracle Binary Files and Oracle Configuration Files for additional information.
A shared file system from the following list:
Note - Beginning with Oracle version 11g release 2, Oracle Clusterware binaries can no longer reside on a PXFS-based cluster file system, an Oracle ACFS file system, or a Sun QFS shared file system.
A Sun QFS shared file system
A PxFS-based cluster file system
An Oracle ACFS file system
A file system on a qualified NAS device
See Using a Shared File System for Oracle Binary Files and Oracle Configuration Files for additional information.
Placing the Oracle binary files and Oracle configuration files on the individual cluster nodes enables you to upgrade the Oracle application later without shutting down the data service.
Note - Some versions of Oracle require you to shut down the data service during an upgrade. To determine whether you can upgrade the Oracle application without shutting down the data service, see your Oracle documentation.
The disadvantage is that you then have several copies of the Oracle application binary files and Oracle configuration files to maintain and administer.
To simplify the maintenance of your Oracle installation, you can install the Oracle binary files and Oracle configuration files on a shared file system.
Note - Beginning with Oracle version 11g release 2, Oracle Clusterware binaries cannot reside on a cluster file system or a Sun QFS shared file system.
The following shared file systems are supported:
A Sun QFS shared file system
A PxFS-based cluster file system
If you use a PxFS-based cluster file system, decide which volume manager to use:
Solaris Volume Manager
VxVM without the cluster feature
Note - VxVM is supported only on the SPARC platform.
An Oracle ACFS file system
A file system on a qualified NAS device
If you put the Oracle binary files and Oracle configuration files on a shared file system, you have only one copy to maintain and manage. However, you must shut down the data service in the entire cluster to upgrade the Oracle application. If a short period of downtime for upgrades is acceptable, place a single copy of the Oracle binary files and Oracle configuration files on a shared file system.
You can use the following storage management schemes for running Oracle RAC in a zone cluster, depending on the version of Oracle RAC you are running.
If you are using Oracle RAC 10g, Oracle RAC 11g, or Oracle RAC 12c, the following storage management schemes are supported:
A Sun QFS shared file system with Solaris Volume Manager
A Sun QFS shared file system with hardware RAID support
Solaris Volume Manager for Sun Cluster
A file system on a qualified NAS device with fencing
If you are using Oracle RAC 9i, the following storage management schemes are supported:
A Sun QFS shared file system with Solaris Volume Manager
A Sun QFS shared file system with hardware RAID support
Solaris Volume Manager for Sun Cluster
A file system on a qualified NAS device with fencing
Before you decide which architecture to use for the UDLM (SPARC) and the Oracle relational database management system (RDBMS), note the following points.
The architecture of both Oracle components must match. For example, if you have 64-bit architecture for your UDLM, you must have 64-bit architecture for your RDBMS.
If you have 32-bit architecture for your Oracle components, you can boot the node on which the components reside in either 32-bit mode or 64-bit mode. However, if you have 64-bit architecture for your Oracle components, you must boot the node on which the components reside in 64-bit mode.
You must use the same architecture when you boot all the nodes. For example, if you boot one node to use 32-bit architecture, you must boot all the nodes to use 32-bit architecture.
You can use Support for Oracle RAC with Oracle Data Guard. To configure Support for Oracle RAC with Oracle Data Guard, perform the tasks in this guide. The tasks for clusters that are to be used in an Oracle Data Guard configuration are identical to the tasks for a standalone cluster.
For information about the installation, administration, and operation of Oracle Data Guard, see your Oracle documentation.