PRVH-00100 to PRVH-01002

150 PRVH-00100 to PRVH-01002

PRVH-00100: Restricted deletion flag is not set for path "{0}" on node "{1}".: Cause: The Cluster Verification Utility (CVU) determined that the indicated path did not have restricted deletion flag (sticky bit) set on the indicated node.; Action: Ensure that the indicated path has the restricted deletion flag set. Use the operating system command 'chmod +t path' to set the restricted deletion flag for the indicated file system path.
PRVH-00101: Restricted deletion flag is set for path "{0}" on node "{1}".: Cause: The Cluster Verification Utility (CVU) determined that the indicated path had a restricted deletion flag (sticky bit) set on the indicated node.; Action: Ensure that the indicated path does not have the restricted deletion flag set. Use the operating system command 'chmod -t path' to remove the restricted deletion flag for the indicated file system path.
PRVH-00102: File "{0}" does not exist on node "{1}".: Cause: The Cluster Verification Utility (CVU) determined that the indicated file did not exist on the indicated node.; Action: Ensure that the indicated file exists.
PRVH-00103: Directory "{0}" does not exist on node "{1}".: Cause: The Cluster Verification Utility (CVU) determined that the indicated directory did not exist on the indicated node.; Action: Ensure that the indicated directory exists.
PRVH-00104: Link "{0}" does not exist on node "{1}".: Cause: The Cluster Verification Utility (CVU) determined that the indicated file system link did not exist on the indicated node.; Action: Ensure that the indicated file system link exists.
PRVH-00105: Path "{0}" with permissions "{1}" does not have read permissions for the owner on node "{2}".: Cause: A check for file system attributes found that the indicated path did not have read permissions for the owner on the indicated node.; Action: Change the permissions of the indicated path to grant the read permissions for the owner.
PRVH-00106: Path "{0}" with permissions "{1}" does not have write permissions for the owner on node "{2}".: Cause: A check for file system attributes found that the indicated path did not have write permissions for the owner on the indicated node.; Action: Change the permissions of the indicated path to grant the write permissions for the owner.
PRVH-00107: Path "{0}" with permissions "{1}" does not have execute permissions for the owner on node "{2}".: Cause: A check for file system attributes found that the indicated path did not have the execute permissions for the owner on the indicated node.; Action: Change the permissions of the indicated path to grant the execute permissions for the owner.
PRVH-00108: Path "{0}" with permissions "{1}" does not have read permissions for the file's group on node "{2}".: Cause: A check for file system attributes found that the indicated path did not have the read permissions for the file's group on the indicated node.; Action: Change the permissions of the indicated path to grant the read permissions for the file's group.
PRVH-00109: Path "{0}" with permissions "{1}" does not have write permissions for the file's group on node "{2}".: Cause: A check for file system attributes found that the indicated path did not have the write permissions for the file's group on the indicated node.; Action: Change the permissions of the indicated path to grant the write permissions for the file's group.
PRVH-00110: Path "{0}" with permissions "{1}" does not have execute permissions for the file's group on node "{2}".: Cause: A check for file system attributes found that the indicated path did not have the execute permissions for the file's group on the indicated node.; Action: Change the permissions of the indicated path to grant the execute permissions for the file's group.
PRVH-00111: Path "{0}" with permissions "{1}" does not have read permissions for others on node "{2}".: Cause: A check for file system attributes found that the indicated path did not have the read permissions for others on the indicated node.; Action: Change the permissions of the indicated path to grant the read permissions for others.
PRVH-00112: Path "{0}" with permissions "{1}" does not have write permissions for others on node "{2}".: Cause: A check for file system attributes found that the indicated path did not have the write permissions for others on the indicated node.; Action: Change the permissions of the indicated path to grant the write permissions for others.
PRVH-00113: Path "{0}" with permissions "{1}" does not have execute permissions for others on node "{2}".: Cause: A check for file system attributes found that the indicated path did not have the execute permissions for others on the indicated node.; Action: Change the permissions of the indicated path to grant the execute permissions for others.
PRVH-00114: Path "{0}" with permissions "{1}" does not have read permissions for the owner, file's group, and others on node "{2}".: Cause: A check for file system attributes found that the indicated path did not have the read permissions for the owner, file's group and other on the indicated node.; Action: Change the permissions of the indicated path to grant the read permissions for user, file's group and others.
PRVH-00115: Path "{0}" with permissions "{1}" does not have write permissions for the owner, file's group, and others on node "{2}".: Cause: A check for file system attributes found that the indicated path did not have the write permissions for the owner, file's group and others on the indicated node.; Action: Change the permissions of the indicated path to grant the write permissions for the owner, file's group and others.
PRVH-00116: Path "{0}" with permissions "{1}" does not have execute permissions for the owner, file's group, and others on node "{2}".: Cause: A check for file system attributes found that the indicated path did not have the execute permissions for the owner, file's group and others on the indicated node.; Action: Change the permissions of the indicated path to grant the execute permissions for the owner, file's group and others.
PRVH-00117: Path "{0}" with permissions "{1}" does not have read permissions for the owner and file's group on node "{2}".: Cause: A check for file system attributes found that the indicated path did not have the read permissions for the owner and file's group on the indicated node.; Action: Change the permissions of the indicated path to grant the read permissions for the owner and file's group.
PRVH-00118: Path "{0}" with permissions "{1}" does not have write permissions for the owner and file's group on node "{2}".: Cause: A check for file system attributes found that the indicated path did not have the write permissions for the owner and file's group on the indicated node.; Action: Change the permissions of the indicated path to grant the write permissions for the owner and file's group.
PRVH-00119: Path "{0}" with permissions "{1}" does not have execute permissions for the owner and file's group on node "{2}".: Cause: A check for file system attributes found that the indicated path did not have the execute permissions for the owner and file's group on the indicated node.; Action: Change the permissions of the indicated path to grant the execute permissions for the owner and file's group.
PRVH-00120: Path "{0}" with permissions "{1}" does not have read permissions for the owner and others on node "{2}".: Cause: A check for file system attributes found that the indicated path did not have the read permissions for the owner and others on the indicated node.; Action: Change the permissions of the indicated path to grant the read permissions for the owner and others.
PRVH-00121: Path "{0}" with permissions "{1}" does not have write permissions for the owner and others on node "{2}".: Cause: A check for file system attributes found that the indicated path did not have the write permissions for the owner and others on the indicated node.; Action: Change the permissions of the indicated path to grant the write permissions for the owner and others.
PRVH-00122: Path "{0}" with permissions "{1}" does not have execute permissions for the owner and others on node "{2}".: Cause: A check for file system attributes found that the indicated path did not have the execute permissions for the owner and others on the indicated node.; Action: Change the permissions of the indicated path to grant the execute permissions for the owner and others.
PRVH-00123: Path "{0}" with permissions "{1}" does not have read permissions for the file's group and others on node "{2}".: Cause: A check for file system attributes found that the indicated path did not have the read permissions for the file's group and others on the indicated node.; Action: Change the permissions of the indicated path to grant the read permissions for the file's group and others.
PRVH-00124: Path "{0}" with permissions "{1}" does not have write permissions for the file's group and others on node "{2}".: Cause: A check for file system attributes found that the indicated path did not have the write permissions for the file's group and others on the indicated node.; Action: Change the permissions of the indicated path to grant the write permissions for the file's group and others.
PRVH-00125: Path "{0}" with permissions "{1}" does not have execute permissions for the file's group and others on node "{2}".: Cause: A check for file system attributes found that the indicated path did not have the execute permissions for the file's group and others on the indicated node.; Action: Change the permissions of the indicated path to grant the execute permissions for the file's group and others.
PRVH-00126: Path "{0}" with permissions "{1}" does not have read permissions for the owner or file's group, or others on node "{2}".: Cause: A check for file system attributes found that the indicated path did not have the read permissions for the owner, file's group and others on the indicated node.; Action: Change the permissions of the indicated path to grant the read permissions either for the owner or file's group or others.
PRVH-00127: Path "{0}" with permissions "{1}" does not have write permissions for the owner or file's group, or others on node "{2}".: Cause: A check for file system attributes found that the indicated path did not have the write permissions for the owner, file's group and others on the indicated node.; Action: Change the permissions of the indicated path to grant the write permissions either for the owner or file's group or others.
PRVH-00128: Path "{0}" with permissions "{1}" does not have execute permissions for the owner or file's group, or others on node "{2}".: Cause: A check for file system attributes found that the indicated path did not have the execute permissions for the owner, file's group and others on the indicated node.; Action: Change the permissions of the indicated path to grant the execute permissions either for the owner or file's group or others.
PRVH-00129: Path "{0}" with permissions "{1}" does not have read permissions for the owner or file's group on node "{2}".: Cause: A check for file system attributes found that the indicated path did not have the read permissions for the owner and file's group on the indicated node.; Action: Change the permissions of the indicated path to grant the read permissions either for the owner or file's group.
PRVH-00130: Path "{0}" with permissions "{1}" does not have write permissions for the owner or file's group on node "{2}".: Cause: A check for file system attributes found that the indicated path did not have the write permissions for the owner and file's group on the indicated node.; Action: Change the permissions of the indicated path to grant the write permissions either for the owner or file's group.
PRVH-00131: Path "{0}" with permissions "{1}" does not have execute permissions for the owner or file's group on node "{2}".: Cause: A check for file system attributes found that the indicated path did not have the execute permissions for the owner and file's group on the indicated node.; Action: Change the permissions of the indicated path to grant the execute permissions either for the owner or file's group.
PRVH-00132: Path "{0}" with permissions "{1}" does not have read permissions for the owner or others on node "{2}".: Cause: A check for file system attributes found that the indicated path did not have the read permissions for the owner and others on the indicated node.; Action: Change the permissions of the indicated path to grant the read permissions either for the owner or others.
PRVH-00133: Path "{0}" with permissions "{1}" does not have write permissions for the owner or others on node "{2}".: Cause: A check for file system attributes found that the indicated path did not have the write permissions for the owner and others on the indicated node.; Action: Change the permissions of the indicated path to grant the write permissions either for the owner or others.
PRVH-00134: Path "{0}" with permissions "{1}" does not have execute permissions for the owner or others on node "{2}".: Cause: A check for file system attributes found that the indicated path did not have the execute permissions for the owner and others on the indicated node.; Action: Change the permissions of the indicated path to grant the execute permissions either for the owner or others.
PRVH-00135: Path "{0}" with permissions "{1}" does not have read permissions for the file's group or others on node "{2}".: Cause: A check for file system attributes found that the indicated path did not have the read permissions for the file's group and others on the indicated node.; Action: Change the permissions of the indicated path to grant the read permissions either for the file's group or others.
PRVH-00136: Path "{0}" with permissions "{1}" does not have write permissions for the file's group or others on node "{2}".: Cause: A check for file system attributes found that the indicated path did not have the write permissions for the file's group and others on the indicated node.; Action: Change the permissions of the indicated path to grant the write permissions either for the file's group or others.
PRVH-00137: Path "{0}" with permissions "{1}" does not have execute permissions for the file's group or others on node "{2}".: Cause: A check for file system attributes found that the indicated path did not have the execute permissions for the file's group and others on the indicated node.; Action: Change the permissions of the indicated path to grant the execute permissions either for the file's group or others.
PRVH-00138: Path "{0}" with permissions "{1}" does not have read permissions for the owner or file's group and others on node "{2}".: Cause: A check for file system attributes found that the indicated path did not have the read permissions either for the owner or owning group and others on the indicated node.; Action: Change the permissions of the indicated path to grant the read permissions either for the owner or file's group and others.
PRVH-00139: Path "{0}" with permissions "{1}" does not have write permissions for the owner or file's group and others on node "{2}".: Cause: A check for file system attributes found that the indicated path did not have the write permissions either for the owner or owning group and others on the indicated node.; Action: Change the permissions of the indicated path to grant the write permissions either for the owner or file's group and others.
PRVH-00140: Path "{0}" with permissions "{1}" does not have execute permissions for the owner or file's group and others on node "{2}".: Cause: A check for file system attributes found that the indicated path did not have the execute permissions either for the owner or owning group and others on the indicated node.; Action: Change the permissions of the indicated path to grant the execute permissions either for the owner or file's group and others.
PRVH-00141: Path "{0}" with permissions "{1}" does not have read permissions for the file's group or owner and others on node "{2}".: Cause: A check for file system attributes found that the indicated path did not have the read permissions either for the file's group or the owner and others on the indicated node.; Action: Change the permissions of the indicated path to grant the read permissions either for the file's group or the owner and others.
PRVH-00142: Path "{0}" with permissions "{1}" does not have write permissions for the file's group or owner and others on node "{2}".: Cause: A check for file system attributes found that the indicated path did not have the write permissions either for the file's group or the owner and others on the indicated node.; Action: Change the permissions of the indicated path to grant the write permissions either for the file's group or the owner and others.
PRVH-00143: Path "{0}" with permissions "{1}" does not have execute permissions for the file's group or owner and others on node "{2}".: Cause: A check for file system attributes found that the indicated path did not have the execute permissions either for the file's group or the owner and others on the indicated node.; Action: Change the permissions of the indicated path to grant the execute permissions either for the file's group or the owner and others.
PRVH-00144: Path "{0}" with permissions "{1}" does not have read permissions for others or the owner and file's group on node "{2}".: Cause: A check for file system attributes found that the indicated path did not have the read permissions either for others or the owner and file's group on the indicated node.; Action: Change the permissions of the indicated path to grant the read permissions either for others or the owner and file's group.
PRVH-00145: Path "{0}" with permissions "{1}" does not have write permissions for others or the owner and file's group on node "{2}".: Cause: A check for file system attributes found that the indicated path did not have the write permissions either for others or the owner and file's group on the indicated node.; Action: Change the permissions of the indicated path to grant the write permissions either for others or the owner and file's group.
PRVH-00146: Path "{0}" with permissions "{1}" does not have execute permissions for others or the owner and file's group on node "{2}".: Cause: A check for file system attributes found that the indicated path did not have the execute permissions either for others or the owner and file's group on the indicated node.; Action: Change the permissions of the indicated path to grant the execute permissions either for others or the owner and file's group.
PRVH-00147: Set group ID bit is not set for file "{0}" on node "{1}".: Cause: The set group ID bit was not set for the identified file on the indicated node.; Action: Log in as the root user and set the set group ID bit for the identified file using command 'chmod g+s file'.
PRVH-00148: Set group ID bit is set for file "{0}" on node "{1}".: Cause: The set group ID bit was set for the identified file on the indicated node.; Action: Log in as the root user and remove the set group ID bit for the identified file using command 'chmod g-s file'.
PRVH-00149: Set user ID bit is set for file "{0}" on node "{1}".: Cause: The set user ID bit was set for the identified file on the indicated node.; Action: Log in as the root user and remove the set user ID bit for the identified file using command 'chmod -s file'.
PRVH-00150: failure to open file "{0}" to read on node "{1}". Operation failed with error "{2}": Cause: An attempt to read the specified file failed on the indicated node because of the indicated error.; Action: Ensure that the file exists at the indicated path and the user running diagnostics operations has read permissions on the indicated file.
PRVH-00151: Directory "{0}" is not empty on node "{1}".: Cause: The identified directory path was found to be not empty on the indicated node.; Action: Ensure that the identified directory path is empty on the indicated node .
PRVH-00152: Directory "{0}" is an empty directory on node "{1}".: Cause: The identified directory path was found to be an empty directory on the indicated node.; Action: Ensure that the identified directory path is not an empty directory on the indicated node .
PRVH-00153: File "{0}" is not empty on node "{1}".: Cause: The identified path was found to be a non empty file on the indicated node.; Action: Ensure that the identified file path is empty on the indicated node .
PRVH-00154: File "{0}" is empty on node "{1}".: Cause: The identified path was found to be zero bytes file on the indicated node.; Action: Ensure that the identified file path is not empty on the indicated node .
PRVH-00158: User ID "{0}" does not exist on node "{1}".: Cause: The specified user ID did not exist on the specified node.; Action: Create the user with specified ID on the specified node.
PRVH-00159: Group ID "{0}" does not exist on node "{1}".: Cause: The specified group ID did not exist on the specified node.; Action: Create the group with specified group ID on the specified node.
PRVH-00161: File "{0}" is not expected on node "{1}".: Cause: The Cluster Verification Utility (CVU) determined that the indicated file already existed on the indicated node.; Action: Ensure that the indicated file does not exist.
PRVH-00162: Directory "{0}" is not expected on node "{1}".: Cause: The Cluster Verification Utility (CVU) determined that the indicated directory already existed on the indicated node.; Action: Ensure that the indicated directory does not exist.
PRVH-00163: Link "{0}" is not expected on node "{1}".: Cause: The Cluster Verification Utility (CVU) determined that the indicated file system link already existed on the indicated node.; Action: Ensure that the indicated file system link does not exist.
PRVH-00180: Path "{0}" is not a file on node "{1}".: Cause: The Cluster Verification Utility (CVU) determined that the indicated path was not a file but a directory on the identified node.; Action: Ensure that the indicated path exists as file on the identified node.
PRVH-00181: Path "{0}" is not a directory on node "{1}".: Cause: The Cluster Verification Utility (CVU) determined that the indicated path was not a directory on the indicated node.; Action: Ensure that the indicated path exists as directory on the identified node.
PRVH-00182: Path "{0}" is not a link on node "{1}".: Cause: The Cluster Verification Utility (CVU) determined that the indicated path was not a file system link on the identified node.; Action: Ensure that the indicated path exists as file system link on the identified node.
PRVH-00183: Path "{0}" is not expected to be owned by user "{1}" on node "{2}".: Cause: The Cluster Verification Utility (CVU) determined that the indicated path was incorrectly owned by the indicated user on the identified node.; Action: Ensure that the indicated path is not owned by the indicated user on the identified node.
PRVH-00184: Path "{0}" is not expected to be owned by group "{1}" on node "{2}".: Cause: The Cluster Verification Utility (CVU) determined that the indicated path was incorrectly owned by the indicated group on the identified node.; Action: Ensure that the indicated path is not owned by the indicated group on the identified node.
PRVH-00185: Path "{0}" does not allow execution on node "{1}".: Cause: The Cluster Verification Utility (CVU) determined that the indicated path did not allow execution of any executable on the identified node.; Action: Ensure that the indicated path does not have security settings restricting the execution of binaries on the identified node. Security enforced restrictions or Access Control Lists configuration limits the ability to execute binaries from the file system location. Examine the accompanying messages for details on the cause of the failure.
PRVH-00500: Server categories "{0}" exist with a leaf role.: Cause: Indicated server categories were found to be configured with a leaf role. An attribute setting of 'ACTIVE_CSS_ROLE=leaf' was found for each of these server categories. Nodes with CSS role of leaf are not supported in Oracle Clusterware 19c onward.; Action: Modify each of the indicated server categories to have an attribute setting of 'ACTIVE_CSS_ROLE=hub'. Otherwise, delete the indicated server categories after performing one of the following two corrective actions for each of the server pools which uses any of the indicated server categories: (1) Delete that server category from its SERVER_CATEGORY attribute, if multiple categories are indicated. Otherwise, delete the server pool. (2) Modify the SERVER_CATEGORY of the server pool to replace the indicated server category with a server category that is not configured with a leaf role.
PRVH-00501: ASM filter driver discovery diskstring "{0}" is invalid.: Cause: Cluster Verification Utility check found that the indicated ASM filter driver discovery diskstring contains path names that are invalid OS path names.; Action: Use the command 'asmcmd afd_dsget' to get the current discovery string. Ensure that the discovery string is set correctly to the path names that the OS accepts using the command 'asmcmd afd_dsset <afd_diskstring>' and retry the operation.
PRVH-00510: IPC protocol used by ASM instances is inconsistent across the cluster nodes. ASM instances use the "{0}" protocol on nodes "{1}" and "{2}" protocol on nodes "{3}".: Cause: Cluster Verification Utility (CVU) found that IPC protocol used by ASM instances was not consistent across the cluster nodes.; Action: Ensure that ASM instances use the same protocol on all the cluster nodes for IPC communication. Run the command 'make -f $ORACLE_HOME/rdbms/lib/ins_rdbms.mk ipc_rds ioracle' to change the protocol to 'rds' or command 'make -f $ORACLE_HOME/rdbms/lib/ins_rdbms.mk ipc_g ioracle' to change the protocol to 'udp' on the applicable nodes to make the IPC protocol consistent across the cluster nodes. Refer to MOS note 2345406.1 for more details.
PRVH-00511: ASM instances do not use the IPC protocol 'RDS' for IPC communication on nodes "{0}".: Cause: Cluster Verification Utility (CVU) found that IPC protocol used by ASM instances was not RDS on the indicated nodes.; Action: Ensure that the ASM instances use the RDS protocol for IPC communication on the indicated nodes by running the command 'make -f $ORACLE_HOME/rdbms/lib/ins_rdbms.mk ipc_rds ioracle'. Refer to MOS note 2345406.1 for more details.
PRVH-00512: ASM instances use the IPC protocol 'UDP' for IPC on nodes "{0}".: Cause: The Cluster Verification Utility (CVU) found that the Inter-process Communication (IPC) protocol used by ASM instances was not Reliable Datagram Sockets (RDS) on the indicated nodes. The User Datagram Protocol (UDP) linked Oracle binary upgrade failed on Oracle Exadata environments.; Action: Ensure that the ASM instances use the RDS protocol for IPC on the indicated nodes by running the command 'make -f $ORACLE_HOME/rdbms/lib/ins_rdbms.mk ipc_rds ioracle'. Refer to MOS note 2345406.1 for more details.
PRVH-00513: ASM instances use the IPC protocol 'RDS' for IPC on nodes "{0}".: Cause: The Cluster Verification Utility (CVU) found that the Inter-process Communication (IPC) protocol used by ASM instances was not User Datagram Protocol (UDP) on the indicated nodes. The Reliable Datagram Sockets (RDS) linked Oracle binary upgrade failed on non-Oracle Exadata environments.; Action: Ensure that the ASM instances use the UDP protocol for IPC on the indicated nodes by running the command 'make -f $ORACLE_HOME/rdbms/lib/ins_rdbms.mk ipc_g'.
PRVH-00516: failed to retrieve CVU remote execution framework version from node "{1}" during an attempt to setup remote execution framework directory "{0}": Cause: An operation requiring remote execution could not complete because the attempt to retrieve CVU remote execution framework version failed. The accompanying message provides detailed failure information.; Action: Ensure that the user executing the checks has sufficient permissions to execute an executable under the indicated directory. Refer to the accompanying error messages for execution failure information, resolve the issues and retry the operation.
PRVH-00520: failed to generate HTML report: Cause: Error occurred while generating the requested HTML report for the Cluster Verification Utility operation.; Action: Examine the accompanying error message for details, resolve issues identified and retry the operation.
PRVH-00521: OS kernel parameter "{0}" does not have expected current value on node "{1}" [Expected = "{2}" ; Current = "{3}";].: Cause: The Cluster Verification Utility (CVU) found that the current value for an OS kernel parameter did not match the expected value.; Action: Modify the indicated kernel parameter current value to match the required value.
PRVH-00554: Grid Infrastructure Management Repository is not yet installed and configured on this cluster.: Cause: Grid Infrastructure Management Repository was selected during Install, however it was not found to be installed or configured.; Action: Ensure that the Grid Infrastructure Management Repository is installed and configured for this cluster.
PRVH-00555: Error encountered while trying to determine whether the Grid Infrastructure Management Repository is configured for the CRS home "{0}".: Cause: The current configuration status of Grid Infrastructure Management Repository for the indicated CRS home was not determined.; Action: Ensure that the Grid Infrastructure Management Repository is installed and configured for the indicated CRS home. Examine the accompanying error message, resolve the problems indicated there, and then retry the operation.
PRVH-00558: TCP connectivity failed for the SCAN listeners on cluster "{0}" with SCAN name "{1}" on node "{2}".: Cause: Cluster Verification Utility (CVU) found that connection to SCAN listeners of shared SCAN client failed from the indicated node.; Action: Ensure that SCAN listeners on the indicated shared SCAN server cluster are running. Also, examine the accompanying messages for more details on the cause of failure.
PRVH-00570: Oracle ACFS was found configured with resources "{0}" from CRS home "{1}" but is not available in Oracle Clusterware release version "{2}" for the current operating system platform.: Cause: The Oracle Automatic Storage Management Cluster File System (Oracle ACFS) was found configured, but was not supported on the current operating system platform by the targeted Oracle Clusterware release.; Action: Ensure that the Oracle ACFS is not in use and that no ACFS resources such as volumes or file system resources are present in the current configuration. Deconfigure and remove the indicated Oracle ACFS resources before proceeding. No data will be available to be recovered after installation, as Oracle ACFS is not available in the latest release. Refer to My Oracle Support note 1369107.1 for more information regarding this requirement.
PRVH-00571: Failed to determine if Oracle ACFS resources are configured from CRS home "{0}" on node "{1}", command "{2}" with error {3}: Cause: An attempt to query Oracle Automatic Storage Management Cluster File System (Oracle ACFS) resources failed with the indicated error.; Action: Examine the accompanying error message, resolve the problems indicated there, and then retry the operation.
PRVH-00572: Oracle ACFS Remote was found configured on Indirect Storage Member Cluster with resources "{0}" from CRS home "{1}" but is not available in Oracle Clusterware release version "{2}" .: Cause: The Oracle Automatic Storage Management Cluster File System Remote (Oracle ACFS Remote) was found configured, but was not supported for Indirect Storage Member Clusters on the current operating system platform by the targeted Oracle Clusterware release.; Action: Contact Oracle Support Services.
PRVH-00577: Vendor cluster is detected from CRS home "{0}" but is not supported in Oracle Clusterware release version "{1}".: Cause: Cluster Verification Utility (CVU) detected that the indicated Cluster Ready Services (CRS) home has a vendor cluster configuration which is not supported in the target version of Oracle Clusterware.; Action: Ensure that the vendor cluster configuration is removed after the successful upgrade to the target version of Oracle Clusterware. Refer to My Oracle Support note 2638525.1 for more information regarding this requirement.
PRVH-00578: Vendor cluster is detected but is not supported in Oracle Clusterware release version "{0}".: Cause: Cluster Verification Utility (CVU) detected the vendor cluster configuration which is not supported in the installed version of Oracle Clusterware.; Action: Ensure that the vendor cluster configuration is removed. Refer to My Oracle Support note 2638525.1 for more information regarding this requirement.
PRVH-00580: Oracle ACFS mount points "{0}" are configured with ACFS replication version older than "{1}" release.: Cause: Cluster Verification Utility (CVU) detected that the indicated mount points of Oracle Automatic Storage Management Cluster File System (Oracle ACFS) were configured with the ACFS replication version which is older than the indicated minimum supported version.; Action: Ensure that the Oracle Automatic Storage Management Cluster File System (Oracle ACFS) is configured with newer than the indicated version of ACFS replication. Examine the accompanying messages for more details. Refer to My Oracle Support note 2608560.1 for more information regarding this requirement.
PRVH-00585: Oracle ACFS mount points "{0}" were found with Oracle ACFS security feature enabled which is not supported in the target Oracle Clusterware release version "{1}".: Cause: Cluster Verification Utility (CVU) detected that the indicated mount points of Oracle Automatic Storage Management Cluster File System (Oracle ACFS) were found with Oracle ACFS security feature enabled which is not supported on the indicated target release version.; Action: Ensure that Oracle ACFS has the security feature disabled for all of the identified mount points. The security feature may be disabled by issuing the command 'acfsutil sec disable -m mount_point'. Refer to the desupport notice in the section entitled 'Changes in Oracle ACFS and Oracle ADVM in Oracle ASM 21c' in the Oracle Automatic Storage Management Cluster File System Administrator's Guide. Refer to My Oracle Support note 2688565.1 for more information regarding this requirement.
PRVH-00586: Oracle ACFS mount points "{0}" were found with Oracle ACFS auditing feature enabled which is not supported in the target Oracle Clusterware release version "{1}".: Cause: Cluster Verification Utility (CVU) detected that the indicated mount points of Oracle Automatic Storage Management Cluster File System (Oracle ACFS) were found with Oracle ACFS auditing feature enabled which is not supported on the indicated target release version.; Action: Ensure that Oracle ACFS has the auditing feature disabled for all of the identified mount points. The auditing feature may be disabled by issuing the command 'acfsutil audit disable -m mount_point -s {encr |sec}'. Refer to the desupport notice in the section entitled 'Changes in Oracle ACFS and Oracle ADVM in Oracle ASM 21c' in the Oracle Automatic Storage Management Cluster File System Administrator's Guide. Refer to My Oracle Support note 2688565.1 for more information regarding this requirement.
PRVH-00600: Exascale files "{0}" are not accessible on node "{1}".: Cause: The indicated Exascale paths were found to be not accessible on the indicated node.; Action: Ensure that the indicated Exascale vault and files are present and accessible on the indicated node and retry the operation.
PRVH-00601: The legacy domain sockets directory path "{0}" is not a filesystem symbolic link to the domain sockets directory "{1}" on nodes "{2}".: Cause: The Cluster Verification Utility (CVU) determined that the indicated symbolic link did not exist on the indicated nodes.; Action: Ensure that the indicated symbolic link exists. If the indicated legacy domain sockets directory exists with contents, then stop the databases and other applications that are using SQL*Net, clear the contents of the directory, create the indicated symbolic link and restart the applications.
PRVH-00602: failed to set up passwordless SSH connectivity on nodes "{0}": Cause: An operation to perform passwordless SSH connectivity setup failed. The accompanying message provides detailed failure information.; Action: Examine the accompanying error messages, resolve the problems indicated there, and then retry the operation. If the accompanying error messages suggest issues with invalidity or incompatibility of public or private keys, then refer to the Oracle Clusterware documentation to configure SSH manually on the cluster nodes.
PRVH-00611: IP addresses "{0}" of network interfaces "{1}" on the node "{2}" conflicted with High Availability IP (HAIP) usage.: Cause: The Cluster Verification Utility (CVU) determined that the indicated network interfaces had IP addresses in the range 169.254.0.0/19 with netmask 255.255.224.0, the range used by HAIP which can create routing conflicts.; Action: Ensure that there are no IP addresses in the range 169.254.0.0/19 on any network interfaces.
PRVH-00612: GIMR is not online.: Cause: The Cluster Verification Utility (CVU) determined that the Grid Infrastructure Management Repository (GIMR) was not online.; Action: Ensure that the GIMR is enabled and running for the Oracle Clusterware upgrade operation to succeed and retry the operation.
PRVH-00656: User with root privileges attempted to perform Cluster Verification Utility operation.: Cause: User with root privileges attempted an operation which is not supported to be performed as a root user.; Action: Retry the operation with a non-root user.
PRVH-00657: Software checks for software home "{0}" with software owner "{1}" was performed by user "{2}" with insufficient privileges.: Cause: The Cluster Verification Utility (CVU) determined that the software checks for the indicated software home were not performed by the indicated software owner.; Action: Ensure that the operation is performed by the indicated software owner.
PRVH-00662: VM resources exist which are registered with Oracle Virtual Machine Manager (OVMM): Cause: Cluster Verification Utility (CVU) determined that there were Oracle Virtual Machine resources registered which were no longer supported.; Action: Remove all the Oracle Virtual Machine resources of type 'ora.vm.type' with the command 'srvctl remove vm' and retry the upgrade. Run 'srvctl config vm' command to find all the configured Virtual Machine (VM) resources.
PRVH-00663: Oracle Clusterware software patch level "{0}" value in Oracle Cluster Registry (OCR) does not match the value "{1}" in Oracle Local Registry (OLR) on node "{2}".: Cause: The Cluster Verification Utility (CVU) found that the indicated Oracle Clusterware software patch level values in OCR and OLR did not match. The patching operation was either in progress or not complete on the indicated node.; Action: Complete the patching operation to ensure the consistency of Oracle Clusterware software patch level and retry the operation.
PRVH-00664: Oracle Clusterware active patch level "{0}" does not match release patch level "{1}" on node "{2}".: Cause: The Cluster Verification Utility (CVU) found that the indicated Oracle Clusterware active patch level did not match the indicated release patch level on the indicated node. The patching operation was either in progress or not complete on the indicated node; Action: Complete the patching operation to ensure the consistency of Oracle Clusterware release patch level and retry the operation.
PRVH-00665: Oracle Clusterware upgrade state is not NORMAL. [Found = "{0}"]: Cause: The Cluster Verification Utility (CVU) pre-check found that Oracle Clusterware was in the middle of an upgrade with the indicated state.; Action: Use the command 'crsctl query crs activeversion -f' to check the upgrade state of the cluster. If the cluster is not intended to be in the middle of an upgrade, then complete the operation to ensure that the cluster is in NORMAL state and retry the operation.
PRVH-00666: No swap devices configured on node "{0}": Cause: The Cluster Verification Utility (CVU) determined that swap devices were not configured on the indicated node.; Action: Ensure that swap devices configured on the indicated node to get the swap space information.
PRVH-00667: SPFILE "{0}" and SPFILE backup "{1}" for ASM are on the same Oracle ASM disk group.: Cause: The Cluster Verification Utility (CVU) check found that the indicated ASM SPFILE backup file was on the same Oracle ASM disk group as the SPFILE.; Action: Ensure that the ASM SPFILE backup is on a different Oracle ASM disk group than the SPFILE.
PRVH-00668: Version consistency check failed for OPatch utility of the software home "{0}".: Cause: The Cluster Verification Utility (CVU) check found that the version of OPatch utility was not consistent across the cluster.; Action: Refer to accompanying messages for node-wise information of OPatch utility version. Ensure that the OPatch utility version is consistent across the cluster.
PRVH-00676: The state of the Oracle ASM cluster is not as expected to allow patch operation. [Expected = "{0}" ; Found = "{1}"]: Cause: The Cluster Verification Utility (CVU) pre-check found that Oracle ASM cluster was in the middle of some other operation with the indicated state. A patch application could not be performed in the indicated state.; Action: Use the command 'asmcmd showclusterstate' to check the state of the cluster. Complete the Oracle ASM operation with the indicated state to ensure that Oracle ASM cluster is in NORMAL state and retry the operation.
PRVH-00680: The socket send buffer size could not be set to the value of "{0}" bytes on the container node "{1}", maximum allowed send buffer size on this container node is "{2}" bytes.: Cause: The Cluster Verification Utility (CVU) pre-check found that the socket send buffer size could not be set to the indicated value on the identified container node.; Action: The container node may not control the value in its namespace and hence the required send buffer size may be configured by setting the wmem_max kernel parameter from the Linux host of the container.
PRVH-00681: The socket send buffer default size is not set to the minimum expected value on the container node "{0}". [Expected = "{1}" bytes ; Found = "{2}" bytes]: Cause: The Cluster Verification Utility (CVU) pre-check found that the default value of socket send buffer size was not be set to the indicated minimum expected value on the identified container node.; Action: The container node may not control the value in its namespace and hence the required send buffer size may be configured by setting the wmem_default kernel parameter from the Linux host of the container.
PRVH-00682: The socket receive buffer size could not be set to the value of "{0}" bytes on the container node "{1}", maximum allowed send buffer size on this container node is "{2}" bytes.: Cause: The Cluster Verification Utility (CVU) pre-check found that the socket receive buffer size could not be set to the indicated value on the identified container node.; Action: The container node may not control the value in its namespace and hence the required send buffer size may be configured by setting the rmem_max kernel parameter from the Linux host of the container.
PRVH-00683: The socket receive buffer default size is not set to the minimum expected value on the container node "{0}". [Expected = "{1}" bytes ; Found = "{2}" bytes]: Cause: The Cluster Verification Utility (CVU) pre-check found that the default value of socket receive buffer size was not be set to the indicated minimum expected value on the identified container node.; Action: The container node may not control the value in its namespace and hence the required send buffer size may be configured by setting the rmem_default kernel parameter from the Linux host of the container.
PRVH-00980: The executable file "{0}" with ownership "{1}" did not match the expected ownership "{2}" on node "{3}": Cause: The Cluster Verification Utility (CVU) check found that the indicated file being executed did not have correct ownership.; Action: Examine the accompanying error messages for more details. An alternate work area location may be selected by updating the CV_DESTLOC property inside the cvu_config file in the software home cv/admin/ directory.
PRVH-00982: The executable path "{0}" is a filesystem symbolic link and not a regular file on node "{1}".: Cause: The Cluster Verification Utility (CVU) determined that the indicated path was not a regular file but a filesystem symbolic link on the identified node.; Action: Examine the accompanying error messages for more details. An alternate work area location may be selected by updating the CV_DESTLOC property inside the cvu_config file in the software home cv/admin/ directory.
PRVH-00997: Some of the verification checks will be skipped due to unavailability of required software in the specified destination CRS home path "{0}".: Cause: The Cluster Verification Utility (CVU) check found that the indicated destination CRS home location was either an empty directory or did not contain all of the required software bits.; Action: Ensure that the specified destination CRS home directory is complete and is an up-to-date copy of the targeted version of CRS home.
PRVH-00998: Selected trace location "{0}" does not meet the minimum requirement.: Cause: The Cluster Verification Utility (CVU) check found that the indicated trace location did not meet the minimum prerequisites.; Action: Examine the accompanying error messages for more details. An alternate trace location may be selected by setting an environment variable CV_TRACELOC to any writable directory with sufficient free space.
PRVH-01001: Failed to update the current clock source using command "{0}" on node "{1}". Detailed error: {2}: Cause: An attempt to update the current clock source with the 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.
PRVH-01002: Parameter "UsePAM" set to "no" in the SSH daemon configuration file "{0}" on node "{1}".: Cause: The Cluster Verification Utility (CVU) determined that the secure shell (SSH) daemon configuration file was updated to not use the Pluggable Authentication Module (PAM) on the indicated node. The shell limits from the limits.conf file would not be in effect if PAM authentication is disabled instead, the default SSH daemon shell limits would be in effect.; Action: Ensure that PAM authentication is enabled by setting the parameter 'UsePAM' to 'yes' in the indicated file on the indicated node to enforce the shell limits from the limits.conf file and retry the fixup operation.