Oracle11g R2: Node Connectivity check failed解决办法

http://blog.csdn.net/wenshuangzhu/article/details/46226179

在oracle11GR2图形界面进行安装检查的时候提示“Node connectivity check failed”，如下图所示：

网上说出现这个问题的原因主要有两个:

1./etc/hosts没有配好

2.Linux中未关闭Firewall

但是我的防火墙是关闭的，hosts文件也确定配置好了。

通过runcluvfy工具来检查：

[email protected]:/home/software/linux_11gR2/grid> ./runcluvfy.sh stage -post hwos -n node74,node76 -verbose

Performing post-checks for hardware and operating system setup

Checking node reachability...

Check: Node reachability from node "node74"

Destination Node Reachable?

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

node74 yes

node76 yes

Result: Node reachability check passed from node "node74"

Checking user equivalence...

Check: User equivalence for user "grid"

Node Name Comment

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

node76 passed

node74 passed

Result: User equivalence check passed for user "grid"

Checking node connectivity...

Checking hosts config file...

Node Name Status Comment

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

node76 passed

node74 passed

Verification of the hosts config file successful

Interface information for node "node76"

Name IP Address Subnet Gateway Def. Gateway HW Address MTU

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

eth0 172.16.54.76 172.16.52.0 0.0.0.0 172.16.52.254 B4:99:BA:BC:31:4A 1500

eth0 172.16.54.176 172.16.52.0 0.0.0.0 172.16.52.254 B4:99:BA:BC:31:4A 1500

eth1 10.10.10.2 10.10.10.0 0.0.0.0 172.16.52.254 B4:99:BA:BC:31:4C 1500

eth2 20.20.20.2 20.20.20.0 0.0.0.0 172.16.52.254 B4:99:BA:BC:31:4E 1500

Interface information for node "node74"

Name IP Address Subnet Gateway Def. Gateway HW Address MTU

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

eth0 172.16.54.74 172.16.52.0 0.0.0.0 172.16.52.254 98:4B:E1:04:C7:B4 1500

eth0 172.16.54.174 172.16.52.0 0.0.0.0 172.16.52.254 98:4B:E1:04:C7:B4 1500

eth0 172.16.54.175 172.16.52.0 0.0.0.0 172.16.52.254 98:4B:E1:04:C7:B4 1500

eth1 10.10.10.1 10.10.10.0 0.0.0.0 172.16.52.254 98:4B:E1:04:C7:B6 1500

eth2 20.20.20.1 20.20.20.0 0.0.0.0 172.16.52.254 98:4B:E1:04:C7:B8 1500

Check: Node connectivity of subnet "172.16.52.0"

Source Destination Connected?

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

node76:eth0 node76:eth0 yes

node76:eth0 node74:eth0 yes

node74:eth0 node74:eth0 yes

Result: Node connectivity passed for subnet "172.16.52.0" with node(s) node76,node74

Check: TCP connectivity of subnet "172.16.52.0"

Source Destination Connected?

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

node74:172.16.54.74 node76:172.16.54.76 passed

node74:172.16.54.74 node76:172.16.54.176 passed

node74:172.16.54.74 node74:172.16.54.174 passed

node74:172.16.54.74 node74:172.16.54.175 passed

Result: TCP connectivity check passed for subnet "172.16.52.0"

Check: Node connectivity of subnet "10.10.10.0"

Source Destination Connected?

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

node76:eth1 node74:eth1 yes

Result: Node connectivity passed for subnet "10.10.10.0" with node(s) node76,node74

Check: TCP connectivity of subnet "10.10.10.0"

Source Destination Connected?

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

node74:10.10.10.1 node76:10.10.10.2 passed

Result: TCP connectivity check passed for subnet "10.10.10.0"

Check: Node connectivity of subnet "20.20.20.0"

WARNING:

Make sure IP address "20.20.20.1" is up and is a valid IP address on node "node74"

Source Destination Connected?

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

node76:eth2 node74:eth2 no

Result: Node connectivity failed for subnet "20.20.20.0"

Check: TCP connectivity of subnet "20.20.20.0"

Source Destination Connected?

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

node74:20.20.20.1 node76:20.20.20.2 failed ------注意：两个节点有一组网卡配置了同一网段的IP，但是却没有联通，造成node
connectivity检查失败。

Result: TCP connectivity check failed for subnet "20.20.20.0"

Interfaces found on subnet "172.16.52.0" that are likely candidates for VIP are:

node76 eth0:172.16.54.76 eth0:172.16.54.176

node74 eth0:172.16.54.74 eth0:172.16.54.174 eth0:172.16.54.175

Interfaces found on subnet "10.10.10.0" that are likely candidates for a private interconnect are:

node76 eth1:10.10.10.2

node74 eth1:10.10.10.1

Result: Node connectivity check failed

Checking for multiple users with UID value 0

Result: Check for multiple users with UID value 0 passed

Post-check for hardware and operating system setup was unsuccessful on all the nodes.

原来是因为两个节点有一对网卡配置了通网段的IP地址，但是实际上两个网卡并没有连通，造成了node connectivity检查失败。

Check: TCP connectivity of subnet "20.20.20.0"

Source Destination Connected?

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

node74:20.20.20.1 node76:20.20.20.2 failed

这样解决办法就有了，要么就是把两个网卡连通，要么就是修改为不同的网段，或者干脆直接停用这两块网卡。

我这边停用这两块网卡后，重新执行安装检查通过。

时间： 2024-10-29 03:07:39

Oracle11g R2: Node Connectivity check failed解决办法的相关文章

perl:warning:Setting locale failed解决办法

perl:warning:Setting locale failed解决办法: $ sudo vi /etc/profile 按a或i进入编辑模式 export LC_ALL=en_US.UTF-8export LANGUAGE=en_US.UTF-8 按Esc键退出编辑模式 :wq (保存并退出) $ source /etc/profile perl:warning:Setting locale failed解决办法,布布扣,bubuko.com

真机测试报错ERROR/AndroidRuntime: java.lang.RuntimeException: setParameters failed解决办法

这个错误是和调用相机摄像头相关的. 产生这个错误的原因主要在于代码控制分辨率的显示和真机测试分辨率不一样. 一:解决办法 WindowManager wm = (WindowManager) getSystemService(Context.WINDOW_SERVICE); Display display = wm.getDefaultDisplay(); Camera.Parameters parameters = camera.getParameters();// 得到摄像头的参数 para

在windows server 2008中安装SQL Server 2008 R2 1433端口未启用解决办法

SQL Server 一般默认的端口为 1433 ,但有时会遇到无法连接端口1433的问题,检查端口1433是否启用的方法为: 开始–>输入cmd –>回车–>telnet localhost 1433->回车出现黑屏,表示本机连接端口1433成功. 或者开始–>输入cmd –>回车–>netstat -an | find "1433"->回车出现1433端口,表示本机1433端口开放. 我本次安装过程中遇到的问题:1433端口

Loadrunner 并发时'Error -27492 HttpSendRequest failed'解决办法

问题点 Loadrunner11对脚本单独回放时,回放100%正常无报错信息,但是运行场景多个用户并发测试时,运行一段时间后,每次均报错: Error -27492: "HttpSendRequest" failed, Windows error code=12002 百度了一下,答案千篇一律,基本解决办法都是: "在Runtime-setting中的preferences-->options-->http-request connect timeout(sec)

Lumia 刷机（强刷）Message send failed解决办法

强刷可以救砖,不需要验证地区code,可以跨刷其它国家/地区的固件,但不是所有机型都可以这样,Lumia 620是支持跨刷的. 看本文你首先要知道使用Nokia Care Suite强刷的步骤,参考从<教程二:[强刷/跨RM刷机教程]>开始读. 如果你不需要跨刷其它地区固件,只为救砖机,可以直接使用恢复工具(Lumia Software Recovery Tool或者Windows Phone Recovery Tool),下文即可不看. 首先描述一下我遇到的问题的4个症状,可以对照一下是否与

RAD Studio 10 安装失败提示错误 License status check failure解决办法

最近在安装RAD Studio 10.1 Berlin 时,运行光盘中的setup.exe,在第一页勾选 lincense agreement后下一步,提示如下错误,无法进行安装. License status check failure License status check failure (Error code: 255). Please try again later, or contact support. 通过一番搜索和尝试得到以下解决办法: 问题原因: 由于电脑中已经安装过其他版

cocos2d-x 3.6运行cocos run出现Ndk build failed解决办法

我运行cocos run -p android编译成安卓APK的时候提示:jni/../../Classes/AppDelegate.cpp:67: error: undefined reference to 'GameMain::c reateScene()', 最后出现错误提示:Ndk build failed!,其中GameMain是我自己写的代码,. 后来找到了原因,有两种解决办法: 第一种方法:在\proj.android\jni下面的Android.mk的文件里面,在LOCAL_SR

使用Robomongo 连接MongoDB 报 Authorization failed 解决办法

就是这个错误! 我在网上搜了解决办法几乎都是说认证机制的问题: > use admin switched to db admin > db.system.version.find() { "_id" : "featureCompatibilityVersion", "version" : "3.4" } { "_id" : "authSchema", "curren

使用Robomongo 连接MongoDB 3.x 报 Authorization failed 解决办法（转）

最近安装了mongodb3.1.4,并启用了权限验证,在dos窗口下操作没有任何问题,为了维护方便就下载了一个客户端工具Robomongo 0.8.5,用户名.密码的等配置好点解测试,结果连接服务没有问题,权限验证没有通过,如图查看日志,发现有一句:Failed to authenticate [email protected] with mechanism MONGODB-CR: AuthenticationFailed MONGODB-CR credentials missing in t