使用 runcluvfy 校验Oracle RAC安装环境

所谓工欲善其事，必先利其器。安装 Orale RAC 可谓是一个浩大的工程，尤其是没有做好前期的规划与配置工作时将导致安装的复杂度绝非想象。幸好有runcluvfy工具，这大大简化了安装工作。下面的演示是基于安装Oracle 10g RAC / Linux来完成的。 1.从安装文件路径下使用runcluvfy实施安装前的校验 [oracle@node1 cluvfy]$ pwd /u01/Clusterware/clusterware/cluvfy [oracle@node1 cluvfy]$ ./runcluvfy.sh stage -pre crsinst -n node1,node2 -verbose Performing pre-checks for cluster services setup Checking node reachability... Check: Node reachability from node "node1" Destination Node Reachable？ ------------------------------------ ------------------------ node1 yes node2 yes Result: Node reachability check passed from node "node1". Checking user equivalence... Check: User equivalence for user "oracle" Node Name Comment ------------------------------------ ------------------------ node2 passed node1 passed Result: User equivalence check passed for user "oracle". Checking administrative privileges... Check: Existence of user "oracle" Node Name User Exists Comment ------------ ------------------------ ------------------------ node2 yes passed node1 yes passed Result: User existence check passed for "oracle". Check: Existence of group "oinstall" Node Name Status Group ID ------------ ------------------------ ------------------------ node2 exists 500 node1 exists 500 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 ---------------- ------------ ------------ ------------ ------------ ------------ node2 yes yes yes yes passed node1 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 "node2" Interface Name IP Address Subnet ------------------------------ ------------------------------ ---------------- eth0 192.168.0.12 192.168.0.0 eth1 10.101.0.12 10.101.0.0 Interface information for node "node1" Interface Name IP Address Subnet ------------------------------ ------------------------------ ---------------- eth0 192.168.0.11 192.168.0.0 eth1 10.101.0.11 10.101.0.0 Check: Node connectivity of subnet "192.168.0.0" Source Destination Connected？ ------------------------------ ------------------------------ ---------------- node2:eth0 node1:eth0 yes Result: Node connectivity check passed for subnet "192.168.0.0" with node（s） node2,node1. Check: Node connectivity of subnet "10.101.0.0" Source Destination Connected？ ------------------------------ ------------------------------ ---------------- node2:eth1 node1:eth1 yes Result: Node connectivity check passed for subnet "10.101.0.0" with node（s） node2,node1. Suitable interfaces for the private interconnect on subnet "192.168.0.0": node2 eth0:192.168.0.12 node1 eth0:192.168.0.11 Suitable interfaces for the private interconnect on subnet "10.101.0.0": node2 eth1:10.101.0.12 node1 eth1:10.101.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 ------------ ------------------------ ------------------------ ---------- node2 689.38MB （705924KB） 512MB （524288KB） passed node1 689.38MB （705924KB） 512MB （524288KB） passed Result: Total memory check passed. Check: Free disk space in "/tmp" dir Node Name Available Required Comment ------------ ------------------------ ------------------------ ---------- node2 4.22GB （4428784KB） 400MB （409600KB） passed node1 4.22GB （4426320KB） 400MB （409600KB） passed Result: Free disk space check passed. Check: Swap space Node Name Available Required Comment ------------ ------------------------ ------------------------ ---------- node2 2GB （2096472KB） 1GB （1048576KB） passed node1 2GB （2096472KB） 1GB （1048576KB） passed Result: Swap space check passed. Check: System architecture Node Name Available Required Comment ------------ ------------------------ ------------------------ ---------- node2 i686 i686 passed node1 i686 i686 passed Result: System architecture check passed. Check: Kernel version Node Name Available Required Comment ------------ ------------------------ ------------------------ ---------- node2 2.6.18-194.el5 2.4.21-15EL passed node1 2.6.18-194.el5 2.4.21-15EL passed Result: Kernel version check passed. Check: Package existence for "make-3.79" Node Name Status Comment ------------------------------ ------------------------------ ---------------- node2 make-3.81-3.el5 passed node1 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 ------------------------------ ------------------------------ ---------------- node2 binutils-2.17.50.0.6-14.el5 passed node1 binutils-2.17.50.0.6-14.el5 passed Result: Package existence check passed for "binutils-2.14". Check: Package existence for "gcc-3.2" Node Name Status Comment ------------------------------ ------------------------------ ---------------- node2 gcc-4.1.2-48.el5 passed node1 gcc-4.1.2-48.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 ------------------------------ ------------------------------ ---------------- node2 glibc-2.5-49 passed node1 glibc-2.5-49 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 ------------------------------ ------------------------------ ---------------- node2 compat-db-4.2.52-5.1 passed node1 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 ------------------------------ ------------------------------ ---------------- node2 missing failed node1 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 ------------------------------ ------------------------------ ---------------- node2 missing failed node1 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 ------------------------------ ------------------------------ ---------------- node2 missing failed node1 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 ------------------------------ ------------------------------ ---------------- node2 missing failed node1 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 ------------------------------ ------------------------------ ---------------- node2 openmotif-2.3.1-2.el5_4.1 passed node1 openmotif-2.3.1-2.el5_4.1 passed Result: Package existence check passed for "openmotif-2.2.3". Check: Package existence for "setarch-1.3-1" Node Name Status Comment ------------------------------ ------------------------------ ---------------- node2 setarch-2.0-1.1 passed node1 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 ------------ ------------------------ ------------------------ node2 exists passed node1 exists passed Result: Group existence check passed for "dba". Check: Group existence for "oinstall" Node Name Status Comment ------------ ------------------------ ------------------------ node2 exists passed node1 exists passed Result: Group existence check passed for "oinstall". Check: User existence for "nobody" Node Name Status Comment ------------ ------------------------ ------------------------ node2 exists passed node1 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. Could not find a suitable set of interfaces for VIPs.”，可以忽略该错误信息，这是一个bug，Metalink中有详细说明，doc.id:338924.1。参考本文尾部列出的内容。对于上面描述的failed的包，尽可能的将其安装到系统。

RedHat Linux 2.6.18下安装MySQL 5.1.7及Navicat 8在Java + Oracle环境下对于clob类型的数据的插入相关资讯 Oracle教程

Oracle中纯数字的varchar2类型和（07/29/2015 07:20:43）
Oracle教程：Oracle中查看DBLink密（07/29/2015 07:16:55）
[Oracle] SQL*Loader 详细使用教程（08/11/2013 21:30:36）

Oracle教程：Oracle中kill死锁进程（07/29/2015 07:18:28）
Oracle教程：ORA-25153 临时表空间（07/29/2015 07:13:37）
Oracle教程之管理安全和资源（04/08/2013 11:39:32）

本文评论查看全部评论（0）