Shulou(Shulou.com)06/01 Report--

This article shows you how the CLUVFY tool installation process is, the content is concise and easy to understand, can definitely make your eyes bright, through the detailed introduction of this article, I hope you can get something.

If you have installed a RAC environment after 10g, you should be familiar with this tool. The runcluvfy.sh script is usually executed to check that the current system meets the installation conditions before installing Cluster and Database.

Describes comp-related options.

When installing RAC, because the cluvfy tool has not been installed, runcluvfy.sh implements the function of the cluvfy tool in shell and provides it with the installation disk, so that users can take advantage of the function of this tool before the database and CLUSTER are installed.

The main purpose of this tool is to verify that the system meets the conditions for installation.

This tool has a large number of options, so it is not possible and necessary to describe all the options in detail. If divided into large categories, the tool can be divided into two broad categories of options: comp to verify the functionality of components; and stage to verify deployment functionality.

You can use comp-list to list all the components that the cluvfy tool supports validation:

Bash-2.03$ cluvfy comp-list

USAGE:

Cluvfy comp [- verbose]

Valid components are:

Nodereach: checks reachability between nodes

Nodecon: checks node connectivity

Ssa: checks shared storage accessibility

Space: checks space availability

Sys: checks minimum system requirements

Clu: checks cluster integrity

Clumgr: checks cluster manager integrity

Ocr: checks OCR integrity

Crs: checks CRS integrity

Nodeapp: checks node applications existence

Admprv: checks administrative privileges

Peer: compares properties with peers

Components such as nodereach, nodecon, and sys are all essential inspection options for installing a Cluster environment:

Bash-2.03$ cluvfy comp nodereach-n racnode1,racnode2

Verifying node reachability

Checking node reachability...

Node reachability check passed from node "racnode2".

Verification of node reachability was successful.

The-n option specifies the node list, which cannot include spaces before and after the comma in the node list, otherwise an error will be reported.

Bash-2.03$ cluvfy comp nodereach-n racnode1,racnode2-verbose

Verifying node reachability

Checking node reachability...

Check: Node reachability from node "racnode2"

Destination Node Reachable?

-

Racnode1 yes

Racnode2 yes

Result: Node reachability check passed from node "racnode2".

Verification of node reachability was successful.

Use-verbose to get more detailed information.

Bash-2.03$ cluvfy comp nodecon-n racnode1,racnode2-verbose

Verifying node connectivity

Checking node connectivity...

Interface information for node "racnode2"

Interface Name IP Address Subnet

-

Ce0 172.25.198.223 172.25.0.0

Ce0 172.25.198.225 172.25.198.0

Ce1 10.0.0.2 10.0.0.0

Interface information for node "racnode1"

Interface Name IP Address Subnet

-

Ce0 172.25.198.222 172.25.0.0

Ce0 172.25.198.224 172.25.198.0

Ce1 10.0.0.1 10.0.0.0

Check: Node connectivity of subnet "172.25.0.0"

Source Destination Connected?

-

Racnode2:ce0 racnode1:ce0 yes

Result: Node connectivity check passed for subnet "172.25.0.0" with node (s) racnode2,racnode1.

Check: Node connectivity of subnet "172.25.198.0"

Source Destination Connected?

-

Racnode2:ce0 racnode1:ce0 yes

Result: Node connectivity check passed for subnet "172.25.198.0" with node (s) racnode2,racnode1.

Check: Node connectivity of subnet "10.0.0.0"

Source Destination Connected?

-

Racnode2:ce1 racnode1:ce1 yes

Result: Node connectivity check passed for subnet "10.0.0.0" with node (s) racnode2,racnode1.

Suitable interfaces for the private interconnect on subnet "172.25.0.0":

Racnode2 ce0:172.25.198.223

Racnode1 ce0:172.25.198.222

Suitable interfaces for the private interconnect on subnet "172.25.198.0":

Racnode2 ce0:172.25.198.225

Racnode1 ce0:172.25.198.224

Suitable interfaces for the private interconnect on subnet "10.0.0.0":

Racnode2 ce1:10.0.0.2

Racnode1 ce1:10.0.0.1

ERROR:

Could not find a suitable set of interfaces for VIPs.

Result: Node connectivity check failed.

Verification of node connectivity was unsuccessful on all the nodes.

The reason for the monitoring failure is that Oracle's bug,Oracle believes that an IP address starting with 172.25 cannot be used as a PUBLIC address, which has been mentioned many times before when installing RAC.

Bash-2.03$ cluvfy comp sys-n racnode1,racnode2-p database-r 10gR2-osdba dba

Verifying system requirement

Checking system requirements for 'database'...

Total memory check passed.

Free disk space check passed.

Swap space check passed.

System architecture check passed.

Operating system version check passed.

Operating system patch check failed for 112760-05.

Check failed on nodes:

Racnode2,racnode1

Operating system patch check passed for 108993-45.

Operating system patch check failed for 112763-13.

Check failed on nodes:

Racnode2,racnode1

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".

Kernel parameter check failed for "noexec_user_stack".

Check failed on nodes:

Racnode2,racnode1

Kernel parameter check passed for "SEMMNI".

Kernel parameter check passed for "SEMMNS".

Kernel parameter check passed for "SEMMSL".

Kernel parameter check passed for "SEMVMX".

Kernel parameter check passed for "SHMMAX".

Kernel parameter check passed for "SHMMIN".

Kernel parameter check passed for "SHMMNI".

Kernel parameter check passed for "SHMSEG".

Group existence check passed for "dba".

User existence check passed for "nobody".

System requirement failed for 'database'

Verification of system requirement was unsuccessful on all the nodes.

In addition to checking the regular installation check components, you can also verify the integrity of ocr, clu, and crs:

Bash-2.03$ cluvfy comp clu-n racnode1,racnode2-verbose

Verifying cluster integrity

Checking cluster integrity...

Node Name

-

Racnode1

Racnode2

Cluster integrity check passed

Verification of cluster integrity was successful.

Bash-2.03$ cluvfy comp ocr-n racnode1,racnode2-verbose

Verifying OCR integrity

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.

Verification of OCR integrity was successful.

Bash-2.03$ cluvfy comp crs-n racnode1,racnode2-verbose

Verifying CRS integrity

Checking CRS integrity...

Checking daemon liveness...

Check: Liveness for "CRS daemon"

Node Name Running

-

Racnode2 yes

Racnode1 yes

Result: Liveness check passed for "CRS daemon".

Checking daemon liveness...

Check: Liveness for "CSS daemon"

Node Name Running

-

Racnode2 yes

Racnode1 yes

Result: Liveness check passed for "CSS daemon".

Checking daemon liveness...

Check: Liveness for "EVM daemon"

Node Name Running

-

Racnode2 yes

Racnode1 yes

Result: Liveness check passed for "EVM daemon".

Liveness of all the daemons

Node Name CRS daemon CSS daemon EVM daemon

Racnode2 yes yes yes

Racnode1 yes yes yes

Checking CRS health...

Check: Health of CRS

Node Name CRS OK?

-

Racnode2 yes

Racnode1 yes

Result: CRS health check passed.

CRS integrity check passed.

Verification of CRS integrity was successful.

Bash-2.03$ cluvfy comp nodeapp-n racnode1,racnode2-verbose

Verifying node application existence

Checking node application existence...

Checking existence of VIP node application

Node Name Required Status Comment

Racnode2 yes exists passed

Racnode1 yes exists passed

Result: Check passed.

Checking existence of ONS node application

Node Name Required Status Comment

Racnode2 no exists passed

Racnode1 no exists passed

Result: Check passed.

Checking existence of GSD node application

Node Name Required Status Comment

Racnode2 no exists passed

Racnode1 no exists passed

Result: Check passed.

Using cluvfy, you can not only check whether the installation requirements are met, but also verify that the components are working properly.

The above is what the installation process of CLUVFY tools is like. Have you learned any knowledge or skills? If you want to learn more skills or enrich your knowledge reserve, you are 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.