Installing Oracle 10g Release 2

Cluster Ready Services

Author: Dipak Sharma

Oracle Consultant

Attain IT

Sydney, Australia

www.attainit.com.au

 

 

 


Overview: 3

Oracle 10g Cluster Registry (CRS) Introduction: 3

New Feature with 10g R2 for CRS: 4

Installation: 6

References: 18


Overview:

This document describes the install procedure for Oracle 10g R2 CRS (Single Node Install) on Redhat ES 3. Please note this note is not a replacement to Oracle documentation.

 

Oracle 10g Cluster Registry (CRS) Introduction:

CRS is a complete Oracle Cluster software solution which is easy to install and manager. When outages occur CRS relocates a database service from an inoperative node to an operative node. Starting with 10g R2, redundancy for the clusterware and voting disk have been introduced.

 


New Feature with 10g R2 for CRS:

Many customers sometimes find that their installation for CRS failed and the causes could be because some pre-requisite steps were missed or not properly done. So as to avoid this issue, Oracle now provides Cluster Verification Utility (here on it will be referred to as CVU). This utility can be used to check that your environment is setup correctly, such as all required RPM’s are installed, kernel parameters are setup correctly, entries for public and private interfaces are configured, supported kernel is installed, there is sufficient swap space on the server, amount of physical memory, etc…

 

For more details on CVU please refer to documentation

This utility is on the CRS software CD, /mountpoint/cluvfy/

Name of this utility is runcluvfy.sh

 

To use this CVU utility you first need to install an RPM that comes as part of Oracle CRS Installation CD.  Name of this rpm is cvuqdisk-1.0.1-1.rpm, which is located on:

/mountpoint/rpm

 

Note: This pre-requisite is done by OUI; however, I prefer to run it anyway.

 

Before installing the CRS, run the following utility to check that all pre-requisites are met:

Performing pre-checks for cluster services setup

 

Checking node reachability...

Node reachability check passed from node "homer".

 

Checking user equivalence...

User equivalence check passed for user "oracle".

 

Checking administrative privileges...

User existence check passed for "oracle".

Group existence check passed for "oinstall".

Membership check for user "oracle" in group "oinstall" [as Primary] failed.

Check failed on nodes:

homer

Administrative privileges check failed.

 

Checking node connectivity...

Node connectivity check passed for subnet "192.168.0.0" with node(s) homer.

Node connectivity check passed for subnet "10.0.0.0" with node(s) homer.

 

Suitable interfaces for the private interconnect on subnet "192.168.0.0":

homer eth0:192.168.0.12 eth0:192.168.0.112

 

Suitable interfaces for the private interconnect on subnet "10.0.0.0":

homer eth1:10.0.0.12

 

ERROR:

Could not find a suitable set of interfaces for VIPs.

Node connectivity check failed.

Checking system requirements for 'crs'...

Total memory check passed.

Free disk space check passed.

Swap space check passed.

System architecture check passed.

Kernel version check passed.

Package existence check passed for "make-3.79".

Package existence check passed for "binutils-2.14".

Package existence check passed for "gcc-3.2".

Package existence check passed for "glibc-2.3.2-95.27".

Package existence check passed for "compat-db-4.0.14-5".

Package existence check passed for "compat-gcc-7.3-2.96.128".

Package existence check passed for "compat-gcc-c++-7.3-2.96.128".

Package existence check passed for "compat-libstdc++-7.3-2.96.128".

Package existence check passed for "compat-libstdc++-devel-7.3-2.96.128".

Package existence check passed for "openmotif-2.2.3".

Package existence check passed for "setarch-1.3-1".

Group existence check passed for "dba".

Group existence check passed for "oinstall".

User existence check passed for "nobody".

 

System requirement passed for 'crs'

Pre-check for cluster services setup was unsuccessful on all the nodes.

 

Please note in the above pre-requisite checks I had two main issues:

 

1.      Administrative privileges check failed: This was due to the fact that oracle didn’t have oinstall as its primary group. However, I haven’t seen any issues with this.

2.      Could not find a suitable set of interface for VIP: Again I am not sure why it complains about this, before I ran runcluvfy.sh script, I had the following entries in my /etc/hosts file:

 

[oracle@homer cluvfy]$ cat /etc/hosts

# Do not remove the following line, or various programs

# that require network functionality will fail.

127.0.0.1       localhost.localdomain     localhost

# Database Node 1

192.168.0.12    homer.dipaksharma.com      homer

10.0.0.12       homer-priv.dipaksharma.com homer-priv

192.168.0.112   homer-vip.dipaksharma.com  homer-vip

 

Installation:

Now once all pre-requisites are completed, invoke the OUI.

 

/mountpoint/runInstaller

 

 

 

Specify the location for the oraInventory directory and also the OS group name.


 

In this step 2, OUI does the pre-requisite checks.

 

 

 

Make sure that the status is succeeded for all checks and then click on Next button, otherwise resolve the issue for the relevant check and then click on retry button for OUI to re-check the status for that task.
In this screen ensure that the interface type for the respective Interface Name is correct, if not select the Interface type and click on the edit button to change.

 

 

 

Once done, click on Next button


In this screen, specify the OCR disk. As mentioned in the Introduction section, with this release 2, you can now choose to have Normal or External Redundancy for OCR.

 

 

I choose to have External Redundancy. Click on Next button


In this screen, specify the voting disk. As mentioned in the Introduction section, with this release 2, you can now choose to have Normal or External Redundancy for Voting disk.

 

 

 

I choose to have External Redundancy. Click on Next button

 


 

 

In this final screen, Click on Install


 

 

Once the laying of the Oracle CRS binaries and linking is done, run the orainstRoot.sh script first and then root.sh


As shown below, when I ran the root.sh script I had the following error at the end of the script:

The given interface(s), “eth0” is not public. Public interfaces should be used to configure virtual IP’s.

 

 

 

 

Infact this root.sh script should have invoked the vipca, but it didn’t, so I manually invoked the vipca

 


To invoke vipca go to $ORA_CRS_HOME/bin and run the following command as root user:

 

./vipca

 

 

 

Click on Next button


 

 

Select eth0 and click on Next button


 

Type in the IP Alias Name for the VIP and IP address and click on Next button


 

Lastly Click on Finish

 

This will configure start up the VIP service.

 

Now you can go back to the first screen and click on ok button and then finish the install.


References:

 

Oracle Installation Documentation on http://tahiti.oracle.com