Run the command as follows,
substituting a list of your cluster??™s node names for oc1,oc2,oc3:
./runcluvfy.sh stage -pre crsinst -n oc1,oc2,oc3 -verbose
The CRS software on the CD or DVD or in the downloadable installation archive is approximately
250MB. After you mount the CD or expand the ZIP file, run the script ./runInstaller as the oracle
user. The first screen you will see after the welcome screen and the Oracle inventory location
screen is shown in Figure 10-2.
?–
?–
?–
?–
?–
Chapter 10: Real Application Clusters 361
The installation for CRS is similar to that for a database install; you specify a home directory
for the executables. In this case, you will use a home directory variable called CRS_HOME (with
a default OUI name of OraCrs11g_home and a pathname of /u01/app/11.1.0/crs), which must be
different from the Oracle Database home.
After OUI performs a number of prerequisite checks, such as memory, network connectivity,
and old versions of CRS, you provide a name for the cluster along with the public, private, and
virtual node names. As you can see in Figure 10-3, you specify the cluster name as shc1 and
provide the public and private node names as defined in the /etc/hosts file I provided earlier in
this chapter. If you plan to manage multiple clusters using Enterprise Manager Grid Control, be
sure to assign a unique name to each cluster.
On the next installation screen, shown in Figure 10-4, you specify which of your network
devices is to be used as the public interface (to connect to the public network) and which will
be used for the private interconnect to support cache fusion and the cluster heartbeat.
Pages:
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582