10gR2 RAC Install issues on Oracle EL5 or RHEL5 or SLES10 (VIPCA /SRVCTL / OUI Failures) [ID 414163.

10gR2 RAC Install issues on Oracle EL5 or RHEL5 or SLES10 (VIPCA / SRVCTL / OUI Failures) [ID 414163.1]
	Modified04-AUG-2010TypePROBLEMStatusARCHIVED

In this Document
Symptoms
Cause
Solution
References

---

Applies to:

Oracle Server - Enterprise Edition - Version: 10.2.0.1 to 10.2.0.3 - Release: 10.2 to 10.2
Linux x86
Generic Linux
Linux x86-64
***Checked for relevance on 04-Aug-2010***

Symptoms

When installing 10gR2 RAC on Oracle Enterprise Linux 5 or RHEL5 or SLES10 there are three issues that users must be aware of.

Issue#1: To install 10gR2, you must first install the base release, which is 10.2.0.1. As these version of OS are newer, you should use the following command to invoke the installer:

$ runInstaller -ignoreSysPrereqs // This will bypass the OS check //

Issue#2: At end of root.sh on the last nodevipca will fail to run with the following error:

OracleCRSstackinstalledandrunningunderinit(1M)
Runningvipca(silent)forconfiguringnodeapps
/home/oracle/crs/oracle/product/10/crs/jdk/jre//bin/java: errorwhileloading
sharedlibraries:libpthread.so.0: cannotopensharedobjectfile:
Nosuchfileordirectory

Also, srvctl will show similar output if workaround below is not implemented.

Issue#3: After working around Issue#2 above, vipca will fail to run with the following error if the VIP IP's are in a non-routable range [10.x.x.x, 172.(16-31).x.x or 192.168.x.x]:

#vipca
Error0(Native:listNetInterfaces:[3])
[Error0(Native:listNetInterfaces:[3])]

Cause

These releases of the Linux kernel fix an old bug inthe Linux threading that Oracle worked around using LD_ASSUME_KERNEL settings in both vipca and srvctl, this workaround is no longer valid on OEL5 or RHEL5 or SLES10 hence the failures.

Solution

If you have not yet run root.sh on the last node, implement workaround for issue#2 below and run root.sh (you mayskip runningthe vipca portion at the bottom of this note).
If you have a non-routable IP range for VIPs you will also need workaround for issue# 3 and then run vipca manually.

Toworkaround Issue#2above, edit vipca (inthe CRS bin directoryon all nodes) to undo the setting of LD_ASSUME_KERNEL. After the IF statement around line 120 add an unset command to ensure LD_ASSUME_KERNEL isnotset as follows:

if["$arch"="i686"-o"$arch"="ia64"-o"$arch"="x86_64"]
then
LD_ASSUME_KERNEL=2.4.19
exportLD_ASSUME_KERNEL
fi

unsetLD_ASSUME_KERNEL<<<==Linetobeadded

Similarly for srvctl (inboththe CRS and, when installed, RDBMS and ASM bin directorieson all nodes), unset LD_ASSUME_KERNEL by adding one line, around line 168 should look like this:

LD_ASSUME_KERNEL=2.4.19
exportLD_ASSUME_KERNEL

unsetLD_ASSUME_KERNEL<<<==Linetobeadded

Remember to re-edit these fileson all nodes:
<CRS_HOME>/bin/vipca
<CRS_HOME>/bin/srvctl
<RDBMS_HOME>/bin/srvctl
<ASM_HOME>/bin/srvctl

after applying the 10.2.0.2 or 10.2.0.3 patchsets, as these patchset will still include those settings unnecessary for OEL5 or RHEL5 or SLES10. This issue was raised with development and isfixed in the10.2.0.4 patchsets.

Note that we are explicitlyunsettingLD_ASSUME_KERNEL and not merely commenting out its setting to handle a case where the user has it set in their environment (login shell).

Toworkaround issue#3(vipca failing on non-routable VIP IP ranges, manually or during root.sh), if you still have the OUI window open, click OK and it will create the "oifcfg" information, then cluvfy will fail due to vipca not completed successfully, skip below in this note and run vipca manually then return to the installer and cluvfy will succeed. Otherwise you may configure the interfaces for RAC manually using the oifcfg command as root, like in the following example (from any node):

<CRS_HOME>/bin#./oifcfgsetif-globaleth0/192.168.1.0:public
<CRS_HOME>/bin#./oifcfgsetif-globaleth1/10.10.10.0:cluster_interconnect
<CRS_HOME>/bin#./oifcfggetif
eth0192.168.1.0globalpublic
eth110.10.10.0globalcluster_interconnect

The goal is to get the output of "oifcfg getif" to include both public and cluster_interconnect interfaces, of course you should exchange your own IP addresses and interface name from your environment. To get the proper IPs in your environment run this command:

<CRS_HOME>/bin#./oifcfgiflist
eth0192.168.1.0
eth110.10.10.0

If you have not yet run root.sh on the last node, implement workaround for issue #2 above and run root.sh (you mayskip runningthe vipca portion below. If you have a non-routable IP range for VIPs you will also need workaround for issue# 3 above, and then run vipca manually.

Running VIPCA:

After implementing the above workaround(s), you should be able invoke vipca (as root, fromlastnode) manually and configure the VIP IPs via the GUI interface.

<CRS_HOME>/bin # export DISPLAY=<x-display:0>
<CRS_HOME>/bin # ./vipca

Make sure the DISPLAY environment variable is set correctly and you can open X-clock or other X applications from that shell.

Once vipca completes running, all the Clusterware resources (VIP, GSD, ONS) will be started,there is no need to re-run root.shsince vipca is thelaststep in root.sh.

To verify the Clusterware resources are running correctly:

<CRS_HOME>/bin # ./crs_stat -t
Name Type Target State Host
------------------------------------------------------------
ora....ux1.gsd application ONLINE ONLINE raclinux1
ora....ux1.ons application ONLINE ONLINE raclinux1
ora....ux1.vip application ONLINE ONLINE raclinux1
ora....ux2.gsdapplicationONLINEONLINEraclinux2
ora....ux2.onsapplicationONLINEONLINEraclinux2
ora....ux2.vipapplicationONLINEONLINEraclinux2

You may now proceed with the rest of the RAC installation.

------------------------------------------------------------------------------