rhel5.6安裝10g clusterware時,節點2執行root.sh報錯

2008081036發表於2014-11-21

[root@tpibpmdb02 oraInventory]# cd /u01/product/crs/

[root@tpibpmdb02 crs]# ll root.sh

-rwxr-xr-x 1 oracle dba 83 Nov  9 13:07 root.sh

[root@tpibpmdb02 crs]# ./root.sh

WARNING: directory '/u01/product' is not owned by root

WARNING: directory '/u01' is not owned by root

Checking to see if Oracle CRS stack is already configured

/etc/oracle does not exist. Creating it now.

 

Setting the permissions on OCR backup directory

Setting up NS directories

Oracle Cluster Registry configuration upgraded successfully

WARNING: directory '/u01/product' is not owned by root

WARNING: directory '/u01' is not owned by root

clscfg: EXISTING configuration version 3 detected.

clscfg: version 3 is 10G Release 2.

Successfully accumulated necessary OCR keys.

Using ports: CSS=49895 CRS=49896 EVMC=49898 and EVMR=49897.

node :

node 1: tpibpmdb01 plb2bcorepri01 tpibpmdb01

node 2: tpibpmdb02 plb2bcorepri02 tpibpmdb02

clscfg: Arguments check out successfully.

 

NO KEYS WERE WRITTEN. Supply -force parameter to override.

-force is destructive and will destroy any previous cluster

configuration.

Oracle Cluster Registry for cluster has already been initialized

Startup will be queued to init within 90 seconds.

Adding daemons to inittab

Expecting the CRS daemons to be up within 600 seconds.

CSS is active on these nodes.

        tpibpmdb01

        tpibpmdb02

CSS is active on all nodes.

Waiting for the Oracle CRSD and EVMD to start

Oracle CRS stack installed and running under init(1M)

Running vipca(silent) for configuring nodeapps

/u01/product/crs/jdk/jre//bin/java: error while loading shared libraries: libpthread.so.0: cannot open shared object file: No such file or directory

 

我們注意到後面到節點2上執行root.sh時有一個報錯。

Running vipca(silent) for configuring nodeapps

/u01/product/crs/jdk/jre//bin/java: error while loading shared libraries: libpthread.so.0: cannot open shared object file: No such file or directory

這是Oracle的一個BugBug號:3937317)。我們來修復這個錯誤。

2節點上修改/u01/product/crs/bin/vipca檔案。找到LD_ASSUME_KERNEL2.4.19位置,在fi後增加一行(下圖中紅色部分).

[root@tpibpmdb01 crs]# vi /u01/product/crs/bin/vipca

#Remove this workaround when the bug 3937317 is fixed

       arch=`uname -m`

       if [ "$arch" = "i686" -o "$arch" = "ia64" -o "$arch" = "x86_64" ]

       then

            LD_ASSUME_KERNEL=2.4.19

            export LD_ASSUME_KERNEL

       fi

       unset LD_ASSUME_KERNEL

       #End workaround

 

再次在節點2上執行root.sh

[root@tpibpmdb01 crs]# ./root.sh

WARNING: directory '/u01/product' is not owned by root

WARNING: directory '/u01' is not owned by root

Checking to see if Oracle CRS stack is already configured

Oracle CRS stack is already configured and will be running under init(1M)

Running vipca(silent) for configuring nodeapps

Error 0(Native: listNetInterfaces:[3])

  [Error 0(Native: listNetInterfaces:[3])]

 

 

以下動作在節點2上執行。

root登入圖形介面,手動執行vipca


Root使用者下:

CRS_HOME下 執行 oifcfg 命令

#./oifcfg iflist

bond0  10.12.16.0

bond1  10.12.18.0

# ./oifcfg setif -global bond0/10.12.16.0:public

# ./oifcfg setif -global bond1/10.12.18.0:cluster_interconnect

# ./oifcfg getif

bond0 10.12.16.0 global public

bond1 10.12.16.0 global cluster_interconnect

 

遇到錯誤Error 0(Native: listNetInterfaces:[3])

  [Error 0(Native: listNetInterfaces:[3])]時,按照上圖中方法修復即可。

然後再執行vipca.



在IP Alisa Name下輸入Virtual Host Name,如果/etc/hosts檔案中配置正確的話,可以自動帶出來IP。要注意這裡VIP一定不能弄錯,不然後面改不了,要全部推掉重灌。



確認一下總結資訊,沒有問題的話,就可以點選Finish開始配置了。

  







 

配置完成後,點選OK會有一個Configration Results出來。


 

然後,我們回到節點1上CRS的安裝介面,點選OK.

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

相關文章