cluvfy comp baseline

Use the cluvfy comp baseline command to capture system and cluster configuration information to create a baseline. You can use this baseline for comparison with the state of the system. You can collect baselines at strategic times, such as after Oracle Clusterware installation, before and after upgrading Oracle Clusterware, or automatically as part of periodic execution of CVU running as an Oracle Clusterware resource. You can also compare several baselines.

Syntax

cluvfy comp baseline -collect {all | cluster | database} [-n node_list]
  [-d Oracle_home] [-db db_unique_name] [-bestpractice | -mandatory] [-binlibfilesonly
  [-reportname report_name] [-savedir save_dir]

cluvfy comp baseline -compare baseline1,baseline2,... [-deviations]

Parameters

Table A-5 cluvfy comp baseline Command Parameters

Parameter Description 
-collect {all | cluster |
 database}

The -collect parameter instructs CVU to create a baseline and save it in the Grid_home/cv/report/xml directory.

You can collect a baseline related to Oracle Clusterware (cluster), the database (database), or both (all).

 
-n node_list

Specify a comma-delimited list of non-domain qualified node names on which the test should be conducted.

 
-d Oracle_home

When collecting a database baseline, if you specify an Oracle home, then CVU collects baselines for all the databases running from the Oracle home.

Use the -db parameter to collect a baseline for a specific database.

 
-db db_unique_name

The name of the database for which you want to collect information.

When collecting a database baseline, if you specify the -db parameter, then CVU only collects the baseline for the specified database. If you do not specify -db, then CVU discovers all of the cluster databases configured in the system and the collects baselines for each of those.

 
-bestpractice | -mandatory

Specify -bestpractice to collect a baseline for only best practice recommendations. Specify -mandatory to collect a baseline for only mandatory requirements.

 
-binlibfilesonly

Specify -binlibfilesonly to collect only files in the bin/, lib/, and jlib/ subdirectories of the software home.

 
-report report_name

Use this optional parameter to specify a name for the report.

 
-savedir save_dir

Use this optional parameter to specify a location in which CVU saves the reports. If you do not specify the -savedir option, then CVU saves the reports in the Grid_home/cv/report directory.

 
-compare baseline1,baseline2,...

Specify -compare to compare baselines. If you specify only one baseline, then CVU displays the results of the collections. If you specify multiple baselines in a comma-delimited list, then CVU compares the values from the baselines against each other in an HTML document.

 
-deviations

Specify this parameter to display only the deviations from best practice recommendations or mandatory requirements, or both, (depending on whether you specified the -bestpractice and -mandatory parameters).

Usage Notes

  • Specify either the -collect or -compare parameter.

  • Items that CVU collects when running this command include:

    • Physical memory
    • Available memory
    • Swap space
    • Free space
    • Required packages
    • Recommended kernel parameters
    • /etc/inittab permissions
    • Domain sockets under /var/tmp/.oracle
    • Oracle Clusterware software file attributes
    • Network MTU size
    • OCR permissions, group, and owner (if OCR is stored on a shared file system)
    • OCR disk group (if OCR is stored on Oracle ASM
    • System requirement pluggable tasks (Zeroconf settings, /boot mount, Huge Pages existence, 8888 port availability, Ethernet jumbo frames)
    • Oracle Clusterware post-check pluggable tasks (css miscount, reboottime, disktimeout)
    • Database best practices

Examples

The following examples illustrate usage for both -collect and -compare command parameters:

$ cluvfy comp baseline -collect all -n all -db orcl -bestpractice -report bl1
   -savedir /tmp

$ cluvfy comp baseline -compare bl1,bl2