145 PRVG-00100 to PRVG-13712
- PRVG-00100: Directory "{0}" does not exist or is not writable for the current user on node "{1}".
-
Cause: A requested operation could not complete because it required writing the indicated directory, which failed because either the directory path did not exist or was not writable by the current user.
- PRVG-00101: Directory "{0}" does not exist or is not readable by the current user on node "{1}".
-
Cause: A requested operation could not complete because it required reading the indicated directory, which failed because either the directory path did not exist or was not readable by the current user.
- PRVG-00102: failed to delete directory "{0}" on node "{1}"
-
Cause: A requested operation could not complete because it required deleting the indicated directory, which failed because the directory path did not have required permissions for the current user to delete it.
- PRVG-00103: failed to delete file "{0}" on node "{1}"
-
Cause: A requested operation could not complete because it required deleting the indicated file, which failed because the file path did not have required permissions for the current user to delete it.
- PRVG-00219: Authorization error establishing connection to database "{0}" using user "{1}". Verification will be skipped for this database.
-
Cause: Authorization error occurred while establishing connection to the database using the specified user. This may be because the user does not exist, password is wrong, or user account is locked.
- PRVG-00221: Cannot launch browser to display the report. Check if the DISPLAY variable is set.
-
Cause: DISPLAY environment variable is not set
- PRVG-00222: Error establishing connection to database "{0}" using user "{1}". Verification will be skipped for this database.
-
Cause: Error occurred while establishing connection with the database using the specified user.
- PRVG-00258: Baseline collection for database "{0}" failed.
-
Cause: An error occurred while collecting baseline for the database.
- PRVG-00277: Specified ASM disk group name is null or an empty string
-
Cause: Internal error.
- PRVG-00278: ASM disk group name cannot contain wildcards
-
Cause: Internal error.
- PRVG-00279: Specified ASM disk group list is null or empty.
-
Cause: Internal error.
- PRVG-00280: The group "{0}" is defined locally with group ID "{1}" on node "{2}" which differs from the group ID "{3}" defined on the NIS or LDAP database for the same group.
-
Cause: The indicated group was duplicated on the indicated node with a different group ID than the group ID available on the NIS or LDAP database.
- PRVG-00281: Failed to retrieve the current effective group.
-
Cause: An attempt to retrieve the current effective group failed.
- PRVG-00282: failed to retrieve the operating system distribution ID
-
Cause: An attempt to retrieve the operating system distribution ID on the indicated node failed. The accompanying messages provide further detail.
- PRVG-00286: Reference data is not available for release "{0}" on the current operating system distribution "{1}". Using earlier operating system distribution "{2}" reference data.
-
Cause: No reference data was found for the current operating system distribution.
- PRVG-00329: Failed to check "{0}" port availability for port number "{1}" on nodes "{2}"
-
Cause: An attempt to check port availability of an indicated port failed on the identified nodes.
- PRVG-00330: "{0}" port number "{1}" required for component "{2}" is already in use on nodes "{3}"
-
Cause: Indicated IP port was found to be in use on the identified nodes.
- PRVG-00337: Protocol "{0}" port numbers "{1}" to be used for multicast communication are already in use on one or more cluster nodes
-
Cause: The Cluster Verification Utility (CVU) determined that the indicated IP ports were already in use on one or more cluster nodes.
- PRVG-00338: Protocol "{0}" port numbers "{1}" to be used for broadcast communication are already in use on one or more cluster nodes
-
Cause: The Cluster Verification Utility (CVU) determined that the indicated IP ports were already in use on one or more cluster nodes.
- PRVG-00341: Failed to retrieve the current login shell from nodes "{0}"
-
Cause: An attempt to retrieve the current login shell from indicated nodes failed.
- PRVG-00360: Location "{0}" file system is not NFS
-
Cause: An existing file system other than NFS was found on the specified location.
- PRVG-00361: Incorrect NFS mount options "{0}" used for "{1}":"{2}" mounted on: "{3}"
-
Cause: An incorrect NFS mount option was found being used for the intended use of the NFS file system mount.
- PRVG-00362: DNFS file system is not enabled on node "{0}".
-
Cause: The DNFS file system was not enabled on the indicated node.
- PRVG-00363: DNFS file system is not supported for the Oracle database version "{0}".
-
Cause: The oracle database version was less than the supported version Oracle 11g.
- PRVG-00364: Failed to check whether DNFS file system is enabled on node "{0}".
-
Cause: An error occurred while checking whether DNFS file system is enabled on the indicated node.
- PRVG-00365: Disk "{0}" is offline on nodes "{1}".
-
Cause: The check to ensure that the specified disk is shared across nodes failed because the indicated disk was offline.
- PRVG-00439: Hard limit check for maximum open file descriptors failed on node "{0}".
-
Cause: The Cluster Verification Utility could not determine the hard limit for the maximum open file descriptors on the indicated node.
- PRVG-00440: Hard limit check for maximum user processes failed on node "{0}".
-
Cause: The Cluster Verification Utility could not determine the hard limit for the maximum user processes on the indicated node.
- PRVG-00441: Hard limit check for maximum stack size failed on node "{0}".
-
Cause: The Cluster Verification Utility could not determine the hard limit for the maximum stack size on the indicated node.
- PRVG-00442: Soft limit check for maximum open file descriptors failed on node "{0}".
-
Cause: The Cluster Verification Utility could not determine the soft limit for the maximum open file descriptors on the indicated node.
- PRVG-00443: Soft limit check for maximum user processes failed on node "{0}".
-
Cause: The Cluster Verification Utility could not determine the soft limit for the maximum user processes on the indicated node.
- PRVG-00444: Soft limit check for maximum stack size failed on node "{0}".
-
Cause: The Cluster Verification Utility could not determine the soft limit for the maximum stack size on the indicated node.
- PRVG-00445: Proper soft limit for maximum open file descriptors was not found on node "{0}" [Expected {1} ; Found = "{2}"].
-
Cause: The Cluster Verification Utility determined that the setting for the indicated soft limit did not meet Oracle's recommendations for proper operation on the indicated nodes.
- PRVG-00446: Proper hard limit for maximum open file descriptors was not found on node "{0}" [Expected {1} ; Found = "{2}"].
-
Cause: The Cluster Verification Utility determined that the setting for the indicated hard limit did not meet Oracle's recommendations for proper operation on the indicated nodes.
- PRVG-00447: Proper soft limit for maximum user processes was not found on node "{0}" [Expected {1} ; Found = "{2}"].
-
Cause: The Cluster Verification Utility determined that the setting for the indicated soft limit did not meet Oracle's recommendations for proper operation on the indicated nodes.
- PRVG-00448: Proper hard limit for maximum user processes was not found on node "{0}" [Expected {1} ; Found = "{2}"].
-
Cause: The Cluster Verification Utility determined that the setting for the indicated hard limit did not meet Oracle's recommendations for proper operation on the indicated nodes.
- PRVG-00449: Proper soft limit for maximum stack size was not found on node "{0}" [Expected {1} ; Found = "{2}"].
-
Cause: The Cluster Verification Utility determined that the setting for the indicated soft limit did not meet Oracle's recommendations for proper operation on the indicated nodes.
- PRVG-00450: Proper hard limit for maximum stack size was not found on node "{0}" [Expected {1} ; Found = "{2}"].
-
Cause: The Cluster Verification Utility determined that the setting for the indicated hard limit did not meet Oracle's recommendations for proper operation on the indicated nodes.
- PRVG-00540: An incorrect value was specified for "{0}"
-
Cause: Incorrect value was specified for the identified command line option.
- PRVG-00550: Failed to retrieve the value of an OCR key "{0}"
-
Cause: An attempt to read the specified OCR key from the local node failed.
- PRVG-00551: The OCR key "{0}" was not found in OCR
-
Cause: Could not find the specified OCR key in OCR.
- PRVG-00601: The current source software is already version "{0}"
-
Cause: Verification of pre-upgrade conditions determined that the software is already at the specified upgrade version.
- PRVG-00602: Failed to retrieve database version of database home "{0}"
-
Cause: An error occurred while retrieving database version of the database home.
- PRVG-00700: Invalid target hub size
-
Cause: An invalid target hub size was specified
- PRVG-00710: CRS stack must be running on the local node for performing rolling upgrade.
-
Cause: CRS stack is not running on the local node.
- PRVG-00712: Cannot upgrade: Oracle Clusterware stack not running on this node.
-
Cause: An upgrade was requested on a node where the CRS stack was not running.
- PRVG-00713: Cannot upgrade: Oracle Clusterware stack not running on the local node, but the Oracle Clusterware stack was found running on nodes "{0}".
-
Cause: An upgrade was requested with Oracle Clusterware stack not running on the local node but one or more remote node had the stack up.
- PRVG-00714: Oracle Clusterware stack is not running on the local node. It is recommended that the upgrade be performed with the Oracle Clusterware stack running.
-
Cause: An upgrade was requested on a node with Oracle Clusterware stack not running.
- PRVG-00740: Failed to compress the content of directory "{0}" to "{1}" file using zip tool "{2}". Errors is "{3}"
-
Cause: An attempt to compress the content of the indicated directory into the indicated file failed using the indicated zip tool.
- PRVG-00801: invalid internal command tags
-
Cause: An attempt to parse an internal command results failed because either incorrect tags were present in the output or expected tags were missing in the output. This is an internal error.
- PRVG-00802: Storage type for path "{0}" could not be determined on node "{1}".
-
Cause: An error occurred while attempting to determine the storage type of the indicated path. Accompanying messages provide further details.
- PRVG-00803: Storage type for path "{0}" is inconsistent across the nodes.
-
Cause: The sharability check for the storage at the indicated path failed because the associated storage type was not consistent across all cluster nodes. The varying storage types were as indicated following the message.
- PRVG-00805: Signature for storage path "{0}" could not be determined on node "{1}".
-
Cause: An error occurred while attempting to determine the storage signature of the indicated path. Accompanying messages provide further details.
- PRVG-00806: Signature for storage path "{0}" is inconsistent across the nodes.
-
Cause: The sharability check for the storage at the indicated path failed because the associated storage signature was not consistent across all cluster nodes. The varying signatures were as indicated following the message.
- PRVG-00808: Incorrect NFS mount options "{0}" are used for file system "{1}" mount on path "{2}" at node "{3}".
-
Cause: The file system was found mounted with one or more mount options which were not appropriate for the intended use of the NFS file system mount.
- PRVG-00809: Mount options for file system "{0}" mounted on path "{1}" at node "{2}" did not meet the requirements for this platform [Expected = "{3}" ; Found = "{4}"]
-
Cause: The mount options found for the indicated file system as displayed in the message did not match the minimum set of mount options (shown in message) that must be used while mounting NFS volumes.
- PRVG-00810: File system details for storage path "{0}" could not be determined on node "{1}"
-
Cause: There was an error in determining details of file system at the indicated path.
- PRVG-00811: Discovery for storage of type "{0}" could not be performed on node "{1}".
-
Cause: An error occurred while attempting to discover the storage of the indicated type. Accompanying messages provide further details.
- PRVG-00812: failed to get the list of vendor cluster nodes
-
Cause: An error occurred while attempting to get the list of nodes of vendor cluster. Accompanying messages provide further details.
- PRVG-00813: Node "{0}" is not recognized by the vendor clusterware.
-
Cause: The indicated node was not recognized by the vendor clusterware.
- PRVG-00814: failed to get the volume groups on node "{0}"
-
Cause: An error occurred while attempting to get the volume groups on the indicated node. Accompanying messages provide further details.
- PRVG-00815: failed to find a volume group with signature "{0}" on node "{1}"
-
Cause: An error occurred while attempting to find a volume group with a specific signature on the indicated node.
- PRVG-00816: The 'reserve_lock' setting prevents sharing of device "{0}" on node "{1}".
-
Cause: The reserve_lock setting for the device was preventing the device from being shared on the node indicated.
- PRVG-00817: The 'reserve_policy' setting prevents sharing of device "{0}" on node "{1}".
-
Cause: The reserve_policy setting for the device was preventing the device from being shared on the node indicated.
- PRVG-00818: Disk "{0}" was offline on node "{1}".
-
Cause: The check to ensure that the specified disk is shared across nodes failed because the indicated disk was offline on the indicated node.
- PRVG-00819: The details of storage "{0}" could not be obtained on node "{1}".
-
Cause: An error occurred while attempting to get the details of the indicated storage. Accompanying messages provide further details.
- PRVG-00820: The amount of free space could not be determined for storage "{0}" on node "{1}".
-
Cause: An error occurred while attempting to get the free space on the indicated storage on the indicated node. Accompanying messages provide further details.
- PRVG-00821: The amount of free space could not be determined for ASM disk group "{0}".
-
Cause: An error occurred while attempting to get the free space on the indicated ASM disk group. Accompanying messages provide further details.
- PRVG-00822: The specified database file location "{0}" did not have read and write access for user "{1}" on node "{2}". Actual octal permissions are "{3}".
-
Cause: The database file location did not have read and write permissions for the indicated user on the indicated node.
- PRVG-00825: Incorrect NFS mount options "{0}" found for the quorum disk "{1}" mounted on path "{2}" at node "{3}".
-
Cause: The quorum disk was found mounted with one or more mount options which were not appropriate.
- PRVG-00826: No entry was found in the password database for the user name corresponding to the user-ID "{0}" for file "{1}" on node "{2}"
-
Cause: An attempt to get the user name for the indicated file on the indicated node failed because no entry was found in the password database for the indicated user-id.
- PRVG-00827: No entry was found in the group database for the group name corresponding to the group-ID "{0}" for file "{1}" on node "{2}"
-
Cause: An attempt to get the group name for the indicated file on the indicated node failed because no entry was found in the group database for the indicated group-id.
- PRVG-00830: Path "{0}" does not exist on nodes "{1}". Storage type for longest existing parent path "{2}" was found as "{3}" on nodes "{1}".
-
Cause: The sharability check for the storage at the indicated path failed because of the inconsistency described. In particular, the indicated path does not exist on the indicated nodes. Storage of the indicated type did exist at the indicated parent on the nodes shown.
- PRVG-01001: Insufficient number of arguments while executing "{0}"
-
Cause: An attempt was made to execute the specified script with insufficient number of arguments.
- PRVG-01002: Command "{0}" to obtain SCAN configuration failed
-
Cause: An attempt to execute the displayed command failed.
- PRVG-01003: Command "{0}" to check if OCR locations are on shared storage failed
-
Cause: An attempt to execute the displayed command failed.
- PRVG-01004: Command "{0}" to obtain GNS domain and GNS-VIP configuration failed
-
Cause: An attempt to execute the displayed command failed.
- PRVG-01005: Command "{0}" to obtain GNS and GNS-VIP status failed
-
Cause: An attempt to execute the displayed command failed.
- PRVG-01006: Command "{0}" to check if ASM instance is running failed
-
Cause: An attempt to execute the displayed command failed.
- PRVG-01007: Command "{0}" to get ASM disk groups configured on local node failed
-
Cause: An attempt to execute the displayed command failed.
- PRVG-01008: ASM status could not be verified on nodes "{0}"
-
Cause: An attempt to verify whether ASM was running on the specified nodes failed.
- PRVG-01009: Command "{0}" to obtain SCAN name failed
-
Cause: An attempt to execute the displayed command failed.
- PRVG-01010: Command "{0}" to obtain configuration of network resource for network number {1} failed
-
Cause: An attempt to execute the displayed command failed.
- PRVG-01011: The CRS software versions found on cluster nodes "{0}" and "{1}" do not match
-
Cause: The CRS software version found on the two nodes indicated do not match, or the CRS software version could not be obtained from one of the nodes indicated.
- PRVG-01012: The shared state of the CRS home path "{0}" on nodes to be added does not match the shared state on existing cluster nodes
-
Cause: The CRS home IS shared on the existing cluster and NOT shared on the nodes to be added, or the CRS home is NOT shared on the existing cluster nodes and IS shared on the nodes to be added.
- PRVG-01013: The path "{0}" does not exist or cannot be created on the nodes to be added
-
Cause: The path does not exist on the nodes being added and the parent path is not writable.
- PRVG-01015: Time server "{0}" has time offsets that are not within permissible limit "{1}" on nodes "{2}".
-
Cause: Offsets on the identified nodes in the cluster were not within limits for specified Time Server.
- PRVG-01016: The Oracle Clusterware configuration check is not valid in an environment in which Oracle Clusterware is not configured
-
Cause: A check valid only for an environment with Oracle Clusterware was attempted.
- PRVG-01017: NTP configuration file "{0}" is present on nodes "{1}" on which NTP daemon or service was not running
-
Cause: The indicated NTP configuration file was found on the indicated nodes where the NTP daemon or service was not running.
- PRVG-01018: NTP daemon or service "{0}" was running on nodes "{1}" on which an NTP configuration file was not found
-
Cause: The indicated NTP daemon or service was running on the indicated nodes on which no NTP configuration file was found.
- PRVG-01019: The NTP configuration file "{0}" does not exist on nodes "{1}"
-
Cause: The configuration file specified was not available or was inaccessible on the specified nodes.
- PRVG-01020: Check for NTP configuration file "{0}" could not be performed on nodes "{1}"
-
Cause: Check of existence of NTP configuration file failed as its existence could not be determined.
- PRVG-01021: NTP configuration file "{0}" found on nodes "{1}"
-
Cause: During an add node operation a NTP configuration file was found on the new node being added, but it was missing from existing cluster nodes.
- PRVG-01024: The NTP daemon or Service was not running on any of the cluster nodes.
-
Cause: The NTP daemon was not running on any of the cluster nodes.
- PRVG-01025: Validation of the state of the GNS server failed.
-
Cause: Proper functioning of the Grid Naming Service (GNS) server cluster could not be validated using client data file for the GNS client cluster. It is possible that GNS is not up, or the DNS domain is not delegated to the GNS server cluster.
- PRVG-01026: Node "{0}" is a member of cluster "{1}".
-
Cause: The cluster name returned from the execution of olsnodes on the node specified does not match the cluster name from the execution of olsnodes on the local node. The node indicated in the message could not be added to this cluster because it was already a member of the indicated cluster.
- PRVG-01027: The Oracle Grid Naming Service (GNS) "{0}" did not respond at IP address "{1}".
-
Cause: The GNS server did not respond to a query sent to the indicated IP address.
- PRVG-01029: NTP daemon "{0}" was running on nodes "{1}" but PID file "{2}" was missing.
-
Cause: While performing prerequisite checks, Cluster Verification Utility (CVU) found that the indicated network time protocol (NTP) daemon was running on the specified nodes, but the daemon had not been started with the PID file command line option. In the absence of the indicated PID file, if the installation proceeds, the Cluster Time Synchronization Services (CTSS) will be started in active mode and there will be two different time synchronization mechanisms running at the same time on the specified nodes.
- PRVG-01030: Command "{0}" to get ASM home failed
-
Cause: An attempt to execute the displayed command failed.
- PRVG-01031: Command "{0}" executed to get ASM SID failed
-
Cause: An attempt to execute the displayed command failed.
- PRVG-01032: slewing option "{0}" not found on the NTP daemon command line on nodes "{1}"
-
Cause: The specified slewing option was not found on the command line of the network time protocol (NTP) daemon on the specified nodes.
- PRVG-01033: Inspection of the NTP daemon command line arguments for slewing option "{0}" could not be performed on nodes "{1}".
-
Cause: An attempt to obtain the command line of the network time protocol (NTP) daemon process running on the specified nodes failed.
- PRVG-01036: NTP daemon boot time configuration file "{0}" does not have slewing option "{1}" set on nodes "{2}".
-
Cause: The network time protocol (NTP) daemon boot time configuration on the specified nodes did not have the specified slewing option set.
- PRVG-01037: NTP daemon boot time configuration file "{0}" could not be inspected for slewing option "{1}" on nodes "{2}".
-
Cause: An attempt to obtain the network time protocol (NTP) daemon boot time configuration file to check if specified slewing option is set failed on the nodes specified.
- PRVG-01040: Command "{0}" to list current Solaris zone failed to run on node "{1}".
-
Cause: An attempt to run the indicated command to list the current Solaris zone failed and did not produce any output.
- PRVG-01041: The command "{0}" to list current Solaris zone did not run successfully on node "{1}". The command exited with status "{2}" and the output was: "{3}".
-
Cause: An attempt to run the indicated command to list the current Solaris zone failed.
- PRVG-01042: Command "{0}" to get current zone name failed to run on node "{1}".
-
Cause: An attempt to run the indicated command to get the current Solaris zone name failed to run on the indicated node and did not produce any output.
- PRVG-01043: The command "{0}" to get current zone name did not run successfully on node "{1}". The command exited with status "{2}" and the output was: "{3}".
-
Cause: An attempt to run the indicated command to get the current Solaris zone name failed.
- PRVG-01046: NTP service is not disabled on nodes "{0}".
-
Cause: An attempt to verify that the network time protocol (NTP) service has been disabled on all nodes found that the service was still enabled on the indicated nodes.
- PRVG-01047: failed to verify that NTP service has been disabled on nodes "{0}"
-
Cause: An attempt to verify that the network time protocol (NTP) service had been disabled failed for the indicated nodes.
- PRVG-01050: Voting disk locations with the voting disk identification numbers "{0}" are offline.
-
Cause: Voting disk locations were found to be offline.
- PRVG-01051: The Oracle Clusterware stack is not running on any hub node.
-
Cause: The Oracle Clusterware stack is not running on any hub node.
- PRVG-01052: unable to validate device attributes for device "{0}" because keywords "{1}" was used in its UDEV rule
-
Cause: Device validation for the indicated device could not be completed properly because the indicated keywords were found in the UDEV rule matching that device. The message does not indicate an error in the rule, but a limitation in the validation algorithm. Possibly the rule was correct.
- PRVG-01060: Failed to retrieve the network interface classification information from an existing CRS home at path "{0}" on the local node
-
Cause: An attempt to obtain the network interface classification information by running 'oifcfg getif' from an existing CRS home failed on the local node.
- PRVG-01062: Leaf Nodes were specified without specifying Grid Naming Service (GNS) Virtual IP address (VIP).
-
Cause: Leaf Nodes were specified without specifying GNS-VIP. Leaf Nodes require GNS VIP, but do not require GNS subdomain.
- PRVG-01063: configuration files for more than one time synchronization service were found on nodes of the cluster
-
Cause: While verifying the setup of the time synchronization services on the cluster nodes, the Cluster Verification Utility (CVU) found that configuration files for more than one type of service were found.
- PRVG-01066: failed to execute command "{0}" to determine configuration of the daemon "{1}"
-
Cause: While verifying time synchronization across the cluster nodes, an attempt to query the indicated daemon using the indicated command failed on all of the nodes of the cluster.
- PRVG-01067: command "{0}" executed on nodes "{1}" produced no output
-
Cause: While verifying time synchronization across the cluster, the indicated command failed to produce any output on the indicated nodes.
- PRVG-01068: command "{0}" executed on node "{1}" produced an output that could not be parsed
-
Cause: While verifying time synchronization across the cluster nodes, the indicated command produced output on the indicated node that could not be parsed by the Cluster Verification Utility (CVU).
- PRVG-01069: failed to execute command "{0}" on node "{1}"
-
Cause: While verifying time synchronization across the cluster nodes, the indicated command could not be executed on the indicated node.
- PRVG-01072: daemon "{0}" running on nodes "{1}" does not synchronize to a common time server
-
Cause: While checking the clock synchronization across the cluster using the command '/usr/bin/chronyc sources', the Cluster Verification Utility (CVU) found that there was no common time server to which all nodes in the cluster synchronize. A list of time servers and the nodes which were configured to use each of them for synchronization accompanies this message.
- PRVG-01073: output of command "{0}" cannot be parsed
-
Cause: While checking for common time server for clock synchronization across cluster nodes using the indicated command, the Cluster Verification Utility (CVU) could not parse the output of the command.
- PRVG-01076: time servers listed by the command "{0}" on node "{1}" were ignored based on tally codes for the server
-
Cause: While checking for a common time server for clock synchronization using the indicated command, on the indicated node, the Cluster Verification Utility (CVU) ignored the time servers listed in the accompanying message because of the tally codes found in the command output.
- PRVG-01100: Found inconsistent 'hosts' entry in file "{0}" on node {1}
-
Cause: Cluster verification found an inconsistency in the 'hosts' specification entry in name service switch configuration file on the indicated node.
- PRVG-01101: SCAN name "{0}" failed to resolve
-
Cause: An attempt to resolve specified SCAN name to a list of IP addresses failed because SCAN could not be resolved in DNS or GNS using 'nslookup'.
- PRVG-01102: Command "{0}" to get network information failed.
-
Cause: An attempt to execute the displayed command failed.
- PRVG-01103: Command "{0}" to get OCR information failed.
-
Cause: An attempt to execute the displayed command failed.
- PRVG-01104: Unable to create the directory "{0}"
-
Cause: An attempt to create the directory specified failed on local node.
- PRVG-01105: Error copying file "{0}" to the local node from the source node "{1}"
-
Cause: The specified file could not be copied from the specified source node to the destination node.
- PRVG-01106: The OCR locations are not up to date on node "{0}". It has extra locations "{1}".
-
Cause: The OCR integrity check found that some extra OCR locations are in list on the specified node.
- PRVG-01107: The OCR locations are not up to date on node "{0}". The locations "{1}" are not present.
-
Cause: The OCR integrity check found that some OCR locations were missing from the OCR location list on the specified node.
- PRVG-01108: Failed to check OCR locations consistency on node "{0}"
-
Cause: An attempt to verify OCR locations failed.
- PRVG-01110: failed to validate the client GNS file
-
Cause: An attempt to execute an internal operation to validate the client GNS file failed. This is an internal error.
- PRVG-01111: failed to validate the GNS VIP
-
Cause: An attempt to execute an internal operation to validate the Grid Naming Service (GNS) VIP failed. This is an internal error.
- PRVG-01112: failed to obtain the list of all users that own CRS resources
-
Cause: During CRS user verification, an attempt to obtain the list of all users that own CRS resources failed.
- PRVG-01153: Easy Connect is not configured in the sqlnet.ora in the location "{0}" on the following nodes:
-
Cause: names.directory_path entry in the sqlnet.ora does not contain 'ezconnect' as one of the name resolution methods
- PRVG-01154: Easy Connect is not configured in the sqlnet.ora in the location "{0}" on node "{1}"
-
Cause: names.directory_path entry in the sqlnet.ora does not contain 'ezconnect' as one of the name resolution methods
- PRVG-01155: Easy Connect configuration could not be determined.
-
Cause: Easy Connect configuration check could not be completed
- PRVG-01162: The OS kernel is not running in 64-bit mode on node "{0}".
-
Cause: The OS kernel was not found to be running in 64-bit mode on the specified node.
- PRVG-01164: Failed to check the running mode of OS kernel in use
-
Cause: An attempt to obtain the type (32-bit or 64-bit) of OS kernel using command '/usr/sbin/prtconf -k' failed.
- PRVG-01169: The kernel version "{0}" detected on node "{1}" is not supported for this release.
-
Cause: An attempt to upgrade or install was rejected because the indicated OS kernel version was not supported.
- PRVG-01170: Private host name "{0}" with private IP address "{1}" on node "{2}" does not belong to any subnet classified for private interconnect
-
Cause: Private IP retrieved from the current configuration do not belong to any subnet classified for private interconnect.
- PRVG-01171: Failed to resolve the private host name "{0}" to an IP address on node "{1}"
-
Cause: IP address for the private host name could not be retrieved.
- PRVG-01172: The IP address "{0}" is on multiple interfaces "{1}" on nodes "{2}"
-
Cause: The given IP address was found on multiple interfaces, when an IP address can be on at most one interface.
- PRVG-01173: The interfaces "{0}" are configured with the same hardware address "{1}" on nodes "{2}"
-
Cause: The cluster verification utility (CVU) determined that the indicated interfaces had the same hardware address on the indicated nodes.
- PRVG-01185: Current OS user is not the owner of the existing database installation. [Expected = "{0}" ; Available = "{1}"]
-
Cause: Current OS user was not found to be the owner of the existing database installation.
- PRVG-01186: Failed to get the owning OS user name for the database home "{0}"
-
Cause: An attempt to obtain the database owner information from an existing database installation failed.
- PRVG-01191: Failed to check existence of ASM resource
-
Cause: An attempt to verify existence of ASM resource failed.
- PRVG-01192: ASM (pre-11.2) is not at the same version as CRS version {0}
-
Cause: The ora.asm resource was not found.
- PRVG-01195: Upgrade checks can only be performed when upgrading to versions greater than or equal to 11.2.0.1.0
-
Cause: The -dest_version specified was lower than 11.2.0.1.0.
- PRVG-01196: CRS configuration file "{0}" missing on node "{1}".
-
Cause: While verifying time zone consistency across cluster nodes, the Cluster Verification Utility found that the indicated file was missing on the indicated nodes.
- PRVG-01201: OS kernel parameter "{0}" does not have expected configured value on node "{1}" [Expected = "{2}" ; Current = "{3}"; Configured = "{4}"].
-
Cause: A check of the configured value for an OS kernel parameter did not find the expected value.
- PRVG-01205: OS kernel parameter "{0}" does not have expected current value on node "{1}" [Expected = "{2}" ; Current = "{3}"; Configured = "{4}"].
-
Cause: A check of the current value for an OS kernel parameter did not find the expected value.
- PRVG-01206: Check cannot be performed for configured value of kernel parameter "{0}" on node "{1}"
-
Cause: Kernel parameter value could not be determined.
- PRVG-01253: Required Oracle patch is not found on node "{0}" in home "{1}".
-
Cause: Required Oracle patch is not applied.
- PRVG-01254: Failed to determine Oracle patch status on the node "{0}"
-
Cause: Oracle patch status could not be determined.
- PRVG-01260: Command "{0}" to obtain Oracle patch status failed
-
Cause: An attempt to execute the displayed command failed.
- PRVG-01261: Required Oracle patch "{2}" in home "{1}" is not found on node "{0}".
-
Cause: An attempted operation could not be completed because the indicated patch had not been applied to the indicated home on the node shown.
- PRVG-01262: failure to determine the status of Oracle patch "{2}" in home "{1}" on node "{0}"
-
Cause: An attempted operation could not be completed because the Oracle patch status could not be determined. Possibly, the opatch binary was not found or could not read the Oracle home's inventory. Accompanying messages provide further failure details.
- PRVG-01265: Failed to determine operating system patch status for patch "{1}" on node "{0}"
-
Cause: Unable to determine the patch existence.
- PRVG-01274: Source home "{0}" is not suitable for upgrading to version "{1}".
-
Cause: The source home version was not suitable for upgrading to the specified version.
- PRVG-01278: failed to check suitability of source home "{0}" for upgrading to version "{1}"
-
Cause: An attempt to verify the suitability of upgrading identified source home to indicated version failed.
- PRVG-01297: The following device paths point to the same physical device: "{0}".
-
Cause: An attempt to check the suitability of listed or discovered device paths for ASM disk group creation found that multiple device paths point to the same physical device.
- PRVG-01299: ACFS file system does not exist at path "{0}".
-
Cause: Attempt to verify ACFS file system at the specified file path failed because no ACFS file system was found.
- PRVG-01300: ACFS verification is not supported on this platform
-
Cause: ADVM/ACFS device drivers have not yet been ported to this OS or CPU type.
- PRVG-01301: The COMPATIBLE.ADVM attribute is set to a version "{0}" which is less than the minimum supported version "{1}" for the disk group "{2}" that contains the ACFS path "{3}".
-
Cause: The COMPATIBLE.ADVM attribute was found to be set to a version which is less than minimum supported version for the ACFS path as indicated.
- PRVG-01302: Failed to perform the ADVM version compatibility check for the path "{0}"
-
Cause: An attempt to perform an ADVM version compatibility check for the specified path failed.
- PRVG-01303: Invalid device paths "{0}" designate a single device and cannot be used as multiple ASM devices.
-
Cause: An attempt to check the suitability of indicated device paths for ASM disk group creation found that the device paths do not represent different physical disks, which can affect availability and ASM file striping.
- PRVG-01306: Oracle ACFS is supported on the cluster nodes "{0}" but not on nodes "{1}".
-
Cause: Cluster Verification Utility (CVU) found that Oracle ACFS is supported only on some cluster nodes but not on all the cluster nodes.
- PRVG-01359: Daemon process "{0}" is configured on node "{1}"
-
Cause: The identified daemon process was found configured on the indicated node.
- PRVG-01360: Daemon process "{0}" is running on node "{1}"
-
Cause: The identified daemon process was found running on the indicated node.
- PRVG-01361: failed to read configuration file "{0}" on node "{1}"
-
Cause: An attempt to check the authentication services parameters failed because the indicated configuration file was not accessible on the indicated node.
- PRVG-01362: Native operating system authentication is not configured as an authentication method in the configuration file "{0}" on node "{1}".
-
Cause: A check of the authentication services parameters determined that the sqlnet.authentication_services parameter in the indicated configuration file on the indicated node was not set to allow the use of native OS authentication.
- PRVG-01363: Authentication method check for the entry "{0}" in the configuration file "{1}" on node "{2}" failed. Native OS authentication is expected to be allowed and the methods "{3}" are not expected to be specified
-
Cause: A check of the authentication services parameters determined that the sqlnet.authentication_services parameter in the indicated configuration file on the indicated node was not set to an expected value.
- PRVG-01370: Nodes "{0}" are configured as leaf nodes.
-
Cause: Indicated cluster nodes were found to be configured as leaf nodes which are not supported in release 19c onward.
- PRVG-01450: Oracle Clusterware is not installed on nodes "{0}".
-
Cause: A valid Oracle Clusterware installation was not found on the specified nodes.
- PRVG-01452: CTSS resource status check using command "{0}" failed as the command did not produce output on nodes "{1}"
-
Cause: An attempt to check the status of the Oracle Cluster Time Synchronization Service (CTSS) resource failed because the command specified did not produce output on the node specified.
- PRVG-01453: Oracle CTSS resource is not in ONLINE state on nodes "{0}"
-
Cause: The Oracle Cluster Time Synchronization Service (CTSS) resource was either in OFFLINE or UNKNOWN state on the nodes specified.
- PRVG-01454: CTSS resource status check using command "{0}" on node "{1}" failed.
-
Cause: An attempt to check the status of the Oracle Cluster Time Synchronization Service (CTSS) resource failed because the command specified failed.
- PRVG-01455: The command "{0}" to query CTSS time offset and reference failed on node "{1}"
-
Cause: An attempt to query Oracle Cluster Time Synchronization Service (CTSS) for time offset and reference using specified command failed on the node specified.
- PRVG-01456: The CTSS time offset and reference could not be determined on any node of the cluster.
-
Cause: An attempt to query CTSS for time offset and reference failed on all nodes of the cluster.
- PRVG-01457: Query of CTSS for time offset failed on nodes "{0}".
-
Cause: An attempt to query CTSS for time offset and reference failed on the nodes displayed in the message.
- PRVG-01508: IPMP fail-over group "{0}" with interface list "{1}" on node "{2}" has interfaces "{3}" which are not part of current private network classifications "{4}"
-
Cause: Found an additional fail-over dependency on an interface in an IPMP group which is not classified as a cluster interconnect on the identified node.
- PRVG-01509: IPMP fail-over group "{0}" with interface list "{1}" on node "{2}" has interfaces "{3}" which are not part of current public network classifications "{4}"
-
Cause: Found an additional fail-over dependency on an interface in an IPMP group which is not classified as a public interface on the identified node.
- PRVG-01510: IPMP configuration information cannot be obtained from any of the nodes
-
Cause: Failed to retrieve the information about IPMP configuration from all nodes.
- PRVG-01511: Failed to get IPMP configuration information from node "{0}"
-
Cause: Failed to retrieve the information about IPMP configuration from identified node.
- PRVG-01512: Failed to retrieve current selection of public and private network classifications
-
Cause: Could not retrieve the list of public and private network classifications selected in current configuration.
- PRVG-01513: Failed to retrieve current selection of public and private network classifications for node "{0}"
-
Cause: Could not retrieve the list of public and private network classifications selected in current configuration.
- PRVG-01515: Solaris IPMP daemon "{0}" is not running on node "{1}"
-
Cause: The indicated daemon process was not running. It may have aborted, been shut down, or simply not have been started.
- PRVG-01516: Operation to check presence of "{0}" daemon or process failed on node "{1}"
-
Cause: The operation to check indicated daemon or process failed on node identified.
- PRVG-01517: The check for "{0}" daemon or process status failed on nodes "{1}"
-
Cause: The indicated daemon was not accessible or there was some unknown failure in the check.
- PRVG-01521: The NIC configuration file at path "{0}" does not exist for IPMP interface "{1}" on node "{2}"
-
Cause: The network interface card (NIC) configuration file required for consistent IP network multipathing (IPMP) configuration of the interface across reboots was missing at the indicated path for the identified interface on the node.
- PRVG-01522: The NIC configuration file does not exist for some or all the IPMP interfaces on nodes "{0}"
-
Cause: The network interface card (NIC) configuration file required for consistent IP network multipathing (IPMP) configuration of the interface across reboots was missing at the indicated path for the identified interface on the indicated nodes.
- PRVG-01526: The IPMP interface "{0}" participating in an IPMP group "{1}" has deprecated flag set on node "{2}"
-
Cause: The identified IPMP interface was found with deprecated flag set on the indicated node.
- PRVG-01527: Some of the IPMP interfaces have deprecated flag set on nodes "{0}"
-
Cause: Some of the IPMP interfaces were found with deprecated flag set on the indicated nodes.
- PRVG-01528: Warning: The IPMP interface "{0}" participating in an IPMP group "{1}" is classified as private interconnection interfaces on node "{2}"
-
Cause: The identified interface classified as private interconnection interface was found to be a member of an IPMP group on the indicated node. The Highly Available IP Address (HAIP) is not supported on Solaris 11 if IPMP interfaces are classified as private interconnection.
- PRVG-01529: Warning: Some of the IPMP interfaces are classified as private interconnection interfaces on nodes "{0}"
-
Cause: The interfaces classified as private interconnection interfaces were found to be a member of an IPMP group on the indicated nodes. The Highly Available IP Address (HAIP) is not supported on Solaris 11 if IPMP interfaces are classified as private interconnection.
- PRVG-01533: The IPMP interfaces "{0}" classified as public network do not belong to the subnet "{1}" on node "{2}"
-
Cause: The identified IPMP interfaces classified as public networks were found to have different subnet on the indicated node.
- PRVG-01534: The IPMP interfaces classified as public network do not belong to the public subnet on nodes "{0}"
-
Cause: The IPMP interfaces classified as public networks were found to have different subnet on the indicated nodes.
- PRVG-01538: The IPMP interfaces "{0}" classified as private interconnection do not belong to the subnet "{1}" on node "{2}"
-
Cause: The identified IPMP interfaces classified as private interconnection were found to have different subnet on the indicated node.
- PRVG-01539: The IPMP interfaces classified as private interconnection do not belong to the private subnet on nodes "{0}"
-
Cause: The IPMP interfaces classified as private interconnection were found to have different subnet on the indicated nodes.
- PRVG-01543: The IPMP interfaces "{0}" share the same MAC or hardware address "{1}" on node "{2}".
-
Cause: The identified interfaces were found to share the same indicated MAC or hardware address on the indicated node.
- PRVG-01544: Some or all of the IPMP interfaces share the same MAC or hardware address on nodes "{0}".
-
Cause: The IP Network Multipathing (IPMP) interfaces were found to share the same MAC or hardware address on the indicated nodes.
- PRVG-01545: Some of the IPMP group interfaces are not classified as private or public network interfaces on nodes "{0}".
-
Cause: The IP Network Multipathing (IPMP) group consistency check found an additional fail-over dependency on an interface in an IPMP group which was not classified as either public or private interconnect on the identified nodes.
- PRVG-01546: IPMP group configuration check is skipped. The network configuration command line failed to specify network classifications PUBLIC or PRIVATE.
-
Cause: The IPMP configuration check could not be performed because the public and private network classifications were omitted from command line input.
- PRVG-01550: Failed to retrieve the list of IP addresses on private network from node "{0}"
-
Cause: An attempt to retrieve the list of private network IP addresses for the private network classifications failed on the indicated node.
- PRVG-01551: Failed to retrieve the list of IP addresses on public network from node "{0}"
-
Cause: An attempt to retrieve the list of public network IP addresses for the public network classifications failed on the indicated node.
- PRVG-01560: Temporary directory path "{0}" is shared on nodes "{1}"
-
Cause: The temporary directory path was found to be shared by two or more nodes.
- PRVG-01561: Setting ORA_CRS_HOME variable is not supported
-
Cause: The environment variable ORA_CRS_HOME has been set before starting an installation or upgrade.
- PRVG-01562: failed to retrieve the information for the cluster public networks
-
Cause: An attempt to retrieve the network information for networks classified as public during cluster network connectivity checks failed because there were no networks classified as public.
- PRVG-01563: Could not find a public cluster network to perform VIP subnet checks on the node "{0}".
-
Cause: An attempt to retrieve the cluster network information classified as public during VIP subnet checks failed because there were no networks classified as public on the specified node.
- PRVG-01564: The VIP name "{0}" could not be resolved to an IP address.
-
Cause: An attempt to resolve the indicated VIP name to an IP address during VIP subnet checks failed because the IP address could not be found.
- PRVG-01600: ASM network not specified
-
Cause: An ASM network was not specified when ASM presence was 'flex'.
- PRVG-01601: ASM network was not configured
-
Cause: An attempt to verify if the ASM network was configured failed when ASM presence was 'flex'.
- PRVG-01604: Failed to validate ASM credentials in file "{0}"
-
Cause: An attempt to verify if the ASM credentials in specified credentials file are valid failed.
- PRVG-01605: Failed to validate ASM credentials
-
Cause: An attempt to verify ASM credentials are valid failed.
- PRVG-01608: Network connectivity check across cluster nodes on the ASM network failed
-
Cause: An attempt to verify connectivity of cluster nodes on the ASM network failed.
- PRVG-01611: ASM network not specified
-
Cause: An ASM network was not specified when ASM presence was 'flex'.
- PRVG-01612: ASM disk groups could not be retrieved
-
Cause: During ASM integrity verification, an attempt to retrieve ASM disk groups failed.
- PRVG-01613: ASM disk group "{0}" did not resolve to any disk
-
Cause: An attempt to retrieve an associated disk path for the indicated ASM disk group did not resolve to any disk paths.
- PRVG-01614: Virtual environment detected. Skipping shared storage check.
-
Cause: Shared storage check was skipped because of limitations in determining the sharedness of the storage devices in virtual environments.
- PRVG-01615: Virtual environment detected. Skipping shared storage check for disks "{0}".
-
Cause: Shared storage check for the indicated disks was skipped because of limitations in determining the sharedness of the disks in virtual environments.
- PRVG-01650: failed to create required native library context.
-
Cause: An attempt to initialize a required native library context failed.
- PRVG-01701: Check for equivalence for user "{0}" from node "{1}" to nodes "{2}" failed.
-
Cause: The CVU check to verify user equivalence among all cluster nodes failed on the indicated node because user equivalence did not exist for the indicated user between that node and all of the other nodes shown in the message.
- PRVG-01703: Check for user equivalence for user "{0}" failed on all cluster nodes.
-
Cause: An error occurred while trying to verify user equivalence among the cluster nodes. The accompanying messages provide detailed information about the failure.
- PRVG-01801: Nodes "{0}" are Windows domain controllers.
-
Cause: The Cluster Verification Utility determined that the specified nodes are Windows domain controllers. Oracle recommends that Oracle Clusterware and Database software should not be installed on machines that are Windows domain controllers.
- PRVG-01803: failed to determine if any of the nodes "{0}" are Windows domain controllers
-
Cause: The Cluster Verification Utility could not determine if any of the specified nodes are Windows domain controllers.
- PRVG-01900: The directory "{0}" cannot be used as work directory on nodes "{1}".
-
Cause: An operation requiring remote execution could not complete because the attempt to set up the Cluster Verification Utility remote execution framework failed because the necessary files could not be copied to the indicated directory on the indicated nodes. The accompanying message provides detailed failure information.
- PRVG-01901: failed to setup CVU remote execution framework directory "{0}" on nodes "{1}"
-
Cause: An operation requiring remote execution could not complete because the attempt to set up the Cluster Verification Utility remote execution framework failed on the indicated nodes at the indicated directory location because the CVU remote execution framework version did not match the CVU java verification framework version. The accompanying message provides detailed failure information.
- PRVG-01903: Directory "{0}" cannot be used as work directory on any of the nodes.
-
Cause: An operation requiring remote execution could not complete because the attempt to set up the Cluster Verification Utility remote execution framework failed on all nodes. The accompanying message provides detailed failure information.
- PRVG-01904: Path "{0}" is not a valid directory.
-
Cause: An operation to set up the Cluster Verification Utility remote execution framework was rejected because the indicated path did not designate a valid directory.
- PRVG-02000: The 'search' entry in the existing "{0}" files is inconsistent.
-
Cause: A check of resolv.conf files across the cluster nodes found inconsistent 'search' entries.
- PRVG-02002: Encountered error in copying file "{0}" from node "{1}" to node "{2}"
-
Cause: The specified file could not be copied from the specified source node to the destination node.
- PRVG-02012: The 'domain' entries in the existing "{0}" files are inconsistent.
-
Cause: A check of nodes' resolv.conf files found inconsistent 'domain' entries.
- PRVG-02016: File "{0}" on node "{1}" has both 'search' and 'domain' entries.
-
Cause: Both 'search' and 'domain' entries were found in the 'resolv.conf' file on the indicated node.
- PRVG-02018: failed to execute DNS query command on nodes "{0}"
-
Cause: An error happened while querying a domain name server.
- PRVG-02019: Check for equivalence of user "{0}" from node "{1}" to node "{2}" failed
-
Cause: The CVU check to verify user equivalence for the indicated user between the indicated nodes failed because user equivalence did not exist.
- PRVG-02020: No OHASD entry was found in /etc/inittab file on node "{0}"
-
Cause: A check of file /etc/inittab did not find the expected entry for OHASD.
- PRVG-02026: no response for name "{0}" from the DNS server "{1}" specified in "resolv.conf"
-
Cause: An attempt to look up the name in DNS has failed.
- PRVG-02027: Owner of file "{0}" is inconsistent across nodes. [Found = "{1}" on Nodes = "{2}"]
-
Cause: Ownership of the indicated file was not the same on all cluster nodes.
- PRVG-02028: Group of file "{0}" is inconsistent across nodes. [Found = "{1}"]
-
Cause: Ownership group of the indicated file was not the same on all cluster nodes.
- PRVG-02029: Octal permissions of file "{0}" are inconsistent across nodes. [Found = "{1}"]
-
Cause: Octal permissions of the indicated file were not the same on all cluster nodes.
- PRVG-02030: Failed to check attributes of file "{0}" on node "{1}"
-
Cause: An attempt to retrieve the file system attributes of the specified file failed.
- PRVG-02031: Owner of file "{0}" did not match the expected value on node "{1}". [Expected = "{2}" ; Found = "{3}"]
-
Cause: A check for file system attributes found that the owner of the indicated file on the indicated node was different from the required owner.
- PRVG-02032: Group of file "{0}" did not match the expected value on node "{1}". [Expected = "{2}" ; Found = "{3}"]
-
Cause: A check for file system attributes found that the group of the indicated file on the indicated node was different from the required group.
- PRVG-02033: Permissions of file "{0}" did not match the expected octal value on node "{1}". [Expected = "{2}" ; Found = "{3}"]
-
Cause: A check for file system attributes found that the permissions of the indicated file on the indicated node were different from the required permissions.
- PRVG-02034: Command "{0}" executed on node "{1}" exited with status value "{2}" and gave the following output:
-
Cause: An executed command produced unexpected results.
- PRVG-02035: Command "{0}" executed on node "{1}" exited with status value "{2}" and gave no output
-
Cause: An executed command produced unexpected results.
- PRVG-02042: Unable to obtain OLR location from node "{0}"
-
Cause: A check of the Oracle Local Registry (OLR) could not determine that file's location on the indicated node.
- PRVG-02043: Command "{0}" failed on node "{1}" and produced the following output:
-
Cause: An executed command failed.
- PRVG-02044: Command "{0}" failed on node "{1}" and produced no output.
-
Cause: An executed command failed.
- PRVG-02045: Operating system function "{0}" failed on node "{1}".
-
Cause: A call to an Operating System dependent service or function returned an error indication.
- PRVG-02046: Operating system error message: "{0}"
-
Cause: This message accompanies message PRVG-2045 above when the Operating System dependent error data can be converted into a text message.
- PRVG-02047: Additional information: "{0}"
-
Cause: This message accompanies message PRVG-2045 and supplies additional information related to the error condition. A single error may include multiple lines of additional information.
- PRVG-02048: no response for name "{0}" from the DNS server "{1}" specified in "resolv.conf"
-
Cause: An attempt to look up the name in DNS using the indicated name server has failed.
- PRVG-02052: There is no 'hosts' entry in the file "{0}" on nodes: "{1}".
-
Cause: The 'hosts' entry was not found in the indicated name service switch configuration file on the nodes indicated while it was present in others.
- PRVG-02054: The following nodes have multiple 'hosts' entries defined in file "{0}": {1}.
-
Cause: The nodes specified had multiple 'hosts' entries defined in the file specified.
- PRVG-02058: The 'hosts' entries in the existing "{0}" files are inconsistent.
-
Cause: A check of nodes' name service switch configuration files found inconsistent 'hosts' entries.
- PRVG-02064: There are no configured name servers in the file '/etc/resolv.conf' on the nodes "{0}"
-
Cause: Entries for 'nameserver' were not found in the file '/etc/resolv.conf' on the indicated nodes.
- PRVG-02070: Disk group for ocr location "{0}" is not available on the following nodes:
-
Cause: Disk group was not found on the specified nodes.
- PRVG-02071: Disk group for ocr location "{0}" is not available on "{1}"
-
Cause: Disk group was not found on the specified node.
- PRVG-02078: Execution of command "{0}" on node "{1}" for disk "{2}" showed there was no UUID in the disk label.
-
Cause: An attempt to retrieve the universally unique ID (UUID) for the indicated disk on the node shown using the indicated command in order to check for sharedness across nodes determined that the disk did not have a UUID. Sharedness could not be checked for this device.
- PRVG-04000: Windows registry key "{0}" is absent on node "{1}"
-
Cause: Could not find the specified Windows registry key on the identified node.
- PRVG-04001: Failed to check existence of Windows registry key "{0}" on node "{1}", [{2}]
-
Cause: Could not check the existence of specified Windows registry key on the identified node.
- PRVG-04002: Missing '-user <user_name>' argument for selected privilege delegation method "{0}".
-
Cause: A user name was not specified on the command line for the specified privilege delegation method.
- PRVG-04500: Parameter "{0}" value is not valid
-
Cause: This is an internal error. The value for the specified parameter is null or empty string.
- PRVG-04505: Windows user "{0}" cannot be the service user
-
Cause: An attempt was made to specify the built-in Windows user 'nt authority\\local service' as the service owner.
- PRVG-04506: Windows user "{0}" is not a domain user
-
Cause: An attempt was made to specify a Windows user account local to this system as the service owner.
- PRVG-04510: Windows user "{0}" is an administrator on the nodes "{1}"
-
Cause: The specified Windows user was found to be an administrator on the nodes specified.
- PRVG-04513: User name or password is invalid for Windows user "{0}"
-
Cause: An attempt to verify the Windows user name and password failed as user name or password is not valid.
- PRVG-04515: Unable to determine if the Windows user "{0}" is a domain user
-
Cause: An attempt to determine if the specified Windows user account is a domain user failed.
- PRVG-04516: Failed to verify Windows user "{0}" is not an administrator on nodes "{1}"
-
Cause: An attempt to determine if the specified Windows user is an administrator on the specified nodes failed.
- PRVG-04517: Failed to validate the user name and password for Windows user "{0}"
-
Cause: An attempt to determine if the specified Windows user name and password are valid failed.
- PRVG-04520: The OSUSER wallet contains incorrect password for Windows user "{0}"
-
Cause: An attempt to verify the password stored in OSUSER wallet for the specified Windows user found that the password is invalid.
- PRVG-04521: Failed to verify the password stored in OSUSER wallet for Windows user "{0}"
-
Cause: An attempt to determine if the password stored in OSUSER wallet for specified Windows user is valid failed.
- PRVG-04522: Failed to check if Windows user "{0}" can be used as service user
-
Cause: An attempt to determine if the specified Windows user can be used as a service user failed.
- PRVG-04524: Windows user "{0}" is not a member of Windows group "{2}" on nodes "{1}"
-
Cause: The specified Windows user was not a member of specified Windows group on the nodes specified.
- PRVG-04526: Failed to verify if Windows user "{0}" is a member of Windows group "{1}"
-
Cause: An attempt to determine if the specified Windows user is a member of specified windows group failed.
- PRVG-04530: Windows virtual account was specified as the Oracle database home service user.
-
Cause: An attempt was made to specify the Windows virtual account as Oracle home service user. This type of user is not supported for a Real Application Cluster database home.
- PRVG-04531: Windows user "{0}" does not have permissions on directory "{1}" on nodes "{2}"
-
Cause: The specified Windows user did not have permissions on directory specified on the nodes specified.
- PRVG-04532: Windows user "{0}" does not have permissions on file "{1}" on nodes "{2}"
-
Cause: The specified Windows user did not have permissions on file specified on the nodes specified.
- PRVG-04533: Windows user "{0}" does not have permissions on Windows registry key "{1}" on nodes "{2}"
-
Cause: The specified Windows user did not have permissions on Windows registry key specified on the nodes specified.
- PRVG-04537: Failed to verify Windows user "{0}" has permissions on directory "{2}" on nodes "{1}"
-
Cause: An attempt to determine if the specified Windows user has permissions on the directory specified on the nodes specified failed.
- PRVG-04538: Failed to verify Windows user "{0}" has permissions on file "{2}" on nodes "{1}"
-
Cause: An attempt to determine if the specified Windows user has permissions on the file specified on the nodes specified failed.
- PRVG-04539: Failed to verify Windows user "{0}" has permissions on Windows registry key "{2}" on nodes "{1}"
-
Cause: An attempt to determine if the specified Windows user has permissions on the Windows registry key specified on the nodes specified failed.
- PRVG-04541: Windows user "{0}" is not a Group Managed Service Account (GMSA) user on nodes "{1}".
-
Cause: The specified Windows user was not a Group Managed Service Account (GMSA) user on the nodes specified.
- PRVG-04543: failed to verify Windows user "{0}" is a Global Managed Service Account (GMSA) user on nodes "{1}"
-
Cause: An attempt to determine if the specified Windows user is a Global Managed Service Account (GMSA) user on the specified nodes failed.
- PRVG-04558: ASM instance was found to be configured and running on nodes "{0}" and not running on the node "{1}" on which upgrade is requested
-
Cause: An ASM instance was found configured and running on the indicated nodes and not on the identified node on which upgrade was requested.
- PRVG-04560: Default listener for node "{0}" was found configured and running on node "{1}"
-
Cause: A default listener was found configured and running on the indicated node and not on the node on which the upgrade was requested.
- PRVG-04562: Failed to determine the status of an ASM instance configuration. Error: {0}
-
Cause: Attempt to retrieve an information about the current configuration of an ASM instance failed with the indicated error.
- PRVG-04563: Failed to determine the status of default listener on the node "{0}" on which upgrade is requested. Error: {1}
-
Cause: Attempt to retrieve the status of the default listener on the node on which upgrade is requested failed with the indicated error.
- PRVG-04564: File "{0}" could not be created
-
Cause: ASM disk ownership, group, permission and size checks failed because ASM discovery string processing was unable to create a temporary file.
- PRVG-04567: An ASM instance was found to be configured but the ASM parameter file used for this instance was not found on the node "{0}" on which upgrade is requested.
-
Cause: An ASM parameter file for an ASM instance configured on the indicated node was not found.
- PRVG-04568: An ASM instance was found to be configured but the ASM parameter file does not exist at location "{0}" on the node "{1}" on which upgrade is requested.
-
Cause: The indicated ASM parameter file did not exist at the identified location.
- PRVG-04572: Parameter file "{0}" for ASM instance is not on an ASM disk group.
-
Cause: The indicated parameter file was not on an ASM disk group.
- PRVG-04574: Password file "{0}" for ASM instance is not on an ASM disk group.
-
Cause: The indicated password file was not on an ASM disk group.
- PRVG-04576: ASM password file "{0}" does not exist on nodes "{1}".
-
Cause: An attempt to upgrade Oracle Grid Infrastructure failed because the indicated ASM password file was not present on indicated nodes.
- PRVG-04585: failed to retrieve the ASM parameter file location on the node "{0}"
-
Cause: A CVU pre-upgrade check could not be completed because an attempt to query the currently running ASM instance on the indicated node to obtain the location of its parameter file failed. The accompanying error messages provide detailed failure information.
- PRVG-04586: Password backup file "{0}" for ASM is not on an Oracle ASM disk group.
-
Cause: The indicated password backup file was not on an Oracle ASM disk group.
- PRVG-04588: Password file "{0}" and Password backup file "{1}" for ASM are on the same Oracle ASM disk group.
-
Cause: The indicated password backup file is on the same Oracle ASM disk group as the password file.
- PRVG-04600: Nodes "{0}" do not have VIPs configured
-
Cause: An attempt to verify if the specified nodes that are configured as 'auto' and are currently Leaf nodes but can become Hub nodes have Virtual Internet Protocol (VIP) addresses configured failed because no IP addresses were assigned for the node VIPs.
- PRVG-04601: Node VIPs for nodes "{0}" are active
-
Cause: An attempt to verify if the specified nodes that are configured as 'auto' and are currently Leaf nodes but can become Hub nodes have Virtual Internet Protocol (VIP) addresses that are not active failed because the VIPs for the specified nodes were active.
- PRVG-04610: Nodes "{0}" do not have VIPs configured
-
Cause: It was found that specified hub nodes do not have node VIPS configured.
- PRVG-04611: Node VIPs for nodes "{0}" are active
-
Cause: The VIPs for the specified hub nodes were found to be reachable.
- PRVG-04654: Disk discovery string mismatch between ASM instance and GPnP profile. GPnP profile: "{0}", ASM Instance: "{1}".
-
Cause: Disk discovery strings in the ASM instance and GPnP profile were different.
- PRVG-04655: The command "{0}" to retrieve ASM discovery string failed
-
Cause: The specified command executed to retrieve ASM discovery string failed.
- PRVG-04656: The command "{0}" to obtain the list of ASM disks failed
-
Cause: The specified command executed to retrieve list of ASM disks failed.
- PRVG-04657: The permissions for block devices "{0}" are incorrect on node "{1}" [Expected = {2} octal, Actual = {3}]
-
Cause: The permissions of the indicated block devices were incorrect on the specified node. Starting in 12g the default ASM disk discovery string was changed from '/dev/raw/raw*' to '/dev/sd*'. The disks corresponding to the block device files in the message were members of ASM disk groups and were accessed using the raw devices (matched by '/dev/raw/raw*' prior to 12g) with the correct permissions. However, the block devices in the message corresponding to the same disks and found with '/dev/sd*' do not have the correct permissions. To ensure continued working of ASM, all disks that were members of disk groups must continue to be members.
- PRVG-04664: Failed to obtain block device corresponding to raw disk "{0}" on node "{1}"
-
Cause: An attempt to obtain block device corresponding to specified raw disk failed on node specified. Starting in 12g the default ASM disk discovery string was changed from '/dev/raw/raw*' to '/dev/sd*'. The specified disks were picked up by using the old default disk discovery string '/dev/raw/raw*'. To ensure continued working of ASM, all disks that were members of disks groups must continue to be members.
- PRVG-04665: The owner for block devices "{0}" are incorrect on node "{1}" [Expected = {2}, Actual = {3}]
-
Cause: The owner of the block device on the node specified were incorrect. Starting in 12g the default ASM disk discovery string was changed from '/dev/raw/raw*' to '/dev/sd*'. The disks corresponding to the block device files in the message were members of ASM disk groups and were accessed using the raw devices (matched by '/dev/raw/raw*' prior to 12g) with the correct ownership. However, the block devices in the message corresponding to the same disks and found with '/dev/sd*' do not have the correct ownership. To ensure continued working of ASM, all disks that were members of disk groups must continue to be members.
- PRVG-04666: The group for block devices "{0}" are incorrect on node "{1}" [Expected = {2}, Actual = {3}]
-
Cause: The group ownership of the block devices on the node specified were incorrect. Starting in 12g the default ASM disk discovery string was changed from '/dev/raw/raw*' to '/dev/sd*'. The disks corresponding to the block device files in the message were members of ASM disk groups and were accessed using the raw devices (matched by '/dev/raw/raw*' prior to 12g) with the correct group ownership. However, the block devices in the message corresponding to the same disks and found with '/dev/sd*' do not have the correct group ownership. To ensure continued working of ASM, all disks that were members of disk groups must continue to be members.
- PRVG-04669: Could not determine ASM disk discovery string on node "{0}"
-
Cause: ASM disk ownership, group, permission and size checks failed because the ASM discovery string could not be determined.
- PRVG-04670: File "{0}" could not be read
-
Cause: An error occurred while reading the specified file while trying to determine whether default ASM discovery string was being used.
- PRVG-04671: Failed to match the block device "{0}" with the new default discovery string
-
Cause: The specified block device could not be discovered with the new default discovery string. Starting in 12g the default ASM disk discovery string was changed from '/dev/raw/raw*' to '/dev/sd*'. To ensure proper upgrade of ASM, all disks that were member disks of diskgroups prior to upgrade must continue to be discovered as member disks after upgrade.
- PRVG-04672: failed to retrieve ASM discovery string information while checking ASM disk size consistency
-
Cause: An attempt to obtain ASM discovery string information failed.
- PRVG-05150: could not determine if path {0} is a valid path on all nodes
-
Cause: Checking for shared devices could not be executed because the indicated path could not be validated for all nodes. Validation was not possible because the device referenced by the path could not be identified. On Linux systems this can occur if the file /etc/multipath.conf is not readable by the requesting user.
- PRVG-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 is partially upgraded.
- PRVG-05500: Failed to retrieve the disk information for path "{0}"
-
Cause: Could not retrieve the disk information for the specified path on all nodes.
- PRVG-05501: Failed to retrieve the disk information for path "{0}" on node "{1}"
-
Cause: Could not retrieve the disk information for the specified path on identified node.
- PRVG-05723: Network CRS resource is configured to use DHCP provided IP addresses
-
Cause: The network Cluster Ready Services (CRS) resource that was configured to request the Dynamic Host Configuration Protocol (DHCP) server for IP addresses was online. DHCP server check must not be performed while the network CRS resource configured to use the DHCP provided IP address is online.
- PRVG-05725: The TCP server process with PID "{0}" on node "{1}" failed to exit normally
-
Cause: The TCP server process with the PID specified, running on the node indicated, failed to exit normally.
- PRVG-05726: Failed to discover DHCP servers on public network listening on port "{0}" using command "{1}"
-
Cause: An attempt to use the indicated command to discover Dynamic Host Configuration Protocol (DHCP) servers listening on the public network on the indicated port failed.
- PRVG-05727: Command "{0}" to generate DHCP client ID failed
-
Cause: An attempt to generate client ID using specified command required for 'crsctl discover dhcp', 'crsctl request dhcp' and 'crsctl release dhcp' commands failed.
- PRVG-05730: DHCP servers on public network listening on port "{0}" could not provide an IP address for node VIP on node "{1}"
-
Cause: An attempt to verify if DHCP servers respond to DHCP discover packets sent on the specified port for specified node's node VIP failed, as no response was received.
- PRVG-05731: DHCP servers on network "{2}" listening on port "{0}" could not provide an IP address for node VIP on node "{1}"
-
Cause: An attempt to verify if DHCP servers respond to DHCP discover packets sent on the specified network and port for specified node's node VIP failed, as no response was received.
- PRVG-05732: No DHCP server were discovered on the network "{1}" listening on port {0}
-
Cause: No reply was received for the DHCP discover packets sent on the specified network and port.
- PRVG-05733: Failed to discover DHCP servers on network "{2}" listening on port "{0}" using command "{1}"
-
Cause: An attempt to use the indicated command to discover Dynamic Host Configuration Protocol (DHCP) servers listening on the indicated network on the indicated port failed.
- PRVG-05736: The "{0}" command returned error "{1}"
-
Cause: An attempt to discover DHCP servers using specified command failed. The command returned error specified.
- PRVG-05737: The file "{0}" could not be copied to "{1}" on local node.
-
Cause: While attempting to discover Dynamic Host Configuration Protocol (DHCP) servers, the indicated source file could not be copied to the indicated destination file on the local node. Details are provided by the accompanying messages.
- PRVG-05738: The time to discover a DHCP server in the network, exceeded {0} seconds.
-
Cause: The pre-installation CVU verification of Dynamic Host Configuration Protocol (DHCP) service for the specified network failed to discover a DHCP server within the indicated time.
- PRVG-05740: Oracle Restart installed, requested check is not valid in this environment
-
Cause: A check invalid for the Oracle Restart environment was attempted.
- PRVG-05741: Oracle Restart installed, multiple nodes not valid in this environment
-
Cause: Multiple nodes were specified as part of the nodelist in an Oracle Restart configuration.
- PRVG-05745: CRS Configuration detected, Restart configuration check not valid in this environment
-
Cause: A check valid for the Oracle Restart configuration was attempted in a multi-node cluster environment.
- PRVG-05818: GNS resource is configured to listen on virtual IP address "{0}" for domain "{1}"
-
Cause: An attempt was made to run 'cluvfy comp dns' command against GNS resource configured to listen to specified domain at specified GNS-VIP while it was online.
- PRVG-05819: VIP address "{0}" is already in use
-
Cause: The identified VIP address was found to be active on the public network.
- PRVG-05820: Failed to retrieve IP address of host "{0}"
-
Cause: An attempt to retrieve an IP address for the indicated host failed.
- PRVG-05821: The subdomain delegation check was not performed as part of GNS check because it needs 'root' user privileges.
-
Cause: A Grid Naming Service (GNS) configuration with subdomain was found and the privilege delegation user and password were not provided.
- PRVG-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 at the indicated address and port failed.
- PRVG-05823: Name lookup for FQDN "{0}" failed.
-
Cause: An attempt to query the indicated domain name server (DNS) for the indicated Fully Qualified Domain Name (FQDN) failed.
- PRVG-05824: GNS resource is configured to listen on virtual IP address "{0}" without a forwarded domain.
-
Cause: An attempt was made to run the 'cluvfy comp dns' command against the Grid Naming Service (GNS) VIP configured at the indicated GNS-VIP while it was online.
- PRVG-05825: Subdomain delegation verification for the subdomain "{0}" failed.
-
Cause: An attempt to verify subdomain delegation for the indicated subdomain failed.
- PRVG-05830: None of the currently configured VIP addresses belong to the public subnet "{0}" on the network interface "{1}" of the node "{2}".
-
Cause: No VIP addresses were found on the indicated public subnet on the identified node.
- PRVG-05831: Public subnet "{0}" has no public IP address except active VIP addresses "{1}" on the node "{2}".
-
Cause: The identified public subnet did not have any additional IP address other than the configured VIP addresses active on the node.
- PRVG-05832: The subnets of VIPs "{0}" do not match the subnet "{1}" associated with their corresponding public network.
-
Cause: The Cluster Verification Utility (CVU) determined that the addresses of the indicated VIPs were not on the indicated subnet, which is the subnet of their associated public network interface.
- PRVG-05834: Failed to retrieve the configured VIP address information for network resource on each of the cluster nodes.
-
Cause: An attempt to retrieve the configured node VIP address information failed.
- PRVG-05835: failed to run srvctl command
-
Cause: An attempt to run srvctl command to get the network information failed. Specific details of the failure are included in the accompanying error messages.
- PRVG-05836: failed to retrieve the configured public network list information for the cluster
-
Cause: An attempt to retrieve the configured public network information failed. Specific details of the failure are included in the accompanying error messages.
- PRVG-05905: Windows firewall is enabled on nodes:
-
Cause: Windows firewall status was found to be enabled.
- PRVG-05906: Windows firewall is enabled on the node "{0}"
-
Cause: Windows firewall status was found to be enabled.
- PRVG-05907: Windows firewall status check cannot be performed on nodes:
-
Cause: An attempt to determine the status of Windows firewall failed.
- PRVG-05908: Windows firewall status check cannot be performed on node "{0}"
-
Cause: An attempt to determine the status of Windows firewall failed.
- PRVG-05909: Error reading key "{0}" from Windows Registry on node "{1}"
-
Cause: Specified Windows Registry key could not be read.
- PRVG-05910: Error reading value 'EnableFirewall' under key "{0}" for Windows firewall status on node "{1}"
-
Cause: Could not read Windows Registry value 'EnableFirewall' under specified key.
- PRVG-06000: OCR "{0}" is on raw or block device storage
-
Cause: An attempt was made to add OCR storage on a raw or block device.
- PRVG-06007: The OCR backup location "{0}" does not have enough space. [Expected="{1}" ; Found="{2}"]
-
Cause: Size of the OCR backup location was found to be insufficient.
- PRVG-06013: Failed to retrieve CRS active version from OCR dump on node "{0}"
-
Cause: An attempt to query the CRS active version key from OCR dump failed.
- PRVG-06014: Failed to parse OCR dump output: "{0}"
-
Cause: An attempt to parse OCR dump failed.
- PRVG-06015: Error retrieving output of OCR dump command on node "{0}"
-
Cause: Command 'ocrdump -stdout -xml' produced no output.
- PRVG-06016: Failed to retrieve the OCR backup location from node "{0}". Command "{1}" failed with errors.
-
Cause: An attempt to retrieve the backup location of OCR failed on indicated node.
- PRVG-06017: OCR backup is located in the same disk group "{0}" as OCR.
-
Cause: While checking OCR integrity, it was found that the OCR and its backup are located in the same disk group. It is recommended to locate the OCR backup in a different disk group from the OCR.
- PRVG-06020: failed to retrieve CRS active version from node "{0}"
-
Cause: An attempt to query the CRS active version from the CRS home on the indicated node failed.
- PRVG-06025: Voting disk "{0}" is on RAW or Block storage
-
Cause: An attempt was made to add voting disk storage on a raw or block device.
- PRVG-06056: Insufficient ASM instances found. Expected {0} but found {1}, on nodes "{2}".
-
Cause: Fewer than the configured ASM instance count were found running.
- PRVG-06057: Command "{0}" to check if ASM I/O server resource instances are running failed
-
Cause: An attempt to execute the displayed command failed.
- PRVG-06059: ASM I/O servers are not running on sufficient number of nodes. [Required= {0}; Found= {1}]
-
Cause: An attempt to verify that ASM I/O servers are running on sufficient number of nodes failed as they running on less number of nodes than I/O server count.
- PRVG-06061: ASM I/O servers running on nodes "{0}" are running on nodes that do not have an ASM instance
-
Cause: An attempt to determine if all ASM I/O server instances are running on nodes with ASM instances found that on nodes specified I/O servers were running but there were no ASM instances.
- PRVG-06062: ASM filter driver library is not loaded on nodes "{0}"
-
Cause: An attempt to check if ASM filter driver library was loaded failed on the nodes specified because the filter driver library was not loaded.
- PRVG-06063: Failed to check if the ASM filter driver library is installed on nodes "{0}"
-
Cause: An attempt to check if ASM filter driver library was loaded failed / on the nodes specified because the ASM filter driver status could not be determined.
- PRVG-06066: Failed to obtain the list of disks managed by ASM on nodes "{0}"
-
Cause: An attempt to obtain the list of disks managed by ASM on the specified nodes failed.
- PRVG-06067: The command "{0}" failed to run on nodes "{0}"
-
Cause: An attempt to obtain the list of disks managed by ASM filter driver failed on the nodes specified because the command could not be executed.
- PRVG-06068: The command "{0}" failed to produce any output on nodes "{0}"
-
Cause: An attempt to obtain the list of disks managed by ASM filter driver failed on the nodes specified because the command did not produce any output.
- PRVG-06069: The disks "{0}" are not managed by ASM filter driver on node "{1}".
-
Cause: The indicated disks were listed by the ASM filter driver on one or more nodes but were not listed by ASM filter driver on the indicated node.
- PRVG-06070: failed to execute command "{0}" on node "{1}"
-
Cause: An attempt to execute the specified command on the node specified failed.
- PRVG-06074: The ASM filter driver library is not installed on nodes "{0}".
-
Cause: The ASM filter driver library was not found installed on the indicated nodes.
- PRVG-06075: failed to check if the ASM filter driver library is loaded on nodes "{0}".
-
Cause: An attempt to check whether the ASM filter driver library was loaded failed on the nodes specified because the ASM filter driver status could not be determined.
- PRVG-06078: ASM filter driver library is not supported on current platform for this release "{0}".
-
Cause: The ASM filter driver library have not been ported for the indicated release on this OS platform.
- PRVG-06081: The disks "{0}" are not managed by ASM filter driver on node "{1}".
-
Cause: An attempt to verify that all disks that are managed by ASM are also managed by ASM filter driver failed because the specified disks were being managed by ASM but not by ASM filter driver.
- PRVG-06083: The disks "{0}" are not listed by ASM filter driver on node "{1}".
-
Cause: The CVU check for ASM filter driver configuration consistency determined that the indicated disks were listed by the ASM filter driver on one or more nodes but were not listed by ASM filter driver on the indicated node.
- PRVG-06084: The ASM parameter "cluster_database" does not have expected value. [Expected = "TRUE"] [Found = "FALSE"]
-
Cause: The Cluster Verification Utility determined that the indicated ASM parameter value did not have expected value.
- PRVG-06085: failed to retrieve the ASM parameter "{0}" value on the node "{1}"
-
Cause: An attempt to obtain the indicated ASM parameter value failed. The accompanying messages provide detailed failure information.
- PRVG-06090: ASM filter driver is installed on node "{0}" but is not supported by Oracle Clusterware release version "{1}" on the current operating system version.
-
Cause: The ASM filter driver was found installed, but was not supported on the current operating system version by the targeted Oracle Clusterware release.
- PRVG-06091: ASM filter driver is not supported on the current operating system version for Oracle Clusterware release version "{0}".
-
Cause: The ASM filter driver was not supported on the current operating system version for the targeted release.
- PRVG-06095: Oracle ACFS driver is installed on node "{0}" but is not supported by Oracle Clusterware release version "{1}" on the current operating system version.
-
Cause: The Oracle Automatic Storage Management Cluster File System (Oracle ACFS) driver was found installed, but was not supported on the current operating system version by the targeted Oracle Clusterware release.
- PRVG-06096: Oracle ACFS driver is not supported on the current operating system version for Oracle Clusterware release version "{0}".
-
Cause: The Oracle Automatic Storage Management Cluster File System (Oracle ACFS) driver was not supported on the current operating system version for the targeted release.
- PRVG-07040: Failed to get LV count for "{0}"
-
Cause: Could not get Logical Volume information for the device specified.
- PRVG-07050: No part of location "{0}" matches an existing path on node "{1}"
-
Cause: Neither the specified location nor any leading portion thereof matched existing file system paths on the indicated node.
- PRVG-07051: No part of location "{0}" matches an existing path with write permissions for current user on node "{1}"
-
Cause: Neither the specified location nor any leading portion thereof matched existing file system paths with write permissions on the indicated node.
- PRVG-07080: Failed to retrieve the 'srvctl' version on node "{0}", [{1}]
-
Cause: Could not get the version of 'srvctl' utility on the identified node.
- PRVG-07090: An internal error occurred within cluster verification fix up framework
-
Cause: An error occurred while performing the selected fix up operations.
- PRVG-07091: Unknown privilege delegation method specified
-
Cause: An unknown privilege delegation method was specified.
- PRVG-07092: User "{0}" does not have sufficient authorization 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.
- PRVG-07500: File "{0}" not found
-
Cause: The specified file was not found.
- PRVG-07501: An error occurred while parsing file "{0}"
-
Cause: An error occurred while parsing the document.
- PRVG-07503: An I/O error occurred while reading file "{0}"
-
Cause: An I/O error occurred while parsing the document.
- PRVG-07504: An internal error occurred while parsing file "{0}"
-
Cause: An internal error occurred while parsing the document.
- PRVG-07505: Failed to get group membership of user "{0}" on node "{1}"
-
Cause: An attempt to get the group membership of the user on the indicated node failed.
- PRVG-08000: Path "{0}" specified for the '-src_crshome' option is not a valid source CRS home.
-
Cause: The identified source CRS home was not found to be the configured CRS home.
- PRVG-08001: CRS home "{0}" is not a valid directory.
-
Cause: While attempting to determine the nodes on which to perform the verification operation, the Oracle Clusterware home discovered was not a valid directory.
- PRVG-08002: The required executable "olsnodes" is missing from the directory "{0}".
-
Cause: While attempting to determine the nodes on which to perform the verification operation, the 'olsnodes' executable was not found in the Oracle Clusterware home.
- PRVG-08003: Unable to retrieve node list from the Oracle Clusterware.
-
Cause: While attempting to determine the nodes on which to perform the verification operation, the nodes that belonged to the cluster could not be obtained from the Oracle Clusterware.
- PRVG-09001: Failed to read input from command line standard input
-
Cause: Failed to read the response from standard input.
- PRVG-09003: Failed to read the "{0}" user credentials
-
Cause: Failed to read the response from standard input.
- PRVG-09015: Failed to execute command "{0}" using "{1}" credentials on node "{2}" with error "{3}"
-
Cause: An attempt to execute the command with the credentials provided for the identified user across all the nodes failed.
- PRVG-09016: failed with an error "{0}" on node "{1}"
-
Cause: An operating system error occurred while executing the fix up on the specified node.
- PRVG-09018: Privilege delegation method and credentials are not specified
-
Cause: The privilege delegation method and credentials were not specified.
- PRVG-09019: Copying required fix up files to directory "{0}" failed on all nodes
-
Cause: An attempt to copy fix up files to the indicated directory failed on all cluster nodes.
- PRVG-09020: Executable file "{0}" not found on node "{1}"
-
Cause: Indicated executable file was not found at the indicated path on the identified node.
- PRVG-09021: File "{0}" not found on nodes "{1}"
-
Cause: Indicated file was not found at the indicated path on the identified nodes.
- PRVG-09023: Manual fix up command "{0}" was not issued by root user on node "{1}"
-
Cause: The indicated manual command to perform a fix up action was either not issued or was issued by an user other than root.
- PRVG-09025: Failed to update the value of parameter "{0}" in configuration file "{1}" on node "{2}"
-
Cause: An attempt to update the value of indicated parameter in the configuration file on the identified node failed.
- PRVG-09026: Failed to adjust the value of parameter "{0}" using command "{1}" on node "{2}"
-
Cause: An attempt to update the system parameter value using indicated command failed on the indicated node.
- PRVG-09027: Failed to retrieve the current value of parameter "{0}" using command "{1}" on node "{2}"
-
Cause: An attempt to retrieve the current value of indicated system parameter using identified command failed on the indicated node.
- PRVG-09028: Failed to set an environment variable "{0}" on node "{1}"
-
Cause: An attempt to set an environment variable failed on indicated node.
- PRVG-09030: Failed to open configuration file "{0}" on node "{1}"
-
Cause: An attempt to open the indicated file for read and write operations failed on the indicated node.
- PRVG-09031: Missing required data in fix up data file.
-
Cause: An internal error occurred while performing the selected fix up operations.
- PRVG-09032: Failed to create new user "{0}" on node "{1}", command "{2}" failed with error {3}
-
Cause: An attempt to add specified new user failed on the indicated node.
- PRVG-09033: Failed to create new group "{0}" on node "{1}"
-
Cause: An attempt to add specified new group failed on the indicated node.
- PRVG-09034: User "{0}" does not exist on node "{1}"
-
Cause: The specified user name was not known to the operating system on the indicated node.
- PRVG-09035: Group "{0}" does not exist on node "{1}"
-
Cause: The specified group name was not known to the operating system on the indicated node.
- PRVG-09036: Failed to add user "{0}" to group "{1}" on node "{2}"
-
Cause: An attempt to add the indicated user to the group failed on the specified node.
- PRVG-09037: Failed to get the list of groups for user "{0}" on node "{1}"
-
Cause: An attempt to retrieve the operating system groups to which the specified user belongs failed on the indicated node.
- PRVG-09038: Failed to modify user "{0}" user ID to "{1}" on node "{2}"
-
Cause: An attempt to modify identified user's ID failed on the indicated node.
- PRVG-09039: Failed to modify group "{0}" group ID to "{1}" on node "{2}"
-
Cause: An attempt to modify identified group's ID failed on the indicated node.
- PRVG-09040: Failed to get available unique user ID from nodes "{0}"
-
Cause: An attempt to retrieve an unused unique user ID from the indicated nodes failed.
- PRVG-09041: Failed to get available unique group ID from nodes "{0}"
-
Cause: An attempt to retrieve an unused unique group ID from the indicated nodes failed.
- PRVG-09042: Failed to get available user ID from node "{0}"
-
Cause: An attempt to retrieve an unused user ID from the indicated node failed.
- PRVG-09043: Failed to get available group ID from node "{0}"
-
Cause: An attempt to retrieve an unused group ID from the indicated node failed.
- PRVG-09044: Failed to adjust the 'runlevel' value in file "{0}" on node "{1}"
-
Cause: An attempt to adjust the 'runlevel' value in entry inside the indicated file failed on the specified node.
- PRVG-09045: Failed to install the package "{0}" from source location "{1}" on node "{2}"
-
Cause: An attempt to install the indicated package failed on the identified node.
- PRVG-09046: Fix up for this verification failure is not supported
-
Cause: An internal error occurred while performing the selected fix up operations.
- PRVG-09047: Fix up initial framework setup is not performed, cannot perform fix up operations
-
Cause: An internal error occurred while performing the selected fix up operations.
- PRVG-09048: Fix up is not supported for Operating System parameter "{0}"
-
Cause: An internal error occurred while performing the selected fix up operations.
- PRVG-09049: Failed to create home directory at path "{0}" for newly created user "{1}" on node "{2}"
-
Cause: An attempt to create the home directory at the indicated path failed for the newly created user on the indicated node.
- PRVG-09050: Failed to determine the Operating System version on node "{0}"
-
Cause: An attempt to retrieve the operating system version failed on the identified node.
- PRVG-09051: Fix up is not supported for the Operating System parameter "{0}" on current version of the Operating System on node "{1}"
-
Cause: A fix up operation was requested for an Operating System version that does not support that operation.
- PRVG-09052: Failed to adjust the value of parameter "{0}" using operating system function call "{1}" on node "{2}" with error \n{3}
-
Cause: An attempt to update the system parameter value using the indicated system call failed on the indicated node.
- PRVG-09053: Failed to retrieve the current value of parameter "{0}" using operating system function call "{1}" on node "{2}" with error \n{3}
-
Cause: An attempt to retrieve the current value of the indicated system parameter using the identified operating system function call failed on the indicated node.
- PRVG-09054: failed to set the 'runlevel' target "{0}" using command "{1}" on node "{2}" with error \n{3}
-
Cause: An attempt to set the indicated 'runlevel' target failed on the indicated node.
- PRVG-09055: Failed to verify the existence of Solaris Project name "{0}" on node "{1}"
-
Cause: An attempt to check the existence of the indicated Solaris Projects failed on the identified node.
- PRVG-09056: Failed to create the Solaris Project "{0}" for Oracle user on node "{1}"
-
Cause: An attempt to create the indicated Solaris Projects for Oracle user failed on the identified node.
- PRVG-09057: Failed to retrieve the home directory of user "{0}" on node "{1}"
-
Cause: An attempt to retrieve the home directory of the identified user failed on the indicated node.
- PRVG-09059: Failed to update the IOCP device status to "Available" using command "{0}" on node "{1}". Detailed error: {2}
-
Cause: An attempt to update the status of an I/O Completion Port (IOCP) to 'Available' on the indicated node failed. The accompanying messages provide detailed failure information.
- PRVG-09060: Fix up is not supported for daemon or process "{0}"
-
Cause: An unsupported daemon or process was requested for fix up.
- PRVG-09061: Daemon or process "{0}" could not be stopped on node "{1}", command "{2}" failed with error: {3}
-
Cause: An attempt to stop the indicated daemon or process failed on the identified node.
- PRVG-09062: Daemon or process "{0}" could not be stopped permanently on node "{1}", command "{2}" failed with error: {3}
-
Cause: An attempt to permanently stop the indicated daemon or process failed on the identified node.
- PRVG-09063: Daemon or process "{0}" is not running on node "{1}"
-
Cause: Indicated daemon or process was not found running on the identified node.
- PRVG-09064: Failed to restart the ASMLib driver on node "{0}" using command "{1}". Detailed error: {2}
-
Cause: An attempt to restart the ASMLib driver failed on the identified node.
- PRVG-09065: Failed to retrieve the unpinned nodes using OLSNODES command "{0}" on node "{1}". Detailed error: {2}
-
Cause: An attempt to determine the pinned status of the cluster nodes using an OLSNODES command failed on the indicated node.
- PRVG-09066: Failed to pin the nodes "{0}" using CRSCTL command "{1}" on node "{2}". Detailed error: {3}
-
Cause: An attempt to pin the specified nodes using a CRSCTL command failed on the indicated node.
- PRVG-09067: Huge page support is not enabled for Linux kernel on node "{0}".
-
Cause: Huge pages support was not found configured for the Linux kernel on indicated node.
- PRVG-09068: Failed to determine the recommended value for huge pages on node "{0}".
-
Cause: An attempt to calculate the recommended value for huge pages failed on the indicated node.
- PRVG-09070: Failed to update the settings of device file "{0}" using command "{1}" on node "{2}". Detailed error: {3}
-
Cause: An attempt to update the major and minor number of the indicated device file failed with the indicated error.
- PRVG-09071: Failed to start the daemon "{0}" using command "{1}" on node "{2}". Detailed error: {3}
-
Cause: An attempt to start the identified daemon failed on the indicated node. Further details are supplied in the additional messages included.
- PRVG-09072: failed to disable the resource "{0}" using srvctl command "{1}" on node "{2}". Detailed error: {3}
-
Cause: An attempt to disable the identified resource failed on the indicated node. See included messages for details.
- PRVG-09073: failed to stop the resource "{0}" using srvctl command "{1}" on node "{2}". Detailed error: {3}
-
Cause: An attempt to stop the identified resource failed on the indicated node. See included messages for details.
- PRVG-09074: failed to get the resource "{0}" status using srvctl command "{1}" on node "{2}". Detailed error: {3}
-
Cause: An attempt to determine the identified resource status on the indicated node. See included messages for details.
- PRVG-09075: failed to grant privilege "{0}" to user "{1}" on node "{2}"
-
Cause: The Automatically generated fix-up script to grant the operating system privilege 'dax_access' to the indicated user failed on the indicated node.
- PRVG-09076: Failure to determine the user's home directory on node "{0}". Operation failed with error "{1}".
-
Cause: An attempt to retrieve the user's home directory failed on the indicated node. The accompanying messages provide detailed information about the failure.
- PRVG-09077: Unable to create the directory "{0}" on node "{1}". Operation failed with error "{2}"
-
Cause: An attempt by the Cluster Verification Utility (CVU) to create the indicated directory failed on the indicated node. The accompanying messages provide detailed information about the failure.
- PRVG-09078: Failure to generate the SSH keys on node "{0}". Command "{1}" failed with error "{2}".
-
Cause: An attempt to generate SSH keys using the indicated command failed on the indicated node because of the indicated error.
- PRVG-09079: Failure to update the SSH agent with the SSH keys on node "{0}". Command "{1}" failed with error "{2}".
-
Cause: An attempt to update the SSH agent with the SSH keys by issuing the indicated command failed on the indicated node because of the indicated error.
- PRVG-09080: Failure to open file "{0}" to read on node "{1}". Operation failed with error "{2}".
-
Cause: An attempt to read the indicated file failed on the indicated node because of the indicated error.
- PRVG-09081: Failure to write to file "{0}" on node "{1}". Operation failed with error "{2}".
-
Cause: An attempt to write content to the indicated file failed on the indicated node because of the indicated error.
- PRVG-09082: Failure to create file "{0}" on node "{1}". Operation failed with error "{2}".
-
Cause: An attempt to create the indicated file failed on the indicated node because of the indicated error.
- PRVG-09083: Failure to update the permissions for file "{0}" to "{1}" on node "{2}". Operation failed with error "{4}".
-
Cause: An attempt to update the permissions of the indicated file on the indicated node failed because of the indicated error.
- PRVG-09084: failure to connect to nodes "{0}" using SSH with specified credentials for user "{1}"
-
Cause: An attempt to connect to the indicated node using SSH with specified credentials for the indicated user failed. The accompanying messages provide detailed failure information.
- PRVG-09085: failure to set up the fix-up work directory "{0}" on node "{1}"
-
Cause: An attempt to set up the indicated work directory failed on the indicated node. The accompanying messages provide detailed failure information.
- PRVG-09086: failure to connect to node "{0}" using secure FTP with specified credentials for user "{1}"
-
Cause: An attempt to connect using secure FTP to the indicated node using specified credentials for the indicated user failed. The accompanying messages provide detailed failure information.
- PRVG-09087: Failure to rename the file "{0}" to "{1}" on node "{2}". Operation failed with error "{3}".
-
Cause: An attempt to rename the indicated file on the indicated node failed because of the indicated error.
- PRVG-09088: Failure to set up the SSH user equivalence for specified user "{0}" on nodes "{1}". Operation failed with error "{2}".
-
Cause: An attempt to set up SSH user equivalence for the specified user on the indicated nodes failed because of the indicated error.
- PRVG-09093: Failed to remove the RPM database files from directory "{0}" on node "{1}". The operation failed with the error : {2}
-
Cause: An attempt by the Cluster Verification Utility (CVU) fix up operation to remove the RPM database files from the indicated directory on the indicated node failed.
- PRVG-09094: Failed to rebuild the RPM database using command "{0}" on node "{1}". The operation failed with the error : {2}
-
Cause: An attempt by the Cluster Verification Utility (CVU) fix up operation to rebuild the RPM database on the indicated node failed.
- PRVG-09095: Failed to update the SELinux context type for file "{0}" to "{1}" on node "{2}". Operation failed with error "{3}".
-
Cause: An attempt to update the SElinux context type of the indicated file on the indicated node failed because of the indicated error.
- PRVG-10005: unable to determine local host name
-
Cause: The host name could not be determined.
- PRVG-10006: APPVIP type needs a VIP name. Specify a VIP name using -vip command line option.
-
Cause: VIP resource name was missing in the command line for APPVIP type.
- PRVG-10008: unable to generate client ID for VIP type "{0}", cluster name "{1}", VIP resource name "{2}"
-
Cause: An attempt to generate client ID for the specified cluster name, VIP type and resource name failed.
- PRVG-10010: unable to discover DHCP server in the network listening on port "{0}" for client ID "{1}"
-
Cause: An attempt to discover DHCP server listening on port specified failed.
- PRVG-10011: unable to request DHCP lease for client ID "{0}" on port "{1}"
-
Cause: An attempt to request DHCP lease for the specified client ID on specified port failed.
- PRVG-10013: unable to release DHCP lease for client ID "{0}", on port "{1}"
-
Cause: An attempt to release DHCP lease for the specified client ID on specified port failed.
- PRVG-10014: HOSTVIP type needs a node name. Specify a node name using -n option.
-
Cause: Node name was missing in the command line for HOSTVIP type.
- PRVG-10015: VIP type "{0}" is invalid
-
Cause: An invalid VIP type was specified for DHCP client ID generation.
- PRVG-10035: Invalid name server "{0}" used to resolve IP addresses.
-
Cause: An invalid name server was used or specified in /etc/resolv.conf.
- PRVG-10036: value for command line parameter "{0}" is not an integer
-
Cause: An invalid value was specified for the specified command line parameter.
- PRVG-10039: invalid subnet "{0}" specified
-
Cause: An invalid IPv4 or IPv6 subnet was supplied on the command line.
- PRVG-10040: unable to get list of network interfaces
-
Cause: An attempt to retrieve the list of network interfaces failed.
- PRVG-10041: subnet "{0}" is not configured on the node
-
Cause: The subnet specified did not match subnet of any network interface on this node.
- PRVG-10044: invalid cluster name "{0}" specified
-
Cause: An invalid cluster name was supplied on the command line.
- PRVG-10045: invalid node name "{0}" specified
-
Cause: An invalid node name was supplied on the command line.
- PRVG-10048: Name "{0}" was not resolved to an address of the specified type by name servers "{1}".
-
Cause: An attempt to look up an address of a specified type for the indicated name using the name servers shown did not yield any addresses of the requested type.
- PRVG-10090: could not retrieve ASM password file location
-
Cause: An attempt to execute an internal 'cvuhelper' command failed to produce any output while retrieving the ASM password file location. This is an internal error.
- PRVG-10091: failed to retrieve the ASM password file location for ASM
-
Cause: An attempt to retrieve the password file location for ASM failed while verifying this file is on an ASM disk group. Possibly no ASM password file was configured.
- PRVG-10092: could not retrieve ASM password backup file location
-
Cause: An attempt to execute internal 'cvuhelper' command failed to produce any output while retrieving the ASM password backup file location. This is an internal error.
- PRVG-10093: failed to retrieve the ASM password backup file location.
-
Cause: An attempt to retrieve the Oracle ASM password backup file location for Oracle ASM failed, while verifying this file on an Oracle ASM disk group. Possibly, no Oracle ASM password backup file was configured.
- PRVG-10120: Failed to access ASMLib configuration file on the node "{0}"
-
Cause: ASMLib configuration file '/etc/sysconfig/oracleasm-_dev_oracleasm' or link '/etc/sysconfig/oracleasm' was not found or cannot be accessed on the indicated node.
- PRVG-10121: Failed to retrieve ASMLib configuration value from ASMLib configuration file "{0}" on the node "{1}"
-
Cause: The check for ASMLib configuration was unable to retrieve the required information from specified configuration file on the indicated node.
- PRVG-10122: ASMLib configuration value set to configuration parameter "{0}" on the node "{1}" does not match with cluster nodes
-
Cause: The ASMLib configuration check found inconsistent settings across cluster nodes.
- PRVG-10123: ASMLib command utility is absent at path "{0}" on the nodes "{1}"
-
Cause: ASMLib command utility was absent at the identified file system path on the indicated nodes.
- PRVG-10130: Unable to determine whether file path "{0}" is shared by nodes "{1}"
-
Cause: An attempt to determine whether the file path is shared across nodes failed.
- PRVG-10400: The Windows Time service "W32Time" setting "{0}" in the Windows registry key "HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\W32Time\\Config" is greater than the value recommended by Oracle. [Recommended = "{1}"] on nodes: "{2}"
-
Cause: The indicated Windows Time service setting in the indicated registry key was greater than the value recommended by Oracle.
- PRVG-10401: The Windows Time service "W32Time" setting "{0}" in the Windows registry key "HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\W32Time\\Config" is not found. [Recommended value = "{1}"] on nodes:"{2}"
-
Cause: The indicated Windows Time service setting in the indicated registry key was not found in the specified node.
- PRVG-10402: The Windows Time service "W32Time" settings in the Windows registry key "HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\W32Time\\Config" do not match the values recommended by Oracle.
-
Cause: The specified Windows Time service settings in the specified registry key were not found or do not match the value recommended by Oracle.
- PRVG-10403: More than one time synchronization service was running on nodes of the cluster. Only one should be active on all the nodes at any given time.
-
Cause: A check to determine whether the time synchronization services were running on nodes of the cluster found that more than one was active.
- PRVG-10404: The network time synchronization service with the name "{0}" is not running on nodes: "{1}"
-
Cause: A check to determine whether the indicated network time synchronization service was running on nodes of the cluster found that it was not running on the indicated nodes.
- PRVG-10405: Service check cannot be performed for service "{0}" on nodes: "{1}"
-
Cause: An error was encountered while trying to determine if the identified service was running on the specified nodes.
- PRVG-10408: A verified network time synchronization service was not running on all of the cluster nodes. A single verified network time synchronization service should be active on all the nodes at any given time.
-
Cause: A check to determine whether the network time synchronization services were running on nodes of the cluster found that none was active on any of the cluster nodes.
- PRVG-10409: The network time synchronization service "{0}" is not installed on nodes: "{1}"
-
Cause: A check to determine whether the indicated network time synchronization service was running on nodes of the cluster found that that service was not installed on the indicated nodes.
- PRVG-10430: failed to retrieve the default gateway address on node "{0}".
-
Cause: The default gateway address was not configured on the specified node.
- PRVG-10450: The device specified by path "{0}" is a block device, which is not supported on the current platform.
-
Cause: An attempt to obtain storage information for a device identified by the indicated path was rejected because the path identified a block device and only character devices were supported on the current platform.
- PRVG-10451: failed to retrieve the NFS mount point information for the mount point "{1}" due to timeout after "{2}" seconds
-
Cause: The cluster verification operation failed because an attempt to retrieve the file system information for the NFS storage at the indicated mount point timed out.
- PRVG-10460: User "{0}" does not belong to group "{1}" selected for privileges "{2}" on node "{3}".
-
Cause: While performing prerequisite checks, Cluster Verification Utility (CVU) checked group membership for the indicated user and found that the indicated user was not a member of the indicated group selected for the indicated privileges on the indicated node.
- PRVG-10461: Group "{0}" selected for privileges "{1}" does not exist on node "{2}".
-
Cause: While performing prerequisite checks, Cluster Verification Utility (CVU) checked for the existence of the indicated group and found that the indicated group selected for the indicated privileges did not exist on the indicated node.
- PRVG-10464: The user "{0}" does not have sufficient privileges to access the Oracle Automatic Storage Management (Oracle ASM) devices on nodes "{1}".
-
Cause: While performing database prerequisite checks, the Cluster Verification Utility (CVU) checked for the granted privileges of the indicated user and found that the indicated user was not a member of the OSDBA group configured in the Grid Infrastructure home and therefore did not have privileges to access the Oracle Automatic Storage Management (Oracle ASM) devices on the indicated nodes.
- PRVG-10466: Failed to determine cluster node roles. Verification will proceed considering nodes "{0}" as hub nodes.
-
Cause: An attempt to determine cluster node roles failed because CRS was not found running on the local node. Since the verification checks were carried out assuming the indicated nodes were hub nodes, the final results were valid only if the nodes were, in fact, Hub nodes.
- PRVG-10467: The default Oracle Inventory group could not be determined.
-
Cause: An attempted Cluster Verification Utility (CVU) validation check failed because either the Oracle Inventory group could not be read from the inventory configuration file or the primary group could not be retrieved. This occurred because either the file did not exist, the property was not found, or the primary group was not found in the /etc/group file. Detailed failure information is provided in the accompanying error messages.
- PRVG-10468: unable to read the configured Oracle Inventory group
-
Cause: Reading from the inventory configuration file failed. Detailed failure information, including the attempted read location, is provided in the accompanying error messages.
- PRVG-10472: The CLASS/TYPE attribute configured on the PUBLIC network interfaces "{0}" is set to an unsupported value 'inherited' on nodes "{1}".
-
Cause: While performing Oracle Grid Infrastructure prerequisite checks, the Cluster Verification Utility (CVU) checked for the network interface attribute CLASS/TYPE configured on the indicated PUBLIC network interfaces and found that the indicated attribute is set to an unsupported value 'inherited' on the indicated nodes.
- PRVG-10487: Storage "{0}" is not shared on all nodes.
-
Cause: The indicated storage was not shared across the nodes.
- PRVG-10488: Error attempting to obtain the OSASM group from CRS home "{0}"
-
Cause: An attempt to obtain the OSASM group failed. The accompanying error messages provide detailed failure information.
- PRVG-10489: Database user OS group is recommended to be different from the OSASM group "{0}"
-
Cause: The OSASM group was found to be the same as the current user OS group. It is recommended that SYSDBA and SYSASM privileges be separate.
- PRVG-10490: The ASM Filter Driver is not available.
-
Cause: An attempt to resolve a label to a disk failed because the ASM Filter Driver (AFD) was not available. The accompanying messages provide detailed failure information.
- PRVG-10491: The AFD did not recognize the disk label "{0}".
-
Cause: An attempt to find a disk with the specified label was rejected because the ASM Filter Driver (AFD) did not recognize the label.
- PRVG-10496: invalid or missing root element in the XML file "{0}"
-
Cause: File validity checking determined that the indicated XML file was not valid because the root element was invalid or missing.
- PRVG-10497: zero or multiple({0}) system elements specified in XML file "{1}"
-
Cause: File validity checking determined that the indicated XML file was not valid because it contained zero or multiple system elements.
- PRVG-10501: Check of hostname length could not be performed on node "{0}"
-
Cause: The length of the host name could not be retrieved on the node indicated.
- PRVG-10502: The length of the host name was greater than 8 characters on node "{0}"
-
Cause: Length of the hostname should be less than or equal to 8 characters or pre-11gR2 Database releases may not run properly.
- PRVG-10507: CVU found an invalid host name "{0}" which resolves to a loopback address on node "{1}".
-
Cause: The Cluster Verification Utility (CVU) determined that the indicated host name resolved to a loopback address on the indicated node.
- PRVG-10510: User "{0}" is not a domain user, domain name absent
-
Cause: Could not identify domain name of current user.
- PRVG-10511: failed to retrieve the host name using command "{0}" on node "{1}"
-
Cause: An error occurred while retrieving the host name using the indicated command on the indicated node. The accompanying messages provide detailed failure information.
- PRVG-10520: ASM disk label "{0}" did not resolve to any device path on node "{1}"
-
Cause: ASM disk label could not be resolved to any device on specified node.
- PRVG-10521: Failed to resolve ASM disk label "{0}" to device path on node "{1}"
-
Cause: Failed to resolve ASM disk label to any device on specified node.
- PRVG-10523: Disk "{0}" is not identified by ASMLib.
-
Cause: The indicated disk was not identified by ASMLib.
- PRVG-10524: failed to determine whether disk "{0}" is managed by ASMLib
-
Cause: An attempt to validate whether the indicated disk was managed by ASMLib failed.
- PRVG-10530: Internal error: {0}
-
Cause: An internal error occurred. The included value is an internal identifier.
- PRVG-10540: OCR location "{0}" is not located on Oracle ASM storage
-
Cause: An attempt was made to add Oracle Cluster Repository (OCR) storage on a device that is not managed by Oracle Automatic Storage Management (Oracle ASM). All OCR storage must be located on Oracle ASM storage.
- PRVG-10541: Voting disk "{0}" is not located on Oracle ASM storage
-
Cause: An attempt was made to add voting disk storage on a device that is not managed by Oracle Automatic Storage Management (Oracle ASM). All voting disk storage must be located on Oracle ASM.
- PRVG-10605: Release version [{0}] is consistent across nodes but does not match the active version [{1}].
-
Cause: During pre-upgrade validation, the Clusterware release version was consistent but did not match the active version. Usually this results from a failed upgrade.
- PRVG-10606: Release versions [{0}] are inconsistent across nodes.
-
Cause: Inconsistent release versions were found on two or more nodes. This might be caused by an upgrade in progress.
- PRVG-10705: Database version "{0}" is not compatible with the Clusterware version "{1}".
-
Cause: Clusterware version has to be equal to or greater than the database version.
- PRVG-10952: Check for consistency of root users primary group failed on the following nodes: "{0}"
-
Cause: The primary group and group id of the root user was not consistent across all the nodes.
- PRVG-10953: Check for consistency of root users primary group had a command failure on the following nodes: "{0}"
-
Cause: An OS command issued while checking user group information failed unexpectedly.
- PRVG-10958: Check for consistency of root users primary group "{0}" on node: "{1}" failed. The group membership of root user for group "{2}" does not exist on the following nodes: "{3}"
-
Cause: The indicated primary group and group id of the root user was not found in the existing membership groups of the root users on the identified nodes.
- PRVG-10959: Check for consistency of root users primary group had a command failure on the following node: "{0}"
-
Cause: An OS command issued while checking user group information failed unexpectedly.
- PRVG-11000: Invalid usage of CVU internal function
-
Cause: This is an internal error.
- PRVG-11001: Failed to execute command "{0}" on node "{1}"
-
Cause: An error occurred while executing the command.
- PRVG-11003: SCAN is not configured
-
Cause: An attempt to retrieve SCAN failed.
- PRVG-11004: SCAN listener is not configured
-
Cause: An attempt to retrieve SCAN listener configuration failed.
- PRVG-11005: Database "{0}" is not defined in this cluster
-
Cause: An attempt to retrieve cluster-specific metadata about the database failed.
- PRVG-11006: VIPs are not defined for the nodes on which database "{0}" is running
-
Cause: An attempt to retrieve the VIP on which the indicated database is running failed.
- PRVG-11007: No instances are defined for database "{0}"
-
Cause: An attempt to retrieve database instances for the database failed.
- PRVG-11008: An internal command "cvuhelper" returned "{0}" while fetching the node list for database unique name "{1}".
-
Cause: An attempt to execute an internal cvuhelper command failed.
- PRVG-11009: An internal command "cvuhelper" exited unexpectedly while fetching the node list for database "{0}".
-
Cause: An attempt to execute an internal cvuhelper command exited unexpectedly.
- PRVG-11010: An internal command 'cvuhelper' returned "{0}" while fetching cluster databases.
-
Cause: An attempt to execute an internal cvuhelper command failed.
- PRVG-11011: An internal command 'cvuhelper' exited unexpectedly while fetching cluster databases.
-
Cause: An attempt to execute an internal cvuhelper command failed.
- PRVG-11049: Interface "{0}" does not exist on nodes "{1}"
-
Cause: The interface was classified as cluster interconnect or public but the interface was not found on the nodes.
- PRVG-11050: No matching interfaces "{0}" for subnet "{1}" on nodes "{2}"
-
Cause: The interfaces classified as cluster interconnect or public were not found on the specified subnet on the nodes.
- PRVG-11051: network list is in invalid format
-
Cause: The processing of a network list argument encountered a syntax error.
- PRVG-11052: Interface name is not enclosed within double quotes
-
Cause: Interface name in the interface list was not enclosed within double quotes.
- PRVG-11053: Invalid subnet type
-
Cause: Invalid subnet type was specified in interface list.
- PRVG-11054: Interface "{0}" not found on this node
-
Cause: Failed to locate the interface on this node.
- PRVG-11055: Interfaces configured with subnet "{0}" have multiple subnet masks.
-
Cause: Cluster Verification Utility (CVU) check determined that interfaces of some nodes were configured with different subnet masks for the same subnet number.
- PRVG-11056: Subnet "{0}" has different subnet masks "{1}" on nodes "{2}".
-
Cause: Cluster Verification Utility (CVU) check determined that interfaces on the indicated ` subnet did not have the same subnet mask, which would result in routing conflicts.
- PRVG-11057: Checking subnet mask consistency...
-
Cause: NO
- PRVG-11058: Subnet mask consistency check passed.
-
Cause: NO
- PRVG-11059: Subnet mask consistency check passed for subnet "{0}".
-
Cause: NO
- PRVG-11060: Subnet mask consistency check failed.
-
Cause: NO
- PRVG-11061: Different MTU values used across cluster interconnect network interfaces "{0}" on subnets "{1}" with MTU values "{2}" on the node "{3}". The most common MTU value is "{4}".
-
Cause: Cluster Verification Utility (CVU) connectivity checking determined that the indicated interfaces on the indicated subnets were configured with different maximum transmission units (MTU) values.
- PRVG-11065: Node connectivity checks will not be performed on network interfaces "{0}" on node "{1}" because they were down.
-
Cause: The indicated network interfaces on the indicated nodes were not considered for node connectivity checks because they were down.
- PRVG-11067: TCP connectivity from node "{0}": "{1}" to node "{2}": "{3}" failed.
-
Cause: Errors occurred while attempting to establish Transmission Control Protocol (TCP) connectivity between the two identified interfaces.
- PRVG-11068: Highly Available IP (HAIP) is enabled on the nodes "{0}".
-
Cause: The Cluster Verification Utility (CVU) found that the HAIP was enabled on the indicated nodes. HAIP is not supported on Exadata for Oracle Clusterware 18c release onwards.
- PRVG-11069: IP address "{0}" of network interface "{1}" on the node "{2}" would conflict with HAIP usage.
-
Cause: One or more network interfaces have IP addresses in the range (169.254.*.*), the range used by HAIP which can create routing conflicts.
- PRVG-11070: IP address "{0}" of non-private network interface "{1}" on the node "{2}" would conflict with HAIP usage.
-
Cause: One or more non-private network interfaces have IP addresses in the range (169.254.*.*), the range used by HAIP which can create routing conflicts.
- PRVG-11071: IP address "{0}" of private network interface "{1}" on the node "{2}" with subnet mask "{3}" would conflict with HAIP usage.
-
Cause: One or more private network interfaces have IP addresses in the range (169.254.*.*) and subnet mask which is not 16-18 bits, the range used by HAIP which can create routing conflicts
- PRVG-11072: Private network Interface "{0}" on node "{1}" with IP address "{2}" is not Infiniband.
-
Cause: One or more private network interfaces on the system were not Infiniband. In an Exadata environment, if private interfaces are not Infiniband, connection failures will result.
- PRVG-11073: Subnet on interface "{0}" of node "{1}" is overlapping with the subnet on interface "{2}". IP address range ["{3}"-"{4}"] is overlapping with IP address range ["{5}"-"{6}"].
-
Cause: IP ranges were overlapping on one or more subnets. This would result in routing failures.
- PRVG-11074: Private network interface "{0}" on node "{1}" with IP address "{2}" does not have MONITOR option set.
-
Cause: One or more private network interfaces on the system did not have the MONITOR option in the interface information. This may lead to network failures if the interfaces are disabled or disconnected.
- PRVG-11076: Found deprecated interfaces "{0}" with corresponding IP addresses "{1}" on the following nodes: "{2}". These interfaces will be skipped for node connectivity checks.
-
Cause: Cluster Verification Utility (CVU) connectivity checking determined that there were interfaces which had the DEPRECATED flag set in the interface information. These deprecated interfaces will not be considered for node connectivity checks.
- PRVG-11077: Different MTU values used across the network for interfaces "{0}" on subnets "{1}" with MTU values "{2}" on the node "{3}". The most common MTU value is "{4}".
-
Cause: Cluster Verification Utility (CVU) connectivity checking determined that there were different maximum transmission unit (MTU) values found on non-private or unclassified interfaces on the indicated subnets.
- PRVG-11078: node connectivity failed for subnet "{0}"
-
Cause: Node connectivity checks for the specified subnet failed.
- PRVG-11079: Subnet value "{1}" of interface "{2}" is invalid on node "{3}".
-
Cause: Cluster Verification Utility (CVU) connectivity checking determined that the subnet attribute had an invalid value on the indicated node for the indicated interface.
- PRVG-11080: empty or null value in the interface field on node "{1}"
-
Cause: An internal error occurred.
- PRVG-11081: unable to find the matching networks for the interface "{0}" and the subnet "{1}" on nodes "{2}"
-
Cause: Cluster Verification Utility (CVU) connectivity checking determined that the interface-subnet combination was not found on the indicated nodes.
- PRVG-11086: could not find any network interface having status as UP on the nodes "{0}"
-
Cause: Cluster Verification Utility (CVU) connectivity checking determined that the indicated nodes did not have any network interface with status UP
- PRVG-11087: Invalid subnet "{0}" was specified in the interconnect list for the interface "{1}". This interface will not be included in further checks.
-
Cause: Cluster Verification Utility (CVU) connectivity checking determined that an invalid IPv4 or IPv6 subnet was supplied on the command line or in the CVU variable.
- PRVG-11088: Interface "{0}" has invalid value "{1}" for the network attribute "{2}" on the node "{3}".
-
Cause: An internal error occurred while performing the node connectivity checks.
- PRVG-11089: Could not find a valid network entry in the interconnect list.
-
Cause: Cluster Verification Utility (CVU) connectivity checking determined that the specified interconnect list did not have a valid network to be considered for the connectivity checks. This could be due to invalid values supplied for one or more interface names, subnets or network types in the interconnect list.
- PRVG-11090: returned network interface list empty on nodes "{0}"
-
Cause: Cluster Verification Utility (CVU) node connectivity check determined that network interfaces discovery returned an empty list. This may indicate a configuration problem or an internal error with the remote check.
- PRVG-11091: Copying directory "{0}" contents from the local node to the remote nodes "{1}" failed.
-
Cause: Cluster Verification Utility (CVU) framework setup checking determined that the remote execution files from the local node could not be copied to the indicated directory on the indicated remote nodes.
- PRVG-11092: Deleting directory "{0}" contents failed on nodes "{1}".
-
Cause: Cluster Verification Utility (CVU) framework setup checking determined that the remote execution files in the indicated directory on the indicated nodes could not be deleted.
- PRVG-11093: The file "{0}" from the node "{1}" could not be copied to "{2}" on the local node.
-
Cause: Cluster Verification Utility (CVU) framework node connectivity checking determined that the indicated ping command output file from the indicated node could not be copied to the local node for processing. The accompanying messages provide detailed information about the failure.
- PRVG-11094: Ping connectivity check from the source IP address "{0}" to the destination IP address "{1}" failed.
-
Cause: Cluster Verification Utility (CVU) framework node connectivity checking determined that ping connectivity between the indicated source IP address and the destination IP address did not exist.
- PRVG-11095: The TCP system call "{0}" failed with error "{1}" while executing exectask on node "{2}"
-
Cause: Cluster Verification Utility (CVU) framework node connectivity checking encountered the indicated error while trying to run the indicated Transmission Control Protocol (TCP) connectivity system call on the indicated node.
- PRVG-11096: Error copying file "{0}" from local node to the directory "{1}" on the remote node "{2}"
-
Cause: The specified file could not be copied from the local node to the specified directory on the specified remote node. The accompanying messages provide detailed failure information.
- PRVG-11097: unable to reach nodes "{0}" from the local node
-
Cause: During a verification operation to check that specified nodes are reachable from the local node using the 'ping' command, the verification failed to reach any of the nodes indicated in the message. Either the addresses for those nodes did not resolve correctly or they were unreachable.
- PRVG-11098: Oracle ACFS is configured and Highly Available IP (HAIP) is enabled on the nodes "{0}".
-
Cause: The Cluster Verification Utility (CVU) found that the HAIP was enabled on the indicated nodes. HAIP is not supported on Exadata for Oracle Clusterware 18c and later.
- PRVG-11101: The disk free space could not be determined for file system path "{0}" on nodes "{1}".
-
Cause: An attempt to determine the disk space for the indicated file system path failed on the nodes indicated. The accompanying messages provide detailed failure information.
- PRVG-11103: The Free Space Component check failed on node(s) "{0}"
-
Cause: The free space in the CRS home directory is below the threshold.
- PRVG-11104: The disk free space for file system path "{0}" on node "{1}" is below "{2}" percent of total disk space. The required free space is "{3}", the available free space is "{4}" and the total disk size is "{5}".
-
Cause: The disk free space in the specified file system was below the specified minimum threshold as a percentage of total disk space on the node specified.
- PRVG-11105: The disk free space for file system path "{0}" on node "{1}" is below required threshold. The required free space is "{2}" and the available free space is "{3}".
-
Cause: The disk free space in the specified file system was below the specified required minimum threshold on the node specified.
- PRVG-11110: The specified database file location "{0}" did not have read and write access to user "{1}" on node "{2}"
-
Cause: The database file location did not have read and write permissions to the user on some nodes.
- PRVG-11111: Path "{0}" is not shared by at least {1} node.
-
Cause: The path was not shared by sufficient nodes to meet the target hub size.
- PRVG-11112: Path "{0}" is not shared by the following hub nodes: {1}
-
Cause: Specified hub nodes do not share the path.
- PRVG-11115: Following error occurred while establishing connection to database "{0}"
-
Cause: An attempt to connect to database failed.
- PRVG-11123: AUDIT_FILE_DEST location "{0}" is shared among instances "{1}" of database "{2}"
-
Cause: Two or more instances of the database were found to be using the same AUDIT_FILE_DEST location on shared storage.
- PRVG-11125: Following error occurred during shared AUDIT_FILE_DEST location check
-
Cause: An error occurred while performing shared AUDIT_FILE_DEST locations check.
- PRVG-11126: Oracle home from which database "{0}" is running could not be determined.
-
Cause: Checks on the directory location pointed to by database initialization parameter 'AUDIT_FILE_DEST' failed to determine the Oracle home from which the specified database was running.
- PRVG-11127: Skipping AUDIT_FILE_DEST location check for database "{0}" because software owner "{1}" of the associated Oracle home "{2}" is not the same as current OS user "{3}".
-
Cause: Checks for the directory location pointed to by database initialization parameter 'AUDIT_FILE_DEST', for the specified database, could not be performed because the software owner of the associated Oracle home was not same as the current operating system user.
- PRVG-11129: Check of subnet "{0}" for multicast communication with multicast group "{1}" failed.
-
Cause: The Cluster Verification Utility (CVU) determined that the interfaces on the indicated subnet were not able to communicate using the indicated multicast group.
- PRVG-11134: Interface "{0}" on node "{1}" is not able to communicate with interface "{2}" on node "{3}"
-
Cause: The specified interfaces were not able to communicate using a multicast address.
- PRVG-11137: Following error occurred during multicast check
-
Cause: An error occurred while performing multicast check.
- PRVG-11138: Interface "{0}" on node "{1}" is not able to communicate with interface "{2}" on node "{3}" over multicast group "{4}"
-
Cause: The specified interfaces were not able to communicate using a multicast address.
- PRVG-11139: Specified subnets "{0}" could not be found in the cluster network interface configured subnets "{1}"
-
Cause: The subnets provided in the -network option were not configured in the cluster network interfaces.
- PRVG-11143: The following error occurred during stale database schema statistics check.
-
Cause: An error occurred while performing database stale schema check.
- PRVG-11144: Schema objects "{0}" have stale statistics in the database "{1}"
-
Cause: The specified schema objects were found to have stale statistics in the database.
- PRVG-11170: Skipping DHCP check for cluster which has only IPv6 interfaces
-
Cause: All the public interfaces in a cluster were IPv6.
- PRVG-11171: DHCP check failed
-
Cause: An error occurred while reading network interface information.
- PRVG-11214: An internal command "cvuhelper" exited unexpectedly while fetching the information from Oracle Cluster Registry.
-
Cause: An attempt to execute an internal cvuhelper command exited unexpectedly.
- PRVG-11250: The check "{0}" was not performed because it needs 'root' user privileges.
-
Cause: In running the pre-requisite test suite for a planned system management operation, the indicated check was not performed because it requires root user privileges, and the root user credentials had not been supplied.
- PRVG-11300: Parameter "{0}" value is not valid
-
Cause: This is an internal error. The value for the specified parameter is null or empty string.
- PRVG-11301: The 'root' user "{0}" password is not valid on the following nodes: {1}.
-
Cause: An attempt to validate the specified superuser password failed.
- PRVG-11302: 'sudo' command does not exist at location "{0}" on nodes "{1}"
-
Cause: An attempt to verify that the specified user has permission to run sudo command from specified path on specified nodes failed.
- PRVG-11303: Commands could not be executed as 'root' using 'sudo' on nodes: {0}.
-
Cause: An attempt to run commands as 'root' using 'sudo' on specified nodes failed.
- PRVG-11304: Executing commands as root not permitted
-
Cause: An attempt was made to execute a command as 'root' user when root execution method and credentials were not specified. This is an internal error.
- PRVG-11305: Commands could not be executed as user 'root' on nodes: {0}.
-
Cause: An attempt to run commands as user 'root' on the indicated nodes failed.
- PRVG-11306: 'NOPASSWD' option is enabled in sudo configuration on nodes "{0}".
-
Cause: An attempt to use sudo for root automation was rejected because sudo was configured for 'NOPASSWD' option on the indicated nodes. The 'NOPASSWD" option was not supported.
- PRVG-11310: "{0}" nodes were not found in the cluster
-
Cause: Zero nodes of specified type were found in the cluster.
- PRVG-11314: The operating system groups for the following databases are not consistent across all nodes: {0}
-
Cause: An operating system group was not found or did not have the same name on all nodes where the corresponding database is present.
- PRVG-11318: The following error occurred during database operating system groups check. "{0}"
-
Cause: An error occurred while performing database operating system groups check.
- PRVG-11320: The database operating system group {0} is inconsistent across nodes {1} for database {2}.
-
Cause: The specified operating system group was not found or did not have the same group name on all the identified nodes where the database is present.
- PRVG-11321: One of the elements of parameter "{0}" value is not valid
-
Cause: This is an internal error. The value for one of the array elements for the specified parameter is null or empty string.
- PRVG-11322: One or more node names "{0}" contain one or more of the following invalid characters "{1}"
-
Cause: One or more of the supplied node names or the local host name contained invalid characters.
- PRVG-11330: Database operating system groups consistency check failed for the databases "{0}" on nodes "{1}"
-
Cause: One or more operating system groups were not found or did not have the same group name on all the identified nodes where the database is present.
- PRVG-11352: Interface "{0}" on node "{1}" is not able to communicate with interface "{2}" on node "{3}" with broadcast address "{4}"
-
Cause: The specified interfaces were not able to communicate using the broadcast address.
- PRVG-11353: Broadcast packets sent on subnet "{0}" with broadcast address "{1}" were not received
-
Cause: All the interfaces on the subnet were not able to communicate using the broadcast address.
- PRVG-11356: Following error occurred during broadcast check
-
Cause: An error occurred while performing broadcast check.
- PRVG-11366: SCAN IP addresses "{0}" of SCAN "{1}" was not on subnet "{2}"
-
Cause: SCAN IP was found to be on a different subnet than the one chosen as a public subnet.
- PRVG-11367: SCAN IP addresses "{0}" of SCAN "{1}" were not on subnet "{2}"
-
Cause: Subnet of network associated with the SCAN were modified but SCAN IP addresses were not modified.
- PRVG-11368: A SCAN is recommended to resolve to "{0}" or more IP addresses, but SCAN "{1}" resolves to only "{2}"
-
Cause: An insufficient number of SCAN IP addresses were defined for the specified SCAN.
- PRVG-11369: SCAN IP addresses "{0}" of SCAN "{1}" were active before Clusterware installation
-
Cause: SCAN IP addresses were found to be active on the network before Clusterware installation.
- PRVG-11372: Number of SCAN IP addresses that SCAN "{0}" resolved to did not match the number of SCAN VIP resources
-
Cause: It was found that the SCAN IP addresses that SCAN resolves to were modified after the SCAN was created.
- PRVG-11373: IPV4 and IPV6 addresses of SCAN VIP resources of SCAN "{0}" were not consistent
-
Cause: The SCAN resolved to differing numbers of IPv4 and IPv6 addresses.
- PRVG-11374: SCAN "{0}" was not resolved
-
Cause: A static SCAN was not resolved to IP addresses.
- PRVG-11375: The Oracle Address Resolution Protocol driver service does not exist on node "{0}".
-
Cause: The Oracle Address Resolution Protocol driver service was not found in the specified node.
- PRVG-11376: The Oracle Address Resolution Protocol driver service is not configured with the start type 'auto' as expected on node "{0}".
-
Cause: The configuration of the Oracle Address Resolution Protocol driver service did not specify the expected start type: 'auto'.
- PRVG-11377: The Oracle Address Resolution Protocol driver service is not configured with the service type 'kernel' as expected on node "{0}".
-
Cause: The configuration of the Oracle Address Resolution Protocol driver service did not specify the expected service type: 'kernel'.
- PRVG-11378: The Oracle Address Resolution Protocol driver service is not running on node "{0}".
-
Cause: The Oracle Address Resolution Protocol driver service was found with current status of 'stopped'.
- PRVG-11380: IP addresses "{0}" resolved for SCAN "{1}" are not reachable.
-
Cause: The Cluster Verification Utility found that the indicated SCAN IP addresses configured on the server cluster are not reachable from the client cluster. The accompanying messages provide additional failure details.
- PRVG-11381: Valid node checking registration for SCAN listener "{0}" is enabled, and set to "{1}" on node "{2}". Invited nodes which are allowed to register with the SCAN listener do not contain the cluster nodes "{3}".
-
Cause: The Cluster Verification Utility found that valid node checking registration was enabled for the indicated SCAN listener, which allows only local node IP addresses and invited nodes to register with the scan listener. And the indicated cluster nodes were not in the list of invited nodes for the indicated SCAN listener.
- PRVG-11382: The permissions on the SCAN listener socket file "{0}" do not match the expected octal value on node "{1}". [Expected = "{2}" ; Found = "{3}"]
-
Cause: The Cluster Verification Utility found that the permissions of the indicated file on the indicated node were different from the required permissions. This might lead to failure in starting the SCAN listener.
- PRVG-11383: The owner of the SCAN listener socket file "{0}" is not the CRS user on node "{1}". [Expected = "{2}" ; Found = "{3}"]
-
Cause: The Cluster Verification Utility found that the owner of the indicated file on the indicated node was not the CRS user. This might lead to failure in starting the SCAN listener.
- PRVG-11384: The list of invited nodes allowed to register with the SCAN listener "{0}" contains invalid or unresolvable names "{1}".
-
Cause: The Cluster Verification Utility found that the indicated invalid or unresolvable names were in the list of invited nodes for the indicated SCAN listener, which would lead to failure in starting or restarting the SCAN listener.
- PRVG-11400: Node role value is not valid.
-
Cause: The value passed to CVU for the node role parameter was not one of the allowed values: 'hub', 'leaf' or 'auto'. This is an internal error.
- PRVG-11401: invalid new node list specified including both nodes with 'auto' role and nodes with 'hub' or 'leaf' role
-
Cause: The supplied list of new nodes consisted of a mix of nodes with the 'auto' role in combination with nodes having the 'hub' or 'leaf' role.
- PRVG-11402: New nodes cannot have AUTO node role unless the existing cluster consists entirely of AUTO nodes
-
Cause: An attempt to validate new nodes for addition supplied one or more AUTO role nodes for a cluster with no AUTO role nodes.
- PRVG-11403: A Leaf Node cannot be added unless existing cluster contains at least one Hub Node.
-
Cause: An attempt was made to add a node with the 'leaf' role when the cluster did not have at least one node with the 'hub' role.
- PRVG-11404: The addition of hub nodes will exceed the target hub size[{0}]
-
Cause: The request to validate new nodes specified enough hub nodes that the cluster target hub size would be exceeded.
- PRVG-11405: API with node roles argument should be called for Flex Cluster only
-
Cause: An internal error occurred.
- PRVG-11406: API with node roles argument must be called for Flex Cluster
-
Cause: An internal error occurred.
- PRVG-11407: API called with unequal sized arrays for nodes and VIPs
-
Cause: An internal error occurred.
- PRVG-11408: API called with unequal sized arrays for nodes, VIPs and node roles
-
Cause: An internal error occurred.
- PRVG-11409: These nodes already appear to be part of the cluster: "{0}"
-
Cause: The supplied list of new nodes contains some nodes which are already part of the cluster.
- PRVG-11410: illegal specification of nodes with 'leaf' role for a non-Flex Cluster
-
Cause: An attempt was made to add a 'leaf' role node to a non-Flex Cluster.
- PRVG-11415: Password entry for user "{0}" in the database "{1}" did not exist in CVUDB wallet
-
Cause: No password entry for the specified user for the specified database was found in the CVUDB walllet.
- PRVG-11420: Storage type of the path "{0}" could not be determined
-
Cause: There was an error in determining storage type of the path.
- PRVG-11421: Storage type of the path "{0}" could not be determined
-
Cause: An internal error occurred.
- PRVG-11422: Missing GNS subdomain name.
-
Cause: GNS subdomain name was not provided.
- PRVG-11423: The password provided on the command line is not valid for user "{0}"
-
Cause: The provided password was wrong.
- PRVG-11424: Missing GNS subdomain for dynamic public network
-
Cause: When checking GNS integrity, the public VIPs were configured to use dynamic addresses (DHCP or autoconfig), but the required GNS subdomain was not configured.
- PRVG-11425: Failed to validate GNS credential in file "{0}"
-
Cause: An attempt to validate the Grid Naming Service (GNS) credential failed.
- PRVG-11426: IP address for GNS VIP "{0}" is not consistent across the cluster nodes.
-
Cause: The Cluster Verification Utility determined that the indicated GNS VIP entry in the hosts file or DNS did not resolve to the same IP address across the cluster nodes.
- PRVG-11427: GNS VIP "{0}" resolves to IP address "{1}" on the majority of cluster nodes but to address "{2}" on nodes "{3}".
-
Cause: The Cluster Verification Utility determined that the indicated GNS VIP resolved to the indicated different IP address on the indicated nodes.
- PRVG-11499: ACFS kernel version "{0}" is different from the version of the ACFS commands "{1}" on node "{2}".
-
Cause: The ACFS kernel version was found to be different from the version of the ACFS commands on the indicated node.
- PRVG-11500: ACFS file systems are not available on Leaf nodes "{1}"
-
Cause: The specified ACFS path was not suitable for Leaf nodes.
- PRVG-11501: Path "{0}" of type "{1}" is not suitable for usage as RAC database software for release "{2}". Supported storage types are "{3}".
-
Cause: The specified path is not found suitable for usage as RAC database software
- PRVG-11502: Path "{0}" of type "{1}" is not suitable for usage as RAC database file for release "{2}". Supported storage types are "{3}".
-
Cause: The specified path is not found suitable for usage as RAC database file
- PRVG-11503: Path "{0}" of type "{1}" is not suitable for usage as Oracle Clusterware storage for release "{2}". Supported storage types are "{3}".
-
Cause: The specified path is not found suitable for usage as Oracle Clusterware storage(OCR or Voting Disk).
- PRVG-11504: Path "{0}" of type "{1}" is not suitable for usage as Single Instance database software for release "{2}". Supported storage types are "{3}".
-
Cause: The specified path is not found suitable for usage as Single Instance database software
- PRVG-11505: Path "{0}" of type "{1}" is not suitable for usage as Single Instance database file for release "{2}". Supported storage types are "{3}".
-
Cause: The specified path is not found suitable for usage as Single Instance database file
- PRVG-11506: Path "{0}" of type "{1}" is not suitable for ASM for release "{2}". Supported storage types are "{3}".
-
Cause: The specified path is not found suitable for ASM
- PRVG-11515: Nodes with mix of 'auto', 'hub' and 'leaf' roles were found in the Flex Cluster.
-
Cause: The Flex Cluster node role check found nodes with both the 'auto' role and either the 'hub' or 'leaf' roles defined.
- PRVG-11516: New nodes "{0}" with 'hub' or 'leaf' role cannot be added to a Flex Cluster that has 'auto' role nodes.
-
Cause: An attempt was made to add nodes with the 'hub' or 'leaf' role to a Flex Cluster already having nodes with the 'auto' role.
- PRVG-11517: New nodes "{0}" with 'auto' role cannot be added to a Flex Cluster already having nodes with the 'hub' and 'leaf' roles.
-
Cause: An attempt was made to add nodes with the 'auto' role to an Flex Cluster already having nodes with the 'hub' and 'leaf' role.
- PRVG-11518: Following error occurred during Flex Cluster node role configuration check
-
Cause: An error occurred while performing the Flex Cluster node role configuration check.
- PRVG-11550: Package "{0}" is missing on node "{1}"
-
Cause: The cvuqdisk RPM is not installed on the specified node. This package is required for shared disk validations. During installation, ASM disk validation cannot be performed without this RPM.
- PRVG-11551: Required version of package "{0}" was not found on node "{1}" [Required = "{2}" ; Found = "{3}"].
-
Cause: The version of installed cvuqdisk RPM does not meet the requirement on the specified node. This package is required for shared disk validations. During installation, ASM disk validation cannot be performed without this RPM.
- PRVG-11635: The ASM disks "{0}" are incorrectly sized
-
Cause: The indicated ASM disks had incorrect size information in the disk header.
- PRVG-11640: The check "{0}" was not performed as it is disabled
-
Cause: The indicated check was suppressed.
- PRVG-11644: Failed to copy baseline to the remote nodes: "{0}"
-
Cause: An error occurred while copying the report to the remote nodes
- PRVG-11658: Baseline could not be collected for database "{0}".
-
Cause: "An attempt to collect baseline information using the command 'cluvfy comp baseline -collect database' failed because the indicated database was not configured in clusterware."
- PRVG-11659: Baseline could not be collected for databases in the database home "{0}".
-
Cause: "An attempt to collect baseline information using the command 'cluvfy comp baseline -collect database' failed because the indicated database home was not installed and configured in clusterware."
- PRVG-11671: reference baseline not specified
-
Cause: The request for baseline cross comparison omitted the required reference baseline.
- PRVG-11750: File "{0}" exists on node "{1}".
-
Cause: The specified file is not expected to be present on the node.
- PRVG-11754: Check for existence of directory "{0}" could not be performed on node "{1}".
-
Cause: An error occurred while checking the existence of the directory on the specified node.
- PRVG-11755: Property "{0}" was not found in configuration file "{1}"
-
Cause: Could not find the specified property in the configuration file.
- PRVG-11774: NIC bind order check failed on nodes: "{0}"
-
Cause: The NIC bind order on the specified nodes did not prioritize the public network above the private network.
- PRVG-11775: Failed to retrieve the NIC bind order information on nodes: "{0}"
-
Cause: An attempt to retrieve the NIC bind order failed on the indicated nodes.
- PRVG-11776: Failed to retrieve the NIC bind order information from all the nodes
-
Cause: An attempt to retrieve the NIC bind order information failed on all the nodes.
- PRVG-11779: Metric value "{0}" for public interface "{1}" is higher than or equal to metric value "{2}" for private interface "{3}" on node "{4}".
-
Cause: The identified public interface metric value was higher or equal to the identified private interface metric value on the indicated node.
- PRVG-11780: Failed to convert string "{0}" to integer value
-
Cause: The network interface metric value could not be determined as the identified string to integer conversion failed.
- PRVG-11800: Failed to discover any devices using the discovery string "{0}" on node "{1}"
-
Cause: The specified discovery string could not discover any devices on the identified node.
- PRVG-11816: Windows user "{0}" is a domain user but a conflicting local user account "{1}" exists on node "{2}"
-
Cause: A conflicting local user account as indicated was found on the identified node.
- PRVG-11817: Windows user "{0}" is a local user but a matching local user account does not exist on nodes "{1}"
-
Cause: A local user account for an Oracle installation user was not found on the identified nodes.
- PRVG-11818: Windows user "{0}" is a domain user but a conflicting local user account was found on nodes "{1}"
-
Cause: A conflicting local user account as indicated was found on the identified nodes.
- PRVG-11819: Current Oracle Home User "{0}" is not a domain user
-
Cause: The current Oracle Home User was found to be a Windows user account local to this system.
- PRVG-11820: Error retrieving the account details for user "{0}" from nodes "{1}"
-
Cause: An error occurred while retrieving the account details of indicated user.
- PRVG-11825: Failed to get the Oracle Home user name for Oracle Home "{0}"
-
Cause: An attempt to retrieve the Oracle Home User for the indicated Oracle Home failed.
- PRVG-11826: DNS resolved IP addresses "{0}" for SCAN name "{1}" not found in the name service returned IP addresses "{2}"
-
Cause: The name resolution setup check for the indicated SCAN name failed because one or more of the indicated IP addresses obtained from DNS could not be found in the IP addresses obtained from the name service on the system as configured in the '/etc/nsswitch.conf' configuration file.
- PRVG-11827: Name service returned IP addresses "{0}" for SCAN name "{1}" not found in the DNS returned IP addresses "{2}"
-
Cause: The name resolution setup check for the indicated SCAN name failed because one or more of the indicated IP addresses obtained from name service on the system as configured in the '/etc/nsswitch.conf' configuration file could not be found in the IP addresses obtained from DNS.
- PRVG-11850: The system call "{0}" failed with error "{1}" while executing exectask on node "{2}"
-
Cause: An attempt to execute exectask on the specified node failed.
- PRVG-11851: The system call "connect" failed while executing exectask on node "{0}"
-
Cause: The connect system call failed on the specified node.
- PRVG-11865: Oracle Home "{0}" for the administrator managed database "{1}" instances "{2}" does not exist on nodes "{3}"
-
Cause: The indicated Oracle Home for the indicated database was not found on the indicated nodes and the automatic root script execution was selected.
- PRVG-11866: Oracle Home "{0}" for the administrator managed database "{1}" instances "{2}" does not exist on nodes "{3}"
-
Cause: The indicated Oracle Home for the indicated database was not found on the indicated nodes.
- PRVG-11867: Oracle Home "{0}" for policy managed database "{1}" does not exist on nodes "{2}"
-
Cause: The indicated Oracle Home for the indicated database was not found on the indicated nodes.
- PRVG-11868: An internal command 'cvuhelper' failed to get the administrator and policy managed database information.
-
Cause: An attempt to execute an internal cvuhelper command failed.
- PRVG-11869: An internal command 'cvuhelper' exited unexpectedly while getting the administrator and policy managed database information.
-
Cause: An attempt to execute an internal cvuhelper command failed.
- PRVG-11870: failed to parse database information from the 'cvuhelper' command output
-
Cause: An attempt to parse output from an internal cvuhelper command failed.
- PRVG-11884: Policy managed database home availability check failed
-
Cause: One or more policy managed database homes were not found on the nodes being added to the cluster.
- PRVG-11885: Oracle Home "{0}" for policy managed database "{1}" does not exist on nodes "{2}"
-
Cause: The indicated Oracle Home for the indicated database was not found on the indicated nodes and the automatic root script execution was selected.
- PRVG-11886: Command "{0}" to get the policy managed database information failed
-
Cause: An attempt to execute the displayed command failed.
- PRVG-11890: failed to determine the space used by directory "{0}" on node "{1}"
-
Cause: An attempt to determine the space used by the identified directory failed on the indicated node.
- PRVG-11891: Connectivity failed between interface "{0}" configured with IP address "{1}" on node "{2}" and interface "{3}" configured with IP address "{4}" on node "{5}" for the subnet "{6}".
-
Cause: Cluster Verification Utility (CVU) node connectivity checking detected the connectivity problem described in the message. Connectivity for the mentioned subnet could not be verified between the two identified interfaces on the identified nodes.
- PRVG-11892: Connectivity failed between IP address "{0}" on node "{1}" and IP address "{2}" on node "{3}" for the subnet "{4}".
-
Cause: Cluster Verification Utility (CVU) node connectivity checking detected the connectivity problem described in the message. Connectivity for the mentioned subnet could not be verified between the two identified IP addresses on the identified nodes.
- PRVG-11893: RDS connectivity failed between interface "{0}" configured with IP address "{1}" on node "{2}" and interface "{3}" configured with IP address "{4}" on node "{5}" for subnet "{6}".
-
Cause: Cluster Verification Utility (CVU) node connectivity checking detected the connectivity problem described in the message. Connectivity for the mentioned subnet could not be verified between the two identified interfaces using the 'rds-ping' command on the identified nodes.
- PRVG-11894: RDS connectivity failed between IP address "{0}" on node "{1}" and IP address "{2}" on node "{3}" for subnet "{4}".
-
Cause: Cluster Verification Utility (CVU) node connectivity checking detected the connectivity problem described in the message. Connectivity for the mentioned subnet could not be verified between the two identified IP addresses using the 'rds-ping' command on the identified nodes.
- PRVG-11900: Oracle Clusterware is not installed on this node.
-
Cause: An attempt to execute the command 'cluvfy comp software' was requested, but files associated with Oracle Clusterware installation were not found.
- PRVG-11901: Oracle Clusterware is not running on this node.
-
Cause: An attempt to execute a 'cluvfy' command that requires Oracle Clusterware to be running failed because Clusterware was not running on the node.
- PRVG-11902: Oracle Clusterware is not configured on node {0}.
-
Cause: A 'cluvfy comp software' command was issued on a system that does not have an Oracle Clusterware configuration.
- PRVG-11903: The specified destination CRS home {0} is the same as the currently configured CRS home {1}.
-
Cause: The pre-upgrade prerequisites check failed because the specified destination CRS home was the same as the currently configured CRS home.
- PRVG-11904: The file 'oracle.key' does not exist for Oracle home {0} on node {1}.
-
Cause: The command 'cluvfy comp software' failed for the indicated node because it does not appear to have a valid Oracle home.
- PRVG-11905: The file 'oracle.key' cannot be read on node {0}.
-
Cause: The command 'cluvfy comp software' failed for the indicated node because it does not have a valid 'oracle.key' file.
- PRVG-11906: The Oracle home {0} does not exist.
-
Cause: The command 'cluvfy comp software' failed because the specified Oracle home could not be found.
- PRVG-11907: The Oracle database edition cannot be obtained from file {0} on node {1}.
-
Cause: The command 'cluvfy comp software' failed because the file which indicates the database edition could not be accessed on the indicated node.
- PRVG-11910: failed to locate Oracle base for home "{0}" on node "{1}"
-
Cause: An attempt to retrieve Oracle base using command <ORACLE_HOME>/bin/orabase failed.
- PRVG-11911: Database services count is not available for Oracle Clusterware versions prior to 11.2.
-
Cause: An attempt was made to retrieve the database services count for an Oracle Clusterware version lower than 11.2.
- PRVG-11912: Command '{0}' to retrieve database services count failed.
-
Cause: An attempt to execute the displayed command failed. This is an internal error.
- PRVG-11913: Syntax errors in the following lines from ONS configuration file "{1}" on node "{0}" :
-
Cause: Invalid lines were found in the ons.config file at the location and node indicated.
- PRVG-11914: The ONS configuration file "{0}" does not exist on following nodes: {1}
-
Cause: The file specified did not exist on the nodes listed, but exists on other nodes.
- PRVG-11915: ONS configuration file "{0}" does not exist on any node of the cluster. Skipping further checks.
-
Cause: The ONS configuration file was missing from all of the nodes.
- PRVG-11919: Unable to create work area directory "{0}"
-
Cause: An attempt to create the specified directory failed on the local node.
- PRVG-11920: Unable to delete CVU work files from directory "{0}"
-
Cause: An attempt to remove files from the specified directory failed.
- PRVG-11921: Error copying ONS configuration file "{0}" from node "{1}" to node "{2}"
-
Cause: The specified file could not be copied from the specified source node to the destination node.
- PRVG-11924: Local and remote ONS ports are same on node "{0}"
-
Cause: The local and remote port specified in the ons.config were the same.
- PRVG-11928: 'remoteport' entry in the existing ONS configuration file "{0}" is inconsistent
-
Cause: The ONS configuration file had inconsistent 'remoteport' entries.
- PRVG-11930: Path "{0}" is not writeable on nodes "{1}".
-
Cause: The identified path was not writeable on the indicated nodes.
- PRVG-11931: Path "{0}" is not writeable on node "{1}".
-
Cause: The identified path was not writeable by current user on the indicated node.
- PRVG-11932: Path "{0}" cannot be created on node "{1}".
-
Cause: The identified path can not be created on the indicated node.
- PRVG-11935: Unable to read file "{0}" copied to local scratch area from node: {1}
-
Cause: An error occurred while trying to read the specified file.
- PRVG-11937: Oracle Database is not configured to run on nodes "{0}".
-
Cause: Oracle Database was not configured to run on the indicated nodes. For administrator-managed databases, the database instances were not configured to run on the indicated nodes. For policy-managed databases, the indicated nodes were not in any of the server pools of the database.
- PRVG-11938: Oracle Database is not configured to run on any of the specified nodes.
-
Cause: Oracle Database was not configured to run on any of the specified nodes.
- PRVG-11945: Oracle Database software home location "{0}" does not have required group permissions on node "{1}". [Expected = "{2}" ; Found = "{3}"].
-
Cause: CVU checking determined that the group permissions were incorrect on the indicated Oracle Database home location on the indicated node.
- PRVG-11946: Oracle Database software home location "{0}" does not have read permission for group on node "{1}".
-
Cause: CVU checking determined that the group permissions were incorrect on the indicated Oracle Database home location on the indicated node.
- PRVG-11947: Oracle Database software home location "{0}" does not have execute permission for group on node "{1}".
-
Cause: CVU checking determined that the group permissions were incorrect on the indicated Oracle Database home location on the indicated node.
- PRVG-11950: Executable "{0}" does not exist on any node. The specified home "{1}" is not a valid Oracle home.
-
Cause: The 'oracle' executable was not found in the expected location on any node.
- PRVG-11951: Executable "{0}" does not exist on node "{1}".
-
Cause: The 'oracle' executable was not found in the expected location on the specified node.
- PRVG-11960: Set user ID bit is not set for file "{0}" on node "{1}".
-
Cause: The set user ID bit was not set for the identified file on the indicated node.
- PRVG-11961: failed to check the set user ID bit for file "{0}" on nodes "{1}"
-
Cause: An attempt to verify the Set user ID bit for the identified file failed on the indicated nodes.
- PRVG-11975: The I/O scheduler parameter of device "{0}" did not match the expected value on nodes "{1}". [Expected scheduler = "{2}" ; Found scheduler = "{3}"]
-
Cause: The I/O scheduler parameter of the indicated device was not the expected value on the indicated nodes.
- PRVG-11976: The I/O scheduler parameter of device "{0}" that belongs to ASM disk "{1}" of the ASM disk group "{2}" did not match the expected value on nodes "{3}". [Expected scheduler = "{4}" ; Found scheduler = "{5}"].
-
Cause: The I/O scheduler parameter of the indicated device was not the expected value on the indicated node.
- PRVG-11977: The I/O scheduler parameter is not configured for device "{0}" on nodes "{1}".
-
Cause: An attempt to obtain the I/O scheduler corresponding to the specified device failed on the node specified.
- PRVG-11983: Grid Infrastructure home check failed
-
Cause: The Grid Infrastructure home path was not writable.
- PRVG-12102: The time difference between nodes "{0}" and "{1}" is beyond the permissible offset of "{2}" seconds
-
Cause: The Cluster Verification Utility detected a time offset between the indicated nodes was more than the indicated permissible value.
- PRVG-12103: The current time offset of "{0}" seconds on node "{1}" is greater than the permissible offset of "{2}" when compared to the time on node "{3}"
-
Cause: The Cluster Verification Utility detected a time offset between the indicated nodes was more than the permissible value.
- PRVG-12104: Failed to retrieve the current time from node "{0}"
-
Cause: An attempt to retrieve the current time from the indicated node failed with the indicated error.
- PRVG-12802: ASM devices "{0}" are not ASM Filter Driver capable.
-
Cause: The indicated devices were not ASM filter driver capable.
- PRVG-12805: Device "{0}" cannot be managed by the ASM Filter Driver on node "{1}".
-
Cause: The indicated ASM device did not have a correct device type and hence was identified as not AFD capable.
- PRVG-12806: failed to discover the device type of devices "{0}" on nodes "{1}"
-
Cause: An attempt to retrieve the device type of the indicated device failed on the identified nodes.
- PRVG-12807: failed to retrieve the device type of device "{0}" on node "{1}"
-
Cause: An attempt to retrieve the device type of the indicated devices failed on all the nodes.
- PRVG-12808: ASMLib is installed on nodes "{0}"; ASM Filter Driver will not be used for managing ASM devices.
-
Cause: ASMLib was found installed on the indicated nodes.
- PRVG-12809: 'remoteport' entry is missing from ONS configuration file "{1}" on nodes "{0}".
-
Cause: The Oracle Notification Sservices (ONS) configuration file was missing the remote port entry.
- PRVG-12810: failed to expand the device path discovery string "{0}"
-
Cause: The requested operation could not be completed because the indicated device path discovery string argument could not be expanded to a list of ASM disk devices.
- PRVG-12855: Configured private networks "{0}" with subnet masks "{1}" do not exist on nodes "{2}".
-
Cause: The indicated CRS private subnets did not match any subnet available on the identified node.
- PRVG-12856: Configured public subnets "{0}" with subnet masks "{1}" do not exist on nodes "{2}".
-
Cause: The indicated CRS public subnets did not match any subnet available on the identified node.
- PRVG-12857: Classfied subnet configuration of the current CRS home "{0}" does not match any existing subnets on nodes "{1}".
-
Cause: The indicated CRS subnet did not match any subnet available on the identified nodes.
- PRVG-12858: Following error occurred during the network configuration consistency checks.
-
Cause: An error occurred while performing the network configuration consistency checks.
- PRVG-12861: 'options {0}' entry does not exist in resolver configuration file "{1}" on nodes "{2}"
-
Cause: The indicated option entry was specified on some nodes, but not all of them.
- PRVG-12864: The resolver configuration file "{0}" on the nodes "{1}" has more than one 'options {2}' entry
-
Cause: The indicated option entry was found more than once on nodes specified in the resolver configuration file indicated.
- PRVG-12867: 'options {0}' entries in the resolver configuration file "{1}" are inconsistent
-
Cause: A check of each node's resolv.conf files found inconsistent entries of the indicated option.
- PRVG-12869: The product of the 'attempts' option value "{0}" and the 'timeout' option value "{1}" in the resolver configuration file "{2}" is greater than the maximum allowed "{3}".
-
Cause: A check of node's resolv.conf files found values greater than the maximum allowed.
- PRVG-12884: Maximum (MTU) size packet check failed on subnets "{0}"
-
Cause: The network switch was not configured with jumbo frames or the identified subnets do not support jumbo frames.
- PRVG-12885: ICMP packet of MTU size "{0}" does not go through subnet "{1}".
-
Cause: The network switch was not configured with jumbo frames or the network subnet does not support the identified MTU size.
- PRVG-12886: Interface "{0}" has an invalid MTU value "{1}".
-
Cause: The retrieved MTU value from ip command contained other than decimal digits.
- PRVG-12887: failed to get the MTU value for interface "{0}" using ip command "{1}" on node "{2}"
-
Cause: An attempt to obtain the MTU value for the identified interface failed on the indicated node.
- PRVG-12893: User "{0}" failed to determine the permissions of path "{1}" on nodes "{2}".
-
Cause: An attempt to check the permissions of the indicated path failed on the indicated nodes.
- PRVG-12894: Failed to get the groups of user "{0}" on nodes "{1}".
-
Cause: An attempt to get the groups of the indicated user failed on the indicated nodes.
- PRVG-12895: The group "{1}" of the path "{0}", does not have execute permissions for "others" "{2}" and "group" "{3}" configured on node "{4}".
-
Cause: The check found a bad permissions configuration of the indicated path on the indicated node.
- PRVG-12896: The owning group "{0}" of path "{1}" is not in the groups "{2}" of the Grid user on node "{3}".
-
Cause: The check for permissions of the indicated path found that the group was not in the indicated groups of the Grid user on the indicated node.
- PRVG-12914: Oracle Fence service file "{0}" is missing on nodes "{1}".
-
Cause: The Oracle Fence Service file was not found at the identified path on the indicated nodes.
- PRVG-12915: The service "{0}" is not configured with the service type 'kernel' as expected on nodes "{1}".
-
Cause: The configuration of the identified Windows service did not specify the expected service type: 'kernel'.
- PRVG-12916: The service "{0}" is not configured with the start type 'auto' as expected on nodes "{1}".
-
Cause: The configuration of the identified Windows service did not specify the expected start type: 'auto'.
- PRVG-12917: The service "{0}" is not running on nodes "{1}".
-
Cause: The identified Windows service was not running on the indicated nodes.
- PRVG-12918: The service "{0}" does not exist on nodes "{1}".
-
Cause: The identified Windows service was not found on the indicated nodes.
- PRVG-12934: The virtual memory manager tunable parameter "{0}" does not have expected "DEF" value on nodes "{1}" [Expected = "{2}"]
-
Cause: The identified parameter did not have the expected "DEF" value on the indicated nodes.
- PRVG-12935: The virtual memory manager tunable parameter "{0}" does not have expected "BOOT" value on nodes "{1}" [Expected = "{2}"]
-
Cause: The identified parameter did not have the expected "BOOT" value on the indicated nodes.
- PRVG-12936: Processor folding parameter "{0}" is not disabled on nodes "{1}".
-
Cause: Processor folding was not turned off on the indicated nodes.
- PRVG-12937: failed to convert string "{0}" to integer value
-
Cause: The identified string to integer conversion failed.
- PRVG-12938: An internal command 'cvuhelper' exited unexpectedly on node "{0}" while running a SQL query on ASM.
-
Cause: An attempt to execute an internal cvuhelper command failed.
- PRVG-12939: An internal command 'cvuhelper' failed to produce any output on node "{0}" while running a SQL query on ASM.
-
Cause: An attempt to execute an internal cvuhelper command failed.
- PRVG-12940: failed to parse 'cvuhelper' command output
-
Cause: An attempt to parse output from an internal cvuhelper command failed.
- PRVG-12941: An internal command 'cvuhelper' failed to run a SQL query on ASM on node "{0}".
-
Cause: An ASM SQL query failed unexpectedly.
- PRVG-12942: failed to obtain ASM instance configuration on node "{0}"
-
Cause: An attempt to retrieve information about configuration of an ASM instance on the indicated node failed.
- PRVG-12943: failed to load Oracle JDBC Driver
-
Cause: An attempt to load Oracle JDBC Driver failed.
- PRVG-12944: failed to obtain credentials to connect to ASM with role {0}
-
Cause: An attempt to obtain ASM credentials for the current OS user failed.
- PRVG-12945: An error occurred while establishing connection to ASM with current OS user and connect descriptor:\n"{0}"
-
Cause: An attempt to connect to ASM failed.
- PRVG-12946: An error occurred while establishing connection to ASM using role {0}.
-
Cause: An attempt to connect to ASM failed.
- PRVG-12947: An internal command 'cvuhelper' failed to obtain ASM connection information on node "{0}".
-
Cause: An attempt to get ASM connection information failed.
- PRVG-12948: Failed to get ASM connection information. Verification cannot proceed.
-
Cause: Error occurred while attempting to get ASM connection information.
- PRVG-12949: Failed to get ASM connection. Verification cannot proceed.
-
Cause: An error occurred attempting to connect to ASM.
- PRVG-12950: An internal 'cvuhelper' command exited unexpectedly on node "{0}" while running a SQL query against the GIMR.
-
Cause: An internal 'cvuhelper' command exited unexpectedly while attempting to run a SQL query against the Grid Infrastructure Management Repository (GIMR). This was an internal error.
- PRVG-12951: An internal 'cvuhelper' command failed to produce any output on node "{0}" while running a SQL query against the GIMR.
-
Cause: An internal 'cvuhelper' command failed to produce any output when running a SQL query against the Grid Infrastructure Management Repository (GIMR). This was an internal error.
- PRVG-12952: failed to parse 'cvuhelper' command output
-
Cause: An attempt to parse the output of an internal 'cvuhelper' command failed. This was an internal error.
- PRVG-12953: An internal 'cvuhelper' command encountered an error while running a SQL query against the GIMR on node "{0}".
-
Cause: A SQL query against the Grid Infrastructure Management Repository (GIMR) failed.
- PRVG-12954: GIMR is not online on node "{0}".
-
Cause: An attempt to run a SQL query against the Grid Infrastructure Management Repository (GIMR) failed because the GIMR was not online on the indicated node.
- PRVG-12955: Management database not running on local node "{0}".
-
Cause: The Cluster Verification Utility (CVU) determined that management database was not running on the indicated local node, but was running on the remote node. CVU could not connect to the management database instance running on the remote node to get the required free space for Oracle base location.
- PRVG-12993: ASM is not running on any of the nodes. Verification cannot proceed.
-
Cause: No ASM instance was found running on any of the nodes while attempting to perform ASM health checks.
- PRVG-13001: target XML file "{0}" for task definition not found
-
Cause: An attempt to retrieve the task definition failed because the target XML file was missing.
- PRVG-13122: encountered error in copying file "{0}" from node "{1}" to node "{2}"
-
Cause: An error was encountered while attempting to copy the indicated file from the indicated source node to the indicated destination node.
- PRVG-13123: File "{0}" does not exist on following nodes: {1}.
-
Cause: File specified did not exist on the nodes listed, but exists on other nodes.
- PRVG-13125: unable to create the directory "{0}".
-
Cause: An attempt by CVU to create the indicated directory failed on the local node.
- PRVG-13126: unable to delete files from directory "{0}".
-
Cause: An attempt by CVU to remove files from the indicated directory failed.
- PRVG-13127: unable to read file "{0}" copied to local scratch area from node {1}.
-
Cause: An error occurred while attempting to read the indicated file.
- PRVG-13159: On node "{0}" the file "/etc/resolv.conf" could not be parsed because the file is empty.
-
Cause: Pre-requisite checking for Oracle grid infrastructure install failed
- PRVG-13167: File access control is enabled for ASM disk groups "{0}".
-
Cause: The ASM disk group property ACCESS_CONTROL.ENABLED was set to TRUE for the indicated ASM disk groups
- PRVG-13168: failed to determine the value of ASM disk group property ACCESS_CONTROL.ENABLED
-
Cause: An ASM query failed unexpectedly.
- PRVG-13201: Internal error: {0}
-
Cause: An internal error occurred. The included value is an internal identifier.
- PRVG-13202: Stage verification is not supported for cluster of type '{0}'.
-
Cause: Cluster stage verification could not proceed because verificatlion is not possible for clusters of the indicated type.
- PRVG-13203: Component verification is not supported for cluster of type '{0}'.
-
Cause: Cluster component verification could not proceed because verificatlion is not possible for clusters of the indicated type.
- PRVG-13204: stage verification not possible for cluster type '{0}'.
-
Cause: Cluster stage verification could not proceed because verification was not possible for clusters of the indicated type. Requested verification applicable on Oracle Flex Cluster.
- PRVG-13210: invalid request for SCAN component check for an Oracle Clusterware Application Cluster
-
Cause: SCAN component verification was requested for an Oracle Application Cluster.
- PRVG-13211: invalid request for node applications check for an Oracle Clusterware Application Cluster
-
Cause: Node application verification was requested for an Oracle Clusterware Application Cluster.
- PRVG-13215: CVU 'header.xml' not found in the report zip file.
-
Cause: The Cluster Verification Utility (CVU) baseline report could not be read because the 'header.xml' was not found in the report zip file.
- PRVG-13301: The CRSD process identifier (PID) is not available in release "{0}".
-
Cause: An attempt to retrieve the process identifier for the CRSD process failed because the operation was not available in releases prior to 11.2.0.3.
- PRVG-13330: error getting the version of 'cvuqdisk' on node "{0}"
-
Cause: An attempt to retrieve the version of 'cvuqdisk' failed on the specified node.
- PRVG-13331: could not locate the disk for path "{0}"
-
Cause: An attempt to locate the disk for the specified path failed.
- PRVG-13332: could not find any disk configured in partion file "{0}"
-
Cause: An attempt to retrieve the list of disks found no disk configured in the indicated partition file.
- PRVG-13333: Path "{0}" is not a valid device path.
-
Cause: The indicated path does not end with a valid disk name.
- PRVG-13334: Path "{0}" is of unknown device type.
-
Cause: The type of the device path could not be determined.
- PRVG-13335: could not determine the version of OCFS on node "{0}"
-
Cause: The OCFS installation directories were not found on the indicated node.
- PRVG-13336: Path "{0}" is an invalid file system path.
-
Cause: The indicated path was neither a directory path nor a regular file path.
- PRVG-13337: error getting details of block device on node "{0}"
-
Cause: An attempt to retrieve the details of the block device failed on the indicated node.
- PRVG-13338: format error in partition file "{0}" for the entry "{1}"
-
Cause: An attempt to read the indicated partition file failed because the indicated entry could not be parsed.
- PRVG-13339: could not resolve the path "{0}" on node "{1}"
-
Cause: The indicated path could not be resolved to produce an absolute pathname.
- PRVG-13351: The virtual memory manager tunable parameter "{0}" does not have expected "CUR" value on nodes "{1}" [Expected = "{2}"]
-
Cause: The identified parameter did not have the expected "CUR" value on the indicated nodes.
- PRVG-13356: The processor scheduler manager tunable parameter "{0}" does not have expected "CUR" value on nodes "{1}" [Expected = "{2}"]
-
Cause: The identified parameter did not have the expected "CUR" value on the indicated nodes.
- PRVG-13357: The processor scheduler manager tunable parameter "{0}" does not have expected "DEF" value on nodes "{1}" [Expected = "{2}"]
-
Cause: The identified parameter did not have the expected "DEF" value on the indicated nodes.
- PRVG-13358: The processor scheduler manager tunable parameter "{0}" does not have expected "BOOT" value on nodes "{1}" [Expected = "{2}"]
-
Cause: The identified parameter did not have the expected "BOOT" value on the indicated nodes.
- PRVG-13362: The loopback network interface configured with an IPv4 address was not found on nodes "{0}".
-
Cause: The Cluster Verification Utility determined that there was no loopback network interface configured with an IPv4 address "127.0.0.1/8" on the indicated nodes.
- PRVG-13363: The loopback network interface configured with an IPv6 address was not found on nodes "{0}".
-
Cause: The Cluster Verification Utility determined that there was no loopback network interface configured with an IPv6 address "::1/128" on the indicated nodes.
- PRVG-13373: The failure flag parameter "{0}" status is panic in the file "{1}" on nodes: "{2}".
-
Cause: The failure flag parameter value was set to 2 in the identified file on the indicated nodes.
- PRVG-13374: The following lines in file "{0}" could not be parsed on node "{1}" as they are not in proper format:\n{2}
-
Cause: Invalid lines were found in the indicated file on the indicated node.
- PRVG-13381: File "{0}" does not have required permissions for group on node "{1}". [Expected = "{2}" ; Found = "{3}"].
-
Cause: The indicated file was found with incorrect permissions for group on the indicated node.
- PRVG-13382: File "{0}" does not have required permissions for others on node "{1}". [Expected = "{2}" ; Found = "{3}"].
-
Cause: The indicated file was found with incorrect permissions for others on the indicated node.
- PRVG-13383: There are fewer than the recommended number of voting files in ASM disk group "{0}" of redundancy "{1}". [Expected = "{2}" ; Found = "{3}"].
-
Cause: The Cluster Verification Utility determined that one or more disks used for voting files in the indicated ASM disk group are offline.
- PRVG-13400: Oracle Clusterware is not configured on nodes "{0}".
-
Cause: The Cluster Verification Utility (CVU) found that Oracle Clusterware had not been configured on the indicated nodes.
- PRVG-13410: The upgrade state of Oracle Clusterware is not as expected to allow upgrade or patch operation. [Expected = "{0}" ; Found = "{1}"]
-
Cause: The Cluster Verification Utility (CVU) pre-check found that Oracle Clusterware was in the middle of some other operation with the indicated state. An upgrade or a patch application could not be performed in the indicated state.
- PRVG-13411: Oracle Clusterware active patch level "{0}" does not match software patch level "{1}" on node "{2}".
-
Cause: The Cluster Verification Utility (CVU) found that the indicated Oracle Clusterware active patch level did not match the indicated software patch level on the indicated node. The patching operation was either in progress or not complete on all the nodes.
- PRVG-13412: Oracle Clusterware active patch level "{0}" value in Oracle Cluster Registry (OCR) does not match the value in Oracle Local Registry (OLR) on node "{2}".
-
Cause: The Cluster Verification Utility (CVU) found that the indicated Oracle Clusterware active patch level values in OCR and OLR did not match. The patching operation was either in progress or not complete on the indicated node.
- PRVG-13600: Query of NTP daemon for its time sources could not be performed on all nodes on which NTP daemon was running.
-
Cause: An attempt to query the NTP daemon for its time sources failed on all the nodes of the cluster because the 'ntpq' command could not be executed successfully. The accompanying messages provide detailed failure information.
- PRVG-13601: Query of NTP daemon for its time sources could not be performed on node "{0}".
-
Cause: An attempt to query the NTP daemon for its time sources failed on the indicated node because the 'ntpq' command could not be executed successfully. The accompanying messages provide detailed failure information.
- PRVG-13602: NTP daemon is not synchronized with any external time source on node "{0}".
-
Cause: The output of the command 'ntpq -pn' executed on the indicated node did not list any external NTP daemon synchronization time source. The values of the tally code and 'refid' columns in the command output reported that the NTP daemon is either not synchronized with any time source or it is synchronized with a locally connected reference clock.
- PRVG-13604: Query of chrony daemon for its time sources could not be performed on all nodes on which chrony daemon was running.
-
Cause: An attempt to query the chrony daemon for its time sources failed on all the nodes of the cluster because the 'chronyc sources' command could not be executed successfully. The accompanying messages provide detailed failure information.
- PRVG-13605: Query of chrony daemon for its time sources could not be performed on node "{0}".
-
Cause: An attempt to query the chrony daemon for its time sources failed on the indicated node because the 'chronyc sources' command could not be executed successfully. The accompanying messages provide detailed failure information.
- PRVG-13606: chrony daemon is not synchronized with any external time source on node "{0}".
-
Cause: The output of the command 'chronyc sources' executed on the indicated node did not list any external chrony daemon synchronization time source. The values of the mode and state columns in the command output reported that the chrony daemon is either not synchronized with any time source or is synchronized with a locally connected reference clock.
- PRVG-13609: The path "{0}" resolving to storage of type "{1}" is not suitable for usage as Oracle Clusterware software for release "{2}". Supported storage types are "{3}".
-
Cause: The Cluster Verification Utility check for storage suitability determined that the storage of the indicated type designated by the indicated path was not suitable for usage as Oracle Clusterware software.
- PRVG-13610: No shared storage was found on nodes "{0}".
-
Cause: The Cluster Verification Utility shared storage discovery did not find any shared storage on the indicated nodes.
- PRVG-13620: Node application "{0}" is offline on node "{1}".
-
Cause: The indicated node application was found to be offline on the indicated node.
- PRVG-13631: IP address for host "{0}" is not consistent across the cluster nodes.
-
Cause: The Cluster Verification Utility determined that the indicated host did not resolve to the same IP address across the cluster nodes. The indicated host entry in the hosts file or DNS did not resolve to the same IP address across the cluster nodes.
- PRVG-13632: Host "{0}" resolves to IP address "{1}" on the majority of cluster nodes but to address "{2}" on nodes "{3}".
-
Cause: The Cluster Verification Utility determined that the indicated host resolved to the different IP address on the indicated nodes.
- PRVG-13633: Entry for non-loopback IP addresses "{0}" contains 'localhost' alias in the file "{1}" on node "{2}".
-
Cause: An attempt to validate the hosts file failed because non-loopback IP address entries were found with the 'localhost' alias in the indicated file on the indicated node.
- PRVG-13634: Host VIP "{0}" resolves to multiple IP addresses "{1}" on node "{2}".
-
Cause: The Cluster Verification Utility determined that the indicated host VIP resolved to more than one IP address on the indicated node.
- PRVG-13635: Host VIP "{0}" of network type "{1}" resolves to more than two IP addresses "{2}" on node "{3}".
-
Cause: The Cluster Verification Utility determined that the indicated host VIP resolved to more than two IP addresses on the indicated node.
- PRVG-13645: Command "{0}" to get VIP network information failed.
-
Cause: An attempt to execute the indicated command failed.
- PRVG-13646: failed to parse VIP network information from the 'cvuhelper' command output
-
Cause: An attempt to parse the output from an internal cvuhelper command failed.
- PRVG-13690: The state of Oracle Clusterware is not ONLINE on node "{0}". [Found state = "{1}"]
-
Cause: The Cluster Verification Utility (CVU) determined that the Oracle Clusterware state is not ONLINE on the indicated node.
- PRVG-13702: RPM Package Manager database files are corrupt on nodes "{0}".
-
Cause: The Cluster Verification Utility (CVU) determined that the RPM Package Manager database files were corrupt on the indicated nodes.
- PRVG-13712: CRS resource parameter "{0}" set to "{1}" on node "{2}". Oracle Clusterware does not allow starting resources on this node. [Expected = "{3}"]
-
Cause: The Cluster Verification Utility (CVU) determined that the indicated Cluster Ready Services (CRS) resource parameter did not match the expected value on the indicated node.