eygle.com   eygle.com
eygle.com  
 

« 2007年 新的开端 | Blog首页 | Eygle观察-关注实事技术动态 »

10gRAC系列之一-cluvfy用法及验证错误解决

作者:eygle |【转载时请以超链接形式标明文章和作者信息及本声明
链接:

在安装Oracle10g RAC之前,可以通过Oracle提供的一个工具进行cluster环境验证,这个工具叫做cluvfy。

cluvfy常用的命令有如下一些,通过这些命令可以对CRS或INSTANCE的安装需求进行验证:


bash-2.05$ cluvfy -help     



USAGE:
cluvfy [ -help ]
cluvfy stage { -list | -help }
cluvfy stage {-pre|-post} <stage-name> <stage-specific options>  [-verbose]
cluvfy comp  { -list | -help }
cluvfy comp  <component-name> <component-specific options>  [-verbose]


但是在Solaris系统下运行这个命令经常会遇到如下一个错误:

bash-2.05$ cluvfy stage -pre crsinst -n db210-rac2

ERROR:
Unable to retrieve database release version.
Verification cannot proceed.

这个错误主要是因为由于环境变量的设置,cluvfy无法找到相应的类库所致。
只需要修改用户环境变量.profile文件中的LD_LIBRARY_PATH_64即可,在使用了EMC的环境中,缺省的该参数可能具有如下设置:

bash-2.05$ env|grep 64
LD_LIBRARY_PATH_64=/opt/EMCpower/lib/sparcv9

在该变量中增加了$ORA_CRS_HOME/lib即可,我的环境设置如下:

bash-2.05$ env|grep 64
LD_LIBRARY_PATH_64=/opt/EMCpower/lib/sparcv9:/opt/oracle/product/10.2.0/Crs10g/lib

现在就可以通过cluvfy进行环境检查:

bash-2.05$ cluvfy stage -pre crsinst -n db210-rac1,db210-rac2

Performing pre-checks for cluster services setup

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


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

Checking administrative privileges...
User existence check passed for "oracle".
Group existence check failed for "oinstall".
Check failed on nodes:
db210-rac2,db210-rac1

Administrative privileges check failed.

Checking node connectivity...


WARNING:
Make sure IP address "172.16.19.18" is up and is a valid IP address on node "db210-rac1".
Node connectivity check failed for subnet "172.16.19.0".
Node connectivity check passed for subnet "192.168.18.0" with node(s) db210-rac2,db210-rac1.
Node connectivity check passed for subnet "192.168.19.0" with node(s) db210-rac2,db210-rac1.

Suitable interfaces for the private interconnect on subnet "192.168.18.0":
db210-rac2 bge1:192.168.18.12
db210-rac1 bge1:192.168.18.11

Suitable interfaces for the private interconnect on subnet "192.168.19.0":
db210-rac2 bge2:192.168.19.12
db210-rac1 bge2:192.168.19.11

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

Node connectivity check failed.


Checking system requirements for 'crs'...
Total memory check passed.
Free disk space check passed.
Swap space check failed.
Check failed on nodes:
db210-rac2,db210-rac1
System architecture check passed.
Operating system version check passed.
Operating system patch check failed for "112760-05".
Check failed on nodes:
db210-rac2,db210-rac1
Operating system patch check failed for "113800-06".
Check failed on nodes:
db210-rac2,db210-rac1
Package existence check passed for "SUNWarc".
Package existence check passed for "SUNWbtool".
Package existence check passed for "SUNWhea".
Package existence check passed for "SUNWlibm".
Package existence check passed for "SUNWlibms".
Package existence check passed for "SUNWsprot".
Package existence check passed for "SUNWsprox".
Package existence check passed for "SUNWtoo".
Package existence check passed for "SUNWi1of".
Package existence check passed for "SUNWi1cs".
Package existence check passed for "SUNWi15cs".
Package existence check passed for "SUNWxwfnt".
Package existence check passed for "SUNWlibC".
Package existence check failed for "SUNWscucm:3.1".
Check failed on nodes:
db210-rac2,db210-rac1
Package existence check failed for "SUNWudlmr:3.1".
Check failed on nodes:
db210-rac2,db210-rac1
Package existence check failed for "SUNWudlm:3.1".
Check failed on nodes:
db210-rac2,db210-rac1
Package existence check failed for "ORCLudlm:Dev_Release_06/11/04,_64bit_3.3.4.8_reentrant".
Check failed on nodes:
db210-rac2,db210-rac1
Package existence check failed for "SUNWscr:3.1".
Check failed on nodes:
db210-rac2,db210-rac1
Package existence check failed for "SUNWscu:3.1".
Check failed on nodes:
db210-rac2,db210-rac1
Group existence check passed for "dba".
Group existence check failed for "oinstall".
Check failed on nodes:
db210-rac2,db210-rac1
User existence check passed for "oracle".
User existence check passed for "nobody".

System requirement failed for 'crs'

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

在进行了相应的调整后,满足了系统要求,就可以安装Oracle10g CRS和RAC环境了。

-The End-


历史上的今天...
      >> 2009-01-04文章:
      >> 2008-01-04文章:
      >> 2006-01-04文章:
------
这篇 【10gRAC系列之一-cluvfy用法及验证错误解决】来自 eygle.com | CSDN网摘| del.icio.us|Google订阅 | 鲜果订阅 | 抓虾订阅

By eygle on 2007-01-04 14:52 | Comments (3) | Posted to Advanced | Edit |

相关文章 随机文章
  • Install Oracle9iRac On Solaris + EMC + Veritas ---All the things you should know
  • 安装Oracle9i RAC软件
  • 创建Oracle9i RAC数据库
  • AIX Oracle 安装纪要 - cpio 、X11 forwarding
  • 并行查询的 PX Deq: reap credit 等待
  • 进京四周年记
    获得Redo Block Size的非典型方法
    此心安处是吾乡
    纪念Veritas的离去
    我的哈根达斯月饼
    搜索本站:

    留言 (3)

    cluvf这个在LINUX下可以不要把,我在LINUX下装RAC的时候都没有使用过这个也可以安装完毕

    Posted by: COMMENT at February 24, 2007 2:37 PM

    System requirement failed for 'crs'

    Pre-check for cluster services setup was unsuccessful on all the nodes
    结尾出现这个信息是配置成功了吗?

    在中间我看见了不能访问
    Could not find a suitable set of interfaces for VIPs.

    Node connectivity check failed.
    这是正常的情况吗
    帮忙解决一下吧,我问了很多人 了

    Posted by: maxul. at March 13, 2008 2:55 PM

    Could not find a suitable set of interfaces for VIPs

    这是一个Bug导致的,可以忽略。

    Posted by: eygle at March 13, 2008 3:51 PM

    发表留言:



    Remember Me?
    (输入验证码后方可评论,谢谢支持)



    CopyRight © 2004~2010 eygle.com, All rights reserved.