10gR2 RAC Install issues on Oracle EL5 or RHEL5 or SLES10 (VIPCA / SRVCTL / OUI Failures) [ID 414163.1]
|
|
|
Modified 04-AUG-2010Type PROBLEMStatus ARCHIVED
|
|
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***
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])]
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.
If you have not yet run root.sh on the last node, implement workaround for issue#2 below and run root.sh (you may skip running the 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.
To workaround Issue#2 above, edit vipca (inthe CRS bin directory on 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 is not set 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 (in both the CRS and, when installed, RDBMS and ASM bin directories on 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 files on 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 is fixed in the 10.2.0.4 patchsets.
Note that we are explicitly unsetting LD_ASSUME_KERNEL and not merely commenting out its setting to handle a case where the user has it set in their environment (login shell).
To workaround 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 may skip running the 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, from last node) 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.sh since vipca is the last step 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.
------------------------------------------------------------------------------
Blog: http://blog.csdn.net/tianlesoftware
网上资源: http://tianlesoftware.download.csdn.net
相关视频:http://blog.csdn.net/tianlesoftware/archive/2009/11/27/4886500.aspx
DBA1 群:62697716(满); DBA2 群:62697977(满)
DBA3 群:62697850 DBA 超级群:63306533;
聊天 群:40132017
--加群需要在备注说明Oracle表空间和数据文件的关系,否则拒绝申请
分享到:
相关推荐
oracleasm-2.6.18-238.5.1.el5-2.0.5-1.el5.x86_64.rpm oracleasm-2.6.18-238.9.1.el5-2.0.5-1.el5.x86_64.rpm oracleasm-2.6.18-238.el5-2.0.5-1.el5.x86_64.rpm oracleasm-2.6.18-274.12.1.el5-2.0.5-1.el5.x86_64...
radhat el5 安装oracle rac需要用到的包kernel-xen-2.6.18-53.el5.i686.rpm
rhel 6中搭建oracle 11gr2 rac环境。
rhel 5.5安装oracle 11gr2 RAC.txtrhel 5.5安装oracle 11gr2 RAC.txtrhel 5.5安装oracle 11gr2 RAC.txtrhel 5.5安装oracle 11gr2 RAC.txtrhel 5.5安装oracle 11gr2 RAC.txtrhel 5.5安装oracle 11gr2 RAC.txtrhel 5.5...
rhel5安装rac10所需要的10余个包,包括compat-binutils215-2.15.92.0.2-24.i386.rpm,compat-libcwait-2.1-1.i386.rpm,compat-libstdc++-egcs-1.1.2-1.i386.rpm,compat-oracle-el5-1.0-5.i386.rpm,kernel-debug-...
radhat el5 安装oracle rac需要用到的包 kernel-debug-2.6.18-53.el5.i686.rpm
deploying-oracle-11gr2-rac-on-rhel6.pdf
linux下安装oracle rac 时用到的包
Oracle 11gR2 RAC ASM on RHEL6.4安装流程
某客户需要将一套Oracle 10gR2 双节点RAC 生产数据库升级至Oracle 11gR2 RAC,所以便有了本系列实战的教程。 为更贴切还原生产过程中的实际操作,本系列教程一个分两大部分: 第一部分已发 一步一步在Linux上部署...
雷宇《Vmware+Linux+Oracle 10G RAC全程详细图解》补丁 君三思的《手把手教你用VMware安装Oracle10g RAC 》补丁 补丁列表 compat-binutils215-2.15.92.0.2-24.i386 compat-libcwait-2.1-1.i386 compat-libstdc++-...
compat-libcwait-2.1-1.i386.prm,compat-libstdc++-egcs-1.1.2-1.i386.rpm,compat-oracle-el5-1.0-5.i386.rpm,openmotif21-2.1.30-11.EL5.i386.rpm,openmotif21-debuginfo-2.1.30-11.EL5.i386.rpm,oracleasm-2.6.18-...
包含以下文件: oracleasm-2.6.18-164.el5-2.0.5-1.el5.i686.rpm oracleasm-2.6.18-164.el5xen-2.0.5-1.el5.i686.rpm oracleasmlib-2.0.4-1.el5.i386.rpm oracleasm-support-2.1.7-1.el5.i386.rpm
Oracle.Database.10g.RAC.on.Linux
Pro.Oracle.Database.11g.Rac.on.Linux.pdf.7z
ORACLE_10gR2_RAC升级ORACLE_10gR2_RAC升级
在Red Hat Linux AS4上安装Oracle 10gR2 RAC.doc在Red Hat Linux AS4上安装Oracle 10gR2 RAC.doc在Red Hat Linux AS4上安装Oracle 10gR2 RAC.doc在Red Hat Linux AS4上安装Oracle 10gR2 RAC.doc
Oracle.Database.11g.RAC.on.Linux
oracle+RAC+enterprise linux5.1所需的補丁含安裝順序 共19個RPM文件 rpm包如下: compat-binutils215-2.15.92.0.2-24.i386.rpm compat-libcwait-2.1-1.i386.rpm compat-libstdc++-egcs-1.1.2-1.i386.rpm ...