This is an excerpt from the bestselling book
Oracle Grid & Real Application Clusters. To get immediate
access to the code depot of working RAC scripts, buy it
directly from the publisher and save more than 30%.
In order to install the CRS,
ensure that the nodes have user equivalence. Use rsh or rlogin to
test the user equivalence for the account used to install. Usually
oracle is the UNIX user account that is used for installation.
In addition to the host
machine's public internet protocol (IP) address, obtain two or more
IP addresses for each node that is going to be part of the
installation for the purpose of VIP. One of the IP addresses must be
a public IP address and another for the node's virtual IP address
(VIP). Oracle uses VIPs for client-to-database connections.
Therefore, the VIP address must be publicly accessible. The other
address must be a private IP address for inter node, or
instance-to-instance Cache Fusion traffic. Using public interfaces
for Cache Fusion can cause performance problems.
In case of Sun Clusters, install
the Oracle-provided UDLM patch onto each node. Install the UDLM
patch before installing Cluster Ready Services. Even with a
pre-Oracle Database 10g UDLM, install the Oracle Database 10g UDLM.
To explain the CRS installation
process, the following example will be used. A 3 Node Linux Cluster
will be referenced that is fitted with polyserve cluster file
If installing CRS on a node that
already has a single-instance Oracle Database 10g installation, and
the ASM instance is running, stop the ASM and CSS daemon by running
the $ORACLE_HOME/bin/localconfig delete in the home that is running
Cluster Synchronization Services (CSS) to reset the OCR
After CRS is installed, then
start up the ASM instances again and the ASM instances will use the
cluster CSS daemon instead of the earlier daemon of the
single-instance Oracle database. The following steps describe the
CRS installation process.
1. Launch the Oracle Universal
Installer by using runInstaller command from the /crs subdirectory
on the Oracle Cluster Ready Services Release 1 (10.1.0.2) CDROM. A
welcome page is displayed as shown below:
Figure 6.5: Oracle Universal
Installer Welcome Page
2. Next, Select the inventory
directory and specify the operating system group name, which is
usually the dba. Then execute the orainstRoot.sh script with root
privilege as shown in Figure 6.6
Figure 6.6: Inventory Selection
3. Next, the Specify Location
Page, as shown in Figure 6.7, will be shown. Ensure that the source
points to the software location, which is either the software CD
directory or the location of the directory where the software is
copied. Also specify the CRS Home Name and its location. Cluster
Ready Services should be installed in a separate Oracle Home, which
is different from the RAC Database Oracle Home. The CRS home
directory is the directory where the software for Oracle Cluster
Ready Services should be installed.
Figure 6.7: CRS Home Location
4. Make the language selection
in the next step. After that, provide a Cluster Name and also the
private and public host names for the nodes in the cluster. In this
example, Cluster Name is specified as PROD and public node names are
shown as node1, node2 and node3. Private host names are shown as
rac1-2, rac2-2 and rac3-2. Oracle uses the private Network for Cache
Fusion block transfers and inter-node messages. Also note that the
Cluster Configuration Information page, shown in Figure 6.8,
contains pre-defined node information if the OUI detects that the
system has vendor clusterware.
Figure 6.8: Cluster
5. On the next page, identify
the interfaces to use as private interconnect. In this example, eth2
has been provided as the private interconnect interface.
Figure 6.9: Private Interconnect
6. Next, the Cluster Registry
Location Information page is shown. Enter the complete path for the
raw device or shared file system file for the Oracle Cluster
Registry (OCR). In this example, /mnt/ps/db/ocr has been entered and
is located on a cluster file system. The OCR stores the cluster
nodes information as shown in Figure 6.10. This file should be about
100MB. In this installation, the Polyserve Cluster file system has
been used and the OCR file has been pre-created as shown below.
Figure 6.10: Oracle Cluster
Note that at the time of writing
of this book, OCFS does not support the CRS files. The CRS files can
be located on the following: 1) RAW device. 2) Any Cluster File
system other than OCFS. 3) NFS file system on a certified NAS
device. However, this situation may change with OCFS Rel 2.0
7. Next, the Voting Disk
Information page appears as shown in Figure 6.11. CSS Voting Disk is
used to arbitrate the ownership of the cluster nodes in the event of
split-brain syndrome. Voting disk is same as the quorum disk, a more
familiar term. Voting Disk needs to reside either on a cluster file
system or on a shared raw disk. In this installation, a voting disk
file css_voting_disk has been pre-created and specified in the
voting disk page.
Figure 6.11: Select the CSS
Note that the storage size for
the OCR should be at least 100MB and the storage size for the voting
disk should be at least 20MB.
8. Next, the OUI displays a
dialog asking that the orainstRoot.sh script be run on all of the
nodes. After the orainstRoot.sh script processing completes, the OUI
displays a Summary page as shown in Figure 6.12.
Figure 6.12: Summary Page for