NOTE: A NOTE indicates important information that helps you make better use ofyour computer.CAUTION: A CAUTION indicates potential damage to hardware or loss of data if instructions are not followed.
This document applies to Oracle Database 11g R2 running on Red Hat Enterprise Linux 5.x AS x86_64 or Oracle Enterprise Linux 5.x AS x86_64. To download a copy of this article please visit:
NOTE: PDF document not available until July 29th 2011.
The following table describes the disk space required for an Oracle installation:
[top]Operating System Requirements
Attaching to RHN/ULN Repository
NOTE: The documentation provided below discusses how to setup a local yum repository using your operating system installation media. If you would like to connect to the RHN/ULN channels, see the appropriate documentation. For Red Hat see, redhat.com/red_hat_network. For information relating to ULN network see, linux.oracle.com.
The recommended configuration is to serve the files over http using an Apache server (package name: httpd). This section discusses hosting the repository files from a local filesystem storage. While other options to host repository files exist, they are outside of the scope of this document. It is highly recommended to use local filesystem storage for speed and simplicity of maintenance.
Once your nodes have attached to the appropriate yum repository, we will need to install the Dell Validated RPM package. The Dell Validated RPM package automates certain pieces of the installation process required for the installation of Oracle RAC.
The process to install the Dell Validated RPM package is as follows:
The Dell Oracle utilities RPM is designed to do the following Dell and Oracle recommended settings:
The process to install the Dell Oracle utilities RPM is as follows:
NOTE: The Dell-Oracle-Deplyoment tar contains the latest supported drivers provided from our Software Deliverable List (SDL). Consult the README file found within the Dell-Oracle-Deployment tar for installation instructions of the latest drivers.[top]
Oracle Software Binary Location
The Oracle software binaries should be located on node 1 of your cluster. It is important to note that starting with Oracle 11g R2 (220.127.116.11), Oracle Database patch sets are full installation of the Oracle software. For more information on how this impacts future Oracle deployments, see My Oracle Support note: 1189783.1 Important Changes to Oracle Database Patch Sets Starting with 18.104.22.168.[top]
NOTE: Ensure that the public IP address is a valid and routable IP address.To configure the public network on each node:
NOTE: Each of the two NIC ports for the private network must be on separate PCI buses.
The grid infrastructure of Oracle 11gR2 (22.214.171.124) supports IP failover natively using a new feature introduced known as Redundant Interconnect. Oracle uses its ora.cluster_interconnect.haip resource to communicate with Oracle RAC, Oracle ASM, and other related services. The Highly Available Internet Protocol (HAIP) has the ability to activate a maximum of four private interconnect connections. These private network adapters can be configured during the initial install process of Oracle Grid or after the installation process using the oifcfg utility.
Oracle Grid currently creates an alias IP (as known as virtual private IP) on your private network adapters using the 169.254.*.* subnet for the HAIP. If subnet range is already in use, Oracle Grid will not attempt to use it. The purpose of HAIP is to load balance across all active interconnect interfaces, and failover to other available interfaces if one of the existing private adapters becomes unresponsive.
- Configure different subnet for each of the private network you want to configure as a part of HAIP
- When adding additional HAIP addresses (maximum of four) after the installation of Oracle Grid, restart of your Oracle Grid environment to make these new HAIP addresses active.
The example below provides step-by-step instructions on enabling redundant interconnect using HAIP on a fresh Oracle 11gR2 (126.96.36.199) Grid Infrastructure installation.
IP Address and Name Resolution Requirements
The steps below show how to setup your cluster nodes for using Domain Name System (DNS). For information on how to setup cluster nodes using GNS, see the wiki article http://en.community.dell.com/dell-groups/enterprise_solutions/w/oracle_solutions/1416.aspx
For a Cluster Using DNSTo set up an Oracle 11g R2 RAC using Oracle DNS (without GNS):
Configuring a DNS Server
To configure changes on a DNS server for an Oracle 11g R2 cluster using a DNS (without GNS):
Configuring a DNS Client
NOTE: In this section, the terms disk(s), volume(s), virtual disk(s), LUN(s) mean the same and are used interchangeably, unless specified otherwise. Similarly, the terms Stripe Element Size and Segment Size both can be used interchangeably.Oracle RAC requires shared LUNs for storing your Oracle Cluster Registry (OCR), voting disks, Oracle Home using ACFS, Oracle Database files, and Flash Recovery Area (FRA). To ensure high availability for Oracle RAC it is recommended that you have:
NOTE: The use of device mapper multipath is recommended for optimal performance and persistent name binding across nodes within the cluster.NOTE: For more information on attaching shared LUNs/volumes, see the Wiki documentation found at: http://en.community.dell.com/dell-groups/enterprise_solutions/w/oracle_solutions/3-storage.aspx[top]
Partitioning the Shared Disk
This section describes how to use Linux’s native partition utility fdisk to create and align a single partition on a volume/virtual disk that spans the entire disk.
CAUTION: In a system running the Linux operating system, align the disk prior to being written to the Volume/Virtual Disk (VD). Failure to do so will cause all data on the disk to be destroyed.
To use the fdisk utility to create a partition and set the alignment:
To use the fdisk utility to adjust a disk partition, do the following steps:
NOTE: This article assumes that the disk to be aligned already contains a single primary partition. If you want to create a partitioning, follow the steps in "Partitioning the Shared Disk".
CAUTION: In a system running the Linux operating system, align the partition table before the data is written to the Volume. Failure to follow the precaution could lead to all the data on the Volume to be destroyed.
At the command prompt, type:
Using ASMLib to Mark the Shared Disks as Candidate Disks
This section gives you the installation information of Oracle 11g R2 grid infrastructure for a cluster.
Before You Begin
Before you install the Oracle 11g R2 RAC software on your system:
Configure the System Clock Settings for All Nodes
To prevent failures during the installation procedure, configure all the nodes with identical system clock settings. Synchronize your node system clock with the Cluster Time Synchronization Service (CTSS) which is built in Oracle 11g R2. To enable CTSS, disable the operating system network time protocol daemon (ntpd) service using the following commands in this order:
Configuring Node One
The following steps are for node oneof your cluster environment, unless otherwise specified.
NOTE: If no candidate disks are displayed, click Change Discovery Path and enter ORCL:*or /dev/oracleasm/disks/*. Ensure that you have marked your Oracle ASM disks, for more informations see,"Using ASMLib to Mark the Shared Disks as Candidate Disks".
The following steps are applicable for node 1 of your cluster environment, unless otherwise specified:
The following steps are for node 1 of your cluster environment, unless otherwise specified.
This section contains procedures to create the ASM disk group for the database files and Flashback Recovery Area (FRA).
under Partitioning the Shared Disk, step 1.d, what is the default for Compellent storage?
I moved on and accepted all defaults for compellent storage, probably not optimal, but got me to keep going, now looking at "Using ASMLib to Mark the Shared Disks as Candidate Disks", somewhere permissions have to be set appropriately for the /dev/mapper devices. In previous versions of the dell validated release it was all done in the permissions.py and permissions.ini files. Those don't seem to exist any longer.