1. Database Error Messages
  2. PRVF-00001 to PRVF-10409

144 PRVF-00001 to PRVF-10409

PRVF-00001: Could not retrieve static nodelist. Verification cannot proceed

Cause: Error running lsnodes/olsnodes.

Action: Ensure that the executable exists and that it is executable by your OS userid.

PRVF-00002: could not retrieve local node name

Cause: The local node name could not be determined because the Java networking support functions failed to return a value.

Action: Ensure that host name is defined correctly using the 'hostname' command. On Linux machines, examine the files '/etc/sysconfig/network' and '/etc/resolv.conf' and ensure that the command 'hostname -f' succeeds.

PRVF-00006: Unable to check the existence of Oracle Home "{0}"

Cause: Could not verify the existence of the Oracle Home specified.

Action: Ensure that the Oracle Home location exists and is writeable by your user ID.

PRVF-00020: "{0}" is not writeable

Cause: The path specified is not writeable.

Action: Ensure that write access exists for the specified path.

PRVF-00040: The Remote Shell "{0}" requested by the client does not exist

Cause: Could not locate remote shell requested by the user.

Action: Ensure that the remote shell exists on all the nodes participating in the operation.

PRVF-00041: The Remote shell "{0}" requested by the client is not an executable file

Cause: The remote shell requested by the user is not a file.

Action: Ensure that the remote shell exists on all the nodes participating in the operation and that it is a file with execute permissions.

PRVF-00042: The Remote Copy command "{0}" requested by the client does not exist

Cause: Cannot locate remote copy command requested by the user.

Action: Ensure that the remote copy command exists on all the nodes participating in the operation.

PRVF-00045: The Secure Shell "{0}" requested by the client does not exist

Cause: Could not locate the secure shell executable specified.

Action: Ensure that the executable file specified exists.

PRVF-00046: The Secure Copy command "{0}" requested by the client does not exist

Cause: Could not locate the secure copy executable specified.

Action: Ensure that the executable file specified exists.

PRVF-00047: Unable to execute the Secure Shell "{0}" requested by the client

Cause: Could not execute the secure shell specified.

Action: Ensure that the secure shell specified allows execute access for the current user ID.

PRVF-00048: Unable to execute the Secure Copy command "{0}" requested by the client

Cause: Could not execute the secure copy specified.

Action: Ensure that the secure copy specified allows execute access for the current user ID.

PRVF-00051: The Remote Copy command "{0}" requested by the client is not an executable file

Cause: The remote copy command requested by the user was not an executable file.

Action: Ensure that the remote copy command exists on all the nodes participating in the operation and that it is a file with execute permissions.

PRVF-00054: Unable to find oifcfg executable file in directory "{0}"

Cause: An attempt to locate oifcfg executable file in specified directory failed.

Action: This is an internal error. Contact Oracle Support Services.

PRVF-00055: User "{0}" does not have administrative privileges to run this command

Cause: An attempt to run the Cluster Verification Utility (CVU) command failed because the user did not have sufficient authority to run it.

Action: The commands can be run as root user (uid=0) or by using the command line option '-method' to specify one of the privilege delegation methods.

PRVF-00056: User "{0}" does not have sufficient authorization to run this command

Cause: An attempt to run the CVU command failed because the user does not have sufficient authority to run it.

Action: The command can be run only by the Oracle installation owner. Make sure that you run these commands as appropriate user.

PRVF-02409: The device file "{0}" does not exist on node "{1}"

Cause: The expected device file could not be found.

Action: To enable asynchronous input-output operations using the asynchronous device driver, create the device file.

PRVF-02410: The device file "{0}" does not exist on nodes:

Cause: The expected device file could not be found.

Action: To enable asynchronous input-output operations using the asynchronous device driver, create the device file.

PRVF-02411: The file "{0}" is not a device file on nodes:

Cause: The file was not a device file.

Action: Ensure that the correct path and filename specified for the device file.

PRVF-02412: The file "{0}" is not a device file on node "{1}"

Cause: The file was not a device file.

Action: Ensure that the correct path and filename are specified for the device file.

PRVF-02413: Failed to retrieve details of the device file "{0}" on nodes:

Cause: An attempt to retrieve the attributes of a device file failed.

Action: Ensure that the file exists on the system and user has correct permissions to retrieve the details of specified device file.

PRVF-02414: Failed to retrieve details of the device file "{0}" on node "{1}"

Cause: An attempt to retrieve the attributes of a device file failed.

Action: Ensure that the file exists on the system and user has correct permissions to retrieve the details of specified device file.

PRVF-02415: The minor number of device file "{0}" is incorrect on the nodes:

Cause: The minor number of a device file was found incorrect as per the requirement.

Action: The third least significant bit (the 0x4 bit hexadecimal) of the minor number must be set.

PRVF-02416: The minor number of device file "{0}" is incorrect on the node "{1}"

Cause: The minor number of a device file was found incorrect as per the requirement.

Action: The third least significant bit (the 0x4 bit hexadecimal) of the minor number must be set.

PRVF-02417: Failed to retrieve the ID for device file "{0}" on the node "{1}"

Cause: Device file ID could not be retrieved on the node.

Action: Ensure that the device file exists at the specified path and is set to correct device ID.

PRVF-02418: Failed to retrieve minor number value for the device file "{0}" on the node "{1}"

Cause: The device file ID does not contain the correct minor number.

Action: Ensure the value of the minor number of the device file is correct.

PRVF-03911: Length of value of environment variable "{0}" exceeds the maximum recommended length of "{1}" on the nodes:

Cause: Length of the value of environment variable exceeds the recommended length.

Action: Ensure that the value of the environment variable does not exceed the standard operating system specified limit.

PRVF-03912: Length of value of environment variable "{0}" exceeds the maximum recommended length of "{1}" on the node "{2}"

Cause: Length of the value of environment variable exceeds the recommended length.

Action: Ensure that the value of the environment variable does not exceed the standard operating system specified limit. Restart the installer after changing the setting for environment variable.

PRVF-03913: Environment variable name "{0}" is set on nodes:

Cause: The environment variable was set on the nodes indicated.

Action: Ensure that the environment variable is not set to any value.

PRVF-03914: Environment variable name "{0}" is set on node "{1}"

Cause: The environment variable was set on the node indicated.

Action: Ensure that the environment variable is not set to any value. Restart the installer after changing the setting for environment variable.

PRVF-03915: Environment variable name "{0}" is not set on nodes:

Cause: Environment variable value could not be determined.

Action: Ensure that the environment variable is set and access permissions for the Oracle user allow access to read the environment variables.

PRVF-03916: Environment variable name "{0}" is not set on node "{1}"

Cause: Environment variable value could not be determined.

Action: Ensure that the environment variable is set and access permissions for the Oracle user allow access to read the environment variables. Restart the installer after changing the setting for environment variable.

PRVF-03917: Environment variable check for variable "{0}" cannot be performed on nodes:

Cause: Environment Variable value could not be determined.

Action: Ensure that the environment variable is set in either system or user environment and access permissions for the Oracle user allow access to read the environment variables.

PRVF-03918: Can not read environment variable "{0}" from node "{1}"

Cause: Environment variable value could not be determined.

Action: Check user equivalence and whether the user has administrative privileges on the node.

PRVF-03919: Failed to retrieve value of environment variable "{0}"

Cause: Environment variable value could not be determined.

Action: Check user equivalence and whether the user has administrative privileges on the node.

PRVF-03920: Environment variable name "{0}" is invalid for this operating system.

Cause: Environment variable name does not meet operating system standards.

Action: Ensure that the environment variable name is as per the operating system standards. Restart the installer after changing the setting for environment variable.

PRVF-03921: Environment variable name not specified.

Cause: Environment variable name was not specified.

Action: Ensure that a valid environment variable name is specified.

PRVF-03928: Adding the Oracle binary location to the PATH environment variable will exceed the OS length limit of [ "{0}" ], The maximum allowed length for PATH environment variable is ["{1}"] on the nodes:

Cause: The environment variable PATH needs to be updated to include the value "%ORACLE_HOME%/bin;". However, doing so will cause PATH to exceed the maximum allowable length that this operating system allows.

Action: Ensure that the length of your current PATH environment variable is less than that of specified maximum allowed length, so that adding of "%ORACLE_HOME%/bin;" does not exceed the operating system's environment variable length limit.

PRVF-03929: Adding the Oracle binary location to the PATH environment variable will exceed the OS length limit of [ "{0}" ], The maximum allowed length for PATH environment variable is ["{1}"] on the node "{2}"

Cause: The installer needs to update the PATH environment variable to include the value "%ORACLE_HOME%/bin;". However, doing so will cause PATH to exceed the maximum allowable length that this operating system allows.

Action: Ensure that the length of your current PATH environment variable is less than that of specified maximum allowed length, so that adding of "%ORACLE_HOME%/bin;" does not exceed the system's environment variable length limit. Restart the installer after changing the setting for environment variable.

PRVF-04001: Check: Space available on "{0}"

Cause: Could not determine mount point for location specified.

Action: Ensure that the location specified is available.

PRVF-04007: User equivalence check failed for user "{0}"

Cause: User equivalence for the specified user did not exist among all the nodes participating in the operation.

Action: Verify user equivalence on all the nodes participating in the operation. See 'Enabling SSH User Equivalency on Cluster Member Nodes' in the product documentation for more details.

PRVF-04008: User equivalence unavailable on all the specified nodes

Cause: User equivalence did not exist between the local node and the remote nodes.

Action: Ensure that user equivalence exists on all the nodes specified. The command 'cluvfy comp admprv -o user_equiv' can be used with the '-fixup' option to set up user equivalence. A password is required.

PRVF-04009: User equivalence is not set for nodes:

Cause: An attempt to perform a verification operation failed because user equivalence was not set up for the user on the indicated nodes.

Action: Ensure that user equivalence is set up between the local node and the indicated nodes. On UNIX platforms, the command 'cluvfy comp admprv -o user_equiv' can be used with the '-fixup' option to set up user equivalence. A password is required.

PRVF-04020: Inconsistent group IDs found for group "{0}"

Cause: The group ID for the specified group is not the same across all the nodes.

Action: Make sure that the group has the same group ID across all the nodes.

PRVF-04025: Inventory configuration file "{0}" does not exist

Cause: Cannot locate the inventory configuration file specified.

Action: Ensure that the correct inventory location was supplied and that the inventory file is there.

PRVF-04037: CRS is not installed on any of the nodes

Cause: Could not identify a CRS installation on any node.

Action: Ensure that CRS is installed on all the nodes participating in the operation.

PRVF-04038: CRS is not installed on nodes:

Cause: An attempt to identify Oracle Clusterware installation failed on specified nodes.

Action: Ensure that Oracle Clusterware is installed on all the nodes participating in the operation.

PRVF-04041: CSS is probably working with a non-clustered, local-only configuration on all the nodes

Cause: Oracle CSS was found to be configured to run in a local-only (non-clustered) environment on all the nodes.

Action: Ensure that cluster setup is correct and reconfigure Cluster Synchronization Services (CSS) as necessary on the nodes that are supposed to be executing in a clustered environment. See Oracle Cluster Synchronization Services documentation for further information.

PRVF-04042: CSS is probably working with a non-clustered, local-only configuration on nodes:

Cause: Oracle CSS was found to be configured to run in a local-only (non-clustered) environment on the nodes specified.

Action: Ensure that cluster setup is correct and reconfigure CSS as necessary on the nodes that are supposed to be executing in a clustered environment, see documentation regarding usage of the 'localconfig' script.

PRVF-04043: Unable to obtain OCR integrity details from any of the nodes

Cause: OCR was not found to be in a healthy state on any of the nodes.

Action: Verify the state of OCR on each of the nodes using 'ocrcheck'.

PRVF-04044: Unable to obtain OCR integrity details from nodes:

Cause: OCR was not found to be in a healthy state on some of the nodes.

Action: Verify the state of OCR on each of the nodes identified using 'ocrcheck'.

PRVF-04046: OCR ID is inconsistent among the nodes

Cause: Multiple OCR ID's found across the cluster nodes specified.

Action: Verify Oracle Clusterware configuration and setup with 'ocrcheck' on each node specified. See 'ocrcheck' documentation for further information.

PRVF-04048: Version of OCR found "{0}", expected version of OCR for this release is "{1}"

Cause: An incorrect version of OCR was found running on all the nodes.

Action: Verify version of OCR running on all the nodes using 'ocrcheck'.

PRVF-04049: OCR version is inconsistent amongst the nodes

Cause: Found different version of OCR running on the cluster nodes.

Action: Ensure that the correct version of OCR is running on all the nodes using 'ocrcheck'.

PRVF-04052: Total space in OCR device is inconsistent amongst the nodes

Cause: Found possible different devices in use across the nodes.

Action: Verify that the same OCR devices are used across the cluster nodes using 'ocrcheck'.

PRVF-04055: OCR integrity is invalid

Cause: Cluster registry integrity check failed.

Action: Verify state of cluster registry using ocrcheck on the nodes participating in the verification operation.

PRVF-04056: OCR integrity results are inconsistent amongst the nodes

Cause: Cluster registry integrity check failed on some of the nodes.

Action: Verify state of cluster registry using ocrcheck on the nodes participating in the verification operation.

PRVF-04060: failed to retrieve storage information

Cause: An internal error occurred while trying to retrieve storage information.

Action: Contact Oracle Support Services.

PRVF-04079: The number of addresses does not match the number of node

Cause: Cannot determine IP address for every node.

Action: Verify each node in the cluster has a valid IP address.

PRVF-04080: Network interface information cannot be obtained from any of the node

Cause: Could not find any network interface on any node in the cluster.

Action: Verify network interface(s) operational status on the cluster nodes.

PRVF-04083: Node reachability check failed from node "{0}"

Cause: Network link to target node could not be verified using PING.

Action: Verify network link to target node using the PING utility.

PRVF-04084: Make sure IP address "{0}" is up and is a valid IP address on node "{1}"

Cause: The network interface, IP address and subnet identified as "network interface : IP address [subnet]" is not available or is not functioning correctly.

Action: Please verify that the network interface identified is functioning as intended.

PRVF-04087: Node connectivity check failed

Cause: Encountered errors attempting to verify node connectivity using the "OS ping" utility.

Action: Ensure that the IP addresses that failed can be reached using the OS ping utility and resolve any issues found with those IP addresses/interfaces.

PRVF-04090: Node connectivity failed for interface "{0}"

Cause: Unable to verify connectivity to the interface indicated using the "OS ping" utility.

Action: Verify that the interface indicated is available.

PRVF-04095: Unable to reach any of the nodes

Cause: Unable to reach any of the nodes using the OS ping command.

Action: Ensure that the nodes specified are accessible.

PRVF-04097: Node "{0}" is not reachable

Cause: Unable to reach the node specified using the OS ping command.

Action: Ensure that the node specified is accessible.

PRVF-04098: User equivalence not found for node "{0}"

Cause: Cannot access node specified using user equivalence.

Action: Ensure that user equivalence is setup between the local node and the node specified.

PRVF-04101: Could not find a suitable set of interfaces for VIPs

Cause: Could not find a set of network interface adapters suitable for Virtual IP communication in the cluster .

Action: Ensure that the network interface adapters are installed and configured correctly on each node in the cluster and that each interface can communicate with a network gateway.

PRVF-04102: Could not find a suitable set of interfaces for the private interconnect

Cause: Could not find a set of network interface adapters suitable for Private communication in the cluster.

Action: Ensure that the network interface adapters are installed and configured correctly on each node in the cluster according to RFC 1918, or that the interfaces are not accessible from the public network.

PRVF-04107: Source node "{0}" is not reachable from local node

Cause: Unable to reach the source node specified using the OS ping command.

Action: Ensure that the source node specified is accessible.

PRVF-04108: User equivalence not found for source node "{0}"

Cause: Cannot access source node specified using user equivalence.

Action: Ensure that user equivalence is setup between the local node and the source node specified.

PRVF-04112: Cannot identify Oracle Restart installation

Cause: Cannot determine location of Oracle Restart installation.

Action: Ensure that the Oracle Restart environment is setup correctly.

PRVF-04113: Unable to obtain OLR integrity details from the local node

Cause: Could not verify the state of OLR on the local node.

Action: Check the status of OLR on the local node using the command 'ocrcheck -local'.

PRVF-04118: Unable to obtain Oracle Restart integrity details from the local node

Cause: Encountered an error when trying to run 'crsctl check has', or OHASD was found to be offline.

Action: Check the status of Oracle Restart using the 'crsctl check has' command on the local node.

PRVF-04123: Inconsistent user IDs found for user "{0}"

Cause: The user ID for the specified user is not the same across all the nodes.

Action: Make sure that the user has the same user ID across all the nodes.

PRVF-04125: Failed to retrieve storage type for "{0}"

Cause: The storage location specified may be non-existent or invalid or the user running the check may not have permissions to access the specified storage.

Action: Specify a valid existing location, and ensure that the user running the check has valid read permissions to this location.

PRVF-04126: Global failure for all nodes during execution of space check command

Cause: CVU's attempt to execute the space check command on all nodes had a total failure.

Action: Make sure that the location specified is a valid location and available on all nodes.

PRVF-04127: Unable to obtain OLR location

Cause: Could not verify the state of OLR.

Action: Check the status of OLR using the command 'ocrcheck -config -local'.

PRVF-04132: Multiple users "{0}" with UID "{1}" exist on nodes "{2}".

Cause: More than one user was found to have the same user ID as indicated in the error message.

Action: Ensure that the indicated user ID is not shared among two or more users. If Network Information Service (NIS) or Lightweight Directory Access Protocol (LDAP) is used, then ensure that the user ID is not duplicated between users in NIS or LDAP and the local user database.

PRVF-04143: Media Sensing of TCP/IP is enabled on the nodes:

Cause: Media Sensing setting for TCP/IP is enabled.

Action: To disable Media Sensing for TCP/IP, add the REG_DWORD registry entry by name 'DisableDHCPMediaSense' and value 1 to the 'HKEY_LOCAL_MACHINE\\System\\CurrentControlSet\\Services\\Tcpip\\Parameters' subkey. It is recommended to backup the Windows Registry before proceeding with any changes, Restart your system to make your changes effective after changing the registry.

PRVF-04144: Media Sensing status check for TCP/IP cannot be performed on nodes:

Cause: Media Sensing status could not be determined.

Action: Ensure that the access permissions for the Oracle user allow access to the Windows Registry and Registry has the REG_WORD entry named 'DisableDHCPMediaSense' with value 1 under 'HKEY_LOCAL_MACHINE\\System\\CurrentControlSet\\Services\\Tcpip\\Parameters' sub key on the node. It is recommended to backup the Windows Registry before proceeding with any changes, Restart your system to make your changes effective after changing the registry.

PRVF-04145: Error reading Registry sub key 'HKEY_LOCAL_MACHINE\\System\\CurrentControlSet\\Services\\Tcpip\\Parameters' from Windows Registry

Cause: Windows Registry sub key 'HKEY_LOCAL_MACHINE\\System\\CurrentControlSet\\Services\\Tcpip\\Parameters' could not be read.

Action: Ensure that the access permissions for the Oracle user allow access to the Windows Registry.

PRVF-04146: Error reading Registry sub key 'HKEY_LOCAL_MACHINE\\Cluster\\Parameters' from Windows Registry

Cause: Windows Registry sub key 'HKEY_LOCAL_MACHINE\\Cluster\\Parameters' could not be read.

Action: Ensure that the access permissions for the Oracle user allow access to the Windows Registry.

PRVF-04147: Error reading Registry value 'DisableDHCPMediaSense' for Windows Media Sensing

Cause: Could not read Windows Registry value 'DisableDHCPMediaSense' under 'HKEY_LOCAL_MACHINE\\System\\CurrentControlSet\\Services\\Tcpip\\Parameters' sub key.

Action: Ensure that the access permissions for the Oracle user allow access to the Windows Registry and the Registry value 'DisableDHCPMediaSense' under 'HKEY_LOCAL_MACHINE\\System\\CurrentControlSet\\Services\\Tcpip\\Parameters' sub key is present on the node.

PRVF-04148: Error reading Registry value 'DisableClusSvcMediaSense' for Windows Media Sensing

Cause: Could not read Windows Registry value 'DisableClusSvcMediaSense' under 'HKEY_LOCAL_MACHINE\\Cluster\\Parameters' sub key.

Action: Ensure that the access permissions for the Oracle user allow access to the Windows Registry and the Registry value 'DisableClusSvcMediaSense' under 'HKEY_LOCAL_MACHINE\\Cluster\\Parameters' sub key is present on the node.

PRVF-04151: Found different access permissions for the above storage location across the nodes specified

Cause: The access permissions for the path specified (i.e. read, write, execute) are different, or could not be determined, across the nodes specified.

Action: Ensure that the access permissions allow access for the Oracle user on all the nodes specified.

PRVF-04152: The access permissions for the above storage location do not allow the user access across the nodes specified

Cause: The access permissions for the path specified (i.e. read, write, execute) do not allow the user access.

Action: Ensure that the access permissions allow access for the Oracle user on all the nodes specified.

PRVF-04164: Size of the OCR location "{0}" does not meet the requirement. [Expected="{1}" ; Found="{2}"]

Cause: Size of the ocr device does not meet the requirement

Action: Increase the size of the ocr device

PRVF-04190: Verification of the hosts config file failed

Cause: The '/etc/hosts' file(s) contain incorrect, or incomplete, network host information.

Action: Review the contents of the node's '/etc/hosts' file and ensure that each entry contains a valid IP address and a canonical host name for the specified IP address.

PRVF-04192: unable to verify the contents of the '/etc/hosts' file.

Cause: An attempt to verify the contents of the '/etc/hosts' file failed.

Action: Review the node's '/etc/hosts' file and ensure that it exists, has the necessary permissions and each entry contains at least an IP address and a host name for the IP address specified.

PRVF-04211: The specified OCR location "{0}" is not a partition

Cause: The location specified should be a disk partition rather than the disk itself.

Action: Specify a disk partition as the OCR storage.

PRVF-04212: The specified Voting Disk location "{0}" is not a partition

Cause: The location specified should be a disk partition rather than the disk itself.

Action: Specify a disk partition as the Voting Disk storage.

PRVF-04213: Encountered issues with the following OCR Device/Files

Cause: 'ocrcheck' returned failure, or warning, messages with the Device(s)/File(s) listed.

Action: Run 'ocrcheck' and resolve issues reported.

PRVF-04253: CRS integrity check passed, but encountered some warnings

Cause: Some warnings were encountered while verifying CRS integrity.

Action: Review warnings and make modifications as necessary.

PRVF-04309: The effective group id "{0}" differs from the primary group id "{1}" of user "{2}"

Cause: The user is currently logged into a group that is not user's primary group.

Action: Invoke the application after logging in to the primary group (using command 'newgrp primary group').

PRVF-04314: There is no primary group on this Operating System

Cause: An attempt was made to check users primary group on an Operating System where there are no primary groups.

Action: This is an internal error; contact Oracle Support.

PRVF-04317: User "{0}" is part of group "{1}". Check failed

Cause: The user who was executing this check was found to be part of root group.

Action: Use the 'id' command to check if the user is part of root group. Remove the user from root group using the 'usermod' command and try again.

PRVF-04318: Checking that user "{0}" is not part of "{1}" group could not be performed on node "{2}"

Cause: A node specific error occurred while checking if user is not part of root group.

Action: Check that the node is accessible and user equivalence exists between the node on which command was executed and the node on which the check failed.

PRVF-04353: Proper soft limit for resource "{0}" not found on node "{1}" [Expected = "{2}" ; Found = "{3}"]

Cause: Soft limit for the resource does not meet the requirement on the specified node.

Action: Modify the resource limits to meet the requirement.

PRVF-04354: Proper hard limit for resource "{0}" not found on node "{1}" [Expected = "{2}" ; Found = "{3}"]

Cause: Hard limit for the resource does not meet the requirement on the specified node.

Action: Modify the resource limits to meet the requirement.

PRVF-04355: Resource soft limit check for "{0}" failed on node "{1}"

Cause: Soft limit of the resource could not be determined.

Action: Ensure that the resource limit configuration is accessible.

PRVF-04356: Resource hard limit check for "{0}" failed on node "{1}"

Cause: Hard limit of the resource could not be determined.

Action: Ensure that the resource limit configuration is accessible.

PRVF-04363: Persistent configuration check for cluster nodes failed

Cause: The nodes IP address configuration was not found to be persistent.

Action: Make the nodes IP address configuration persistent using the 'crsctl pin css' command, see Oracle documentation 'Pinning Cluster Nodes for Oracle Database Release' for further information."

PRVF-04528: Check for existence of config file "{0}" could not be performed on node "{1}".

Cause: Could not verify existence of configuration file specified.

Action: Verify access to node indicated and that the config file exists.

PRVF-04529: Host-guid of node "{0}" is not unique

Cause: The system guid value is not unique across all the cluster nodes.

Action: Ensure that the guid value is unique across all cluster nodes using 'ocrcheck'.

PRVF-04530: OCFS is not configured in runlevel 3,4 and 5 on the node

Cause: Runlevel was not configured with levels 3,4 and 5 all being on.

Action: Check OCFS configuration and ensure the run levels indicated are on.

PRVF-04554: Unable to retrieve {0} resource name from node {1}.

Cause: Could not identify node application resource name specified on the node specified.

Action: Ensure that the node application resource name specified is available for the node specified.

PRVF-04555: Node application "{0}" does not exist on node "{1}"

Cause: Could not identify resource specified on the node specified.

Action: Ensure that the resource specified is available for the node specified.

PRVF-04556: Failed to check existence of node application "{0}" on node "{1}"

Cause: Could not verify existence of the nodeapp identified on the node specified .

Action: Ensure that the resource specified is available on the node specified, see 'srvctl add nodeapps' for further information.

PRVF-04567: Failed to check existence of VIP node application on nodes "{0}"

Cause: An attempt to verify existence of the VIP on the nodes specified failed.

Action: Look at the accompanying messages for details on the cause of failure.

PRVF-04570: Failed to check existence of NETWORK node application on nodes "{0}"

Cause: An attempt to verify existence of the NETWORK node application on the nodes specified failed.

Action: Look at the accompanying messages for details on the cause of failure.

PRVF-04573: Failed to check existence of GSD node application on nodes "{0}"

Cause: An attempt to verify existence of the GSD node application on the nodes specified failed.

Action: Look at the accompanying messages for details on the cause of failure.

PRVF-04576: Failed to check existence of ONS node application on nodes "{0}"

Cause: An attempt to verify existence of the ONS node application on the nodes specified failed.

Action: Look at the accompanying messages for details on the cause of failure.

PRVF-04578: Failed to check existence of node applications on nodes "{0}"

Cause: An attempt to verify existence of node applications on the nodes specified failed.

Action: Look at the accompanying messages for details on the cause of failure.

PRVF-04579: An error occurred while parsing the output of the command "{0}" for node application resource "{1}". The output is: "{2}"

Cause: An error occurred while parsing output of the command listed for the resource listed.

Action: This is an internal error. Contact Oracle Support Services.

PRVF-04580: Node applications do not exist on any node of the cluster

Cause: Node applications were not configured on the cluster nodes.

Action: Node applications are created when root scripts are run. They can be also be created using the command 'srvctl add nodeapps'.

PRVF-04606: User equivalence not found for reference node "{0}"

Cause: Cannot access reference node using user equivalence.

Action: Ensure that user equivalence is configured between the local node and the node specified. See Enabling SSH User Equivalency on Cluster Member Nodes documentation for further information.

PRVF-04657: Name resolution setup check for "{0}" (IP address: {1}) failed

Cause: Inconsistent IP address definitions found for the SCAN name identified using DNS and configured name resolution mechanism(s).

Action: Look up the SCAN name with nslookup, and make sure the returned IP addresses are consistent with those defined in NIS and /etc/hosts as configured in /etc/nsswitch.conf by reconfiguring the latter. Check the Name Service Cache Daemon (/usr/sbin/nscd) by clearing its cache and restarting it.

PRVF-04661: found inconsistent 'hosts' entry in /etc/nsswitch.conf on node {0}

Cause: The 'hosts' specifications in the /etc/nsswitch.conf file is different the indicated node.

Action: Ensure that the 'hosts' entries define the same lookup order in the /etc/nsswitch.conf file across all cluster nodes.

PRVF-04663: found configuration issue with the 'hosts' entry in the /etc/nsswitch.conf file

Cause: The 'hosts' specifications in the /etc/nsswitch.conf file should specify 'dns' before 'nis' to ensure proper IP address to name mapping.

Action: Ensure that the 'hosts' entries across the cluster nodes define 'dns' lookup before 'nis' lookup.

PRVF-04664: Found inconsistent name resolution entries for SCAN name "{0}"

Cause: The nslookup utility and the configured name resolution mechanisms, as defined in /etc/nsswitch.conf, returned inconsistent IP address information for the SCAN name identified.

Action: Check the Name Service Cache Daemon (/usr/sbin/nscd), the Domain Name Server (nslookup) and the /etc/hosts file to make sure the IP address for the SCAN names is registered correctly. Clear the stale IP addresses from the name service cache using the command '/usr/sbin/nscd -i hosts'.

PRVF-04758: 'lsnodes' could not be executed on the node

Cause: Error running 'lsnodes'.

Action: Ensure that the executable exists and that it is executable by your OS userid.

PRVF-04759: 'lsnodes' execution failed on the node

Cause: Error running 'lsnodes'.

Action: Ensure that the executable CRSHOME/bin/lsnodes exists and that it is executable by your OS userid.

PRVF-04761: Multiple partitions found. Cluster is fragmented.

Cause: An attempt to verify that the list of nodes that constitute the cluster is same on all nodes failed because different lists of cluster nodes were obtained on different nodes.

Action: Make sure that all nodes specified in the command belong to the same cluster. Make sure that all nodes share the same voting disk.

PRVF-04859: Location "{0}" not accessible on nodes to be added.

Cause: Location does not exist, or cannot be created, on node(s) to be added.

Action: Ensure that the location either exists or can be created on the node(s) to be added.

PRVF-04864: Path "{0}" exists but the current user has no write access on the following nodes: "{1}"

Cause: During write access verification, the path (or its parent) could not be written by the current user.

Action: Verify writeable access, by the current user, to entire path specified on the nodes(s) listed.

PRVF-04866: Device location check failed for: "{0}"

Cause: Cannot verify location specified.

Action: Verify location specified is accessible across cluster node(s).

PRVF-04868: Virtual IP (VIP) "{0}" found for node "{1}"

Cause: The VIP node application identified was found on the node specified.

Action: Removed the specified VIP node application from the node specified.

PRVF-04869: Shared OCR location check failed

Cause: Problem reading inventory file for CRS home location.

Action: Verify inventory file integrity.

PRVF-04950: Error checking Operating System Version compatibility for Universal Storage Manager on node "{0}"

Cause: A remote operation to check Operating System version on the remote node failed.

Action: See the action for the additional error message displayed.

PRVF-04954: Version "{0}" is NOT supported for installing ACFS on node "{1}"

Cause: The version of operating system on the node is not compatible for installing ACFS.

Action: Check documentation for compatible version and install compatible version.

PRVF-05054: Verification of SCAN VIP and listener setup failed

Cause: Could not identify any SCAN, or SCAN listener, resources on the cluster.

Action: Verify SCAN configuration using 'srvctl config scan'.

PRVF-05056: SCAN listener "{0}" not running

Cause: The identified listener was not in the running state.

Action: Start the identified listener using 'srvctl start scan_listener'.

PRVF-05057: SCAN listener port for listener "{0}" does not match other ports

Cause: The port number used for the listener did not match those of all the instances of the listener that were started.

Action: Ensure that all the port numbers for the identified listener match. Check the documentation to get the details about the commands 'srvctl config scan' and 'srvctl modify scan' used for inspecting and modifying details of SCAN resource port numbers.

PRVF-05059: An error was encountered while verifying the SCAN configuration

Cause: An error was encountered while obtaining SCAN information.

Action: Review additional messages displayed for details of the error that was encountered.

PRVF-05060: SCAN listener processing error

Cause: An error was encountered while obtaining SCAN listener information.

Action: Review additional messages displayed for details of the error that was encountered.

PRVF-05061: SCAN VIP "{0}" not running

Cause: The SCAN VIP resources is not in the 'running' state.

Action: Start the SCAN VIP resource using using 'srvctl start scan -i num'.

PRVF-05062: SCAN VIP "{0}" and Scan listener "{1}" not running

Cause: The SCAN VIP and SCAN listener resources are not in the 'running' state.

Action: Start the SCAN VIP and SCAN listener resources using 'srvctl'.

PRVF-05064: SCAN and SCAN listener may not function correctly

Cause: Either the SCAN VIP or the SCAN listener was not running, or the port numbers used for the listeners did not match across the nodes.

Action: Either start the SCAN VIP or the SCAN listener, or ensure that the port numbers used for the SCAN listeners match across the nodes in the cluster.

PRVF-05065: Warning: all SCAN VIPs and SCAN listeners are running on node "{0}"

Cause: All the SCAN VIPs and SCAN listeners were found to be running on specified node.

Action: Relocate scan using 'srvctl relocate scan' command to different nodes of the cluster.

PRVF-05067: TCP connectivity check for SCAN listener "{0}" failed on node "{1}"

Cause: An attempt to connect to SCAN listener specified failed from the node specified.

Action: Examine the accompanying TNS error messages and respond accordingly.

PRVF-05109: ASM Running check failed. ASM is not running on all specified nodes

Cause: ASM was not running on all the specified nodes.

Action: Ensure that ASM is running on all the nodes specified, see 'srvctl start asm' for further information.

PRVF-05110: ASM is not running on nodes: "{0}"

Cause: ASM was not running on the cluster nodes specified.

Action: Ensure that ASM is running on all the cluster nodes.

PRVF-05114: Disk Group check failed. No Disk Groups configured

Cause: No ASM disk groups were found configured on the ASM instance.

Action: Ensure that the necessary disk groups are configured in ASM.

PRVF-05117: The owner of device "{0}" is different across cluster nodes.

Cause: The attempted task could not be completed because the owner for the identified device was not the same across all the nodes.

Action: Ensure that the device has the same owner across all the nodes.

PRVF-05121: Group of device "{0}" is different across cluster nodes.

Cause: The attempted task could not be completed because the group for the identified device was not the same across all the nodes.

Action: Ensure that the device has the same group across all the nodes.

PRVF-05125: The permissions for device "{0}" are different across cluster nodes.

Cause: The Cluster Verification Utility determined that the permissions for the indicated device were not the same across all the cluster nodes.

Action: Ensure that the indicated device has the same permissions across all the nodes and retry the operation.

PRVF-05137: Failure while checking ASM status on node "{0}"

Cause: Could not verify ASM running on node specified.

Action: Ensure that ASM is running on the node specified.

PRVF-05144: ASM Disk group "{0}" is unavailable on nodes "{1}"

Cause: Could not verify existence of ASM disk group specified on the nodes indicated.

Action: Verify existence of ASM group identified on the specified nodes, see 'asmcmd' for further information.

PRVF-05145: ASM Disk group "{0}" is unavailable on all nodes

Cause: Could not verify existence of ASM disk group specified on all the nodes.

Action: Verify existence of ASM group identified on the cluster nodes.

PRVF-05157: could not verify ASM disk group "{0}" for voting disk location "{1}" is available on node "{2}"

Cause: The ASM disk group specified was not running on the indicated node.

Action: Ensure that the ASM disk group is configured correctly and defined on the node indicated, and ensure that the voting disk locations are configured correctly.

PRVF-05174: ACFS Driver version is not compatible with Operating System version on node "{0}"

Cause: The version of ACFS driver is not compatible with the Operating system version on the node.

Action: Check documentation for compatible version and install compatible version.

PRVF-05175: Failed to retrieve ACFS driver version on node "{0}". Driver version compatibility check cannot be performed

Cause: The version of the ACFS driver could not be retrieved from specified nodes.

Action: Make sure that ACFS driver is installed on these nodes.

PRVF-05176: Failed to retrieve Operating System version on the local node. ACFS driver version compatibility check will not be performed

Cause: Operating system version on local node could not be determined.

Action: Look at the accompanying error messages displayed and fix the problems indicated.

PRVF-05177: Global failure when attempting to query ACFS driver state option "{0}" on all nodes

Cause: ACFS driver state could not be obtained on all the nodes.

Action: Make sure that user executing this check has execute permissions on the usm_driver_state command.

PRVF-05184: Check of following Udev attributes of "{0}" failed: {1} \nData used for above verification obtained from file: \n{2}\nRule used from above file: \n{3}

Cause: Found incorrect attributes for the specified device.

Action: Ensure that the device attributes are set correctly. See Configurable Dynamic Device Naming documentation (udev) for further information.

PRVF-05193: No devices found matching discovery string "{0}"

Cause: The specified device may not exist on the node being tested.

Action: Specify a correct discovery string that matches to existing devices on the node being tested.

PRVF-05195: No shared devices found

Cause: No shared storage was found based on the discovery string used in the verification.

Action: A message should have been displayed for each shared storage check failure. For each such message, perform the suggested action for that message.

PRVF-05196: Failed to retrieve OCR locations

Cause: An attempt to retrieve the OCR locations failed, possibly due to incorrect or incomplete Clusterware install, or due to incorrect configuration of the OCR, or due to invalid or incorrect OCR location file ocr.loc.

Action: Make sure that the Clusterware installation and Clusterware configuration has been correctly completed, and the ocr.loc file is present and accessible.

PRVF-05197: Failed to retrieve voting disk locations

Cause: An attempt to retrieve the voting disk locations failed, possibly due to incorrect or incomplete Clusterware install, or due to incorrect configuration of the Clusterware.

Action: Make sure that the Clusterware installation and Clusterware configuration has been correctly completed.

PRVF-05205: GNS VIP resource configuration check failed.

Cause: An error occurred while trying to obtain GNS VIP resource configuration information.

Action: Look at the accompanying messages for details on the cause of failure.

PRVF-05210: GNS resource is running on multiple nodes "{0}"

Cause: GNS resource should be running on only one node in the cluster at any given time. It was found to be running on multiple nodes at the same time.

Action: Stop the GNS resources running on various nodes using 'srvctl stop gns' command and leave it running on just one node of the cluster.

PRVF-05211: GNS resource is not running on any node of the cluster

Cause: GNS resource should be running on one node of the cluster. GNS resource wasn't running on any node.

Action: GNS can be configured using 'srvctl add gns' command. Use 'srvctl start gns' command to start GNS.

PRVF-05213: GNS resource configuration check failed

Cause: An error occurred while trying to obtain GNS resource configuration information.

Action: Look at the accompanying messages for details on the cause of failure.

PRVF-05216: The following GNS resolved IP addresses for "{0}" are not reachable: "{1}"

Cause: The listed IP addresses for the fully domain qualified name (FDQN) listed in the message and resolved by GNS were not reachable.

Action: Make sure that the configuration of GNS resource is proper using 'srvctl config gns' command. If GNS is configured correctly make sure that the network administrator has provided a set of IP addresses for the subdomain of the cluster and Domain Name Server (DNS) is forwarding requests for these to the GNS.

PRVF-05217: An error occurred while trying to look up IP address for "{0}"

Cause: An error occurred while trying to translate the fully domain qualified name (FDQN), listed in the message, to IP addresses.

Action: These IP address requests should have been forwarded to GNS by the Domain Name Server (DNS). Check the configuration of GNS resource using 'srvctl config gns' command. If GNS is configured correctly make sure that the network administrator has provided a set of IP addresses for the subdomain of the cluster and DNS is forwarding requests for these to the GNS.

PRVF-05218: Domain name "{0}" did not resolve to an IP address.

Cause: The fully qualified domain name (FQDN) listed in the message did not resolve to an IP address.

Action: Ensure that the configuration of GNS resource is correct using the 'srvctl config gns' command. If GNS is configured correctly, ensure that the network administrator has provided a set of IP addresses for the subdomain of the cluster and that the domain name server (DNS) is forwarding requests for these to the GNS.

PRVF-05219: GNS and GNS VIP resources are running on different nodes. GNS is running on nodes "{1}" while GNS VIP is running on "{0}".

Cause: The GNS and GNS VIP resources were running on different nodes.

Action: If GNS should be running on one node of the cluster at any given point of time. Make sure that GNS is not running on multiple nodes of the cluster using 'srvctl config gns' command. If GNS is running on multiple nodes then shut down all but one using 'srvctl stop gns' command.

PRVF-05220: GNS VIP resource was not running on any node of the cluster

Cause: The GNS VIP resource was not running on any nodes of the cluster.

Action: Make sure that the VIP name specified in 'srvctl add gns' command is an unused address belonging to one of the public networks of the cluster nodes.

PRVF-05223: The GNS subdomain name "{0}" is not a valid domain name

Cause: The GNS domain name specified was not a valid domain name.

Action: A valid domain name starts with an alphabet and contain characters [A-Z], [a-z], [0-9], '.', '-'. Refer to RFC-1035 for more information.

PRVF-05227: GNS VIP "{0}" does not resolve to a valid IP address

Cause: The specified GNS VIP does not resolve to an IP address.

Action: Make sure that the VIP name is spelled correctly. Make sure that the VIP name is registered with the DNS. Make sure that there are no firewalls between the cluster and the DNS server.

PRVF-05229: GNS VIP is active before Clusterware installation

Cause: GNS VIP was found to be active on the public network before Clusterware installation.

Action: If you are upgrading an older release of Clusterware this is not an error. In case of new installation GNS VIP will be brought up by GNS resource after Clusterware installation. Make sure that GNS VIP is configured to be an unused IP address.

PRVF-05230: GNS VIP is inactive after Clusterware installation

Cause: GNS VIP was not reachable after Clusterware installation.

Action: Bring the GNS resource online using 'srvctl start gns' command.

PRVF-05232: The GNS subdomain qualified host name "{0}" was resolved into an IP address

Cause: The specified GNS subdomain qualified host name was resolved into an IP address before Clusterware installation.

Action: Ensure that the DNS is configured to forward (rather than resolve) names in the GNS subdomain.

PRVF-05233: There are no public networks that match the GNS VIP "{0}"

Cause: GNS VIP subnet number did not match any of the public networks on the node.

Action: Specify an address that matches the public subnet number for GNS VIP.

PRVF-05253: Command "{0}" executed to retrieve GPNP resource status failed on all of the nodes

Cause: An attempt to execute the displayed command failed on all of the nodes.

Action: Make sure that the nodes of the cluster are accessible from the current node. Make sure that the user executing the check has permission to execute commands on nodes using 'ssh'.

PRVF-05254: Command "{0}" executed on node "{1}" produced no output

Cause: An attempt to run the command listed on the node listed produced no output.

Action: This is an internal error. Contact Oracle support services.

PRVF-05255: The GPNP resource is not in ONLINE status on the following nodes: {0}

Cause: The GPNP resource was found to be in OFFLINE or UNKNOWN state on the nodes listed.

Action: This is not an error if the GPNP resource was shutdown. If it is not the expected state then use the command 'crsctl start res ora.gpnpd -init' to start the GPNP resource.

PRVF-05256: Command "{0}" executed to retrieve the GPNP resource status failed on nodes: {1}

Cause: An attempt to run the command listed failed on the node listed.

Action: Make sure that the nodes listed are accessible from the current node. Make sure that the user executing the check has permission to executed commands on the node(s) listed using 'ssh'.

PRVF-05300: Failed to retrieve active version for CRS on this node

Cause: Could not identify location of CRS home.

Action: Ensure that correct installation of CRS exists.

PRVF-05301: Failed to locate CRS home

Cause: Could not locate the CRS home.

Action: Ensure that the install of CRS has completed successfully and the CRS home is setup correctly.

PRVF-05302: Failed to execute the exectask command on node "{0}"

Cause: Could not execute command specified on node listed.

Action: Verify command specified can be exectued on node listed.

PRVF-05305: The Oracle Clusterware is not healthy on node "{0}"

Cause: An error was found with the Oracle Clusterware on the node specified.

Action: Review the error reported and resolve the issue specified.

PRVF-05307: Failed to retrieve Oracle Restart home

Cause: Could not identify location of Oracle Restart home.

Action: Ensure that Oracle Local Repository (OLR) was created correctly. See Oracle Local Repository documentation for further information.

PRVF-05308: ohasd is either not running or could not be contacted on node "{0}"

Cause: CRSCTL did not report that OHAS was online.

Action: Review the error information displayed and verify the state of OHAS on the node identified.

PRVF-05310: Check for existence of file "{0}" could not be performed on node "{1}".

Cause: An attempt to verify the existence of the indicated file failed on the indicated node.

Action: Examine the accompanying error messages for details.

PRVF-05311: File "{0}" either does not exist or is not accessible on node "{1}".

Cause: Cannot access the file specified.

Action: Verify that the specified file exists and can be access on the node identified.

PRVF-05312: No ohasd entry was found in /etc/inittab file

Cause: Did not find 'respawn:/etc/init.d/init.ohasd' line in '/etc/inittab' file.

Action: Ensure that the OHASD environment has been setup correctly.

PRVF-05313: Failed to search for ohasd entry in /etc/inittab file on node "{0}"

Cause: An error was encountered trying to search for OHASD information in /etc/inittab.

Action: Ensure that the OHASD environment has been setup correctly and that /etc/inittab is accessible on the specified node.

PRVF-05314: Could not find CRS, or Oracle Restart, installed on the local node

Cause: Could not locate the CRS, or Oracle Restart, installation from the local node.

Action: Ensure that the install of CRS, or Oracle Restart, has completed successfully and the CRS, or Oracle Restart, home is setup correctly.

PRVF-05316: Failed to retrieve version of CRS installed on node "{0}"

Cause: Could not identify location of CRS home.

Action: Verify installation of CRS on the identified node.

PRVF-05317: The Clusterware is currently being upgraded to version: "{0}".\n The following nodes have not been upgraded and are\n running Clusterware version: "{1}".\n "{2}"

Cause: The CRS integrity may have discovered that your Oracle Clusterware stack is partially upgraded.

Action: Review warnings and make modifications as necessary. If the warning is due to partial upgrade of Oracle Clusterware stack then continue with upgrade and finish it.

PRVF-05318: No Oracle Restart is found configured on the local node

Cause: Could not locate the Oracle Restart configuration on the specified node.

Action: Ensure that the install of Oracle Restart has completed successfully and the Oracle Restart home is set up correctly.

PRVF-05319: Oracle Cluster Synchronization Services do not appear to be online.

Cause: An error was encountered when trying to verify the status of Oracle Cluster Synchronization Services.

Action: Verify the state of the Oracle Cluster Synchronization Services using 'crsctl check cluster'.

PRVF-05321: Failed to get the CRS or Oracle Restart home

Cause: Could not locate the CRS, or Oracle Restart, home.

Action: Ensure that the install of CRS, or Oracle Restart, has completed successfully and the CRS, or Oracle Restart, home is setup correctly.

PRVF-05322: Failed to get the CRS user name for CRS home "{0}"

Cause: An attempt to obtain the Clusterware owner information from CRS home failed.

Action: Ensure that the user executing the CVU check has read permission for CRS or Oracle Restart home.

PRVF-05323: Failed to get information for file "{0}"

Cause: An attempt to read information for a file failed.

Action: Make sure that the user executing the CVU check has read permission for the file and the file exists in the specified path.

PRVF-05324: Could not find CRS installed on the node "{0}"

Cause: Could not locate the CRS installation on the specified node.

Action: Ensure that the install of CRS has completed successfully and the CRS home is setup correctly.

PRVF-05325: Failed to retrieve release version for Oracle Restart

Cause: Could not get release version for Oracle Restart.

Action: Ensure that the install of Oracle Restart has completed successfully.

PRVF-05401: Clock synchronization check using Network Time Protocol(NTP) failed

Cause: One or more of the Clock Synchronization checks failed.

Action: Correlate with the other failure messages displayed and fix those failures.

PRVF-05402: Warning: Could not find NTP configuration file "{0}" on node "{1}"

Cause: NTP might not have been configured on the node, or NTP might have been configured with a configuration file different from the one indicated.

Action: Configure NTP on the node if not done so yet. Refer to your NTP vendor documentation for details.

PRVF-05403: Operation to check presence of NTP configuration file "{0}" failed on node "{1}"

Cause: The operation to check NTP configuration file failed on node indicated. The failure is due to a reason like incorrect permissions on the configuration file, communications error with the node, missing or inaccessible remote execution binary on the node, etc.

Action: Review the error messages that follow this message and fix the problem(s) indicated.

PRVF-05405: The NTP configuration file "{0}" does not exist on all nodes

Cause: The configuration file specified was not available or was inaccessible on the given nodes.

Action: If you want to use NTP for time synchronization, create this file and setup its configuration as described in your vendor's NTP document. If you plan to use CTSS for time synchronization then NTP configuration should be uninstalled on all nodes of the cluster. Refer to "Preparing Your Cluster" of "Oracle Database 2 Day + Real Application Clusters Guide".

PRVF-05406: NTP Configuration file Check failed

Cause: Attempt to check presence of configuration file failed on one or more nodes.

Action: Look at the related error messages and fix them.

PRVF-05408: NTP Time Server "{0}" is common only to the following nodes "{1}"

Cause: One or more nodes in the cluster do not synchronize with the NTP Time Server indicated.

Action: At least one common NTP Time Server is required for a successful Clock Synchronization check. If there are none, reconfigure all of the nodes in the cluster to synchronize with at least one common NTP Time Server.

PRVF-05410: Check of common NTP Time Server failed

Cause: The NTP query command showed there is no common time server among all of the nodes in the cluster.

Action: At least one common NTP Time Server is required for a successful Clock Synchronization check. Reconfigure all of the nodes in the cluster to synchronize with at least one common NTP Time Server. If you plan to use CTSS for time synchronization then NTP configuration should be uninstalled on all nodes of the cluster. Refer to "Preparing Your Cluster" of "Oracle Database 2 Day+ Real Application Clusters Guide".

PRVF-05411: Query of NTP daemon failed on all nodes on which NTP daemon is running

Cause: Attempt to query the NTP daemon failed on all of the nodes of the cluster because the 'ntpq' command could not be found.

Action: Make sure that the NTP query command 'ntpq' is available on all nodes and the user running the CVU check has execute privilege for it.

PRVF-05413: Node "{0}" has a time offset of {1} that is beyond permissible limit of {2} from NTP Time Server "{3}"

Cause: The time offset for the given node clock with the specified NTP Time Server is beyond permissible limits, possibly due to a clock drift, or due to an incorrectly functioning time server.

Action: Make sure that the Time Server is functioning properly, and if yes, adjust the system clock so that the offset is within limits.

PRVF-05414: Check of NTP Config file failed on all nodes. Cannot proceed further for the NTP tests

Cause: Attempt to check existence of config file failed on all nodes.

Action: Look at the individual error messages displayed for the respective nodes and the overall result message and take appropriate action.

PRVF-05415: Check to see if NTP daemon or service is running failed

Cause: Attempt to check if the NTP daemon was running failed on nodes of the cluster.

Action: Look at the accompanying error messages for the nodes on which the check failed and fix the problem. If you plan to use CTSS for time synchronization then NTP configuration should be uninstalled on all nodes of the cluster. Refer to "Preparing Your Cluster" of "Oracle Database 2 Day+ Real Application Clusters Guide".

PRVF-05416: Query of NTP daemon failed on all nodes

Cause: An attempt to query the NTP daemon using the 'ntpq' command failed on all nodes.

Action: Make sure that the NTP query command 'ntpq' is available on all nodes and make sure that user running the CVU check has permissions to execute it.

PRVF-05421: NTP configuration file check failed on the following nodes:

Cause: Check of existence of NTP configuration file failed on nodes listed because NTP was not configured on those nodes.

Action: If you plan to use NTP for time synchronization across nodes of the cluster then configure NTP on all of the nodes. If you plan to use CTSS for time synchronization then NTP configuration should be uninstalled on all nodes of the cluster. Refer to "Preparing Your Cluster" of "Oracle Database 2 Day+ Real Application Clusters Guide".

PRVF-05424: Clock time offset check failed

Cause: Offsets on all of the nodes in the cluster were not within limits for any Time Server.

Action: Look at the individual messages displayed and fix the problems indicated.

PRVF-05428: Network Time Protocol(NTP) configuration file not found on any of the nodes. Oracle Cluster Time Synchronization Service(CTSS) can be used instead of NTP for time synchronization on the cluster nodes

Cause: NTP is not configured on the cluster nodes.

Action: This is not an error if the system administrator intended to use Oracle Cluster Time Synchronization Service (CTSS) for clock synchronization on the cluster. If not then install NTP on all nodes of the cluster according to your NTP vendor documentation.

PRVF-05430: Voting disk configuration does not meet Oracle's recommendation of three voting disk locations

Cause: For high availability, Oracle recommends that you have a minimum of three voting disk locations.

Action: Add additional voting disk locations to meet the Oracle recommended amount of three voting disks.

PRVF-05431: Oracle Cluster Voting Disk configuration check failed

Cause: The Voting Disk configuration does not meet Oracle's recommendations.

Action: Review Clusterware and Voting Disk configuration.

PRVF-05433: The current voting disk state is at high risk

Cause: The current state of the voting disk locations is susceptible to the loss of one voting disk location resulting in failure of the cluster.

Action: Add additional voting disk locations, or bring existing locations online, to reduce the risk of losing one voting disk location.

PRVF-05434: Cannot identify the current CRS software version

Cause: Unable to obtain CRS version from CRSCTL.

Action: Ensure that CRSCTL is accessible on the nodes being verified.

PRVF-05435: Voting disk configuration does not meet Oracle's recommendation

Cause: For high availability, Oracle recommends that you have more than two voting disk locations.

Action: Add additional voting disk locations.

PRVF-05436: The NTP daemon running on one or more nodes lacks the slewing option "{0}"

Cause: NTP daemon on one or more nodes lacked slewing option.

Action: Shut down and restart the NTP daemon after setting the slewing option as follows: For Linux, edit /etc/sysconfig/ntpd and add -x to the command line option. For SUSE Linux, edit /etc/sysconfig/ntp and add -x to the OPTIONS variable. For AIX, edit /etc/rc.tcpip and add -x to the command line option. For HP-UX, edit /etc/rc.config.d/netdaemons and add -x to the command line option. For Solaris release 10 or earlier, edit /etc/inet/ntp.conf and add 'slewalways yes' and 'disable pll' to the file. For Solaris release 11 and higher, logon as root user and issue command: /usr/sbin/svccfg -s svc:/network/ntp:default setprop config/slew_always = true to change the setting, then refresh the service by issuing: svcadm refresh svc:/network/ntp:default

PRVF-05442: Could not obtain NTP daemon's command line on any node

Cause: An attempt to obtain the command line options for the NTP daemon's failed on all nodes.

Action: Make sure that the NTP daemon is running on all the nodes. Make sure that slewing option is set on all the nodes of the cluster.

PRVF-05447: Could not verify sharedness of Oracle Cluster Voting Disk configuration

Cause: Unabled to obtain list of nodes with CRS installed.

Action: Ensure that Clusterware is up and running and verify Voting Disk configuration.

PRVF-05448: Voting Disk location "{0}" is not shared across cluster nodes

Cause: Voting Disk location specified is not shared across all cluster nodes.

Action: Verify Voting Disk configuration and ensure all Voting Disk locations are shared across all cluster nodes and are of the same storage type.

PRVF-05449: Check of Voting Disk location "{0}" failed on the following nodes:

Cause: Voting Disk location specified did not have owner, group or permissions set correctly on the nodes identified.

Action: Correct the owner, group or permissions settings on the location indicated as mentioned in one of the accompanying message.

PRVF-05450: Constraint type does not match

Cause: The specified constraint does not relate to space checks.

Action: Make sure that the space constraint data is well formed and consistent in the constratint xml.

PRVF-05451: Missing key data "{0}"

Cause: The data required for constraint check is missing.

Action: Verify that the space constraint data is correctly specified in the constraint xml.

PRVF-05452: Missing key reference data "{0}"

Cause: The reference data required for constraint check is missing.

Action: For a greater than/equal comparison, reference data is required.Verify that the space constraint check reference data is correctly specified in the constraint xml.

PRVF-05453: Invalid data set for "{0}", EXPECTED:"{1}", FOUND: "{2}"

Cause: The specified data is invalid for the space constraint check being performed.

Action: Make sure that correct data is specified, using the values indicated in the message.

PRVF-05454: Qualifier "{0}" is not supported for "{1}"

Cause: The indicated qualifier is not supported for the class indicated in the message.

Action: Make sure that the correct qualifier is specified.

PRVF-05455: Cannot apply invalid constraint

Cause: The specified constraint is invalid.

Action: Specify the correct constraint.

PRVF-05456: Invalid constraint. Compatibility check cannot proceed

Cause: The specified constraint is invalid.

Action: Specify the correct constraint for the compatibility check.

PRVF-05461: Encountered an invalid setting for internal variable "{0}"

Cause: This is an internal error.

Action: Please contact Oracle Support.

PRVF-05470: The NTP daemon''s boot time configuration, in file "{0}", on one or more nodes lacks the slewing option "{1}"

Cause: NTP daemon boot time configuration on one or more nodes lacked slewing option.

Action: Make sure that the slewing option is specified in the file listed. For a list of nodes on which this check failed look at the accompanying error messages.

PRVF-05473: NTP daemon''s boot time configuration check could not be performed on node "{0}"

Cause: An attempt to obtain the NTP daemon's boot time configuration file failed on the node specified.

Action: Make sure that the NTP daemon is configured on the node and will be started when the node boots up. Make sure that the user running this check has access to the configuration file specified. Also look at other messages accompanying this message.

PRVF-05475: Could not obtain NTP daemon's boot time configuration on any node

Cause: An attempt to obtain the command line options for the NTP daemon's failed on all nodes.

Action: Make sure that the NTP daemon is running on all the nodes. Make sure that slewing option is set on all the nodes of the cluster.

PRVF-05478: TZ value missing in configuration file "{0}" on node "{1}".

Cause: Time Zone value is missing in specified configuration file.

Action: Enter appropriate Time Zone value in the specified configuration file on the indicated node.

PRVF-05479: Time zone is not the same on all cluster nodes.

Cause: Nodes have different time zone settings.

Action: Ensure that time zone is same on all nodes.

PRVF-05486: The NTP daemon on the indicated nodes is not using UDP port 123

Cause: The port 123 for udp is not opened for the NTP daemon or service.

Action: For Unix, edit the /etc/services file appropriately.

PRVF-05492: Warning: Could not find NTP Daemon or Service running on node "{0}".

Cause: NTP Daemon may have aborted , shut down or may not have been installed.

Action: Restart NTP Daemon on the indicated node or install if necessary.

PRVF-05493: Operation to check presence of NTP Daemon or Service failed on node "{0}".

Cause: The operation to check NTP Daemon or service failed on node indicated. The failure is due to a reason like incorrect setup, communications error with the node, missing or inaccessible remote execution binary on the node, etc.

Action: Review the error messages that follow this message and fix the problem(s) indicated.

PRVF-05494: The NTP Daemon or Service was not alive on all nodes

Cause: The NTP Daemon was not alive on all the nodes.

Action: Examine the status of ntp on each of the nodes indicated after this message and restart the daemon or install the NTP software if necessary.

PRVF-05495: The Check for NTP Daemon or Service status failed on some nodes

Cause: The NTP Daemon was not accessible or there was some unknown failure in the check.The failure is due to a reason like incorrect setup, communications error with the node, missing or inaccessible remote execution binary on the node, etc.

Action: Review the error that follow this message and fix the problem(s) in the indicated nodes.

PRVF-05498: Timezone file "{0}" missing on node "{1}".

Cause: A check for the indicated timezone file did not find it on the node shown.

Action: Restore the file on the indicated node by reinstalling timezone patches for your operating system.

PRVF-05499: There are more than one NTP daemons or Services running on various nodes of the cluster

Cause: An attempt to check if NTP daemons or Service were running on nodes of the cluster found that more than one NTP daemons or Services were active.

Action: The accompanying messages will list the NTP daemon or service names along with the nodes on which they are running. Make sure that only one time synchronization service is active on all nodes of the cluster at any given time by shutting down others.

PRVF-05501: The user "{0}" is currently logged in to the group "{1}" which is not the primary group for the user

Cause: The user is currently logged into a group that is not user's primary group.

Action: Invoke the application after logging in to the primary group (using command newgrp primary group).

PRVF-05502: Current group ID check cannot be performed

Cause: Attempt to check if the current group ID matches with primary group ID failed.

Action: Look at the accompanying error messages displayed and fix the problems indicated.

PRVF-05505: The NTP daemon on node "{0}" is not using UDP port 123

Cause: The port 123 for UDP was not being used by the NTP daemon or service.

Action: For Unix, edit the /etc/services file appropriately.

PRVF-05506: Check for UDP port 123 being used by NTP daemon or service could not be performed on node "{0}"

Cause: Attempt to check for UDP port 123 being used by NTP daemon or service failed.

Action: Look at the accompanying error messages displayed and fix the problems indicated.

PRVF-05507: NTP daemon or service is not running on any node but NTP configuration file exists on the following nodes:

Cause: The configuration file was found on at least one node though no NTP daemon or service was running.

Action: If you plan to use CTSS for time synchronization then NTP configuration must be uninstalled on all nodes of the cluster.

PRVF-05555: Automount feature is disabled on nodes:

Cause: Automount feature for new volumes was found disabled.

Action: To enable Automount feature for new volumes, use 'mountvol /e' or use the 'diskpart' utility's 'automount enable' command Restart your system to make your changes effective after enabling the Automount feature.

PRVF-05556: Automount feature is disabled on the node "{0}"

Cause: Automount feature for new volumes was found disabled on specified node.

Action: To enable Automount feature for new volumes, use 'mountvol /e' or use the 'diskpart' utility's 'automount enable' command. Restart your system to make your changes effective after enabling the Automount feature.

PRVF-05557: Error reading Registry subkey "{0}" from Windows Registry on node "{1}"

Cause: Windows Registry subkey 'HKEY_LOCAL_MACHINE\\System\\CurrentControlSet\\Services\\MountMgr' could not be read on specified node.

Action: Ensure that the specified subkey exists in registry and access permissions for the Oracle user allow access to the Windows Registry. Restart your system to make your changes effective after changing the registry.

PRVF-05558: Check for status of Automount feature cannot be performed on nodes:

Cause: Windows Registry subkey 'HKEY_LOCAL_MACHINE\\System\\CurrentControlSet\\Services\\MountMgr' could not be read.

Action: Ensure that the specified subkey exists in registry and the access permissions for the Oracle user allow access to the Windows Registry. Restart your system to make your changes effective after changing the registry.

PRVF-05559: Failed to perform the Automount status verification.

Cause: An error occurred while attempting to retrieve the information about Automount feature.

Action: Look at the accompanying messages and respond accordingly.

PRVF-05600: On node "{0}" The following lines in file "{1}" could not be parsed as they are not in proper format: {2}

Cause: Invalid lines were found in the file resolv.conf at the location and on the node indicated.

Action: Correct the errors indicated. On UNIX the general format of file resolv.conf is "keyword <value(s)>". For more details refer to resolv.conf man page.

PRVF-05603: 'domain' entry does not exist in file "{0}" on nodes: "{1}".

Cause: The 'domain' entry was not found in the resolv.conf file on the indicated nodes while it was present in others.

Action: Examine the indicated file on all nodes. Make sure that either 'domain' entry is defined on all nodes or is not defined on any nodes.

PRVF-05604: 'domain' entry in file "{0}" on node "{1}" is "{2}" which differs from reference node.

Cause: The 'domain' entry on the indicated node was not the same as the reference node 'domain' option specified above.

Action: Make sure that all nodes of the cluster have same 'domain' entry in the indicated file.

PRVF-05605: File "{0}" does not exist on following nodes: {1}

Cause: File specified did not exist on the nodes listed, but exists on other nodes.

Action: Make sure that the file is either present on all nodes or is not present on any node.

PRVF-05607: The file "{0}" on following nodes has more than "{1}" 'nameserver' entries: {2}.

Cause: The indicated file had more than the allowed number of 'nameserver' entries.

Action: Reduce the number of 'nameserver' entries on the indicated nodes to the allowed number.

PRVF-05608: The file "{0}" on the following nodes has more than one 'attempts' entry: {1}.

Cause: More than one 'option attempts:' entry was found on nodes specified.

Action: Make sure that there is only one 'option attempts:' entry in the indicated file.

PRVF-05609: The following nodes have multiple 'domain' entries defined in file "{0}": {1}.

Cause: The nodes specified had multiple 'domain' entry defined in the indicated file.

Action: Make sure that the indicated file has only one 'domain' entry.

PRVF-05610: The file "{0}" on the following nodes have more than one 'search' entry: {1}.

Cause: More than one 'search' entry was found on nodes specified, in the indicated file.

Action: Make sure that there is only one 'search' entry in the indicated file. Multiple domains can be listed in the same search entry.

PRVF-05613: 'nameserver' entry does not exist in file "{0}" on nodes: "{1}"

Cause: The 'nameserver' entry was not found on the indicated nodes, while it was present in others.

Action: Examine the indicated file on all nodes and ensure that either the 'nameserver' entry is defined on all nodes or is not defined any nodes.

PRVF-05614: The 'nameserver' entry in file "{0}" on node "{1}" is "{2}", which differs from reference node.

Cause: The 'nameserver' entry shown from the indicated file on the indicated node is not the same as the 'nameserver' option on the reference node.

Action: Ensure that all nodes of the cluster have same 'nameserver' entry in the indicated file.

PRVF-05622: The 'search' entry does not exist in file "{0}" on nodes: "{1}".

Cause: The 'search' entry was not found on the indicated nodes while it was present in others.

Action: Examine the indicated file on all nodes. Make sure that either 'search' entry is defined on all nodes or is not defined any nodes.

PRVF-05623: The 'search' entry in file "{0}" on node "{1}" is "{2}", which differs from reference node.

Cause: The 'search' entry on the indicated node was not the same as the reference node 'search' option specified above.

Action: Make sure that all nodes of the cluster have same 'search' entry in the indicated file.

PRVF-05629: Unable to read file "{0}" copied to local scratch area from node {1}

Cause: An error occurred while trying to read indicated file.

Action: Make sure that the CV_DESTLOC area was not being used by another process. Make sure that CV_DESTLOC has sufficient permissions. Also look for messages accompanying this message for details.

PRVF-05636: The DNS response time for an unreachable node exceeded "{0}" ms on following nodes: {1}

Cause: The DNS response time for an unreachable node exceeded the value specified on nodes specified.

Action: Make sure that 'options timeout', 'options attempts' and 'nameserver' entries in file resolv.conf are proper. On HPUX these entries will be 'retrans', 'retry' and 'nameserver'. On Solaris these will be 'options retrans', 'options retry' and 'nameserver'. Make sure that the DNS server responds back to name lookup request within the specified time when looking up an unknown host name.

PRVF-05637: DNS response time could not be checked on following nodes: {0}

Cause: An attempt to check DNS response time for unreachable node failed on nodes specified.

Action: Make sure that 'nslookup' command exists on the nodes listed and the user executing the CVU check has execute privileges for it.

PRVF-05640: Both 'search' and 'domain' entries are present in file "{0}" on the following nodes: {1}.

Cause: Both 'search' and 'domain' entries were found in the 'resolv.conf' file on the indicated nodes.

Action: Make sure that only one of these entries exists in the 'resolv.conf' file. It is preferable to use entry 'search' in the 'resolv.conf' file.

PRVF-05642: Unable to create the directory "{0}"

Cause: An attempt to create the directory specified failed on local node.

Action: Make sure that the user running CVU has read and write permissions on directory specified or specify a different work area using CV_DESTLOC environment variable where user has write permission.

PRVF-05643: Unable to delete files from directory "{0}"

Cause: An attempt to remove files from the directory specified failed.

Action: Make sure that the user running CVU has read and write permissions on directory specified or specify a different work area using CV_DESTLOC environment variable where user executing this check has write permission.

PRVF-05704: No DHCP server were discovered on the public network listening on port {0}

Cause: No reply was received for the DHCP discover packets sent on the specified port.

Action: Contact the network administrator to make sure that DHCP servers exist on the network. If the DHCP servers are listening to a different port then specify it by using -port option.

PRVF-05707: DHCP server was not able to provide sufficient IP addresses (required "{1}" , provided "{0}")

Cause: DHCP server was unable to provide sufficient number of IP address.

Action: An IP is required for each node VIP. Three IP addresses are needed for SCAN VIP. One IP address is required for each application VIP specified. Make sure that the DHCP server listening on port specified in above messages has sufficient number of IP addresses to give out.

PRVF-05711: DHCP server response time could not be measured

Cause: An attempt to measure DHCP server response time using 'crsctl discover' command failed.

Action: Look at messages accompanying this message for more information.

PRVF-05712: Warning: The DHCP server response time of {0} seconds is greater than VIP resource's SCRIPT_TIMEOUT attribute of {1} seconds

Cause: An attempt to obtain a DHCP lease took more time than VIP resource's SCRIPT_TIMEOUT attribute.

Action: This check is network load sensitive and can yield different result at different times. Make sure that the DHCP server and the network is not overloaded. Also consider a higher SCRIPT_TIMEOUT value.

PRVF-05713: Command "{0}" executed on node "{1}" produced no output

Cause: An attempt to run the command listed on the node listed produced no output.

Action: This is an internal error. Contact Oracle Support Services.

PRVF-05714: An error occurred while parsing the output of the command "{0}". The output is: "{1}"

Cause: An attempt to parse output of the command listed failed.

Action: This is an internal error. Contact Oracle Support Services.

PRVF-05715: The number of IP addresses assigned to the network interface "{0}" exceeds recommended value (recommended {1}, actual {2})

Cause: Too many IP addresses were assigned to the specified interface.

Action: If there are IP addresses that are not needed stop them in the operating system specific way. If too many resources are running on this node then relocate them to other nodes of the cluster relocate using 'srvctl relocate' command.

PRVF-05716: Unable to obtain network interface details on local node

Cause: An attempt to obtain network interface details on local node failed.

Action: Make sure that the user executing CVU has sufficient permissions to query network interfaces on the node. Also look at accompanying messages and take action as per those messages.

PRVF-05718: Command "{0}" failed to execute on node "{1}". The output produced by the command is: "{2}"

Cause: An attempt to execute specified command on the node specified failed.

Action: Refer to the specified output and fix the error.

PRVF-05801: Failed to execute command "{0}" on all nodes

Cause: CVU's attempt to execute the specified command failed on all of the nodes.

Action: Examine the messages displayed for each node and take action as per those messages.

PRVF-05803: An error occurred while starting the IP address "{0}" on node "{1}"

Cause: An attempt to start the specified IP address on the node specified failed.

Action: Look at messages accompanying this message for more information.

PRVF-05805: Unable to start the test DNS server

Cause: An attempt to start the test DNS server failed with errors.

Action: Look at messages accompanying this message for more information.

PRVF-05809: Unable to start the test DNS server on address: "{0}", listening on port: {1}

Cause: An attempt to start the test DNS server failed with errors.

Action: Look at messages accompanying this message for more information.

PRVF-05810: Unable to stop the test DNS server on address: "{0}", listening on port: {1}

Cause: An attempt to stop the test DNS server failed with errors.

Action: Look at messages accompanying this message for more information.

PRVF-05811: Unable to stop the IP address "{0}" on node "{1}"

Cause: An attempt to stop the IP address specified on the node specified failed.

Action: Look at messages accompanying this message for more information.

PRVF-05813: Unable to reach the IP address "{0}" from local node

Cause: An attempt to reach the specified IP address from current node failed.

Action: Make sure that the specified IP address is a valid IP address. Check messages of the 'cluvfy comp dns -server' instance to make sure that there are no errors. If the address has been started then make sure that there are no firewalls between the local node and node on which this IP address has been started.

PRVF-05816: Unable to query the test DNS server started on address "{0}", listening on port {1}

Cause: An attempt to query the test DNS server, started on specified address and port, failed.

Action: Look at messages on the 'cluvfy comp dns -server' instance to make sure that the test DNS server was stared. Also look at any messages accompanying this message.

PRVF-05819: Failed to verify DNS delegation of the GNS subdomain "{0}"

Cause: An attempt to perform name resolution for nodename.<gns_subdomain> failed as DNS did not forward requests to the test DNS server.

Action: Look at messages accompanying this message for more information. Also look at any messages from 'cluvfy comp dns -server' invocation for CVU.

PRVF-05821: Unable to reach the IP address "{0}" from local node

Cause: An attempt to reach the specified IP address failed.

Action: Make sure that the specified IP address is a valid IP address and is assigned to an interface on the node on which 'cluvfy comp dns -server' was run. Make sure that there are no firewalls between local node and node on which specified IP address is assigned.

PRVF-05822: Name lookup for FQDN "{0}" failed with test DNS server running at address "{1}" and listening on port {2}.

Cause: An attempt to query the indicated Fully Qualified Domain Name (FQDN) on the test domain name server (DNS) running on the indicated address and port failed.

Action: Ensure that the indicated address and the port are correct. Ensure that there are no firewalls between the node on which 'cluvfy comp dns -server' is run and the node on which this command is run. Also, examine any error messages on the node on which 'cluvfy comp dns -server' is run.

PRVF-05823: Name lookup for FQDN "{0}" failed.

Cause: An attempt to query a domain name server for the indicated Fully Qualified Domain Name (FQDN) failed.

Action: Ensure that there are no firewalls between the local node and DNS. Ensure that there are no firewalls between DNS and the node on which 'cluvfy comp dns -server' was run. Ensure that Grid Naming Service subdomain delegation is set up correctly in DNS. Also, examine any error messages on the node on which 'cluvfy comp dns -server' was run.

PRVF-05826: The domain name "{0}" is not valid

Cause: The GNS domain name specified did not conform to the industry standard.

Action: A valid domain name starts with an alphabetic character and consists only of characters [A-Z], [a-z], [0-9], '.', '-'. Refer to the RFC-1035 standard for more information.

PRVF-05827: The response time for name lookup for name "{1}" exceeded {0} seconds.

Cause: The DNS response time for the indicated name exceeded the indicated time limit.

Action: On Linux and AIX ensure that 'options timeout', 'options attempts' and 'nameserver' entries in file resolv.conf are proper. On HPUX these entries will be 'retrans', 'retry' and 'nameserver'. On Solaris these will be 'options retrans', 'options retry' and 'nameserver'. On windows examine registry key 'HKEY_LOCAL_MACHINE\\System\\CurrentControlSet\\Services\\VxD\\MSTCP' for values 'BcastQueryTimeout' and 'MaxConnectRetries'.

PRVF-06001: Could not get required information about the interface "{0}"

Cause: Could not get interface information for the interface specified.

Action: Ensure that the interface is installed and online on the nodes in the cluster.

PRVF-06002: Unable to get information about interface "{0}" on the following nodes:

Cause: Could not get interface information for the interface specified on the nodes listed.

Action: Ensure that the interface is installed and online on the nodes specified.

PRVF-06003: Unable to get network information from node: {0}

Cause: Could not obtain any network interface information from the node specified.

Action: Verify state of network interface adapters on the specified node.

PRVF-06005: Could not find a fully connected subnet that covers all the nodes

Cause: Could not find a network interface adapter that exists in the same subnet on every node in the cluster .

Action: Ensure that the network interface adapters are installed and configured correctly on each node in the cluster.

PRVF-06006: unable to reach the IP addresses "{0}" from the local node

Cause: During a verification operation to check that the indicated IP addresses are reachable from the local node using the 'ping' command, the verification failed to reach any of the addresses specified. Either the addresses did not resolve correctly or the nodes were unreachable.

Action: Ensure that the indicated IP addresses are accessible with the 'ping' command. If the host names do not resolve correctly, ensure that the domain naming services cache has been purged using the command '/etc/rc.d/init.d/nscd restart' on Linux and UNIX machines and the command 'ipconfig /flushdns' on Windows operating system machines.

PRVF-06011: could not find any network interface on node "{0}"

Cause: Node connectivity checking determined that the indicated node did not have any network interface configured.

Action: Verify the operational status of the network interfaces on the indicated node, configure the network interfaces according to the documentation and retry the node connectivity check.

PRVF-06019: Interface subnet "{0}" does not have a gateway defined

Cause: Could not identify the gateway for the subnet identified.

Action: Define a gateway for the specified subnet.

PRVF-06020: Different MTU values used across network interfaces in subnet "{0}"

Cause: Different MTU values found for the network adapter used between cluster nodes across the specified subnet.

Action: Set the MTU value for that network adapter/subnet to be the same on each node in the cluster.

PRVF-06402: Core file name pattern is not same on all the nodes.

Cause: The core file name pattern is not same on all the nodes.

Action: Ensure that the mechanism for core file naming works consistently on all the nodes. Typically for Linux, the elements to look into are the contents of two files /proc/sys/kernel/core_pattern or /proc/sys/kernel/core_uses_pid. Refer OS vendor documentation for platforms AIX, HP-UX, and Solaris.

PRVF-06407: Core file name pattern can not be obtained from nodes "{0}".

Cause: Unable to execute commands on the nodes specified.

Action: Ensure the ability to communicate with, and execute commands on, nodes specified .

PRVF-07017: Package cvuqdisk not installed

Cause: The required cvuqdisk package to perform this operation was found missing.

Action: Ensure that the required version of cvuqdisk package is installed on all the nodes participating in the operation.

PRVF-07019: OCFS file system does not exist on location "{0}"

Cause: OCFS file system was not found on the specified location.

Action: Ensure that OCFS file system is correctly created on the specified location.

PRVF-07020: Cannot verify the shared state for device {0} due to Universally Unique Identifiers (UUIDs) not being found, or different values being found, for this device across nodes:

Cause: An attempt to retrieve devices' Universally Unique Identifier (UUID) failed, or UUID's do not match, on the nodes indicated.

Action: Ensure the devices' UUID can be obtained and that the UUID value matches across all the nodes indicated.

PRVF-07036: Mount options did not meet the requirements for this platform [Expected = "{0}" ; Found = "{1}"]

Cause: The mount options found did not match the minimum set of mount options that must be used while mounting NFS volumes.

Action: Ensure that all of the required mount options are specified.

PRVF-07037: Reserve_policy setting prevents sharing of {0} on nodes:

Cause: The reserve_policy setting for the device is preventing the device from being shared on the nodes indicated.

Action: Change the reserve_policy setting for the device. See the chdev command for further details.

PRVF-07038: Reserve_lock setting prevents sharing of {0} on nodes:

Cause: The reserve_lock setting for the device is preventing the device from being shared on the nodes indicated.

Action: Change the reserve_lock setting for the device. See the chdev command for further details.

PRVF-07039: File system exists on location "{0}"

Cause: Existing file system found on the specified location.

Action: Ensure that the specified location does not have an existing file system.

PRVF-07501: Sufficient space is not available at location "{0}" on node "{1}" [Required space = {2}; available space = {3}]

Cause: There was not enough free space at location specified.

Action: Free up additional space or select another location.

PRVF-07524: Kernel version is not consistent across all the nodes.

Cause: The operating system kernel versions do not match across cluster nodes.

Action: Update the kernel version where necessary to have all cluster nodes running the same kernel version.

PRVF-07530: Sufficient physical memory is not available on node "{0}" [Required physical memory = {1}]

Cause: Amount of physical memory (RAM) found does not meet minimum memory requirements.

Action: Add physical memory (RAM) to the node specified.

PRVF-07531: Physical memory check cannot be performed on node "{0}"

Cause: Could not perform check of physical memory on the node indicated.

Action: Ensure the ability to access the node specified and view memory information.

PRVF-07532: Package "{0}" is missing on node "{1}"

Cause: A required package is either not installed or, if the package is a kernel module, is not loaded on the specified node.

Action: Ensure that the required package is installed and available.

PRVF-07533: Proper version of package "{0}" is not found on node "{1}" [Required = "{2}" ; Found = "{3}"].

Cause: Package does not meet the requirement.

Action: Upgrade the package to meet the requirement.

PRVF-07534: Package check cannot be performed on node "{0}"

Cause: Package configuration could not be determined.

Action: Ensure that the package configuration is accessible.

PRVF-07535: Proper architecture is not found on node "{0}" [Expected = "{1}" ; Found = "{2}"]

Cause: System architecture does not meet the requirement.

Action: Ensure that the correct software bundle is being used.

PRVF-07536: Architecture check cannot be performed on node "{0}"

Cause: System architecture could not be determined.

Action: Ensure that the correct software bundle is being used.

PRVF-07537: User "{0}" does not exist on node "{1}"

Cause: The specified user does not exist on the specified node.

Action: Create the user on the specified node.

PRVF-07538: User existence check cannot be performed on node "{0}"

Cause: Attempt to check the existence of user on the specified node failed.

Action: Look at the accompanying error messages displayed and fix the problems indicated.

PRVF-07539: Group "{0}" does not exist on node "{1}"

Cause: The specified group does not exist on the specified node.

Action: Create the group on the specified node.

PRVF-07540: Group existence check cannot be performed on node "{0}"

Cause: Attempt to check the existence of group on the specified node failed.

Action: Look at the accompanying error messages displayed and fix the problems indicated.

PRVF-07542: Kernel version check cannot be performed on node "{0}"

Cause: Unable to execute commands on node specified.

Action: Ensure the ability to communicate with, and execute commands on, node specified .

PRVF-07543: OS Kernel parameter "{0}" does not have proper value on node "{1}" [Expected = "{2}" ; Found = "{3}"].

Cause: Kernel parameter value did not meet the requirement.

Action: Modify the kernel parameter value to meet the requirement and ensure that the corrected kernel parameter value takes effect before retrying this check.

PRVF-07544: Check cannot be performed for kernel parameter "{0}" on node "{1}"

Cause: Kernel parameter value could not be determined.

Action: Ensure that the correct software bundle is being used.

PRVF-07562: Sufficient available memory is not available on node "{0}" [Required available memory = {1}]

Cause: Amount of available memory (RAM) does not meet minimum memory requirements.

Action: Add physical memory (RAM) to the node specified, or free memory being used.

PRVF-07563: Available memory check cannot be performed on node "{0}"

Cause: Could not perform check of available memory on the node indicated.

Action: Ensure the ability to access the node specified and view memory information.

PRVF-07564: The runlevel found on node "{0}" did not match a supported runlevel. [Expected="{1}"; Found="{2}"]

Cause: The runlevel mode of operation for the computer operating system was found to be an unsupported runlevel on the node specified.

Action: Reboot the specified node with one of the correct runlevels indicated.

PRVF-07565: Could not perform the runlevel verification check on node "{0}"

Cause: Errors were encountered when trying to obtain the runlevel set on the system.

Action: Ensure that the command used to obtain the runlevel value 'who -r' can be run on the specified node and the file accessed by this command '/var/run/utmp' has read access for the current user.

PRVF-07566: User "{0}" does not belong to group "{1}" on node "{2}"

Cause: The specified user is not a member of the specified group on the specified node.

Action: Make the user a member of the group on the specified node.

PRVF-07567: Group "{0}" is not the primary group for user "{1}" on node "{2}"

Cause: The specified group is not the primary group for the specified user.

Action: Make the specified group as the primary group for the user.

PRVF-07568: Check cannot be performed for membership of user "{0}" with group "{1}" on node "{2}"

Cause: Attempt to check the group membership of the user on the specified node failed.

Action: Look at the accompanying error messages displayed and fix the problems indicated.

PRVF-07571: Process "{0}" not running on node "{1}"

Cause: Required process not running on the specified node.

Action: Ensure that the identified process can be started on the node .

PRVF-07572: Process running check cannot be performed on node "{0}"

Cause: Could not collect process information from the specified node.

Action: Ensure the access to node specified and ability to view process information.

PRVF-07573: Sufficient swap size is not available on node "{0}" [Required = {1} ; Found = {2}]

Cause: The swap size found does not meet the minimum requirement.

Action: Increase swap size to at least meet the minimum swap space requirement.

PRVF-07574: Swap size check cannot be performed on node "{0}"

Cause: Could not perform check of swap space on the node indicated.

Action: Ensure the ability to access the node specified and view swap space information.

PRVF-07575: Encountered an internal error. The range of reference data for verifying swap size has not been correctly defined

Cause: Swap size could not be determined based on the physical memory available.

Action: This is an internal error that should be reported to Oracle.

PRVF-07584: Multiple versions of package "{0}" found on node {1}: {2}

Cause: Multiple versions of the package were found when only one version was expected.

Action: Ensure that the specified package is installed correctly.

PRVF-07590: "{0}" is not running on node "{1}"

Cause: The process identified is not running on the specified node.

Action: Ensure that the identified process is started and running on the specified node. If it is one of the Clusterware daemons then you can use 'crsctl check' command to check status.

PRVF-07591: Daemon process check cannot be performed for process "{0}" on node "{1}"

Cause: An error was encountered while trying to determine if the identified process was running on the specified node.

Action: Ensure that the user has the ability to execute the command displayed.

PRVF-07592: Space availability check for location "{0}" cannot be performed on node "{1}"

Cause: Unable to determine amount of free space available for the specified location on the node identified.

Action: Ensure the ability to communicate with the specified node and the ability to access the location identified.

PRVF-07593: CRS is not found to be installed on node "{0}"

Cause: Could not identify CRS installation on the specified node.

Action: Ensure that CRS is installed on the specified node.

PRVF-07594: {0} is running but is not working effectively on node "{1}"

Cause: Could not communicate with the process specified on the node indicated.

Action: Verify state of CRS on the node indicated using the 'crsctl check' command.

PRVF-07595: CRS status check cannot be performed on node "{0}"

Cause: Could not verify the status of CRS on the node indicated using 'crsctl check'.

Action: Ensure the ability to communicate with the specified node. Make sure that Clusterware daemons are running using 'ps' command. Make sure that the Clusterware stack is up.

PRVF-07596: CSS is probably working with a non-clustered, local-only configuration on node "{0}"

Cause: Oracle CSS was found to be configured to run in a local-only (non-clustered) environment on the specified node.

Action: Ensure that cluster setup is correct and reconfigure Cluster Synchronization Services (CSS) as necessary on the nodes that are supposed to be executing in a clustered environment. See Oracle Cluster Synchronization Services documentation for further information.

PRVF-07597: Unable to obtain OCR integrity details from node "{0}"

Cause: OCR was not found to be in a healthy state on the node specified.

Action: Verify the state of OCR on the node specified using 'ocrcheck'.

PRVF-07610: Cannot verify user equivalence/reachability on existing cluster nodes

Cause: Attempts to verify user equivalence, or node reachability, failed for all the existing cluster nodes.

Action: Verify that all the cluster nodes have user equivalence and are reachable.

PRVF-07611: Proper user file creation mask (umask) for user "{0}" is not found on node "{1}" [Expected = "{2}" ; Found = "{3}"]

Cause: The user's OS file creation mask (umask) was not the required setting.

Action: Set appropriate user file creation mask. Modify the users .profile or .cshrc or .bashrc to include the required umask.

PRVF-07612: User file creation mask check cannot be performed for user "{0}" on node "{1}"

Cause: Attempt to check the file creation mask of user on the specified node failed.

Action: Look at the accompanying error messages displayed and fix the problems indicated.

PRVF-07615: Unable to obtain network interface list using the "{0}" tool from Oracle Clusterware home "{1}"

Cause: The Oracle Interface Configuration Tool (OIFCFG) executable did not return the network interface list.

Action: Ensure that the 'oifcfg getif' and 'oifcfg iflist' commands return the valid interface list.

PRVF-07617: Node connectivity between "{0}" and "{1}" failed

Cause: Node connectivity between the two interfaces identified ( node : IP addr ) could not be verified.

Action: Verify the interface configurations for the network interfaces identified on the nodes indicated using utilities like ipconfig or ping.

PRVF-07650: Remote execution files could not be copied to "{0}" on the following nodes:

Cause: An attempt to copy files to the directory specified failed.

Action: Make sure that the user running CVU has read and write permissions on directory specified or specify a different work area using CV_DESTLOC environment variable where user executing this check has write permission.

PRVF-07700: Path for fixup root directory is either null or is an empty string

Cause: Provided fixup root directory path is either null or an empty string.

Action: Provide appropriate and absolute path for fixup root directory.

PRVF-07701: Path "{0}" for fixup root directory is invalid. It must be specified as an absolute pathname

Cause: Fixup root directory was not specified as an absolute pathname.

Action: Respecify fixup root directory as an absolute pathname.

PRVF-07702: The path "{0}" for fixup root directory is not a valid directory

Cause: Fixup root directory path was not a valid directory.

Action: Respecify fixup root path as a valid directory where files can be created and executed from.

PRVF-07703: The fixup root directory "{0}" is not writeable

Cause: Directory identified is not writeable.

Action: Verify write access to directory specified.

PRVF-07704: The fixup root directory "{0}" cannot be created

Cause: Could not create fixup root directory specified.

Action: Ensure that write access exists for the path for the directory specified.

PRVF-07705: Directory "{0}" cannot be created

Cause: Could not create directory specified.

Action: Ensure that write access exists for the path for the directory specified.

PRVF-07706: File "{0}" cannot be created

Cause: Could not create file specified.

Action: Ensure that write access exists for file location.

PRVF-07709: File "{0}" cannot be copied to file "{1}" on node "{2}"

Cause: Could not copy the source file specified to the target file specified on the identified node.

Action: Ensure that the node identified and the target location for the file specified can be accessed.

PRVF-07710: Invalid path has been specified for fixup root directory

Cause: The path specified for the fixup root directory is not correct.

Action: Specify an absolute path for a directory that exists and is writeable by the user performing the verification.

PRVF-07720: Fixup cannot be generated for creating group "{0}" on node "{1}"

Cause: Attempt to generate fixup for group creation on the specified node failed.

Action: Look at the accompanying error messages displayed and fix the problems indicated.

PRVF-07721: Fixup cannot be generated for creating user "{0}" on node "{1}"

Cause: Attempt to generate fixup for user creation on the specified node failed.

Action: Look at the accompanying error messages displayed and fix the problems indicated.

PRVF-07722: Fixup cannot be generated for setting kernel param "{0}" on node "{1}"

Cause: Attempt to generate fixup for kernel param on the specified node failed.

Action: Look at the accompanying error messages displayed and fix the problems indicated.

PRVF-07723: Fixup cannot be generated for setting soft limit for resource "{0}" on node "{1}"

Cause: Attempt to generate fixup for resource soft limit on the specified node failed.

Action: Look at the accompanying error messages displayed and fix the problems indicated.

PRVF-07724: Fixup cannot be generated for setting hard limit for resource "{0}" on node "{1}"

Cause: Attempt to generate fixup for resource hard limit on the specified node failed.

Action: Look at the accompanying error messages displayed and fix the problems indicated.

PRVF-07725: Fixup cannot be generated for setting runlevel "{0}" on node "{1}"

Cause: Attempt to generate fixup for run level on the specified node failed.

Action: Look at the accompanying error messages displayed and fix the problems indicated.

PRVF-07726: Fixup cannot be generated for setting membership of user "{0}" with group "{1}" on node "{2}"

Cause: Attempt to generate fixup for group membership on the specified node failed.

Action: Look at the accompanying error messages displayed and fix the problems indicated.

PRVF-07728: Could not access or create trace file path "{0}". Trace information could not be collected

Cause: Trace file location could not be created, or is not writeable.

Action: Make sure user has write access to location specified, or specify a different location using the environmental variable CV_TRACELOC.

PRVF-07729: Fixup cannot be generated for user "{0}", group "{1}", on node "{2}" because the user is not defined locally on the node

Cause: Fixup for group membership could not be generated because user was not found to be locally defined on the specified node.

Action: The fixup will have to be done manually. The user could be a Network Information Service (NIS) or Lightweight Directory Access Protocol (LDAP) user. Based on where the user is defined use appropriate tools to modify the user account.

PRVF-07730: Fixup cannot be generated for user "{0}", group "{1}", on node "{2}" because the group is not defined locally on the node

Cause: Fixup for group membership could not be generated because the group was not found to be locally defined on the specified node.

Action: The fixup will have to be done manually. The group could be a Network Information Service (NIS) or Lightweight Directory Access Protocol (LDAP) user. Based on where the group is defined use appropriate tools to modify the user account.

PRVF-09041: String has bad format: "{0}"

Cause: A parsing exception has occurred, and the string displayed could not parsed.

Action: This message should be part of one or more other messages. Please look at those messages and take appropriate action.

PRVF-09105: Linux RPM package version found to be lower than minimum required version of <"{0}"> on nodes:

Cause: Linux RPM package version found to be older than recommended version.

Action: Ensure that the Linux RPM package version installed on the system is version 4.4.2.3 or higher.

PRVF-09106: Linux RPM package version was lower than the expected value. [Expected = "{0}" ; Found = "{1}"] on node "{2}"

Cause: Linux RPM package version found to be older than recommended version.

Action: Ensure that the Linux RPM package version installed on the system is version 4.4.2.3 or higher.

PRVF-09107: Could not retrieve the version of Linux RPM package on node:

Cause: An error occurred while running rpm command on system to determine the current version of Linux RPM package.

Action: Ensure that the Linux RPM package is correctly installed and is accessible to current user.

PRVF-09108: Could not retrieve the version of Linux RPM package on node "{0}"

Cause: An error occurred while running rpm command on system to determine the current version of Linux RPM package.

Action: Ensure that the Linux RPM package is correctly installed and is accessible to current user.

PRVF-09306: OCFS2 is not configured in runlevel 3,4 and 5 on all the nodes

Cause: Runlevel was not configured with levels 3,4 and 5 all being on.

Action: Check OCFS2 configuration and ensure the run levels indicated are on.

PRVF-09555: Current installation user "{0}" is not the owner "{1}" of the existing CRS installation

Cause: The current user was not found to be an owner of an existing CRS installation.

Action: Ensure that the user upgrading the CRS installation is an owner of the already existing installation.

PRVF-09556: Failed to get the CRS user name for an existing CRS installation

Cause: An attempt to obtain the Clusterware owner information from an existing CRS installation failed.

Action: Ensure that the user executing the CVU check has read permission for CRS or Oracle Restart home.

PRVF-09653: Command "{0}" to check CTSS status failed on all of the nodes

Cause: CVU attempts to execute the displayed command failed on all of the nodes.

Action: Examine the messages displayed for each node and take action as per those messages.

PRVF-09654: CTSS status check command "{0}" executed successfully on node "{1}", but there was a failure in retrieving the output of this command

Cause: Reason for failure to retrieve output could be due to improper execution.

Action: Try the command manually on the node to verify proper execution, and fix any issues arising out of this.

PRVF-09655: Query of CTSS for time offset and reference produced invalid output on node "{0}" \nOutput: "{1}"

Cause: Failure to correctly parse output could be due to improper execution.

Action: Try the command manually on the node to verify proper execution, and fix any issues arising out of this.

PRVF-09656: The CTSS command to query time offset and reference failed on node "{0}" with error message "{1}"

Cause: Reason for failure to retrieve output could have been be due to improper execution.

Action: Try the command manually on the node to verify proper execution, and fix any issues arising out of this.

PRVF-09657: The CTSS command "{0}" failed to execute correctly or failed to produce valid output on all of the nodes

Cause: Reason for failure could be due to improper execution.

Action: Look at the individual messages for each node and take action as per those messages.

PRVF-09659: The time offset of "{1}" on node "{0}" against reference node "{3}" is NOT within specified limit of "{2}" milliseconds

Cause: One of the clocks, either on the current node, or on the reference node has drifted beyond limits.

Action: Monitor the offset over a longer duration and verify if the offset reduces over this period and falls within the threshold limits. Oracle Time Synchronization Service does periodic adjustments of the clock to attempt to bring it within threshold limits. If the threshold does not fall within limits over a period of time possibly due to a large deviation or drift, it is recommended that the Oracle processes on this node be shutdown, and the clock be adjusted on the problematic node suitably. It is NOT recommended to set a clock backwards.

PRVF-09661: Time offset is greater than acceptable limit on node "{0}" [actual = "{1}", acceptable = "{2}" ]

Cause: System clock has drifted from the clock on the reference node for the specified set of nodes.

Action: Look at the individual messages for each node and take action as per those messages.

PRVF-09664: CTSS is in an inconsistent state with some nodes in Observer state and some nodes in Active state. All nodes must be either in Observer state or in Active state.\nNodes with CTSS in Active state:"{0}"\nNodes with CTSS in Observer state:\n"{1}"

Cause: Some nodes may have NTP configured and some other nodes may not have NTP configured, resulting in an inconsistent state of CTSS.

Action: Stop Oracle CTSS service on all nodes and restart. Ensure that NTP is either configured on all nodes or not configured on any node.

PRVF-09665: Check of Clusterware install failed on some nodes. Clock Synchronization check will proceed with remnaining nodes

Cause: A valid CRSHome was not found on one or more nodes. The messages displayed prior to this message indicate the list of nodes where a valid Clusteerware install was not found.

Action: Specify the correct set of nodes that contain a valid Clusterware installation, or complete the Clusterware installation on those node(s) and repeat this CVU verification.

PRVF-09666: CTSS is in Observer state. Switching over to clock synchronization checks using NTP

Cause: All of the nodes queried for CTSS state indicate they are in Observer state. In the Observer state, CTSS is not performing active clock synchronization adjustments, but letting the underlying NTP handle this action.

Action: None. This is a normal state.

PRVF-09667: CTSS is in Observer state. Switching over to Windows-specific time synchronization checks

Cause: All of the nodes queried for CTSS state indicate they are in Observer state. In the Observer state, CTSS is not performing active clock synchronization adjustments, but letting the underlying Windows time synchronization mechanisms handle this action.

Action: Look at the results of the Windows time synchronization checks displayed following this message. If there are any errors reported, perform action suggested for those error messages.

PRVF-09668: Command "{0}" executed to retrieve CTSS resource status failed on all of the nodes

Cause: CVU attempts to execute the displayed command failed on all of the nodes.

Action: Examine the messages displayed for each node and take action as per those messages.

PRVF-09669: Failure to query CTSS resource on all nodes in the cluster

Cause: Attempt to query CTSS resource on all of the nodes in the cluster failed. Possibly because Clusterware may not be running on the nodes.

Action: Look at the specific error messages reported for each of the nodes and take action as per those messages.

PRVF-09670: Failure checking status of CTSS on node "{1}" using command "{0}"

Cause: CTSS may not OFFLINE, or may not be running, or the remote node may not be accessible.

Action: Try running in the indicated command directly on the specified node and ensure it is up and running, check that the remote node, and check user equivalence.

PRVF-09671: CTSS on node "{1}" is not in ONLINE state, when checked with command "{0}"

Cause: The CTSS daemon is not running on the node, it may have died or may have been stopped.

Action: Restart the CTSS daemon on the specified node.

PRVF-09672: All nodes for which CTSS state was checked failed the check: Nodes: "{0}"

Cause: CTSS is not in ONLINE state on any of nodes, possibly due to node accessibility, or being stopped.

Action: Look at the indvidual messages displayed for each node and perform the suggested action for those messages.

PRVF-09676: Clusterware is not installed on all nodes checked : "{0}"

Cause: A valid Clusterware installation was not found on these nodes.

Action: Make sure the correct nodes are being specified in this check, or make sure that Clusterware is fully installed on the nodes before running this check for those nodes.

PRVF-09691: Clock Synchronization check without Oracle Cluster Time Synchronization Service (CTSS) is not supported on this platform

Cause: The command line parameter, '-noctss', was specified on the command line which indicates that Clock Synchronization check should be performed without Oracle Cluster Time Synchronization Service (CTSS). This is not supported on this platform.

Action: Run the Clock Synchronization check without the '-noctss' flag.

PRVF-09692: CRS Active version is less than 11.2, performing NTP checks

Cause: CTSS is supported only from release 11.2 onwards. Therefore, the clocksync component check can only run NTP checks.

Action: None

PRVF-09695: Failed to determine operating system patch status on the node "{0}"

Cause: Operating system patch status could not be determined.

Action: Ensure that the operating system configuration is accessible.

PRVF-09800: An exception occurred while attempting to determine storage type for location "{0}"

Cause: The location indicated may not be available on the node, or may have insufficient permissions for access by the user running the CVU check.

Action: Make sure that the location is available on the node, and has the right permissions to allow the user running the CVU check to read its attributes.

PRVF-09801: The storage location "{0}" is not a device, and therefore invalid for running Udev permissions check

Cause: UDev permissions check are valid only for storage devices, and not valid for any kind of file system.

Action: Make sure that a valid storage device location is specified. If the location is derived from an ASM discovery string, make sure that the discovery string specified points to one or more storage devices, and not filesystems.

PRVF-09802: Attempt to get 'udev' information from node "{0}" failed

Cause: An attempt to read the 'udev' permission or rule file failed, or the permission or rule file did not contain any rules for the specified device or devices.

Action: Make sure that the 'udev' permission or rule directory is created, the 'udev' permission or rule file is available and accessible by the user running the check and that the permission or rule file contains the correct 'udev' rule for the device or devices being checked.

PRVF-09806: Failed to get storage attributes to compare udev attributes against, udev attributes check aborted

Cause: In order to compare Udev attributes for a given storage location, the expected storage attributes are required to compare against. There was a failure to get these attributes, possibly due to invalid on non-existing Clusterware installation.

Action: Make sure that a valid Clusterware install exists on the node.

PRVF-09807: Encountered an internal error. The range of reference data for verification of kernel param "{0}" has not been correctly defined for node "{1}"

Cause: No reference range defined to be used to calculate expected value.

Action: Define a reference range.

PRVF-09809: Proper OS Patch is not found on node "{0}" [Expected = "{1}" ; Found = "{2}"]

Cause: Required OS Patch is not applied.

Action: Apply the required OS Patch.

PRVF-09810: No prereq file defined

Cause: Prereq file was not set.

Action: Set prereq file.

PRVF-09811: Reference data is not available for release "{0}" on the operating system distribution "{1}"

Cause: No reference data was found for this operating system distribution.

Action: Consult the installation guide for the Oracle product and platform (for example, the Oracle Grid Infrastructure Installation Guide for Linux) for a list of supported operating system distributions.

PRVF-09903: Check of Clusterware install failed on some nodes. Oracle patch check will proceed with remaining nodes

Cause: A valid CRS home was not found on one or more nodes. The messages displayed prior to this message indicate the list of nodes where a valid Clusteerware install was not found.

Action: Specify the correct set of nodes that contain a valid Clusterware installation, or complete the Clusterware installation on those node(s) and repeat this CVU verification.

PRVF-09905: Clusterware is not installed on the following nodes : "{0}"

Cause: A valid Clusterware installation was not found on these nodes.

Action: Make sure the correct nodes are being specified, and that the Clusterware is fully installed on the nodes before running this check for those nodes.

PRVF-09907: Failed to query patch information from OPatch inventory

Cause: The execution of opatch lsinventory command failed.

Action: Make sure that the install inventory is readable by the user.

PRVF-09908: Failed to query patch information from Oracle executable

Cause: Oracle executable could not be queried for patch information.

Action: Make sure that Oracle executable is present and is readable by the user running CVU.

PRVF-09909: Patch information from OPatch did not match patch information from Oracle executable

Cause: Bug information from OPatch inventory does not match patch information recorded with Oracle executable.

Action: Make sure that all patches are applied correctly, refer to the OPatch user guide for information on patch application. Make sure that Oracle executable is relinked, refer to the Oracle Administrator Guide for information on relinking executables.

PRVF-09910: Patch information is not consistent across nodes

Cause: Bug information from OPatch do not match between the nodes.

Action: Make sure that all patches are applied correctly on all nodes, refer to the OPatch user guide for information on patch application.

PRVF-09913: Patch information from OPatch did not match patch information from Oracle executable on the following nodes:

Cause: Bug information from OPatch inventory does not match patch information recorded with Oracle executable.

Action: Make sure that all patches are applied correctly, refer to the OPatch user guide for information on patch application. Make sure that Oracle executable is relinked, refer to the Oracle Administrator Guide for information on relinking executables.

PRVF-09914: bug list did not match across nodes for the following nodes

Cause: Bug information from OPatch do not match between the nodes.

Action: Make sure that all patches are applied correctly on all nodes, refer to the OPatch user guide for information on patch application.

PRVF-09990: Antivirus software is running

Cause: Antivirus software was detected to be running.

Action: Oracle recommends that the Antivirus software be disabled. Antivirus may introduce delays in processing that interfere with time-sensitive cluster operations.

PRVF-09991: Owner of device "{0}" did not match the expected owner. [Expected = "{1}"; Found = "{2}"] on nodes: {3}

Cause: Owner of the device listed was different than required owner.

Action: Change the owner of the device listed or specify a different device.

PRVF-09992: Group of device "{0}" did not match the expected group. [Expected = "{1}"; Found = "{2}"] on nodes: {3}

Cause: Group of the device listed was different than required group.

Action: Change the group of the device listed or specify a different device.

PRVF-09993: Permissions of device "{0}" did not match the expected permissions. [Expected = "{1}"; Found = "{2}"] on nodes: {3}

Cause: Permissions of the device listed was different than the required permissions.

Action: Change the permissions on the device listed or specify a different device.

PRVF-09994: Owner, group, permission information could not be obtained for device(s) "{0}" on node "{1}"

Cause: Owner, group and permission information could not be obtained for devices listed on the nodes listed.

Action: "Ensure that the correct devices were specified and that they are created on the indicated node. Make sure that the path exists and is accessible by the user.

PRVF-09995: The information related to owner, group, and permissions could not be obtained for all devices on node "{0}".

Cause: The informaion related to owner, group, and permissions could not be obtained for all devices on the listed node.

Action: Ensure that the node is up and that the user equivalence exists on the listed node.

PRVF-09998: User "{0}" could not be verified as a domain user, domain "{1}" is either an invalid domain or can not be contacted

Cause: Current user could not be verified as domain user. The identified domain name was either an invalid domain name or the domain could not be contacted.

Action: Ensure that the Windows Domain Server is reachable; log in to the OS as a domain user.

PRVF-10002: Node "{0}" is not yet deleted from the Oracle inventory node list

Cause: The indicated node still exists in the list of nodes for the CRS home in the Oracle inventory.

Action: Use 'runInstaller -updateNodeList' to remove the indicated node from the CRS home node list.

PRVF-10014: Clusterware home "{0}" is located under Oracle base directory "{1}" on nodes "{2}"

Cause: Clusterware home directory was found to be located in a subdirectory of ORACLE_BASE.

Action: Choose a Clusterware home directory that is not a subdirectory of the ORACLE_BASE. After Clusterware installation the owner will be changed to root for all of the directories above Clusterware home.

PRVF-10015: Clusterware home "{0}" is located under Oracle base directory "{1}" on node "{2}"

Cause: Clusterware home directory was found to be located in a subdirectory of ORACLE_BASE.

Action: Choose a Clusterware home directory that is not a subdirectory of the ORACLE_BASE. After Clusterware installation the owner will be changed to root for all of the directories above Clusterware home.

PRVF-10016: Unable to check for the locations of Clusterware home and Oracle Base directory on nodes "{0}"

Cause: Clusterware home or Oracle Base is not accessible or do not exist.

Action: Ensure that Oracle Base and Clusterware home exist and are accessible.

PRVF-10017: Unable to check for the locations of Clusterware home and Oracle Base directory on node "{0}"

Cause: Clusterware home or Oracle Base is not accessible or do not exist.

Action: Ensure that Oracle Base and Clusterware home exist and are accessible.

PRVF-10018: Clusterware home "{0}" is located under Oracle base directory "{1}"

Cause: The Clusterware home directory was found to be a subdirectory of the Oracle base directory.

Action: Choose a Clusterware home directory that is not a subdirectory of the Oracle base directory. After Clusterware installation the owner will be changed to root for all of the directories above Clusterware home.

PRVF-10035: OCR location is not the same across the cluster nodes

Cause: More than one OCR location was found across the cluster nodes.

Action: Ensure that the OCR location is the same across the cluster nodes.

PRVF-10037: Failed to retrieve storage type for "{0}" on node "{1}"

Cause: The storage location specified may be non-existent or invalid or the user running the check may not have permissions to access the specified storage.

Action: Specify a valid existing location, and ensure that the user running the check has valid read permissions to this location.

PRVF-10038: Could not find any OCR Locations

Cause: OCR Locations were not passed to the check.

Action: Pass Oracle locations to the check.

PRVF-10105: ASMLib is not installed on the nodes:

Cause: The ASMLib installation file /etc/init.d/oracleasm was not found or could not be accessed on one or more nodes.

Action: Ensure that the ASMLib is correctly installed on all the nodes, or is not installed on any node.

PRVF-10106: ASMLib is not installed on the node "{0}"

Cause: The ASMLib installation file /etc/init.d/oracleasm was not found or could not be accessed on the indicated node.

Action: Ensure that the ASMLib is correctly installed on the specified node, or is not installed on any node.

PRVF-10107: Failed to retrieve ASMLib information on the nodes:

Cause: The check for ASMLib installation was unable to retrieve the required information on one or more nodes.

Action: Ensure that the ASMLib is correctly installed on all the nodes and that the user has the necessary access privileges.

PRVF-10108: Failed to retrieve ASMLib information on the node "{0}"

Cause: The check for ASMLib installation was unable to retrieve the required information on the indicated node.

Action: Ensure that the ASMLib is correctly installed on all the nodes and that the user has the necessary access privileges.

PRVF-10109: ASMLib is not configured correctly on the nodes:

Cause: ASMLib was found configured on some nodes, but not on the listed nodes.

Action: Ensure that the ASMLib is configured correctly and enabled on all the nodes, or is not configured on any node.

PRVF-10110: ASMLib is not configured correctly on the node "{0}"

Cause: ASMLib was found configured on some nodes, but not on the indicated node.

Action: Ensure that the ASMLib is configured correctly and enabled on all the nodes, or is not configured on any node.

PRVF-10111: ASMLib does not identify the disks "{0}" on the nodes:

Cause: ASMLib could not list all the disks on one or more nodes.

Action: Ensure that the ASMLib is configured correctly to list all the created disks, To refresh the list of disks execute "/etc/init.d/oracleasm scandisks".

PRVF-10112: ASMLib does not identify the disks "{0}" on the node "{1}"

Cause: ASMLib could not list all the disks on the indicated node.

Action: Ensure that the ASMLib is configured correctly to list all the created disks, To refresh the list of disks execute "/etc/init.d/oracleasm scandisks".

PRVF-10208: Following error occurred during the VIP subnet configuration check

Cause: An error occurred while performing the VIP subnet check.

Action: Look at the accompanying messages for details on the cause of failure.

PRVF-10209: VIPs "{0}" are active before Clusterware installation

Cause: Node VIPs were found to be active on the network before Clusterware installation.

Action: If you are upgrading an older release of Clusterware this is not an error. In case of new installation, make sure that the IP addresses to be configured as VIPs are currently unused.

PRVF-10210: VIPs "{0}" are not active after Clusterware installation

Cause: Node VIPs were found to be not active on the network after Clusterware installation.

Action: Please run the command 'srvctl start nodeapps' to bring up VIPs

PRVF-10211: Failed lookup of IP address for host "{0}"

Cause: An error occurred while trying to get IP address of the node VIP name.

Action: Run 'nslookup' on the name and make sure the name is resolved or add the node VIP name into OS hosts file.

PRVF-10304: IPMI device driver does not exist on nodes {0}

Cause: Open IPMI device driver is not installed on the nodes.

Action: Install Open IPMI device drivers.

PRVF-10306: Error occurred while retrieving IP address of IPMI device on nodes {0}

Cause: An internally-issued 'crsctl get css ipmiaddr' on the nodes failed.

Action: Configure IPMI device over LAN and run command 'crsctl set css ipmiaddr' command on the nodes to set the IP address.

PRVF-10307: IPMI IP address {0} on node {1} is not reachable

Cause: A timeout occurred while receiving IPMI ping response. Usually this results from having the wrong IP address.

Action: Run 'crsctl set css ipmiaddr' command to set the correct IP address.

PRVF-10308: Login to node {0} BMC device using stored credentials failed

Cause: An attempt to login to BMC on the node using username and password present in IPMI wallet failed.

Action: Run 'crsctl set css ipmiadmin' command to set correct credentials.

PRVF-10405: Path "{0}" is not suitable for usage as RAC database software for release "{1}"

Cause: The specified path is not found suitable for usage as RAC database software

Action: Ensure that you have selected a path that is suitable for the desired usage.

PRVF-10406: Path "{0}" is not suitable for usage as RAC database file for release "{1}"

Cause: The specified path is not found suitable for usage as RAC database file

Action: Ensure that you have selected a path that is suitable for the desired usage.

PRVF-10407: Path "{0}" is not suitable for usage as Oracle Clusterware storage for release "{1}"

Cause: The specified path is not found suitable for usage as Oracle Clusterware storage(OCR or Voting Disk).

Action: Ensure that you have selected a path that is suitable for the desired usage.

PRVF-10408: Path "{0}" is not suitable for usage as Single Instance database software for release "{1}"

Cause: The specified path is not found suitable for usage as Single Instance database software

Action: Ensure that you have selected a path that is suitable for the desired usage.

PRVF-10409: Path "{0}" is not suitable for usage as Single Instance database file for release "{1}"

Cause: The specified path is not found suitable for usage as Single Instance database file

Action: Ensure that you have selected a path that is suitable for the desired usage.