===============================================================

[nom]

Linux x86 README File

(OTN Distribution Kit - Sept, 2012)

===============================================================

• · Availability of CVU · 1
• · CVU installation from OTN · 2
• · Enhancements · 2
• · Known Limitations · 3
• · References · 3

=============================

• Availability of CVU

=============================

Welcome to the downloadable OTN distribution version of the [nom]

[nom] (CVU).

The [nom] (CVU) is a [nom] distributed with Oracle [nom] to assist in the [nom] of the components required to install and run Oracle [nom] and Oracle Real

Application [nom] (RAC). CVU was first released with Oracle Database

10g Release 2. CVU is available in the following three forms:

• · Installed in Oracle [nom] home
• · Available in Oracle [nom] DVD as packaged version
• · Available in Oracle Technology Network (OTN)

CVU is backward compatible to all the previous Oracle [nom] and Oracle RAC releases up to 10g Release 1. This version of CVU supports

10g Release 1, 10g Release 2, 11g Release 1, and 11g Release 2 for Oracle [nom] and RAC products.

For each [nom] command that supports the optional –r option to specify the supported Oracle release, the default release is assumed to be 11g Release 2. To perform [nom] for any previous release, ‘- r 10gR1’ or ‘-r 10gR2’ or ‘-r 11gR1’ must be specified. If the

[nom] are to be performed for a specific release earlier than

11g Release 2 then use of –r option can be avoided by setting the intended release value (‘10gR1’ or ‘10gR2’ or ‘11gR1’) for CV_ORACLE_RELEASE property in CVU’s configuration file, cvu_config

(located under <CVU installation root dir>/cv/admin directory).

=============================

• CVU installation from OTN

=============================

To install CVU from a zip file (cvupack.zip) downloaded from OTN:

• · Create a CVhome directory, for example:

“/home/<userid>/mycvhome”. It should have at least 200MB of free disk space.

• · Unzip cvupack.zip into <CVhome> directory.
• · (Optional) Set the environmental variable CV_DESTLOC. This should point to a writable area on *all* nodes. When invoked, the tool will attempt to copy the necessary bits as required to this location. Make sure the location exists on all nodes and it has write permission for CVU user. It is strongly recommended that you set this variable. If this variable has not been set, CVU will use "/tmp" as the default.
• · Run cluvfy from <CVhome>/bin directory. To verify, typically run /home/<userid>/mycvhome/bin/cluvfy. This should show the usage.

NOTE:

For ‘comp healthcheck’ command, CVU uses JDBC to connect to the database to verify various database parameters for the best practices recommendation. In order for CVU to be able to connect to the database, a CVU specific user, ‘cvusys’, with a CVU specific role, ‘cvusapp’, must be created and granted select permissions on system tables.

A sql script is included in <CVhome>/cv/admin/cvusys.sql to facilitate the creation of this user. Please create the user using this script on all the databases that are to be verified by CVU.

=============================

• Enhancements

=============================

• Fixed failure of VIP subnet checks when CVU is run second time
• Fixed issue of CVU failing to detect ASM instance
• Added a check to see all [nom] interconnect interfaces have same MTU across all the nodes
• Added a check to verify the connectivity of all the interfaces given a subnet or an interface
• Added a check to verify subnet masks of same subnet id are same across all the nodes.
• Made ASM checks more robust
• Slewing option is in NTPD in not needed for 11.2 or later

[nom] versions.

• Added few more critical bug fixes to stabilize CVU apart from the above mentioned.

=============================

• Known Limitations

=============================

• comp ocr no longer verifies logical integrity of OCR because this check requires super user privileges. It is recommended to verify logical integrity of OCR by running the command <crs_home>/bin/ocrcheck as a privileged user.
• When using, -html option for ‘comp healtcheck’ to display the best practices report in HTML, CVU searches for a browser to use in the following order: firefox, mozilla, opera, konqueror, epiphany. Browser is looked up strictly in the order mentioned, no effort is made to determine a default browser. If a browser is found in the default location, it will be used regardless of the correctness of the browser. This behavior can be altered by specifying the absolute path of the browser binary through CV_DEFAULT_BROWSER_LOCATION property in CVU’s configuration file, cvu_config(located under <CVU installation root dir>/cv/admin directory).

=============================

• References

=============================

For detailed information on using CVU, refer to:

Oracle® Grid Infrastructure Installation Guide 11g Release 2 (11.2) for Linux

Oracle® Real Application [nom] Installation Guide 11g Release 2

(11.2) for Linux and UNIX

Oracle® [nom] Administration and Deployment Guide 11g Release 2

(11.2)

For queries on CVU, refer to:

CVU FAQ on OTN

([lien]

download_homepage.html)