150 PRVH-00100 to PRVH-01507
- PRVH-00100: Restricted deletion flag is not set for path "{0}" on node "{1}".
-
Cause: The Configuration Verification Utility (CVU) determined that the indicated path did not have restricted deletion flag (sticky bit) set on the indicated node.
- PRVH-00101: Restricted deletion flag is set for path "{0}" on node "{1}".
-
Cause: The Configuration Verification Utility (CVU) determined that the indicated path had a restricted deletion flag (sticky bit) set on the indicated node.
- PRVH-00102: File "{0}" does not exist on node "{1}".
-
Cause: The Configuration Verification Utility (CVU) determined that the indicated file did not exist on the indicated node.
- PRVH-00103: Directory "{0}" does not exist on node "{1}".
-
Cause: The Configuration Verification Utility (CVU) determined that the indicated directory did not exist on the indicated node.
- PRVH-00104: Link "{0}" does not exist on node "{1}".
-
Cause: The Configuration Verification Utility (CVU) determined that the indicated file system link did not exist on the indicated node.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- PRVH-00154: File "{0}" is empty on node "{1}".
-
Cause: The identified path was found to be zero bytes file 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.
- PRVH-00159: Group ID "{0}" does not exist on node "{1}".
-
Cause: The specified group ID did not exist on the specified node.
- PRVH-00161: File "{0}" is not expected on node "{1}".
-
Cause: The Configuration Verification Utility (CVU) determined that the indicated file already existed on the indicated node.
- PRVH-00162: Directory "{0}" is not expected on node "{1}".
-
Cause: The Configuration Verification Utility (CVU) determined that the indicated directory already existed on the indicated node.
- PRVH-00163: Link "{0}" is not expected on node "{1}".
-
Cause: The Configuration Verification Utility (CVU) determined that the indicated file system link already existed on the indicated node.
- PRVH-00169: Checksum of the file "{0}" is inconsistent across nodes. [Found = "{1}"]
-
Cause: The Configuration Verification Utility (CVU) determined the checksum of the indicated file was not the same on all cluster nodes.
- PRVH-00180: Path "{0}" is not a file on node "{1}".
-
Cause: The Configuration Verification Utility (CVU) determined that the indicated path was not a file but a directory on the identified node.
- PRVH-00181: Path "{0}" is not a directory on node "{1}".
-
Cause: The Configuration Verification Utility (CVU) determined that the indicated path was not a directory on the indicated node.
- PRVH-00182: Path "{0}" is not a link on node "{1}".
-
Cause: The Configuration Verification Utility (CVU) determined that the indicated path was not a 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 Configuration Verification Utility (CVU) determined that the indicated path was incorrectly 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 Configuration Verification Utility (CVU) determined that the indicated path was incorrectly owned by the indicated group on the identified node.
- PRVH-00185: Path "{0}" does not allow execution on node "{1}".
-
Cause: The Configuration Verification Utility (CVU) determined that the indicated path did not allow execution of any executable on the identified node.
- PRVH-00186: Path "{0}" is not owned by user "{1}" and user is not the member of group "{2}" of the path on node "{3}".
-
Cause: The Configuration Verification Utility (CVU) determined that the indicated path was not owned by the indicated user and the user was not a member of the group of the path on the indicated node.
- 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.
- PRVH-00501: ASM filter driver discovery diskstring "{0}" is invalid.
-
Cause: Configuration Verification Utility check found that the indicated ASM filter driver discovery diskstring contains path names that are invalid OS path names.
- 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: Configuration Verification Utility (CVU) found that IPC protocol used by ASM instances was not consistent across the cluster nodes.
- PRVH-00511: ASM instances do not use the IPC protocol 'RDS' for IPC communication on nodes "{0}".
-
Cause: Configuration Verification Utility (CVU) found that IPC protocol used by ASM instances was not RDS on the indicated nodes.
- PRVH-00512: ASM instances use the IPC protocol 'UDP' for IPC on nodes "{0}".
-
Cause: The Configuration 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.
- PRVH-00513: ASM instances use the IPC protocol 'RDS' for IPC on nodes "{0}".
-
Cause: The Configuration 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.
- 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.
- PRVH-00520: failed to generate HTML report
-
Cause: Error occurred while generating the requested HTML report for the Configuration Verification Utility operation.
- PRVH-00521: OS kernel parameter "{0}" does not have expected current value on node "{1}" [Expected = "{2}" ; Current = "{3}";].
-
Cause: The Configuration Verification Utility (CVU) found that the current value for an OS kernel parameter did not match the expected value.
- PRVH-00525: The specified command is only supported from the configured Cluster Ready Services (CRS) or High Availability (HA) home.
-
Cause: The specified command was not run from the configured CRS or HA home. The command is supported only from configured Cluster Ready Services (CRS) or High Availability (HA) home.
- 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.
- 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.
- PRVH-00556: The specified command is not compatible with the configured home "{0}". Run command from the location "{1}".
-
Cause: The specified command was not compatible with the home from which it was run.
- PRVH-00557: The specified command is not compatible with the configured home "{0}". This command is only supported from the configured CRS home.
-
Cause: The specified command was not compatible with the home from which it was run. The command is supported only from configured Cluster Ready Services (CRS) home.
- PRVH-00558: TCP connectivity failed for the SCAN listeners on cluster "{0}" with SCAN name "{1}" on node "{2}".
-
Cause: Configuration Verification Utility (CVU) found that connection to SCAN listeners of shared SCAN client failed from the indicated node.
- 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.
- 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.
- 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.
- PRVH-00573: Oracle ACFS driver from CRS home "{0}" is supported on the current kernel version of the operating system, but will not be supported on the specified target kernel "{1}"
-
Cause: The Oracle Automatic Storage Management Cluster File System (Oracle ACFS) was found supported on the current operating system kernel version, but was not compatible with the indicated kernel of the operating system.
- PRVH-00574: Failed to determine if Oracle ACFS driver from CRS home "{0}" is compatible with kernel "{1}" , command "{2}" failed with error:
-
Cause: An attempt to check if Oracle Automatic Storage Management Cluster File System (Oracle ACFS) driver is compatible with the specified kernel failed with the indicated error.
- PRVH-00577: Vendor cluster is detected from CRS home "{0}" but is not supported in Oracle Clusterware release version "{1}".
-
Cause: Configuration 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.
- PRVH-00578: Vendor cluster is detected but is not supported in Oracle Clusterware release version "{0}".
-
Cause: Configuration Verification Utility (CVU) detected the vendor cluster configuration which is not supported in the installed version of Oracle Clusterware.
- PRVH-00580: Oracle ACFS mount points "{0}" are configured with ACFS replication version older than "{1}" release.
-
Cause: Configuration 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.
- 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: Configuration 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.
- 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: Configuration 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.
- PRVH-00591: Oracle ASM Filter Driver (AFD) from CRS home "{0}" is supported on the current kernel version of the operating system, but will not be supported on the specified target kernel "{1}"
-
Cause: The Oracle ASM Filter Driver (AFD) was found supported on the current operating system kernel version, but was not compatible with the indicated kernel of the operating system.
- PRVH-00592: Failed to determine if Oracle ASM Filter Driver (AFD) from CRS home "{0}" is compatible with kernel "{1}" , command "{2}" failed with error:
-
Cause: An attempt to check if Oracle ASM Filter Driver (AFD) is compatible with the specified kernel failed with the indicated error.
- 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 Configuration Verification Utility (CVU) determined that the indicated symbolic link did not exist on the indicated nodes.
- 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.
- PRVH-00611: IP addresses "{0}" of network interfaces "{1}" on the node "{2}" conflicted with High Availability IP (HAIP) usage.
-
Cause: The Configuration 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.
- PRVH-00612: GIMR is not online.
-
Cause: The Configuration Verification Utility (CVU) determined that the Grid Infrastructure Management Repository (GIMR) was not online.
- PRVH-00656: User with root privileges attempted to perform Configuration Verification Utility operation.
-
Cause: User with root privileges attempted an operation which is not supported to be performed as a root user.
- PRVH-00657: Software checks for software home "{0}" with software owner "{1}" was performed by user "{2}" with insufficient privileges.
-
Cause: The Configuration Verification Utility (CVU) determined that the software checks for the indicated software home were not performed by the indicated software owner.
- PRVH-00662: VM resources exist which are registered with Oracle Virtual Machine Manager (OVMM)
-
Cause: Configuration Verification Utility (CVU) determined that there were Oracle Virtual Machine resources registered which were no longer supported.
- 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 Configuration 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.
- PRVH-00664: Oracle Clusterware active patch level "{0}" does not match release patch level "{1}" on node "{2}".
-
Cause: The Configuration 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
- PRVH-00665: Oracle Clusterware upgrade state is not NORMAL. [Found = "{0}"]
-
Cause: The Configuration Verification Utility (CVU) pre-check found that Oracle Clusterware was in the middle of an upgrade with the indicated state.
- PRVH-00666: No swap devices configured on node "{0}"
-
Cause: The Configuration Verification Utility (CVU) determined that swap devices were not configured on the indicated node.
- PRVH-00667: SPFILE "{0}" and SPFILE backup "{1}" for ASM are on the same Oracle ASM disk group.
-
Cause: The Configuration Verification Utility (CVU) check found that the indicated ASM SPFILE backup file was on the same Oracle ASM disk group as the SPFILE.
- PRVH-00668: Version consistency check failed for OPatch utility of the software home "{0}".
-
Cause: The Configuration Verification Utility (CVU) check found that the version of OPatch utility was not 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 Configuration 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.
- PRVH-00679: Grid Infrastructure Management Repository validation failed on node "{0}".
-
Cause: The Configuration Verification Utility (CVU) found that Oracle GIMR was not configured properly.
- 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 Configuration 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.
- 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 Configuration 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.
- 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 Configuration 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.
- 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 Configuration 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.
- PRVH-00686: AutoUpgrade check "{0}" failed.
-
Cause: The specified AutoUpgrade check failed during the pre-upgrade checks.
- PRVH-00695: Swap size is enabled and set to "{0}" on kubernetes container host "{1}".
-
Cause: The Configuration Verification Utility (CVU) pre-check found that the specified kubernetes container host had swap size enabled.
- PRVH-00698: Datapatch check "{0}" failed.
-
Cause: The specified Datapatch check failed during the pre-patch checks.
- PRVH-00700: Oracle High availability managed resource "{0}" is found in state "{1}" but is expected to be in state "{2}" on node "{3}".
-
Cause: The Configuration Verification Utility (CVU) determined that the indicated resource was not in an ONLINE state on the identified node.
- PRVH-00732: Oracle Autonomous Health Framework service resource "{0}" is not configured.
-
Cause: The Configuration Verification Utility (CVU) identified the specified Oracle Autonomous Health Framework service resource was not configured.
- PRVH-00733: Failed to check the existence of Oracle Autonomous Health Framework service resource "{0}".
-
Cause: The Configuration Verification Utility (CVU) failed to determine the existence of the specified Oracle Autonomous Health Framework service resource.
- PRVH-00753: Policy managed database "{0}" was found configured from Oracle Home "{1}" and is not supported from the target release of the Oracle Clusterware
-
Cause: The Configuration Verification Utility (CVU) identified the indicated policy managed database configured from the specified home which was not supported by the target release of the Oracle Clusterware.
- PRVH-00755: Policy "{0}" was found configured and is not supported from the target release of the Oracle Clusterware
-
Cause: The Configuration Verification Utility (CVU) identified the indicated policy configured, which was not supported by the target release of the Oracle Clusterware.
- PRVH-00757: Server pool "{0}" was found configured and is not supported from the target release of the Oracle Clusterware
-
Cause: The Configuration Verification Utility (CVU) identified the indicated server pool configured, which was not supported by the target release of the Oracle Clusterware.
- PRVH-00979: CVU destination directory path "{0}" is shared on nodes "{1}"
-
Cause: The Configuration Verification Utility (CVU) determined that the indicated directory path was shared between the indicated nodes.
- PRVH-00980: The executable file "{0}" with ownership "{1}" did not match the expected ownership "{2}" on node "{3}"
-
Cause: The Configuration Verification Utility (CVU) check found that the indicated file being executed did not have correct ownership.
- PRVH-00982: The executable path "{0}" is a filesystem symbolic link and not a regular file on node "{1}".
-
Cause: The Configuration Verification Utility (CVU) determined that the indicated path was not a regular file but a filesystem symbolic link on the identified node.
- 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 Configuration 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.
- PRVH-00998: Selected trace location "{0}" does not meet the minimum requirement.
-
Cause: The Configuration Verification Utility (CVU) check found that the indicated trace location did not meet the minimum prerequisites.
- 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.
- PRVH-01002: Parameter "UsePAM" set to "no" in the SSH daemon configuration file "{0}" on node "{1}".
-
Cause: The Configuration 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.
- PRVH-01003: CVU automated fix up operation failed in the cluster.
-
Cause: An attempt to perform the Configuration Verification Utility (CVU) automated fix up operation failed.
- PRVH-01004: Failed to generate the fix up data for the failed tasks.
-
Cause: An attempt to generate the fix up data was failed during Cluster Verification Utility (CVU) automated fix up operation.
- PRVH-01501: The location "{0}" for stand alone pluggable CVU home is not suitable to use.
-
Cause: The Configuration Verification Utility (CVU) determined that the indicated location did not contain the required software or the CVU software version was not supported.
- PRVH-01502: failed to run the cluster verification checks from the stand alone pluggable CVU home location "{0}"
-
Cause: The Configuration Verification Utility (CVU) determined that the cluster verification checks could not be performed from the specified location.
- PRVH-01503: failed to run the cluster verification check "{0}" from the stand alone pluggable CVU home location "{1}"
-
Cause: The Configuration Verification Utility (CVU) determined that the indicated cluster verification check could not be performed from the specified location.
- PRVH-01505: Oracle Database "{0}" version "{1}" is lower than the minimum compatible version "{2}" for target release version "{3}" of Oracle Clusterware.
-
Cause: The specified database was found to be not compatible with the target release of Oracle Clusterware.
- PRVH-01506: failed to perform the Oracle Database version compatibility check
-
Cause: The Configuration Verification Utility (CVU) upgrade prerequisite checks failed to determine the compatibility of configured Oracle Databases with target release of the Oracle Clusterware.
- PRVH-01507: ORAchk/EXAchk checks are skipped.
-
Cause: The Configuration Verification Utility (CVU) could not determine the location of ORAchk/EXAchk utility to perform the checks.