使用 runcluvfy 校验Oracle RAC安装环境

使用 校验 环境

--*****************************************

--使用runcluvfy校验Oracle RAC安装环境

--*****************************************

所谓工欲善其事，必先利其器。安装Orale RAC可谓是一个浩大的工程，尤其是没有做好前期的规划与配置工作时将导致安装的复杂

度绝非想象。幸好有runcluvfy工具，这大大简化了安装工作。下面的演示是基于安装Oracle10g RAC / Linux来完成的。

1.从安装文件路径下使用runcluvfy实施安装前的校验

[oracle@rac1 cluvfy]$ pwd
/home/oracle/clusterware/cluvfy

[oracle@rac1 cluvfy]$./runcluvfy.sh stage -pre crsinst -n rac1,rac2 -verbose

Performing pre-checks for cluster services setup

Checking node reachability...

Check: Node reachability from node "rac1"
Destination Node Reachable?
------------------------------------ ------------------------
rac2 yes
rac1 yes
Result: Node reachability check passed from node "rac1".

Checking user equivalence...

Check: User equivalence for user "oracle"
Node Name Comment
------------------------------------ ------------------------
rac2 passed
rac1 passed
Result: User equivalence check passed for user "oracle".

Checking administrative privileges...

Check: Existence of user "oracle"
Node Name User Exists Comment
------------ ------------------------ ------------------------
rac2 yes passed
rac1 yes passed
Result: User existence check passed for "oracle".

Check: Existence of group "oinstall"
Node Name Status Group ID
------------ ------------------------ ------------------------
rac2 exists 501
rac1 exists 501
Result: Group existence check passed for "oinstall".

Check: Membership of user "oracle" in group "oinstall" [as Primary]
Node Name User Exists Group Exists User in Group Primary Comment
---------------- ------------ ------------ ------------ ------------ ------------
rac2 yes yes yes yes passed
rac1 yes yes yes yes passed
Result: Membership check for user "oracle" in group "oinstall" [as Primary] passed.

Administrative privileges check passed.

Checking node connectivity...

Interface information for node "rac2"
Interface Name IP Address Subnet
------------------------------ ------------------------------ ----------------
eth0 172.21.1.31 172.21.1.0
eth1 10.0.0.12 10.0.0.0

Interface information for node "rac1"
Interface Name IP Address Subnet
------------------------------ ------------------------------ ----------------
eth0 172.21.1.30 172.21.1.0
eth1 10.0.0.11 10.0.0.0

Check: Node connectivity of subnet "172.21.1.0"
Source Destination Connected?
------------------------------ ------------------------------ ----------------
rac2:eth0 rac1:eth0 yes
Result: Node connectivity check passed for subnet "172.21.1.0" with node(s) rac2,rac1.

Check: Node connectivity of subnet "10.0.0.0"
Source Destination Connected?
------------------------------ ------------------------------ ----------------
rac2:eth1 rac1:eth1 yes
Result: Node connectivity check passed for subnet "10.0.0.0" with node(s) rac2,rac1.

Suitable interfaces for the private interconnect on subnet "172.21.1.0":
rac2 eth0:172.21.1.31
rac1 eth0:172.21.1.30

Suitable interfaces for the private interconnect on subnet "10.0.0.0":
rac2 eth1:10.0.0.12
rac1 eth1:10.0.0.11

ERROR:
Could not find a suitable set of interfaces for VIPs.

Result: Node connectivity check failed.

Checking system requirements for 'crs'...

Check: Total memory
Node Name Available Required Comment
------------ ------------------------ ------------------------ ----------
rac2 1010.84MB (1035096KB) 512MB (524288KB) passed
rac1 1010.84MB (1035096KB) 512MB (524288KB) passed
Result: Total memory check passed.

Check: Free disk space in "/tmp" dir
Node Name Available Required Comment
------------ ------------------------ ------------------------ ----------
rac2 1.68GB (1757092KB) 400MB (409600KB) passed
rac1 1.59GB (1670076KB) 400MB (409600KB) passed
Result: Free disk space check passed.

Check: Swap space
Node Name Available Required Comment
------------ ------------------------ ------------------------ ----------
rac2 1GB (1052248KB) 1GB (1048576KB) passed
rac1 1GB (1052248KB) 1GB (1048576KB) passed
Result: Swap space check passed.

Check: System architecture
Node Name Available Required Comment
------------ ------------------------ ------------------------ ----------
rac2 i686 i686 passed
rac1 i686 i686 passed
Result: System architecture check passed.

Check: Kernel version
Node Name Available Required Comment
------------ ------------------------ ------------------------ ----------
rac2 2.6.18-164.el5 2.4.21-15EL passed
rac1 2.6.18-164.el5 2.4.21-15EL passed
Result: Kernel version check passed.

Check: Package existence for "make-3.79"
Node Name Status Comment
------------------------------ ------------------------------ ----------------
rac2 make-3.81-3.el5 passed
rac1 make-3.81-3.el5 passed
Result: Package existence check passed for "make-3.79".

Check: Package existence for "binutils-2.14"
Node Name Status Comment
------------------------------ ------------------------------ ----------------
rac2 binutils-2.17.50.0.6-12.el5 passed
rac1 binutils-2.17.50.0.6-12.el5 passed
Result: Package existence check passed for "binutils-2.14".

Check: Package existence for "gcc-3.2"
Node Name Status Comment
------------------------------ ------------------------------ ----------------
rac2 gcc-4.1.2-46.el5 passed
rac1 gcc-4.1.2-46.el5 passed
Result: Package existence check passed for "gcc-3.2".

Check: Package existence for "glibc-2.3.2-95.27"
Node Name Status Comment
------------------------------ ------------------------------ ----------------
rac2 glibc-2.5-42 passed
rac1 glibc-2.5-42 passed
Result: Package existence check passed for "glibc-2.3.2-95.27".

Check: Package existence for "compat-db-4.0.14-5"
Node Name Status Comment
------------------------------ ------------------------------ ----------------
rac2 compat-db-4.2.52-5.1 passed
rac1 compat-db-4.2.52-5.1 passed
Result: Package existence check passed for "compat-db-4.0.14-5".

Check: Package existence for "compat-gcc-7.3-2.96.128"
Node Name Status Comment
------------------------------ ------------------------------ ----------------
rac2 missing failed
rac1 missing failed
Result: Package existence check failed for "compat-gcc-7.3-2.96.128".

Check: Package existence for "compat-gcc-c -7.3-2.96.128"
Node Name Status Comment
------------------------------ ------------------------------ ----------------
rac2 missing failed
rac1 missing failed
Result: Package existence check failed for "compat-gcc-c -7.3-2.96.128".

Check: Package existence for "compat-libstdc -7.3-2.96.128"
Node Name Status Comment
------------------------------ ------------------------------ ----------------
rac2 missing failed
rac1 missing failed
Result: Package existence check failed for "compat-libstdc -7.3-2.96.128".

Check: Package existence for "compat-libstdc -devel-7.3-2.96.128"
Node Name Status Comment
------------------------------ ------------------------------ ----------------
rac2 missing failed
rac1 missing failed
Result: Package existence check failed for "compat-libstdc -devel-7.3-2.96.128".

Check: Package existence for "openmotif-2.2.3"
Node Name Status Comment
------------------------------ ------------------------------ ----------------
rac2 openmotif-2.3.1-2.el5 passed
rac1 openmotif-2.3.1-2.el5 passed
Result: Package existence check passed for "openmotif-2.2.3".

Check: Package existence for "setarch-1.3-1"
Node Name Status Comment
------------------------------ ------------------------------ ----------------
rac2 setarch-2.0-1.1 passed
rac1 setarch-2.0-1.1 passed
Result: Package existence check passed for "setarch-1.3-1".

Check: Group existence for "dba"
Node Name Status Comment
------------ ------------------------ ------------------------
rac2 exists passed
rac1 exists passed
Result: Group existence check passed for "dba".

Check: Group existence for "oinstall"
Node Name Status Comment
------------ ------------------------ ------------------------
rac2 exists passed
rac1 exists passed
Result: Group existence check passed for "oinstall".

Check: User existence for "nobody"
Node Name Status Comment
------------ ------------------------ ------------------------
rac2 exists passed
rac1 exists passed
Result: User existence check passed for "nobody".

System requirement failed for 'crs'

Pre-check for cluster services setup was unsuccessful on all the nodes.

 

 

Couldnotfind a suitablesetofinterfacesforVIPs.”，可以忽略该错误

信息，这是一个bug，Metalink中有详细说明，doc.id:338924.1。参考本文尾部列出的内容。

对于上面描述的failed的包，尽可能的将其安装到系统。

 

 

2.安装Clusterware后的检查,注意，此时执行的cluvfy是位于已安装的路径

[oracle@rac1 bin]$ pwd
/u01/oracle/product/crs/bin

[oracle@rac1 bin]$ ./cluvfy stage -post crsinst -n rac1,rac2

Performing post-checks for cluster services setup

Checking node reachability...
Node reachability check passed from node "rac1".

Checking user equivalence...
User equivalence check passed for user "oracle".

Checking Cluster manager integrity...

Checking CSS daemon...
Daemon status check passed for "CSS daemon".

Cluster manager integrity check passed.

Checking cluster integrity...

Cluster integrity check passed

Checking OCR integrity...

Checking the absence of a non-clustered configuration...
All nodes free of non-clustered, local-only configurations.

Uniqueness check for OCR device passed.

Checking the version of OCR...
OCR of correct Version "2" exists.

Checking data integrity of OCR...
Data integrity check for OCR passed.

OCR integrity check passed.

Checking CRS integrity...

Checking daemon liveness...
Liveness check passed for "CRS daemon".

Checking daemon liveness...
Liveness check passed for "CSS daemon".

Checking daemon liveness...
Liveness check passed for "EVM daemon".

Checking CRS health...
CRS health check passed.

CRS integrity check passed.

Checking node application existence...

Checking existence of VIP node application (required)
Check passed.

Checking existence of ONS node application (optional)
Check passed.

Checking existence of GSD node application (optional)
Check passed.

Post-check for cluster services setup was successful.