Shulou(Shulou.com)05/31 Report--

Editor to share with you how to use the runcluvfy.sh script before Oracle installation, I believe most people do not know much about it, so share this article for your reference, I hope you can learn a lot after reading this article, let's go to know it!

Oracle officially recommends running this script before installing Oracle Grid Infrastructure to check that each node meets the official requirements for GI installation.

In the process of deploying Grid Infrastructure, we should not only learn how to use this script, but also understand some of its principles.

Runcluvfy.sh implements the functionality in shell and provides it to users along with GI's installation media, allowing users to take advantage of the tool's capabilities before the database and CLUSTER are installed.

Take a look at the basic usage of the script first.

. / runcluvfy.sh stage-pre crsinst-n rac1,rac2-verbose

. / runcluvfy.sh stage-pre crsinst-n rac1,rac2-fixup-verbose

Syntax description:

-pre: this option mainly checks whether the installation needs are met.

-post: the main purpose of this selection is to check whether the components are normal after installation.

-n: this option is used to specify a list of nodes, where 2 nodes are specified.

-verbose: this option is used to output detailed validation information.

-fixup: this is a new parameter added to Oracle 11gR2. With this parameter, you can generate a script called runfixup.sh.

The runfixup.sh script contains a series of operating system commands, which can be used to modify the operating system to meet the installation conditions.

After the verification of the system is completed, executing the script runfixup.sh as the root user can solve some situations in the operating system that do not meet the installation conditions.

Attach the output of my test library

Crmdb1:/oracle@grid >. / runcluvfy.sh stage-pre crsinst-n crmdb1,crmdb2-verbose

Performing pre-checks for cluster services setup

Checking node reachability...

Check: Node reachability from node "crmdb1"

Destination Node Reachable?

-

Crmdb2 yes

Crmdb1 yes

Result: Node reachability check passed from node "crmdb1"

Checking user equivalence...

Check: User equivalence for user "oracle"

Node Name Status

-

Crmdb2 passed

Crmdb1 passed

Result: User equivalence check passed for user "oracle"

Checking node connectivity...

Checking hosts config file...

Node Name Status

-

Crmdb2 passed

Crmdb1 passed

Verification of the hosts config file successful

Interface information for node "crmdb2"

Name IP Address Subnet Gateway Def. Gateway HW Address MTU

Eth0 192.168.1.5 192.168.1.0 0.0.0.0 132.64.196.1 78:58:60:B1:26:38 1500

Eth2 132.64.196.45 132.64.196.0 0.0.0.0 132.64.196.1 9C:37:F4:01:02:06 1500

Interface information for node "crmdb1"

Name IP Address Subnet Gateway Def. Gateway HW Address MTU

Eth0 192.168.1.4 192.168.1.0 0.0.0.0 132.64.196.1 78:58:60:B1:26:04 1500

Eth2 132.64.196.44 132.64.196.0 0.0.0.0 132.64.196.1 E4:35:C8:7C:03:AB 1500

Check: Node connectivity of subnet "192.168.1.0"

Source Destination Connected?

-

Crmdb2 [192.168.1.5] crmdb1 [192.168.1.4] yes

Result: Node connectivity passed for subnet "192.168.1.0" with node (s) crmdb2,crmdb1

Check: TCP connectivity of subnet "192.168.1.0"

Source Destination Connected?

-

Crmdb1:192.168.1.4 crmdb2:192.168.1.5 passed

Result: TCP connectivity check passed for subnet "192.168.1.0"

Check: Node connectivity of subnet "132.64.196.0"

Source Destination Connected?

-

Crmdb2 [132.64.196.45] crmdb1 [132.64.196.44] yes

Result: Node connectivity passed for subnet "132.64.196.0" with node (s) crmdb2,crmdb1

Check: TCP connectivity of subnet "132.64.196.0"

Source Destination Connected?

-

Crmdb1:132.64.196.44 crmdb2:132.64.196.45 passed

Result: TCP connectivity check passed for subnet "132.64.196.0"

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

Crmdb2 eth5:132.64.196.45

Crmdb1 eth5:132.64.196.44

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

Crmdb2 eth0:192.168.1.5

Crmdb1 eth0:192.168.1.4

Checking subnet mask consistency...

Subnet mask consistency check passed for subnet "192.168.1.0".

Subnet mask consistency check passed for subnet "132.64.196.0".

Subnet mask consistency check passed.

Result: Node connectivity check passed

Checking multicast communication...

Checking subnet "192.168.1.0" for multicast communication with multicast group "230.0.1.0"...

Check of subnet "192.168.1.0" for multicast communication with multicast group "230.0.1.0" passed.

Checking subnet "132.64.196.0" for multicast communication with multicast group "230.0.1.0".

PRVG-11134: Interface "132.64.196.44" on node "crmdb1" is not able to communicate with interface "132.64.196.45" on node "crmdb2"

Checking subnet "132.64.196.0" for multicast communication with multicast group "224.0.0.251".

Check of subnet "132.64.196.0" for multicast communication with multicast group "224.0.251" passed.

Check of multicast communication passed.

Checking ASMLib configuration.

Node Name Status

-

Crmdb2 passed

Crmdb1 passed

Result: Check for ASMLib configuration passed.

Check: Total memory

Node Name Available Required Status

Crmdb2 504.6577GB (5.29171932E8KB) 1.5GB (1572864.0KB) passed

Crmdb1 504.6577GB (5.29171932E8KB) 1.5GB (1572864.0KB) passed

Result: Total memory check passed

Check: Available memory

Node Name Available Required Status

Crmdb2 402.1997GB (4.21736976E8KB) 50MB (51200.0KB) passed

Crmdb1 401.8191GB (4.2133782E8KB) 50MB (51200.0KB) passed

Result: Available memory check passed

Check: Swap space

Node Name Available Required Status

Crmdb2 31.25GB (3.2767996E7KB) 16GB (1.6777216E7KB) passed

Crmdb1 31.25GB (3.2767996E7KB) 16GB (1.6777216E7KB) passed

Result: Swap space check passed

Check: Free disk space for "crmdb2:/tmp"

Path Node Name Mount point Available Required Status

--

/ tmp crmdb2 / tmp 28.5234GB 1GB passed

Result: Free disk space check passed for "crmdb2:/tmp"

Check: Free disk space for "crmdb1:/tmp"

Path Node Name Mount point Available Required Status

--

/ tmp crmdb1 / tmp 28.4948GB 1GB passed

Result: Free disk space check passed for "crmdb1:/tmp"

Check: User existence for "oracle"

Node Name Status Comment

Crmdb2 passed exists (501)

Crmdb1 passed exists (501)

Checking for multiple users with UID value 501

Result: Check for multiple users with UID value 501 passed

Result: User existence check passed for "oracle"

Check: Group existence for "oinstall"

Node Name Status Comment

Crmdb2 passed exists

Crmdb1 passed exists

Result: Group existence check passed for "oinstall"

Check: Group existence for "dba"

Node Name Status Comment

Crmdb2 passed exists

Crmdb1 passed exists

Result: Group existence check passed for "dba"

Check: Membership of user "oracle" in group "oinstall" [as Primary]

Node Name User Exists Group Exists User in Group Primary Status

--

Crmdb2 yes yes yes no failed

Crmdb1 yes yes yes no failed

Result: Membership check for user "oracle" in group "oinstall" [as Primary] failed

Check: Membership of user "oracle" in group "dba"

Node Name User Exists Group Exists User in Group Status

--

Crmdb2 yes yes yes passed

Crmdb1 yes yes yes passed

Result: Membership check for user "oracle" in group "dba" passed

Check: Run level

Node Name run level Required Status

Crmdb2 5 3,5 passed

Crmdb1 5 3,5 passed

Result: Run level check passed

Check: Hard limits for "maximum open file descriptors"

Node Name Type Available Required Status

--

Crmdb2 hard 65536 65536 passed

Crmdb1 hard 65536 65536 passed

Result: Hard limits check passed for "maximum open file descriptors"

Check: Soft limits for "maximum open file descriptors"

Node Name Type Available Required Status

--

Crmdb2 soft 65536 1024 passed

Crmdb1 soft 65536 1024 passed

Result: Soft limits check passed for "maximum open file descriptors"

Check: Hard limits for "maximum user processes"

Node Name Type Available Required Status

--

Crmdb2 hard 16384 16384 passed

Crmdb1 hard 16384 16384 passed

Result: Hard limits check passed for "maximum user processes"

Check: Soft limits for "maximum user processes"

Node Name Type Available Required Status

--

Crmdb2 soft 16384 2047 passed

Crmdb1 soft 16384 2047 passed

Result: Soft limits check passed for "maximum user processes"

Check: System architecture

Node Name Available Required Status

Crmdb2 x86_64 x86_64 passed

Crmdb1 x86_64 x86_64 passed

Result: System architecture check passed

Check: Kernel version

Node Name Available Required Status

Crmdb2 2.6.32-696.el6.x86_64 2.6.9 passed

Crmdb1 2.6.32-696.el6.x86_64 2.6.9 passed

Result: Kernel version check passed

Check: Kernel parameter for "semmsl"

Node Name Current Configured Required Status Comment

--

Crmdb2 6010 6010 250 passed

Crmdb1 6010 6010 250 passed

Result: Kernel parameter check passed for "semmsl"

Check: Kernel parameter for "semmns"

Node Name Current Configured Required Status Comment

--

Crmdb2 769280 769280 32000 passed

Crmdb1 769280 769280 32000 passed

Result: Kernel parameter check passed for "semmns"

Check: Kernel parameter for "semopm"

Node Name Current Configured Required Status Comment

--

Crmdb2 6010 6010 100 passed

Crmdb1 6010 6010 100 passed

Result: Kernel parameter check passed for "semopm"

Check: Kernel parameter for "semmni"

Node Name Current Configured Required Status Comment

--

Crmdb2 128 128 128 passed

Crmdb1 128 128 128 passed

Result: Kernel parameter check passed for "semmni"

Check: Kernel parameter for "shmmax"

Node Name Current Configured Required Status Comment

--

Crmdb2 270989756416 270989756416 4294967295 passed

Crmdb1 270989756416 270989756416 4294967295 passed

Result: Kernel parameter check passed for "shmmax"

Check: Kernel parameter for "shmmni"

Node Name Current Configured Required Status Comment

--

Crmdb2 4096 4096 4096 passed

Crmdb1 4096 4096 4096 passed

Result: Kernel parameter check passed for "shmmni"

Check: Kernel parameter for "shmall"

Node Name Current Configured Required Status Comment

--

Crmdb2 132318976 132318976 2097152 passed

Crmdb1 132318976 132318976 2097152 passed

Result: Kernel parameter check passed for "shmall"

Check: Kernel parameter for "file-max"

Node Name Current Configured Required Status Comment

--

Crmdb2 6815744 6815744 6815744 passed

Crmdb1 6815744 6815744 6815744 passed

Result: Kernel parameter check passed for "file-max"

Check: Kernel parameter for "ip_local_port_range"

Node Name Current Configured Required Status Comment

--

Crmdb2 between 9000.0 & 65500.0 between 9000.0 & 65500.0 between 9000.0 & 65500.0 passed

Crmdb1 between 9000.0 & 65500.0 between 9000.0 & 65500.0 between 9000.0 & 65500.0 passed

Result: Kernel parameter check passed for "ip_local_port_range"

Check: Kernel parameter for "rmem_default"

Node Name Current Configured Required Status Comment

--

Crmdb2 262144 262144 262144 passed

Crmdb1 262144 262144 262144 passed

Result: Kernel parameter check passed for "rmem_default"

Check: Kernel parameter for "rmem_max"

Node Name Current Configured Required Status Comment

--

Crmdb2 4194304 4194304 4194304 passed

Crmdb1 4194304 4194304 4194304 passed

Result: Kernel parameter check passed for "rmem_max"

Check: Kernel parameter for "wmem_default"

Node Name Current Configured Required Status Comment

--

Crmdb2 262144 262144 262144 passed

Crmdb1 262144 262144 262144 passed

Result: Kernel parameter check passed for "wmem_default"

Check: Kernel parameter for "wmem_max"

Node Name Current Configured Required Status Comment

--

Crmdb2 1048576 1048576 1048576 passed

Crmdb1 1048576 1048576 1048576 passed

Result: Kernel parameter check passed for "wmem_max"

Check: Kernel parameter for "aio-max-nr"

Node Name Current Configured Required Status Comment

--

Crmdb2 1048576 1048576 1048576 passed

Crmdb1 1048576 1048576 1048576 passed

Result: Kernel parameter check passed for "aio-max-nr"

Check: Package existence for "make"

Node Name Available Required Status

Crmdb2 make-3.81-23.el6 make-3.80 passed

Crmdb1 make-3.81-23.el6 make-3.80 passed

Result: Package existence check passed for "make"

Check: Package existence for "binutils"

Node Name Available Required Status

Crmdb2 binutils-2.20.51.0.2-5.46.el6 binutils-2.15.92.0.2 passed

Crmdb1 binutils-2.20.51.0.2-5.46.el6 binutils-2.15.92.0.2 passed

Result: Package existence check passed for "binutils"

Check: Package existence for "gcc (x86 / 64)"

Node Name Available Required Status

Crmdb2 gcc (x86 / 64)-4.4.7-18.el6 gcc (x86 / 64)-3.4.6 passed

Crmdb1 gcc (x86 / 64)-4.4.7-18.el6 gcc (x86 / 64)-3.4.6 passed

Result: Package existence check passed for "gcc (x86 / 64)"

Check: Package existence for "libaio (x86 / 64)"

Node Name Available Required Status

Crmdb2 libaio (x86 / 64)-0.3.107-10.el6 libaio (x86 / 64)-0.3.105 passed

Crmdb1 libaio (x86 / 64)-0.3.107-10.el6 libaio (x86 / 64)-0.3.105 passed

Result: Package existence check passed for "libaio (x86 / 64)"

Check: Package existence for "glibc (x86 / 64)"

Node Name Available Required Status

Crmdb2 glibc (x86-64)-2.12-1.209.el6 glibc (x86-64)-2.3.4-2.41 passed

Crmdb1 glibc (x86-64)-2.12-1.209.el6 glibc (x86-64)-2.3.4-2.41 passed

Result: Package existence check passed for "glibc (x86 / 64)"

Check: Package existence for "compat-libstdc++-33 (x86 / 64)"

Node Name Available Required Status

Crmdb2 compat-libstdc++-33 (x86 / 64)-3.2.3-69.el6 compat-libstdc++-33 (x86 / 64)-3.2.3 passed

Crmdb1 compat-libstdc++-33 (x86 / 64)-3.2.3-69.el6 compat-libstdc++-33 (x86 / 64)-3.2.3 passed

Result: Package existence check passed for "compat-libstdc++-33 (x86 / 64)"

Check: Package existence for "elfutils-libelf (x86 / 64)"

Node Name Available Required Status

Crmdb2 elfutils-libelf (x86 / 64)-0.164-2.el6 elfutils-libelf (x86 / 64)-0.97 passed

Crmdb1 elfutils-libelf (x86 / 64)-0.164-2.el6 elfutils-libelf (x86 / 64)-0.97 passed

Result: Package existence check passed for "elfutils-libelf (x86 / 64)"

Check: Package existence for "elfutils-libelf-devel"

Node Name Available Required Status

Crmdb2 elfutils-libelf-devel-0.164-2.el6 elfutils-libelf-devel-0.97 passed

Crmdb1 elfutils-libelf-devel-0.164-2.el6 elfutils-libelf-devel-0.97 passed

Result: Package existence check passed for "elfutils-libelf-devel"

Check: Package existence for "glibc-common"

Node Name Available Required Status

Crmdb2 glibc-common-2.12-1.209.el6 glibc-common-2.3.4 passed

Crmdb1 glibc-common-2.12-1.209.el6 glibc-common-2.3.4 passed

Result: Package existence check passed for "glibc-common"

Check: Package existence for "glibc-devel (x86 / 64)"

Node Name Available Required Status

Crmdb2 glibc-devel (x86 / 64)-2.12-1.209.el6 glibc-devel (x86 / 64)-2.3.4 passed

Crmdb1 glibc-devel (x86 / 64)-2.12-1.209.el6 glibc-devel (x86 / 64)-2.3.4 passed

Result: Package existence check passed for "glibc-devel (x86 / 64)"

Check: Package existence for "glibc-headers"

Node Name Available Required Status

Crmdb2 glibc-headers-2.12-1.209.el6 glibc-headers-2.3.4 passed

Crmdb1 glibc-headers-2.12-1.209.el6 glibc-headers-2.3.4 passed

Result: Package existence check passed for "glibc-headers"

Check: Package existence for "gcc-c++ (x86 / 64)"

Node Name Available Required Status

Crmdb2 gcc-c++ (x86 / 64)-4.4.7-18.el6 gcc-c++ (x86 / 64)-3.4.6 passed

Crmdb1 gcc-c++ (x86 / 64)-4.4.7-18.el6 gcc-c++ (x86 / 64)-3.4.6 passed

Result: Package existence check passed for "gcc-c++ (x86 / 64)"

Check: Package existence for "libaio-devel (x86 / 64)"

Node Name Available Required Status

Crmdb2 libaio-devel (x86 / 64)-0.3.107-10.el6 libaio-devel (x86 / 64)-0.3.105 passed

Crmdb1 libaio-devel (x86 / 64)-0.3.107-10.el6 libaio-devel (x86 / 64)-0.3.105 passed

Result: Package existence check passed for "libaio-devel (x86 / 64)"

Check: Package existence for "libgcc (x86 / 64)"

Node Name Available Required Status

Crmdb2 libgcc (x86 / 64)-4.4.7-18.el6 libgcc (x86 / 64)-3.4.6 passed

Crmdb1 libgcc (x86 / 64)-4.4.7-18.el6 libgcc (x86 / 64)-3.4.6 passed

Result: Package existence check passed for "libgcc (x86 / 64)"

Check: Package existence for "libstdc++ (x86 / 64)"

Node Name Available Required Status

Crmdb2 libstdc++ (x86 / 64)-4.4.7-18.el6 libstdc++ (x86 / 64)-3.4.6 passed

Crmdb1 libstdc++ (x86 / 64)-4.4.7-18.el6 libstdc++ (x86 / 64)-3.4.6 passed

Result: Package existence check passed for "libstdc++ (x86 / 64)"

Check: Package existence for "libstdc++-devel (x86 / 64)"

Node Name Available Required Status

Crmdb2 libstdc++-devel (x86 / 64)-4.4.7-18.el6 libstdc++-devel (x86 / 64)-3.4.6 passed

Crmdb1 libstdc++-devel (x86 / 64)-4.4.7-18.el6 libstdc++-devel (x86 / 64)-3.4.6 passed

Result: Package existence check passed for "libstdc++-devel (x86 / 64)"

Check: Package existence for "sysstat"

Node Name Available Required Status

Crmdb2 sysstat-9.0.4-33.el6 sysstat-5.0.5 passed

Crmdb1 sysstat-9.0.4-33.el6 sysstat-5.0.5 passed

Result: Package existence check passed for "sysstat"

Check: Package existence for "pdksh"

Node Name Available Required Status

Crmdb2 missing pdksh-5.2.14 failed

Crmdb1 missing pdksh-5.2.14 failed

Result: Package existence check failed for "pdksh"

Check: Package existence for "expat (x86 / 64)"

Node Name Available Required Status

Crmdb2 expat (x86 / 64)-2.0.1-13.el6_8 expat (x86 / 64)-1.95.7 passed

Crmdb1 expat (x86 / 64)-2.0.1-13.el6_8 expat (x86 / 64)-1.95.7 passed

Result: Package existence check passed for "expat (x86 / 64)"

Checking for multiple users with UID value 0

Result: Check for multiple users with UID value 0 passed

Check: Current group ID

Result: Current group ID check passed

Starting check for consistency of primary group of root user

Node Name Status

-

Crmdb2 passed

Crmdb1 passed

Check for consistency of root user's primary group passed

Starting Clock synchronization checks using Network Time Protocol (NTP)...

NTP Configuration file check started...

The NTP configuration file "/ etc/ntp.conf" is available on all nodes

NTP Configuration file check passed

Checking daemon liveness...

Check: Liveness for "ntpd"

Node Name Running?

-

Crmdb2 no

Crmdb1 yes

Result: Liveness check failed for "ntpd"

PRVF-5508: NTP configuration file is present on at least one node on which NTP daemon or service is not running.

Result: Clock synchronization check using Network Time Protocol (NTP) failed

Checking Core file name pattern consistency...

Core file name pattern consistency check passed.

Checking to make sure user "oracle" is not in "root" group

Node Name Status Comment

Crmdb2 passed does not exist

Crmdb1 passed does not exist

Result: User "oracle" is not part of "root" group. Check passed

Check default user file creation mask

Node Name Available Required Comment

Crmdb2 0022 0022 passed

Crmdb1 0022 0022 passed

Result: Default user file creation mask check passed

Checking consistency of file "/ etc/resolv.conf" across nodes

Checking the file "/ etc/resolv.conf" to make sure only one of domain and search entries is defined

File "/ etc/resolv.conf" does not have both domain and search entries defined

Checking if domain entry in file "/ etc/resolv.conf" is consistent across the nodes...

Domain entry in file "/ etc/resolv.conf" is consistent across nodes

Checking if search entry in file "/ etc/resolv.conf" is consistent across the nodes...

Search entry in file "/ etc/resolv.conf" is consistent across nodes

Checking file "/ etc/resolv.conf" to make sure that only one search entry is defined

All nodes have one search entry defined in file "/ etc/resolv.conf"

Checking all nodes to make sure that search entry is "localdomain.localdomain" as found on node "crmdb2"

All nodes of the cluster have same value for 'search'

Checking DNS response time for an unreachable node

Node Name Status

-

Crmdb2 failed

Crmdb1 failed

PRVF-5636: The DNS response time for an unreachable node exceeded "15000" ms on following nodes: crmdb2,crmdb1

File "/ etc/resolv.conf" is not consistent across nodes

Check: Time zone consistency

Result: Time zone consistency check passed

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

The above is all the contents of the article "how to use the runcluvfy.sh script before Oracle installation". Thank you for reading! I believe we all have a certain understanding, hope to share the content to help you, if you want to learn more knowledge, welcome to follow the industry information channel!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.