oracle 10g clusterware 在redhat as 5上的bug

root.sh時,到最後呼叫vipca時,出現以下錯誤

/home/oracle/10gR2/crs/jdk/jre/bin/java:error while loading shared libraries:libpthread.so.0:

cannot open shared object file:No such file or directory

這個問題在redhat as 4版本時不會出現,而且執行root.sh也正常

通過查metalink,確認是bug,需要把CRS打補丁升級到10.2.0.4才可以,後來通過打補丁後,呼叫vipca正常

以下是metalink414163.1的解釋

In this Document
(k{hwiV5^119501  Symptoms
6f(z#@?/nW*h q119501  Cause
G6l)e }a1Cu?119501  Solution
k aoD [1y'F119501  ReferencesITPUB個人空間BdZ W(n!K+z+E#KA Jx

Applies to:

Oracle Server - Enterprise Edition - Version: 10.2.0.1 to 10.2.0.3ITPUB個人空間-B5f3V&SDbC
Linux x86-64
_3PM%os]? vy119501Generic LinuxITPUB個人空間5t1Lc@8_
Intel Based Server LINUXITPUB個人空間Tob+Xy8Y)g

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:
+b7K'm!r'v2l119501

A"fbzT`K119501Issue#2:  At end of root.sh on the last node vipca will fail to run with the following error:ITPUB個人空間Q\d4?O
ITPUB個人空間?m:\6r]h

Also, srvctl will show similar output if workaround below is not implemented.ITPUB個人空間{g~?w%NO0LF

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]:

Cause

These releases of the Linux kernel fix an old bug in the 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

Toworkaround Issue#2above, edit vipca (in the 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:

ITPUB個人空間H3|S!wZ;`
 

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:

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).ITPUB個人空間!v vdf+D l9p

ITPUB個人空間1D!oV|#e/NR-L

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):

ITPUB個人空間p:N3WB0ew,@
 

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:

oKe}Z^ B!c119501
l uG Ku!ZL119501 

ITPUB個人空間i.@[:{VN3D S
Running VIPCA:
7[ \b!w.lod X119501ITPUB個人空間O&{XP ysY8H FH
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.
N$?'`2]:I3U:}|2B119501

Make sure the DISPLAY environment variable is set correctly and you can open X-clock or other X applications from that shell.ITPUB個人空間}cCOoR

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. ITPUB個人空間a4zq M2z

ITPUB個人空間K:v [7A X5}&t+[6e

To verify the Clusterware resources are running correctly:
U&S$ypa1N)S,E119501

ITPUB個人空間-P1utMT
You may now proceed with the rest of the RAC installation.

來自 “ ITPUB部落格 ” ，連結：http://blog.itpub.net/119501/viewspace-620576/，如需轉載，請註明出處，否則將追究法律責任。