PRVG-00219 to PRVG-12887

138 PRVG-00219 to PRVG-12887

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.; Action: Make sure that the specified user exists in the database, account is unlocked and the supplied password is correct.
PRVG-00221: Cannot launch browser to display the report. Check if the DISPLAY variable is set.: Cause: DISPLAY environment variable is not set; Action: set DISPLAY
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.; Action: Examine the accompanying error message for details.
PRVG-00258: Baseline collection for database "{0}" failed.: Cause: An error occurred while collecting baseline for the database.; Action: Examine the accompanying messages for details on the cause of failure.
PRVG-00277: Specified ASM disk group name is null or an empty string: Cause: Internal error.; Action: Contact Oracle Support Services.
PRVG-00278: ASM disk group name cannot contain wildcards: Cause: Internal error.; Action: Contact Oracle Support Services.
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.; Action: Ensure that the nodes are reachable and the user running this command has required privileges on the nodes identified.
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.; Action: Stop any applications listening on the indicated port on the identified 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.; Action: Ensure that the required login shell settings for current user are correct on the indicated nodes.
PRVG-00360: Location "{0}" file system is not NFS: Cause: An existing file system other than NFS was found on the specified location.; Action: Ensure that the specified location has either an NFS file system or no file system.
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.; Action: Ensure that the file system is mounted with the correct options, Refer the Grid Infrastructure Installation Guide for detailed information on NFS mount options requirement.
PRVG-00540: An incorrect value was specified for "{0}": Cause: Incorrect value was specified for the identified command line option.; Action: Ensure that the correct value is 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.; Action: Ensure that current user has required privileges to access 'ocrdump'.
PRVG-00551: The OCR key "{0}" was not found in OCR: Cause: Could not find the specified OCR key in OCR.; Action: Ensure that current user has required privileges to access 'ocrdump'.
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.; Action: Ensure that the correct '-dest_version' was specified.
PRVG-00602: Failed to retrieve database version of database home "{0}": Cause: An error occurred while retrieving database version of the database home.; Action: Look at the accompanying messages for details on the cause of failure.
PRVG-00700: Invalid target hub size: Cause: An invalid target hub size was specified; Action: Specify a valid target hub size
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.; Action: Start the stack 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.; Action: Start the stack on the local node using the command 'crsctl start crs'.
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.; Action: Start the stack on the local node using the command 'crsctl start crs'.
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.; Action: Start the stack on the local node using the command 'crsctl start crs'.
PRVG-01001: Insufficient number of arguments while executing "{0}": Cause: An attempt was made to execute the specified script with insufficient number of arguments.; Action: This is an internal error. Contact Oracle Support Services.
PRVG-01002: Command "{0}" to obtain SCAN configuration failed: Cause: An attempt to execute the displayed command failed.; Action: This is an internal error. Contact Oracle Support Services.
PRVG-01003: Command "{0}" to check if OCR locations are on shared storage failed: Cause: An attempt to execute the displayed command failed.; Action: This is an internal error. Contact Oracle Support Services.
PRVG-01004: Command "{0}" to obtain GNS domain and GNS-VIP configuration failed: Cause: An attempt to execute the displayed command failed.; Action: This is an internal error. Contact Oracle Support Services.
PRVG-01005: Command "{0}" to obtain GNS and GNS-VIP status failed: Cause: An attempt to execute the displayed command failed.; Action: This is an internal error. Contact Oracle Support Services.
PRVG-01006: Command "{0}" to check if ASM instance is running failed: Cause: An attempt to execute the displayed command failed.; Action: This is an internal error. Contact Oracle Support Services.
PRVG-01007: Command "{0}" to get ASM disk groups configured on local node failed: Cause: An attempt to execute the displayed command failed.; Action: This is an internal error. Contact Oracle Support Services.
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.; Action: Look at the error messages that accompany this message.
PRVG-01009: Command "{0}" to obtain SCAN name failed: Cause: An attempt to execute the displayed command failed.; Action: This is an internal error. Contact Oracle Support Services.
PRVG-01010: Command "{0}" to obtain configuration of network resource for network number {1} failed: Cause: An attempt to execute the displayed command failed.; Action: This is an internal error. Contact Oracle Support Services.
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.; Action: Make sure the existing cluster nodes have the same CRS software version installed before trying to add another node to the cluster.
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.; Action: The CRS home must be shared by all nodes or by none.
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.; Action: Ensure that the path identified either exists or can be created.
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.; Action: Ensure that the offsets for specified time server are within limits on each node of the cluster.
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 Clustware was attempted.; Action: Ensure that the Clusterware has been correctly installed and configured before attempting the check.
PRVG-01017: NTP configuration file is present on nodes "{0}" on which NTP daemon or service was not running: Cause: NTP configuration file was found on specified nodes where the NTP daemon or service was not running.; Action: NTP configuration must be uninstalled on all nodes of the cluster.
PRVG-01018: NTP daemon or service was running on nodes "{0}" on which NTP configuration file was not found: Cause: NTP daemon or service was running on specified nodes on which no NTP configuration file was found.; Action: NTP configuration must be uninstalled on all nodes of the cluster.
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.; Action: To use NTP for time synchronization, create this file and set up its configuration as described in your vendor's NTP document. To use CTSS for time synchronization the NTP configuration should be uninstalled on all nodes of the cluster. Refer to section "Preparing Your Cluster" of the book "Oracle Database 2 Day + Real Application Clusters Guide".
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.; Action: Look at the accompanying error messages and respond accordingly.
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.; Action: To use NTP for time synchronization, create this file and set up its configuration as described in your vendor's NTP document on all nodes of the cluster. If you plan to use CTSS for time synchronization then NTP configuration should be uninstalled on all nodes of the cluster. Refer to section "Preparing Your Cluster" of the book "Oracle Database 2 Day + Real Application Clusters Guide".
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.; Action: Look at the accompanying error messages and respond accordingly.
PRVG-01025: Validation of the state of the GNS server and DNS domain delegation failed from the client cluster.: Cause: Proper functioning of the GNS server cluster could not be validated using client data file for the GNS client cluster. Possibly GNS is not up on the server cluster, or the DNS domain is not delegated to the GNS server cluster.; Action: Examine the accompanying error messages and respond accordingly to ensure that GNS is up on the GNS server cluster and that the domain delegation is operating correctly. The integrity of GNS can be validated by executing the command 'cluvfy comp gns -postcrsinst' on 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.; Action: Ensure that the node being added is not part of another cluster before attempting to add the node to this cluster.
PRVG-01030: Command "{0}" to get ASM home failed: Cause: An attempt to execute the displayed command failed.; Action: This is an internal error. Contact Oracle Support Services.
PRVG-01031: Command "{0}" executed to get ASM SID failed: Cause: An attempt to execute the displayed command failed.; Action: This is an internal error. Contact Oracle Support Services.
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.; Action: Shut down and restart the NTP Daemon with the slewing option set. In each case add -x to the NTPD command line options. For Linux, edit /etc/sysconfig/ntpd. For SUSE Linux, edit /etc/sysconfig/ntp and add -x to the OPTIONS variable. For AIX, edit /etc/rc.tcpip. For HP-UX edit /etc/rc.config.d/netdaemons. For Solaris release 10 or earlier, edit /etc/inet/ntp.conf. For Solaris release 11, set the 'slew_always' property by running the command '/usr/sbin/svccfg -s svc:/network/ntp:default setprop config/slew_always = true' as root user and refresh the service by running the command 'svcadm refresh svc:/network/ntp:default'.
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.; Action: Ensure that the specified nodes are accessible. Make sure that the NTP Daemon is running on the specified nodes. Also, look at other messages accompanying this message.
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.; Action: Ensure that the slewing option is set in the configuration file on the nodes specified. For more information on the NTP Daemon slewing option, refer to NTP Daemon manual pages.
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.; Action: Ensure that the user running this check has access to the configuration file specified. Also, look at other messages accompanying this message.
PRVG-01050: Voting disk locations with the voting disk identification numbers "{0}" are offline.: Cause: Voting disk locations were found to be offline.; Action: Voting disk must be brought online or should be removed from the configuration by executing 'crsctl delete css votedisk <varname>vdiskGUID</varname> [...]'.
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.; Action: Start the Oracle Clusterware stack on at least one hub node.
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.; Action: Ensure that the user executing the CVU check has read permission for the indicated CRS or Oracle Restart home and that the indicated CRS home path is not left over due to partial clean-up of any previous CRS installation attempts.
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.; Action: Ensure the 'hosts' entries define the same lookup order in the name service switch configuration file across all cluster nodes.
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'.; Action: Check whether the specified SCAN name is correct. If SCAN name should be resolved in DNS, check the configuration of SCAN name in DNS. If it should be resolved in GNS make sure that GNS resource is online.
PRVG-01102: Command "{0}" to get network information failed.: Cause: An attempt to execute the displayed command failed.; Action: Examine the accompanying error messages for details. Address issues found and retry the command.
PRVG-01103: Command "{0}" to get OCR information failed.: Cause: An attempt to execute the displayed command failed.; Action: Examine the accompanying error messages for details.
PRVG-01104: Unable to create the directory "{0}": Cause: An attempt to create the directory specified failed on local node.; Action: Ensure that the user running CVU has read and write access to the specified directory, or set the CV_DESTLOC environment variable to a different directory to which the user has read and write access.
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.; Action: Examine the accompanying error message for details.
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.; Action: Use the 'ocrconfig -repair' utility to repair the OCR locations 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.; Action: Use the 'ocrconfig -repair' utility to repair the OCR locations on the specified node.
PRVG-01108: Failed to check OCR locations consistency on node "{0}": Cause: An attempt to verify OCR locations failed.; Action: Look at the accompanying messages for details on the cause of failure.
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.; Action: Contact Oracle Support Services.
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.; Action: Contact Oracle Support Services.
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.; Action: Look at the accompanying messages for details on the cause of failure.
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; Action: add 'ezconnect' to names.directory_path entry in the sqlnet.ora
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; Action: add 'ezconnect' to names.directory_path entry in the sqlnet.ora
PRVG-01155: Easy Connect configuration could not be determined.: Cause: Easy Connect configuration check could not be completed; Action: Contact Oracle Support Services.
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.; Action: Make the kernel run in 64-bit mode on the cluster node. This might involve setting up the symlink /unix -> /usr/lib/boot/unix_64 and rebooting the 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.; Action: Run the command '/usr/sbin/prtconf -k' manually and follow the command output to fix any issues associated ith its execution.
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.; Action: Ensure that the private host name is configured correctly, use 'oifcfg' tool to classify the subnet containing the private IPs as private using 'oifcfg setif -global <if_name>/<varname>subnet</varname>:cluster_interconnect' command.
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.; Action: Ensure that the identified private host name can be resolved to a private IP address.
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.; Action: Remove the given IP address from all but one interface on each node.
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.; Action: Ensure that the OS user upgrading database installation is the owner of the already existing 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.; Action: Ensure that the OS user executing the CVU check has read permission for database.
PRVG-01191: Failed to check existence of ASM resource: Cause: An attempt to verify existence of ASM resource failed.; Action: Look at the accompanying messages for details on the cause of failure.
PRVG-01192: ASM (pre-11.2) is not at the same version as CRS version {0}: Cause: The ora.asm resource was not found.; Action: Ensure that ASM Configuration Assistant 'asmca -upgradeASM' has been run and ASM has been upgraded.
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.; Action: Specify -dest_version greater than or equal to 11.2.0.1.0.
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.; Action: Modify the kernel parameter configured value to meet the requirement.
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.; Action: Modify the kernel parameter current value to meet the requirement.
PRVG-01206: Check cannot be performed for configured value of kernel parameter "{0}" on node "{1}": Cause: Kernel parameter value could not be determined.; Action: Examine the accompanying error message for details.
PRVG-01253: Required Oracle patch is not found on node "{0}" in home "{1}".: Cause: Required Oracle patch is not applied.; Action: Apply the required Oracle patch.
PRVG-01254: Failed to determine Oracle patch status on the node "{0}": Cause: Oracle patch status could not be determined.; Action: Ensure that OPatch is functioning correctly.
PRVG-01260: Command "{0}" to obtain Oracle patch status failed: Cause: An attempt to execute the displayed command failed.; Action: This is an internal error. Contact Oracle Support Services.
PRVG-01265: Failed to determine operating system patch status for patch "{1}" on node "{0}": Cause: Unable to determine the patch existence.; Action: Manual o/s verification required. Contact IBM support for assistance if needed.
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.; Action: Upgrade to a supported version before proceeding to upgrade to the specified version.
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.; Action: Ensure that all listed or discovered device paths point to distinct physical devices.
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.; Action: Ensure that ACFS file system is correctly created on the specified location.
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.; Action: None
PRVG-01359: Daemon process "{0}" is configured on node "{1}": Cause: The identified daemon process was found configured on the indicated node.; Action: Ensure that the identified daemon process is not 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.; Action: Ensure that the identified daemon process is stopped and not running on the indicated node.
PRVG-01450: Oracle Clusterware is not installed on nodes "{0}".: Cause: A valid Oracle Clusterware installation was not found on the specified nodes.; Action: Ensure that Oracle Clusterware is installed on the nodes before running this check.
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.; Action: Ensure that the command specified exists and the current user has execute permission.
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.; Action: Check the status of the Oracle CTSS resource using the command 'crsctl check ctss'. If CTSS is not running then restart the Clusterware stack.
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.; Action: Look at the accompanying error messages and respond accordingly.
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.; Action: Look at the accompanying error messages and respond accordingly.
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.; Action: Look at the accompanying error messages and respond accordingly.
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.; Action: Look at the accompanying error messages and respond accordingly.
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.; Action: Ensure that all the identified non-participating network interfaces in the IPMP group are classified as a cluster interconnect on the identified node. Use command 'oifcfg setif -global <if_name>/<varname>subnet</varname>:cluster_interconnect' to classify the network interface as private.
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.; Action: Ensure that all the identified non-participating network interfaces in the IPMP group are classified as public network interface on the identified node. Use command 'oifcfg setif {-node <varname>nodename</varname> | -global} {<if_name>/<varname>subnet</varname>:public}' to classify the network interface as public.
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.; Action: Ensure that current user has required privileges to retrieve IPMP configuration information if IPMP is required to be configured on the cluster nodes.
PRVG-01511: Failed to get IPMP configuration information from node "{0}": Cause: Failed to retrieve the information about IPMP configuration from identified node.; Action: Ensure that current user has required privileges to retrieve IPMP configuration information if IPMP is required to be configured on the 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.; Action: Ensure that the configuration of public and private network classifications is done correctly during the installation process.
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.; Action: Ensure that the configuration of public and private network classifications is done correctly during the installation process.
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.; Action: Install and configure the program if necessary, then start it.
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.; Action: Ensure that the node is accessible and IPMP configuration on the node is correct.
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.; Action: Review the messages that accompany this message and fix the problem(s) on the indicated nodes.
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.; Action: Ensure that the IPMP configuration for the indicated network interface is correct and that the NIC configuration file at the identified path exists.
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.; Action: Ensure that the IPMP configuration for the indicated network interface is correct and that the NIC configuration file at the identified path exists.
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.; Action: Ensure that none of the classified IPMP interfaces have the deprecated flag set to ensure the correct functioning of IPMP on the 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.; Action: Ensure that none of the classified IPMP interfaces have the deprecated flag set to ensure the correct functioning of IPMP 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.; Action: If HAIP support is required then ensure that only non-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.; Action: If HAIP support is required then ensure that only non-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.; Action: If IPMP interfaces are classified as public network for the clusterware configuration then all the configured interfaces must belong to same subnet.
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.; Action: If IPMP interfaces are classified as public network for the clusterware configuration then all the configured interfaces must belong to same subnet.
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.; Action: If IPMP interfaces are classified as private interconnection for the clusterware configuration then all the configured interfaces must belong to same subnet.
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.; Action: If IPMP interfaces are classified as private interconnection for the clusterware configuration then all the configured interfaces must belong to same subnet.
PRVG-01543: The IPMP interfaces "{0}" share MAC or hardware address on node "{1}": Cause: The identified interfaces were found to share the same MAC or hardware address on indicated node.; Action: If an IPMP interface is classified as private or public network then it must have a unique MAC or hardware address configured.
PRVG-01544: Some or all of the IPMP interfaces share MAC or hardware address on nodes "{0}": Cause: The IPMP interfaces were found to share the same MAC or hardware address on indicated nodes.; Action: If an IPMP interface is classified as private or public network then it must have a unique MAC or hardware address configured.
PRVG-01545: Some of the IPMP group interfaces are not classified as private or public network interfaces on nodes "{0}": Cause: Found an additional fail-over dependency on an interface in an IPMP group which is not classified as a public or private interconnect interfaces on the identified nodes.; Action: Ensure that all the IPMP group interfaces are classified as public or private interconnect interfaces on the identified nodes. Use command 'oifcfg setif {-node <varname>nodename</varname> | -global} {<if_name>/<varname>subnet</varname>:public/cluster_interconnect}' to classify the network interface as public or private interconnect interface.
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.; Action: Ensure that the configuration of public and private network classifications is specified correctly in the 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.; Action: Ensure that the configuration of private network classifications is done correctly 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.; Action: Ensure that the configuration of public network classifications is done correctly 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.; Action: Ensure that the temporary directory path is not shared between the nodes specified.
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.; Action: Unset environment variable ORA_CRS_HOME.
PRVG-01600: ASM network not specified: Cause: An ASM network was not specified when ASM presence was 'flex'.; Action: Make sure that there is at least one network of type 'ASM' or 'ASM-PRIV' selected in the Network Interface dialog screen of Oracle Universal Installer.
PRVG-01601: ASM network was not configured: Cause: An attempt to verify if the ASM network was configured failed when ASM presence was 'flex'.; Action: Make sure that there is at least one ASM network configured using the 'oifcfg setif' command.
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.; Action: Make sure that the path to specified file is correct. Also look at accompanying messages and respond accordingly.
PRVG-01605: Failed to validate ASM credentials: Cause: An attempt to verify ASM credentials are valid failed.; Action: Look at the accompanying messages and respond accordingly.
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.; Action: Look at the accompanying messages and respond accordingly.
PRVG-01611: ASM network not specified: Cause: An ASM network was not specified when ASM presence was 'flex'.; Action: Make sure that there is at least one ASM network specified using the -networks command line parameter.
PRVG-01612: ASM disk groups could not be retrieved: Cause: During ASM integrity verification, an attempt to retrieve ASM disk groups failed.; Action: Look at the accompanying messages and respond accordingly.
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.; Action: Ensure that the ASM disk group is correctly configured with valid disk paths and that the ASM filter driver if used lists the associated devices for this disk group when the command 'afdtool -getdevlist' is issued. If ASM filter driver is not in use then ensure that the ASM kfod command 'kfod op=DISKS disks=all dscvgroup=TRUE' lists the associated disks for the indicated ASM disk group.
PRVG-01650: failed to create required native library context.: Cause: An attempt to initialize a required native library context failed.; Action: Ensure that the Grid user has write authority on Oracle base path.
PRVG-02000: "search" entry in the existing "{0}" files is inconsistent: Cause: A check of nodes' resolv.conf files found inconsistent 'search' entries.; Action: Make sure that all nodes of the cluster have same 'search' entry in the file specified.
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.; Action: Examine the accompanying error message for details.
PRVG-02012: "domain" entry in the existing "{0}" files is inconsistent: Cause: A check of nodes' resolv.conf files found inconsistent 'domain' entries.; Action: Make sure that all nodes of the cluster have same 'domain' entry in the file specified.
PRVG-02016: "search" and "domain" entries coexist in file "{0}" on node "{1}": Cause: Both 'search' and 'domain' entries were found in resolv.conf file on the node specified.; Action: Make sure that only one of these entries exist in file resolv.conf. It is preferable to use entry 'search' in resolv.conf.
PRVG-02019: Check for equivalence of user "{0}" from node "{1}" to node "{2}" failed: Cause: User equivalence doesn't exist between the specified nodes.; Action: Ensure that user equivalence exists between the specified nodes.
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.; Action: Deconfigure Grid Infrastructure and reconfigure it.
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.; Action: Make sure that all DNS servers specified in the file 'resolv.conf' respond to all the nodes.
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.; Action: Change the owner of the indicated file to ensure it is the same on all 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.; Action: Change the group of the indicated file to ensure it is the same on all 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.; Action: Change the permissions of the indicated file to ensure they are the same on all 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.; Action: Ensure that the file exists on the system and user has permissions to retrieve the details of specified file.
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.; Action: Change the owner of the indicated file to match 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.; Action: Change the group of the indicated file to match 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.; Action: Change the permissions of the indicated file to match 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.; Action: Respond based on the failing command and the reported 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.; Action: Respond based on the failing command and the reported 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.; Action: Check the status of OLR using the command 'ocrcheck -config -local' on the indicated node.
PRVG-02043: Command "{0}" failed on node "{1}" and produced the following output:: Cause: An executed command failed.; Action: Respond based on the failing command and the reported results.
PRVG-02044: Command "{0}" failed on node "{1}" and produced no output.: Cause: An executed command failed.; Action: Respond based on the failing command.
PRVG-02045: Operating system function "{0}" failed on node "{1}" with error data: "{2}".: Cause: A call to an Operating System dependent service or function returned an error indication. The message includes the name of the function and the returned error data. The latter varies by platform but typically is numeric; on most platforms it is the value of C "errno" after the failing call.; Action: This error normally is accompanied by other (higher-level) messages describing the operation that is affected by the failure. It may also include one or more of messages PRVG-2046 and PRVG-2047 providing additional error details. All of the messages should be examined to assess the error, which may have a very ordinary cause and correction, such as an input file failing to open because the supplied name was misspelled.
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. On most Oracle platforms the message is a text representation of the C "errno" value reported in message PRVG-2045.; Action: See message PRVG-2045.
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.; Action: See message PRVG-2045.
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.; Action: Remove the obsolete DNS servers specified in the file 'resolv.conf'.
PRVG-02052: "hosts" entry does not exist in file "{0}" on nodes: "{1}": Cause: The 'hosts' entry was not found in the specified name service switch configuration file on nodes indicated while it was present in others.; Action: Look at the file specified on all nodes. Make sure that either 'hosts' entry is defined on all nodes or is not defined on any nodes.
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.; Action: Make sure that the file specified has only one 'hosts' entry.
PRVG-02058: "hosts" entry in the existing "{0}" files is inconsistent: Cause: A check of nodes' name service switch configuration files found inconsistent 'hosts' entries.; Action: Make sure that all nodes of the cluster have same 'hosts' entry in the file specified.
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.; Action: Ensure that the disks underlying the disk group are accessible from 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.; Action: Ensure that the disks underlying the disk group are accessible from the specified node.
PRVG-04000: Windows registry key "{0}" is absent on node "{1}": Cause: Could not find the specified Windows registry key on the identified node.; Action: Contact Oracle Support Services.
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.; Action: Look at the accompanying messages and respond accordingly.
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.; Action: Specify a user name using the '-user' option following the privilege delegation method on the command line.
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.; Action: Contact Oracle Support Services.
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.; Action: Specify either the Windows user 'nt authority\\local system' or a Windows domain user without administrative privilege 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.; Action: Specify either the Windows user 'nt authority\\local system' or a Windows domain user without administrative privilege 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.; Action: Make sure that the Windows user name specified as service user is not an administrator on any of the nodes.
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.; Action: Make sure that the Windows user name and password specified are correct.
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.; Action: Examine the accompanying error messages for details.
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.; Action: Examine the accompanying error messages for details.
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.; Action: Examine the accompanying error messages for details.
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.; Action: Use the command 'crsctl modify wallet -type OSUSER' to update the password in the wallet for the specified user.
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.; Action: Examine the accompanying error messages for details.
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.; Action: Examine the accompanying error messages for details.
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.; Action: Add the specified Windows user to the specified Windows group using the 'net group' command.
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.; Action: Examine the accompanying error messages for details.
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.; Action: Grant full control to the directory specified to the Windows user specified on the nodes specified. Use Windows Explorer or a comparable mechanism to grant full control.
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.; Action: Grant full control to the file specified to the Windows user specified on the nodes specified. Use Windows Explorer or a comparable mechanism to grant full control.
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.; Action: Grant full control to the Windows registry key specified to the Windows user specified on the nodes specified. Use Windows registry tool to grant permissions.
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.; Action: Examine the accompanying error messages for details.
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.; Action: Examine the accompanying error messages for details.
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.; Action: Examine the accompanying error messages for details.
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.; Action: Ensure that the upgrade is performed on one of the indicated nodes on which the ASM instance is currently configured and running.
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.; Action: Ensure that the default listener, if configured, is running on the node on which the upgrade is being performed.
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.; Action: Ensure that the ASM instance, if configured, is correctly configured and an ASM instance is up and running on one of the cluster nodes.
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.; Action: Ensure that the default listener, if configured, for the node on which upgrade is requested is correctly configured and is running from the node.
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.; Action: Ensure that there is at least 1GB space in the location where the file is being created. Ensure that the user executing the check has write permission at the specified location.
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.; Action: Ensure that the ASM instance is configured using an existing ASM parameter file, SPFILE or PFILE, on the indicated node.
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.; Action: Ensure that the ASM instance is configured using an existing ASM parameter file, SPFILE or PFILE, on the indicated node.
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.; Action: Ensure that the nodes specified have node VIPs that are configured but not in use.
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.; Action: Ensure that the node VIPs for the nodes specified have VIP's that are not active.
PRVG-04610: Nodes "{0}" do not have VIPs configured: Cause: It was found that specified hub nodes do not have node VIPS configured.; Action: Ensure that the nodes specified have node VIPs that are configured but not in use.
PRVG-04611: Node VIPs for nodes "{0}" are active: Cause: The VIPs for the specified hub nodes were found to be reachable.; Action: Ensure that the node VIPs for the nodes specified have VIP's that are not reachable using ping.
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.; Action: Use the command 'asmcmd dsset' to set the ASM discovery string to the correct value in both places.
PRVG-04655: The command "{0}" to retrieve ASM discovery string failed: Cause: The specified command executed to retrieve ASM discovery string failed.; Action: Look at the accompanying messages and respond accordingly.
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.; Action: Look at the accompanying messages and respond accordingly.
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.; Action: Make sure that the permissions for the specified block devices matches the expected value (this will be necessary in the long run because raw devices are being deprecated). Alternatively set the string '/dev/raw/raw*' as the disk discovery path using command 'asmcmd dsset --normal <varname>discovery string</varname>' in ASM 11.2 or later, using command 'alter system set asm_diskstring=<varname>discovery string</varname> scope=spfile;' in 11.1 or earlier ASM.
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.; Action: Look at the accompanying error message and respond accordingly.
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.; Action: Make sure that the owner of the specified block devices matches the expected value (this will be necessary in the long run because raw devices are being deprecated). Alternatively set the string '/dev/raw/raw*' as the disk discovery path using command 'asmcmd dsset --normal <varname>discovery string</varname>' in ASM 11.2 or later, using command 'alter system set asm_diskstring=<varname>discovery string</varname> scope=spfile;' in 11.1 or earlier ASM.
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.; Action: Make sure that the group of the specified block devices matches the expected value (this will be necessary in the long run because raw devices are being deprecated). Alternatively set the string '/dev/raw/raw*' as the disk discovery path using command 'asmcmd dsset --normal <varname>discovery string</varname>' in ASM 11.2 or later, using command 'alter system set asm_diskstring=<varname>discovery string</varname> scope=spfile;' in 11.1 or earlier ASM.
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.; Action: Examine the accompanying error messages and correct the problem indicated.
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.; Action: Look at the accompanying messages for details on the cause of failure.
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.; Action: Make sure that the specified devices are discoverable using the new default discovery string (this will be necessary in the long run because raw devices are being deprecated). Alternatively set the string '/dev/raw/raw*' as the disk discovery path using command 'asmcmd dsset --normal <varname>discovery string</varname>' in ASM 11.2 or later, using command 'alter system set asm_diskstring=<varname>discovery string</varname> scope=spfile;' in 11.1 or earlier ASM.
PRVG-05150: could not determine if path {0} is a valid path on all nodes: Cause: Attempts to identify the device referenced by the path failed.; Action: Ensure that the path exists on all of the nodes participating in the operation and that the user has read access to '/etc/multipath.conf'.
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.; Action: Review warnings and make modifications as necessary. If the warning is due to partial upgrade of Oracle Clusterware stack then continue with upgrade and finish it.
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.; Action: Ensure that the path specified is an existing path and current user has access permission for this 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.; Action: Ensure that the path specified is an existing path and current user has access permission for this 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.; Action: No action is required.
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.; Action: Use OS commands to terminate the TCP server process with the indicated PID.
PRVG-05726: Failed to discover DHCP servers on public network listening on port "{0}" using command "{1}": Cause: An attempt to discover DHCP servers listening on public network on port specified using command specified failed.; Action: Contact the network administrator to make sure that DHCP servers exist on the network. If the DHCP servers are listening to a different port then specify it by using -port option.
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.; Action: Look at the accompanying messages for details on the cause of failure.
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.; Action: Contact the network administrator to make sure that DHCP servers exist on the network. If the DHCP servers are listening to a different port then specify it by using -port option. Make sure that DHCP servers can provide VIPs for all nodes in the cluster that can start as a 'hub' node.
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.; Action: Contact the network administrator to make sure that DHCP servers exist on the network specified. If the DHCP servers are listening to a different port then specify it by using -port option. Make sure that DHCP servers can provide VIPs for all nodes in the cluster that can start as a 'hub' node.
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.; Action: Contact the network administrator to make sure that DHCP servers exist on the network. If the DHCP servers are listening to a different port then specify it by using -port option.
PRVG-05733: Failed to discover DHCP servers on network "{2}" listening on port "{0}" using command "{1}": Cause: An attempt to discover DHCP servers listening on specified network and port using command specified failed.; Action: Contact the network administrator to make sure that DHCP servers exist on the network. If the DHCP servers are listening to a different port then specify it by using -port option.
PRVG-05736: The "{0}" command returned error "{1}": Cause: An attempt to discover DHCP servers using specified command failed. The command returned error specified.; Action: Since CVU is operating not operating from a clusterware home it does not have access to all error messages. Look at the Oracle database error messages manual for the exact error message and act accordingly.
PRVG-05737: The file "{0}" could not be copied to "{1}" on local node.: Cause: While attempting to discover DHCP servers, the specified source file could not be copied to the specified destination file on the local node. Details are provided by the accompanying messages.; Action: Examine the accompanying messages and respond accordingly.
PRVG-05740: Oracle Restart installed, requested check is not valid in this environment: Cause: A check invalid for the Oracle Restart environment was attempted.; Action: Check the documentation and use a valid command for this environment.
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.; Action: Specify the node on which Oracle Restart has been configured.
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.; Action: Try a valid check for 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.; Action: If GNS needs to be verified use 'cluvfy comp gns' command. If DNS setup needs to be checked then stop the GNS resource and start 'cluvfy comp dns -server'.
PRVG-05819: VIP address "{0}" is already in use: Cause: The identified VIP address was found to be active on the public network.; Action: Specify a VIP address that is not in use.
PRVG-05820: Failed to retrieve IP address of host "{0}": Cause: An attempt to retrieve an IP address for the indicated host failed.; Action: Run 'nslookup' on the host name and make sure the name is resolved.
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.; Action: Ensure that the indicated public subnet has at least one VIP address configured on it or deconfigure the public subnet.
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.; Action: Ensure that the indicated public subnet has at least one active public IP in addition to the identified VIP address.
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.; Action: Ensure that the clusterware is up and running and also examine the accompanying messages and respond accordingly.
PRVG-05905: Windows firewall is enabled on nodes:: Cause: Windows firewall status was found to be enabled.; Action: To disable Windows firewall, on Windows 2003 or earlier run 'netsh firewall set opmode DISABLE'; on Windows 2008 or later run 'netsh advfirewall set allprofiles state off' at command prompt as an administrator on all the indicated nodes.
PRVG-05906: Windows firewall is enabled on the node "{0}": Cause: Windows firewall status was found to be enabled.; Action: To disable Windows firewall, on Windows 2003 or earlier run 'netsh firewall set opmode DISABLE'; on Windows 2008 or later run 'netsh advfirewall set allprofiles state off' at command prompt as an administrator on the indicated node.
PRVG-05907: Windows firewall status check cannot be performed on nodes:: Cause: An attempt to determine the status of Windows firewall failed.; Action: Ensure that the access permissions for the Oracle user allow access to the Windows Registry and the registry has the REG_DWORD entry named 'EnableFirewall' with value 0 under 'HKEY_LOCAL_MACHINE\\System\\CurrentControlSet\\Services\\SharedAccess\\Parameters\\FirewallPolicy\\StandardProfile' and 'HKEY_LOCAL_MACHINE\\System\\CurrentControlSet\\Services\\SharedAccess\\Parameters\\FirewallPolicy\\DomainProfile' sub-keys on the node. It is recommended to back up the Windows Registry before proceeding with any changes. Restart your system to make your changes effective.
PRVG-05908: Windows firewall status check cannot be performed on node "{0}": Cause: An attempt to determine the status of Windows firewall failed.; Action: Ensure that the access permissions for the Oracle user allow access to the Windows Registry and the registry has the REG_DWORD entry named 'EnableFirewall' with value 0 under 'HKEY_LOCAL_MACHINE\\System\\CurrentControlSet\\Services\\SharedAccess\\Parameters\\FirewallPolicy\\StandardProfile' and 'HKEY_LOCAL_MACHINE\\System\\CurrentControlSet\\Services\\SharedAccess\\Parameters\\FirewallPolicy\\DomainProfile' sub-key on the node. It is recommended to back up the Windows Registry before proceeding with any changes. Restart your system to make your changes effective.
PRVG-05909: Error reading key "{0}" from Windows Registry on node "{1}": Cause: Specified Windows Registry key could not be read.; Action: Ensure that the specified key exists in Windows Registry and access permissions for the Oracle user allow access to the Windows Registry.
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.; Action: Ensure that the access permissions for the Oracle user allow access to the Windows Registry and the Registry value 'EnableFirewall' under specified key is present on the node.
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.; Action: Choose a different location for storing OCR.
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.; Action: Increase the size of the OCR backup location or move the OCR backup to a location with sufficient space.
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.; Action: Make sure Oracle Clusterware is up and running. Examine any accompanying error messages for details.
PRVG-06014: Failed to parse OCR dump output: "{0}": Cause: An attempt to parse OCR dump failed.; Action: Make sure Oracle Clusterware is up and running. Examine any accompanying error messages for details.
PRVG-06015: Error retrieving output of OCR dump command on node "{0}": Cause: Command 'ocrdump -stdout -xml' produced no output.; Action: Examine any accompanying error messages for details.
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.; Action: Make sure Oracle Clusterware is up and running. Examine any accompanying error messages for details.
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.; Action: Make sure Oracle Clusterware is up and running, address any issues described in accompanying error messages, and retry.
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.; Action: Choose a different location for storing Voting disk.
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.; Action: Make sure that ASM is started on enough nodes by using the 'srvctl start asm' command.
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.; Action: This is an internal error. Contact Oracle Support Services.
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.; Action: Make sure that ASM I/O servers are started on sufficient number of nodes by using 'srvctl start ioserver' command. If required count is greater than number of nodes in the cluster make sure that the ASM I/O servers are started on all nodes of the cluster.
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.; Action: The ASM I/O servers can be relocated using the command 'srvctl relocate ioserver' to nodes on which ASM instances are running on.
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.; Action: Make sure that the ASM filter driver is installed on all nodes of the cluster and the ASM filter driver is managing all ASM managed disks.
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.; Action: Look at the accompanying messages and respond accordingly.
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.; Action: Look at the accompanying messages and respond accordingly.
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.; Action: Look at the accompanying messages and respond accordingly.
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.; Action: This is an internal error. Contact Oracle support services.
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.; Action: Ensure that the disks listed by the ASM filter driver are consistent across all the cluster nodes.
PRVG-06070: failed to execute command "{0}" on node "{1}": Cause: An attempt to execute the specified command on the node specified failed.; Action: Look at the accompanying messages and respond accordingly.
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.; Action: Ensure that the ASM filter driver library is consistently installed and loaded across all the cluster 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.; Action: Look at the accompanying messages and respond accordingly.
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.; Action: None
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.; Action: Use the command 'afdtool' to stamp the disks for management by ASM filter driver.
PRVG-07040: Failed to get LV count for "{0}": Cause: Could not get Logical Volume information for the device specified.; Action: Ensure that the device specified is available.
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.; Action: Ensure that the path is absolute and at least some leading portion of it matches an existing file system path 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.; Action: Ensure that the path is absolute and at least some leading portion of it matches an existing file system path writable by the current user 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.; Action: Look at the accompanying messages and respond accordingly.
PRVG-07090: An internal error occurred within cluster verification fix up framework: Cause: An error occurred while performing the selected fix up operations.; Action: This is an internal error. Contact Oracle Support Services.
PRVG-07091: Unknown privilege delegation method specified: Cause: An unknown privilege delegation method was specified.; Action: Specify a valid value for the privilege delegation method. 'sudo' and 'root' are the only acceptable method values.
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.; Action: Use the command line option '-method' to specify one of the privilege delegation methods.
PRVG-07500: File "{0}" not found: Cause: The specified file was not found.; Action: Ensure that the file exists and is readable.
PRVG-07501: An error occurred while parsing file "{0}": Cause: An error occurred while parsing the document.; Action: Ensure that the document is well formatted and a valid XML document.
PRVG-07503: An I/O error occurred while reading file "{0}": Cause: An I/O error occurred while parsing the document.; Action: Ensure that the document is accessible. Copy the document to a new location and retry.
PRVG-07504: An internal error occurred while parsing file "{0}": Cause: An internal error occurred while parsing the document.; Action: This is an internal error. Contact Oracle Support Services.
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.; Action: Ensure that any previous Oracle Clusterware installation has been deinstalled properly.
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.; Action: Ensure that the Oracle Clusterware was installed properly. Ensure that any previous Oracle Clusterware configuration files have been cleaned up.
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.; Action: Ensure that the Oracle Clusterware stack is up so that Cluster Verification Utility (CVU) can retrieve the node list. The node list can be specified using the command line option '-n <varname>nodelist</varname>' or using CV_NODE_ALL property in the 'cvu_config' file so that CVU perform verification operation on those nodes.
PRVG-09001: Failed to read input from command line standard input: Cause: Failed to read the response from standard input.; Action: Ensure that the input is correctly entered on standard input.
PRVG-09003: Failed to read the "{0}" user credentials: Cause: Failed to read the response from standard input.; Action: Ensure that the input is correctly entered on 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.; Action: Ensure that the credentials provided are correct.
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.; Action: Look at the error details and respond accordingly.
PRVG-09018: Privilege delegation method and credentials are not specified: Cause: The privilege delegation method and credentials were not specified.; Action: Ensure that the privilege delegation method and its credentials are 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.; Action: Make sure that the user running fix up has read and write permissions on the indicated directory.
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.; Action: Ensure that the executable file exists at the indicated path.
PRVG-09021: File "{0}" not found on nodes "{1}": Cause: Indicated file was not found at the indicated path on the identified nodes.; Action: Ensure that the file exists at the indicated path.
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.; Action: Ensure that the indicated manual fix up command is executed as root user on the identified node.
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.; Action: Ensure that the file exists and the privilege delegation method used to run this command is run with correct credentials.
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.; Action: Examine the accompanying error messages for details and also ensure that the command executable exists at the identified path and the privilege delegation method used to run this command is run with correct credentials.
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.; Action: Examine the accompanying error messages for details and also ensure that the command executable exists at the identified path and the privilege delegation method used to run this command is run with correct credentials.
PRVG-09028: Failed to set an environment variable "{0}" on node "{1}": Cause: An attempt to set an environment variable failed on indicated node.; Action: This is an internal error. Contact Oracle Support Services.
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.; Action: Ensure that the file exists and the privilege delegation method used to run this command is run with correct credentials.
PRVG-09031: Missing required data in fix up data file.: Cause: An internal error occurred while performing the selected fix up operations.; Action: This is an internal error. Contact Oracle Support Services.
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.; Action: Ensure that the privilege delegation method used to run this command is run with correct credentials.
PRVG-09033: Failed to create new group "{0}" on node "{1}": Cause: An attempt to add specified new group failed on the indicated node.; Action: Ensure that the privilege delegation method used to run this command is run with correct credentials.
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.; Action: Ensure that the user account exists 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.; Action: Ensure that the group account exists 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.; Action: Ensure that the privilege delegation method used to run this command is run with correct credentials and the user and group exist on the 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.; Action: Ensure that the user account exists on the 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.; Action: Ensure that the privilege delegation method used to run this command is run with correct credentials.
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.; Action: Ensure that the privilege delegation method used to run this command is run with correct credentials.
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.; Action: Ensure that the node is reachable and the user running the command has required privileges to retrieve the information from user accounts database.
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.; Action: Ensure that the node is reachable and the user running the command has required privileges to retrieve the information from group accounts database.
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.; Action: Ensure that the node is reachable and the user running the command has required privileges to retrieve the information from user accounts database.
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.; Action: Ensure that the node is reachable and the user running the command has required privileges to retrieve the information from group accounts database.
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.; Action: Ensure that the indicated file is in correct format and that the entry for 'initdefault' runlevel exists in the file.
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.; Action: Ensure that the package source file exists at the identified location and the 'rpm' tool is available on the node.
PRVG-09046: Fix up for this verification failure is not supported: Cause: An internal error occurred while performing the selected fix up operations.; Action: This is an internal error. Contact Oracle Support Services.
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.; Action: This is an internal error. Contact Oracle Support Services.
PRVG-09048: Fix up is not supported for Operating System parameter "{0}": Cause: An internal error occurred while performing the selected fix up operations.; Action: This is an internal error. Contact Oracle Support Services.
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.; Action: Manually create the home directory at the indicated path for the newly added user account.
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.; Action: Ensure that the command is being run in the correct operating system environment.
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.; Action: None, or address the situation manually on the indicated node.
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.; Action: Examine the accompanying error messages for details.
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.; Action: Examine the accompanying error messages for details.
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.; Action: Ensure that the project specific configuration is correct 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.; Action: Ensure that the Solaris Project specific configuration is correct 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.; Action: Ensure that the file /etc/passwd is in correct format and that the contents of this file are correct on the indicated node.
PRVG-09060: Fix up is not supported for daemon or process "{0}": Cause: An unsupported daemon or process was requested for fix up.; Action: This is an internal error. Contact Oracle Support Services.
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.; Action: This is an internal error. Contact Oracle Support Services.
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.; Action: This is an internal error. Contact Oracle Support Services.
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.; Action: Ensure that the daemon name is correct and it is running on the node indicated.
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.; Action: Ensure that ASMLib is configured correctly and look at the accompanying messages for details. If the problem persists, contact Oracle Support Services.
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.; Action: Ensure that the 'olsnodes' executable tool exists at the specified location and look at the accompanying messages for details.
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.; Action: Ensure that the 'crsctl' executable tool exists at the specified location and look at the accompanying messages for details.
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.; Action: Ensure that the huge pages support is enabled for the Linux kernel on the 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.; Action: This is an internal error. Contact Oracle Support Services.
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.; Action: Ensure that the indicated command exists at the specified location and look at the accompanying messages for details.
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.; Action: Rectify the issues described in the detailed messages and retry.
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.; Action: Ensure that the 'srvctl' executable exists at the specified location and look at the accompanying 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.; Action: Ensure that the 'srvctl' executable exists at the specified location and look at the accompanying 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.; Action: Ensure that the 'srvctl' executable exists at the specified location and look at the accompanying messages for details.
PRVG-10005: unable to determine local hostname: Cause: The hostname could not be determined.; Action: Check that the hostname for the local machine is valid. Look at the accompanying messages. If the problem persists, contact Oracle Support Services.
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.; Action: Specify a VIP name using -vip option.
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 specified cluster name, VIP type and resource name failed.; Action: Make sure that cluster name and VIP resource name do not exceed 252 characters. Make sure that VIP type is a valid VIP type. Refer to 'crsctl get clientid -help' for more information.
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.; Action: Make sure that DHCP servers exist on the network and are listening on port specified. If they are listening on a different port then specify that port using the -port option. For more information refer to help for 'crsctl discover dhcp' command.
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.; Action: Make sure that there are DHCP servers with IP addresses available on the network. If other DHCP servers are available which are listening on a different port specify an alternative port using the -port option. For more information refer to help for 'crsctl request dhcp' command.
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.; Action: Make sure that there are DHCP servers listening on port specified. If the DHCP server is listening on a different port specify an alternative port using -port option. For more information refer to help for 'crsctl release dhcp' command.
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.; Action: For HOSTVIP type node name needs to be specified via -n option.
PRVG-10015: VIP type "{0}" is invalid: Cause: An invalid VIP type was specified for DHCP client ID generation.; Action: Make sure that VIP type is a valid VIP type. Refer to 'crsctl get clientid -help' for more information.
PRVG-10036: value for command line parameter "{0}" is not an integer: Cause: An invalid value was specified for the specified command line parameter.; Action: Re-submit the request with an integer value.
PRVG-10039: invalid subnet "{0}" specified: Cause: An invalid IPv4 or IPv6 subnet was supplied on command line.; Action: Supply a subnet address that conforms to IETF RFC-950 or IETF RFC-5942.
PRVG-10040: unable to get list of network interfaces: Cause: An attempt to get the list of network interfaces failed.; Action: Look at the accompanying messages for more information.
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.; Action: Specify a subnet that matches at least one network interface's subnet on this node.
PRVG-10044: invalid cluster name "{0}" specified: Cause: An invalid cluster name was supplied on the command line.; Action: Specify a cluster name which is at least one character but no more than 15 characters in length. The cluster name must be alphanumeric, it cannot begin with a numeric character, and it may contain hyphen (-) characters. However, it cannot end with a hyphen (-) character.
PRVG-10045: invalid node name "{0}" specified: Cause: An invalid node name was supplied on the command line.; Action: Specify a node name which is at least one character but no more than 63 characters in length. The node name must be alphanumeric, it cannot begin with a numeric character, and it may contain hyphen (-) characters. However, it cannot end with a hyphen (-) character.
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.; Action: Ensure that the ASMLib is correctly installed and configured, and specified file is present at the given path and that the user has the necessary access privileges for the configuration file.
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.; Action: Ensure that the ASMLib is correctly installed and configured on all the nodes and that the user has the necessary access privileges for the configuration file.
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.; Action: Ensure that the ASMLib is correctly installed and configured on all the nodes with same configuration settings and that the user has the necessary access privileges for the configuration file.
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.; Action: Ensure that the ASMLib is correctly configured on all the cluster nodes with same configuration settings and that the ASMLib version is the same on all cluster 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.; Action: Examine the accompanying error messages for details.
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.; Action: Ensure that nodes that will run Oracle database releases prior to 11gR2 have an unqualified host name less than or equal to 8 characters.
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.; Action: Rename the host to have a length less than or equal to 8 characters.
PRVG-10510: User "{0}" is not a domain user, domain name absent: Cause: Could not identify domain name of current user.; Action: Log in to the OS as a domain user.
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.; Action: Ensure that the specified ASM label is correctly stamped on a shared device on the node specified. To verify the label to disk mapping use tools 'Asmtoolg' on Windows operating system platforms and 'oracleasm' on the Linux operating system platform.
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.; Action: Ensure that the specified ASM label is correctly stamped on a shared device on the node specified and that the labeled devices are accessible to current user. To verify the label to disk mapping use tools 'Asmtoolg' on Windows operating system platforms and 'oracleasm' on the Linux operating system platform.
PRVG-10523: Disk "{0}" is not identified by ASMLib.: Cause: The indicated disk was not identified by ASMLib.; Action: Ensure that the ASMLib is correctly configured on all the cluster nodes and that the indicated disk is listed by 'oracleasm' on the Linux operating system platform.
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.; Action: Ensure that the ASMLib is correctly configured on all the cluster nodes and that the indicated disk is listed by 'oracleasm' on the Linux operating system platform.
PRVG-10530: Internal error: {0}: Cause: An internal error occurred. The included value is an internal identifier.; Action: Oracle internal error. Contact Oracle Support Services.
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.; Action: A forced upgrade may be required.
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.; Action: Ensure that any pending upgrade is complete.
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.; Action: Upgrade Clusterware to a higher 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.; Action: Ensure that the root user's primary group name and ID exists on all the nodes and that the root user is a member of this group.
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.; Action: Contact Oracle Support.
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.; Action: Ensure that the indicated primary group name and ID of the root user exists on all the cluster nodes, and that the root user has membership in the indicated group on each of the cluster 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.; Action: Contact Oracle Support.
PRVG-11000: Invalid usage of CVU internal function: Cause: This is an internal error.; Action: Please contact Oracle Support.
PRVG-11001: Failed to execute command "{0}" on node "{1}": Cause: An error occurred while executing the command.; Action: Look at the accompanying messages for details on the cause of failure.
PRVG-11003: SCAN is not configured: Cause: An attempt to retrieve SCAN failed.; Action: Ensure that SCAN is properly defined in this cluster. Use 'srvctl add scan' to add SCAN.
PRVG-11004: SCAN listener is not configured: Cause: An attempt to retrieve SCAN listener configuration failed.; Action: Ensure that SCAN is properly defined in this cluster. Use 'srvctl add scan_listener' to add SCAN listener.
PRVG-11005: Database "{0}" is not defined in this cluster: Cause: An attempt to retrieve cluster-specific metadata about the database failed.; Action: Ensure that the database name was specified correctly. Use 'srvctl add database' to enable Clusterware support for the database.
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.; Action: Ensure that VIPs are properly defined in this cluster. Use 'srvctl add vip' to add VIP.
PRVG-11007: No instances are defined for database "{0}": Cause: An attempt to retrieve database instances for the database failed.; Action: Ensure that at least one database instance is defined. Use 'srvctl add instance' to add database instance.
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.; Action: Examine the accompanying error messages for details. Address issues found and retry the operation.
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.; Action: Examine the accompanying error messages for details. Address issues found and retry the operation.
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.; Action: Ensure that the same network interface is defined on each node of Cluster.
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.; Action: Ensure that at least one interface with specified name is on the specified subnet on each node of Cluster.
PRVG-11051: network list is in invalid format: Cause: The processing of a network list argument encountered a syntax error.; Action: Network list is a comma separated list of networks. Each network can be specified in the format "if_name"[:subnet_id[:public|cluster_interconnect]]. if_name can have "*" as in "eth*" to match interfaces like eth1, eth02, etc. Provide network list in valid format.
PRVG-11052: Interface name is not enclosed within double quotes: Cause: Interface name in the interface list was not enclosed within double quotes.; Action: Provide interface name within double quotes.
PRVG-11053: Invalid subnet type: Cause: Invalid subnet type was specified in interface list.; Action: Provide public or cluster_interconnect as subnet type.
PRVG-11054: Interface "{0}" not found on this node: Cause: Failed to locate the interface on this node.; Action: Provide interface names configured on the node on which CVU is running.
PRVG-11055: Interfaces configured with subnet number "{0}" have multiple subnets masks: Cause: Interfaces of some nodes were configured with different subnet masks for the same subnet number.; Action: This message is accompanied by another message that lists the subnet masks information on the nodes. Configure interfaces on the nodes with same subnet mask for a subnet number.
PRVG-11056: subnet masks "{0}" are configured with subnet number "{1}" on nodes "{2}": Cause: NO; Action: n/a
PRVG-11057: Checking subnet mask consistency...: Cause: NO; Action: n/a
PRVG-11058: Subnet mask consistency check passed.: Cause: NO; Action: n/a
PRVG-11059: Subnet mask consistency check passed for subnet "{0}".: Cause: NO; Action: n/a
PRVG-11060: Subnet mask consistency check failed.: Cause: NO; Action: n/a
PRVG-11061: Different MTU values used across cluster interconnect network interfaces on subnets "{0}": Cause: Different MTU values found for the cluster interconnect interfaces on the specified subnets.; Action: Set the same MTU value for all cluster interconnect interfaces on the specified subnets.
PRVG-11065: Node connectivity checks will not be performed on network interfaces "{0}" on node "{1}" as they were down: Cause: The indicated network interfaces were not checked because they were down.; Action: If the indicated interfaces are to be used by the cluster bring them up and repeat this test.
PRVG-11067: TCP connectivity from node "{0}": "{1}" to node "{2}": "{3}" failed: Cause: Errors occurred while attempting to establish TCP connectivity between the identified two interfaces.; Action: Ensure that there are no firewalls blocking TCP operations and no process monitors running that can interfere with programs' network operations.
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.; Action: Make sure there are no IP addresses in the range (169.254.*.*) on any network interfaces.
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.; Action: Make sure there are no IP addresses in the range (169.254.*.*) on any non-private network interfaces.
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; Action: Make sure there are no IP addresses in the range (169.254.*.*) with subnet mask which is not 16-18 bits on any private network interfaces.
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.; Action: Make sure all the private interfaces in an Exadata environment are Infiniband type.
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.; Action: Ensure that subnets do not have overlapping IP address ranges.
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 specified file system path failed on the nodes specified.; Action: This is an internal error. Contact Oracle Support Services.
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.; Action: Free up space in this directory to avoid disk free space issues.
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.; Action: Ensure that the specified file system has at least the specified required free space.
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.; Action: Ensure that the specified file system has at least the required free space.
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.; Action: If the current user intends to be the Oracle installation owner, ensure that the user has read and write access to the database file location
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.; Action: Select a different path.
PRVG-11112: Path "{0}" is not shared by the following hub nodes: {1}: Cause: Specified hub nodes do not share the path.; Action: Select a path that is shared by all of the hub nodes.
PRVG-11115: Following error occurred while establishing connection to database "{0}": Cause: An attempt to connect to database failed.; Action: Look at the accompanying messages for details on the cause of failure.
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.; Action: Ensure that AUDIT_FILE_DEST location is not shared among instances.
PRVG-11125: Following error occurred during shared AUDIT_FILE_DEST location check: Cause: An error occurred while performing shared AUDIT_FILE_DEST locations check.; Action: Look at the accompanying messages for details on the cause of failure.
PRVG-11126: Oracle home from which database "{0}" is running could not be determined.: Cause: Checks on the directory location pointed to by the database initialization parameter 'AUDIT_FILE_DEST' failed to determine the Oracle home from which the specified database was running.; Action: Examine the accompanying messages for details on the cause of failure, address the issues described and retry.
PRVG-11127: skipping AUDIT_FILE_DEST location check for database "{0}" as software owner "{1}" of the associated Oracle home "{2}" is not same as current OS user "{3}".: Cause: Checks for the directory location pointed to by the database initialization parameter 'AUDIT_FILE_DEST' for the specified database could not be performed as the software owner of the associated Oracle home was not same as the current operating system user.; Action: Run this check as the specified software owner.
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.; Action: Ensure that multicast is enabled on the specified interfaces and network path exists between the interfaces.
PRVG-11137: Following error occurred during multicast check: Cause: An error occurred while performing multicast check.; Action: Look at the accompanying messages for details on the cause of failure.
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.; Action: Ensure that multicast is enabled on the specified interfaces and that a network path exists between the interfaces.
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.; Action: Ensure that the subnets specified in the -network option are configured in the cluster and are up and running.
PRVG-11143: The following error occurred during stale database schema statistics check.: Cause: An error occurred while performing database stale schema check.; Action: Look at the accompanying messages for details on the cause of failure.
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.; Action: Refer to MOS note 560336.1 at oracle support to fix the issue.
PRVG-11170: Skipping DHCP check for cluster which has only IPv6 interfaces: Cause: All the public interfaces in a cluster were IPv6.; Action: IPv6 addresses are automatically generated, hence the check is not required.
PRVG-11171: DHCP check failed: Cause: An error occurred while reading network interface information.; Action: n/a
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.; Action: Contact Oracle Support Services.
PRVG-11301: 'root' user "{0}" password is not valid on the following nodes "{1}": Cause: An attempt to validate the specified superuser password failed.; Action: Make sure that the 'root' user password specified is correct and valid. Make sure that the password is same across all nodes of the cluster.
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.; Action: Make sure that the specified path to sudo command exists on all nodes. Make sure that the permission to read and execute exists for current user.
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.; Action: Make sure that the 'sudo' command exists on all nodes. Make sure that 'id' command can be executed using 'sudo'.
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.; Action: This is an internal error. Contact Oracle Support Services.
PRVG-11305: Commands could not be executed as user 'root' on nodes "{0}": Cause: An attempt to run commands as user 'root' on the specified nodes failed.; Action: Look at the accompanying error messages for details and make sure that: - The command exists on the nodes specified. - The specified command has execute permission on the node specified. - The 'root' user password specified is correct.
PRVG-11310: "{0}" nodes were not found in the cluster: Cause: Zero nodes of specified type were found in the cluster.; Action: If this message is accompanied by error messages, respond according to those messages.
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.; Action: Ensure that the same operating system groups exist and 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.; Action: Look at the accompanying messages for details on the cause of failure.
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.; Action: Ensure that the operating system group exist and have the same group name on all the nodes where the database is present, and invoke the cluster verification utility post-database-install check to ensure the configuration is correct.
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.; Action: Contact Oracle Support Services.
PRVG-11322: One or more node names "{0}" contain one or more of the following invalid characters "{1}": Cause: One or more invalid node names were supplied.; Action: Ensure that all node names supplied use only valid characters. Only alphanumeric characters and hyphen are allowed as per RFC-952.
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.; Action: Ensure that the operating system groups exist and have the same group name on all the nodes where the database is present, and invoke the cluster verification utility post-database-install check to ensure the configuration is correct.
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.; Action: Ensure that broadcast is enabled on the specified interfaces and that the network path allows broadcast.
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.; Action: Ensure that broadcast is enabled on all interfaces and that the network path allows broadcast.
PRVG-11356: Following error occurred during broadcast check: Cause: An error occurred while performing broadcast check.; Action: Look at the accompanying messages for details on the cause of failure.
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.; Action: Select a different public subnet or change the IP addresses that the SCAN resolves to.
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.; Action: If network associated with the SCAN is DHCP, restart SCAN using 'srvctl stop' and 'srvctl start' commands. If network is static, configure SCAN IP addresses to be on the subnets of network. If IP addresses were already configured, recreate the SCAN using 'srvctl remove scan' and 'srvctl add scan' commands.
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.; Action: Define at least specified number of SCAN IP addresses in DNS for the 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.; Action: Make sure that the SCAN IP addresses are currently unused.
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.; Action: Modify SCAN using 'srvctl modify scan -n <scan_name>' and listener using 'srvctl modify scan_listener -u'.
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.; Action: Recreate the SCAN using 'srvctl remove' and 'srvctl add' commands.
PRVG-11374: SCAN "{0}" was not resolved: Cause: A static SCAN was not resolved to IP addresses.; Action: Make sure that the SCAN is resolved.
PRVG-11400: Node role value is not valid: Cause: This is an internal error. The value for the specified parameter must be 'hub', 'leaf' or 'auto'.; Action: Contact Oracle Support Services.
PRVG-11401: New nodes having both nodes with 'auto' role and nodes with 'hub' or 'leaf' role cannot be specified: 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.; Action: Either supply a list of new nodes that all have the 'auto' role or supply a list of new nodes that have the 'hub' or 'leaf' role specified for each node, but not both.
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.; Action: Supply a list of new nodes with AUTO role only when the existing cluster contains nodes with AUTO role.
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.; Action: Supply a list of new nodes with the 'leaf' role only when the existing cluster contains 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.; Action: Specify fewer hub nodes.
PRVG-11405: API with node roles argument should be called for Flex Cluster only: Cause: An internal error occurred.; Action: Contact Oracle Support Services.
PRVG-11406: API with node roles argument must be called for Flex Cluster: Cause: An internal error occurred.; Action: Contact Oracle Support Services.
PRVG-11407: API called with unequal sized arrays for nodes and VIPs: Cause: An internal error occurred.; Action: Contact Oracle Support Services.
PRVG-11408: API called with unequal sized arrays for nodes, VIPs and node roles: Cause: An internal error occurred.; Action: Contact Oracle Support Services.
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.; Action: Specify new nodes that are not already in the 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.; Action: Add a password entry for the user to the CVUDB wallet using 'crsctl add wallet -type CVUDB -name <varname>dbname</varname>'
PRVG-11420: Storage type of the path "{0}" could not be determined: Cause: There was an error in determining storage type of the path.; Action: Examine any accompanying error messages for details.
PRVG-11421: Storage type of the path "{0}" could not be determined: Cause: An internal error occurred.; Action: Contact Oracle Support Services.
PRVG-11422: Missing GNS subdomain name.: Cause: GNS subdomain name was not provided.; Action: The subdomain name for GNS must be provided via the '-domain' parameter in Oracle Clusterware Version 11.2.
PRVG-11423: The password provided on the command line is not valid for user "{0}": Cause: The provided password was wrong.; Action: Provide the correct password.
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.; Action: Configure a GNS subdomain by using the command 'srvctl add gns'.
PRVG-11425: Failed to validate GNS credential in file "{0}": Cause: An attempt to validate the Grid Naming Service (GNS) credential failed.; Action: Ensure that the credential file provided has been generated in a GNS server cluster by 'srvctl export gns -clientdata <varname>filename</varname>'.
PRVG-11500: ACFS file systems are not available on Leaf nodes "{1}": Cause: The specified ACFS path was not suitable for Leaf nodes.; Action: Ensure that you have selected a path that is suitable for all the 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; Action: Ensure that you have selected a path that is suitable for the desired usage.
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; Action: Ensure that you have selected a path that is suitable for the desired usage.
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).; Action: Ensure that you have selected a path that is suitable for the desired usage.
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; Action: Ensure that you have selected a path that is suitable for the desired usage.
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; Action: Ensure that you have selected a path that is suitable for the desired usage.
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; Action: Ensure that you have selected a path that is suitable for the desired usage.
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.; Action: Use the 'crsctl set node role' command to make all node roles 'auto', or to make node roles a mix of 'hub' and 'leaf'.
PRVG-11516: New nodes "{0}" with 'hub' or 'leaf' role cannot be added to an Flex Cluster which has 'auto' role nodes: Cause: An attempt was made to add nodes with the 'hub' or 'leaf' role to an Flex Cluster already having nodes with the 'auto' role.; Action: Only add nodes with the 'auto' role to the cluster.
PRVG-11517: New nodes "{0}" with 'auto' role cannot be added to an Flex Cluster already having nodes with the 'hub' and 'leaf' role: 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.; Action: Only add nodes with the 'hub' or 'leaf' role to the cluster.
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.; Action: Look at the accompanying messages for the cause of the failure.
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.; Action: Install the required version of the cvuqdisk RPM using fix up action or manual steps as listed in the documentation.
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.; Action: Install the required version of the cvuqdisk RPM using fix up action or manual steps as listed in the documentation.
PRVG-11635: The ASM disks "{0}" are incorrectly sized: Cause: The indicated ASM disks had incorrect size information in the disk header.; Action: This is an internal error. Contact Oracle Support Services.
PRVG-11640: The check "{0}" was not performed as it is disabled: Cause: The indicated check was suppressed.; Action: Suppressed checks usually occur at the request of Oracle Support; if this is unexpected, contact Oracle Support Services.
PRVG-11644: Failed to copy baseline to the remote nodes: "{0}": Cause: An error occurred while copying the report to the remote nodes; Action: Examine the accompanying error messages for details.
PRVG-11750: File "{0}" exists on node "{1}".: Cause: The specified file is not expected to be present on the node.; Action: Remove the specified file from 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.; Action: Examine the accompanying error messages for details.
PRVG-11755: Property "{0}" was not found in configuration file "{1}": Cause: Could not find the specified property in the configuration file.; Action: Define the specified property in the configuration file. Otherwise, the validations needing this property will not be performed.
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.; Action: Ensure that the public network NIC takes precedence over the private network NIC in the configured network bind order.
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.; Action: Contact Oracle Support Services.
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.; Action: Contact Oracle Support Services.
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.; Action: Change the identified public interface metric value to a lower value than the identified private interface metric value.
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.; Action: Look at the accompanying messages for details.
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.; Action: Specify a discovery string that will discover the devices on the given node and make sure the devices to be used as ASM disks have permissions that allow them to be discovered.
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.; Action: Ensure that the Windows user account used for Oracle installation and configuration is defined as a domain user on all nodes or as a local user on all nodes, but not a mixture of the two.
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.; Action: Ensure that the Windows user account used for Oracle installation and configuration is defined as a domain user on all nodes or as a local user on all nodes, but not a mixture of the two.
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.; Action: Ensure that the Windows user account used for Oracle installation and configuration is defined as a domain user on all nodes or as a local user on all nodes, but not a mixture of the two.
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.; Action: Specify a Windows domain user as the Oracle Home User.
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.; Action: Examine the accompanying error messages for details.
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.; Action: Examine the accompanying error messages for details.
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.; Action: Examine the accompanying error message for details or contact Oracle Support Services.
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.; Action: Ensure that all the policy managed database homes exist 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 identified Oracle Home for policy managed database was not found on the indicated nodes.; Action: Ensure that the identified Oracle Home exists on the indicated nodes by running addNode.sh from the indicated Oracle Home.
PRVG-11886: Command "{0}" to get the policy managed database information failed: Cause: An attempt to execute the displayed command failed.; Action: This is an internal error. Contact Oracle Support Services.
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.; Action: Ensure that the current user has read and execute permissions for the directory cited in the message and its subdirectories. Look at the accompanying messages for more details.
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.; Action: Execute the 'cluvfy comp software' command only on nodes where Oracle Clusterware is installed.
PRVG-11901: Oracle Clusterware is not running on this node.: Cause: An attempt to execute the command 'cluvfy comp software' was requested, but Oracle Clusterware was not running on the node.; Action: Ensure that the Clusterware stack is running; if appropriate, issue 'crsctl start crs' to start it.
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.; Action: Issue the 'cluvfy comp software' command only on nodes where Oracle Clusterware is configured.
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.; Action: Retry the upgrade using the '-dest_crshome' option to specify a CRS home that is different from 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.; Action: Verify that the installation of Oracle software has completed successfully.
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.; Action: Verify that the installation of Oracle software has completed successfully.
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.; Action: Verify that the installation of Oracle software has completed successfully.
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.; Action: Verify that the installation of Oracle software has completed successfully and that the specified file exists and is readable.
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.; Action: Verify that the installation of the Oracle software has completed successfully and that the Oracle home is set up correctly.
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.; Action: Make sure that the configured Oracle Clusterware is version 11.2 or greater.
PRVG-11912: Command '{0}' to retrieve database services count failed.: Cause: An attempt to execute the displayed command failed. This is an internal error.; Action: Contact Oracle Support Services.
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.; Action: Contact Oracle Support Services.
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.; Action: Contact Oracle Support Services.
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.; Action: Contact Oracle Support Services.
PRVG-11919: Unable to create work area directory "{0}": Cause: An attempt to create the specified directory failed on the local node.; Action: Make sure that the user running Cluster Verification Utility has the authority to create the indicated directory or specify a different (usable) directory with the CV_DESTLOC environment variable.
PRVG-11920: Unable to delete CVU work files from directory "{0}": Cause: An attempt to remove files from the specified directory failed.; Action: Make sure that the user running Cluster Verification Utility has the authority to create the indicated directory or specify a different (usable) directory with the CV_DESTLOC environment variable.
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.; Action: Examine the accompanying error message for details.
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.; Action: Ensure that different local and remote ports were specified in the ONS configuration file.
PRVG-11928: 'remoteport' entry in the existing ONS configuration file "{0}" is inconsistent: Cause: The ONS configuration file had inconsistent 'remoteport' entries.; Action: Make sure that all nodes of the cluster have the same 'remoteport' entry in the specified file.
PRVG-11930: Path "{0}" is not writeable on nodes "{1}".: Cause: The identified path was not writeable on the indicated nodes.; Action: Ensure that write access is enabled for the current user on the identified path.
PRVG-11931: Path "{0}" is not writeable on node "{1}".: Cause: The identified path was not writeable by current user on the indicated node.; Action: Ensure that write access is enabled for the identified path by the current user.
PRVG-11932: Path "{0}" cannot be created on node "{1}".: Cause: The identified path can not be created on the indicated node.; Action: Ensure that the current user has authorization to create the identified path.
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.; Action: Ensure that the user running Cluster Verification Utility has the authority to create the indicated directory, or specify a different (usable) directory with the CV_DESTLOC environment variable. Also, look for messages accompanying this message for details.
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.; Action: Remove the nodes from the command line and rerun the check.
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.; Action: Ensure that Oracle Database is configured to run on the specified nodes. For administrator-managed databases, ensure that the database instances are configured to run on the nodes. For policy-managed databases, ensure that the nodes are in the server pools of the database.
PRVG-11946: Ping Target "{0}" is not reachable: Cause: Unable to reach the Ping Target specified using the OS ping command.; Action: Ensure that the Ping Target specified is accessible.
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.; Action: Specify a valid Oracle home.
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.; Action: Ensure that the specified home is a valid Oracle home 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 indentified file on the indicated node.; Action: Login as the root user and set the Set user ID bit for the identified file using command 'chmod +s <varname>file</varname>'.
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.; Action: Ensure that the identified file exists and that the user has read and execute permissions on it.
PRVG-11971: Grid Infrastructure home check failed: Cause: The Grid Infrastructure home path was not writable.; Action: Ensure that the Grid Infrastructure user has write permissions for the indicated path.
PRVG-12802: ASM devices "{0}" are not ASM Filter Driver capable.: Cause: The indicated devices were not ASM filter driver capable.; Action: To make them AFD capable, ensure that the devices selected for ASM are configured as block devices on Linux or character devices on AIX and Solaris operating system platforms.
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.; Action: If you intend to use the ASM Filter Driver to manage this device, ensure that the device selected for ASM is a block device on Linux or a character device on AIX and Solaris operating system platforms.
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.; Action: Ensure that the device is correctly configured on the indicated node and that the user has permission to read its attributes.
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.; Action: Ensure that the device is correctly configured and that the user has permission to read the device attributes. Examine the accompanying error messages for details.
PRVG-12855: Configured private sub-network "{0}" with sub-network mask "{1}" does not exist on node "{2}".: Cause: The indicated CRS private sub-network did not match any sub-network available on the identified node.; Action: The network configuration used for the existing CRS installation must be available networks on each of the cluster nodes. Use the 'oifcfg setif' command to correctly configure the sub-network for the existing installation.
PRVG-12856: Configured public sub-network "{0}" with sub-network mask "{1}" does not exist on node "{2}".: Cause: The indicated CRS public sub-network did not match any sub-network available on the identified node.; Action: The network configuration used for the existing CRS installation must be available networks on each of the cluster nodes. Use the 'oifcfg setif' command to correctly configure the sub-network for the existing installation.
PRVG-12857: Classfied sub-network configuration of the current CRS home "{0}" does not match any existing sub-networks on nodes "{1}".: Cause: The indicated CRS sub-network did not match any sub-network available on the identified nodes.; Action: The network configuration used for the existing CRS installation must be available networks on each of the cluster nodes. Use the 'oifcfg setif' command to correctly configure the sub-network for the existing installation.
PRVG-12858: Following error occurred during the network configuration consistency checks.: Cause: An error occurred while performing the network configuration consistency checks.; Action: Examine the accompanying messages for specific details on the network configuration problem, and rectify the issues.
PRVG-12884: Maximum (MTU) size packet check failed on subnets "{0}": Cause: The network switch was not configured with jumbo frames or the; Action: Ensure that the network switch is configured with 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; Action: Ensure that the network switch is configured with jumbo frames
PRVG-12886: Interface "{0}" has an invalid MTU value "{1}".: Cause: The retrieved MTU value from ip command contained other than decimal digits.; Action: Configure an MTU value for the identified interface with decimal digits only. Look at the accompanying messages for more details.
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.; Action: Ensure that the indicated executable accessible on the node. Look at the accompanying messages for more details.