117 PRCT-01000 to PRCT-01570
- PRCT-01000: File path is null
-
Cause: The supplied path is set to null.
- PRCT-01001: Node name is null
-
Cause: The supplied node name is set to null.
- PRCT-01003: failed to run "{0}" on node "{1}"
-
Cause: An attempt to execute the specified command failed. The accompanying error messages provide more details.
- PRCT-01004: Directory name passed was null
-
Cause: The supplied directory name is set to null.
- PRCT-01005: Directory {0} does not exist
-
Cause: The supplied directory path does not exist.
- PRCT-01006: Failed to retrieve cluster name from node "{0}"
-
Cause: Failed to get the cluster name using the command 'olsnodes -c' from the specified node.
- PRCT-01007: Failed to retrieve local node name
-
Cause: Underlying call failed to get the local hostname.
- PRCT-01008: Failed to retrieve node names
-
Cause: Failed to get the node names using the command 'olsnodes'.
- PRCT-01009: crsctl execution failed. Detailed error:\n{0}
-
Cause: Failed to execute crsctl command.
- PRCT-01010: crsctl execution failed on node {0}. Detailed error:\n{1}
-
Cause: Failed to execute crsctl command on the specified node.
- PRCT-01011: Failed to run "{0}". Detailed error: {1}
-
Cause: Failed to execute the specified command on the local node.
- PRCT-01012: Invalid file path {0}
-
Cause: The supplied path does not exist.
- PRCT-01013: failed to start remote execution server on local node
-
Cause: An attempt to start the required remote execution server on the local node failed. Detailed failure information is supplied by the accompanying messages.
- PRCT-01014: Internal error: {0}
-
Cause: An internal error occurred. The included value is an internal identifier.
- PRCT-01015: Version supplied is null
-
Cause: The supplied version was set to null.
- PRCT-01050: Failed to parse output returned by kfod when executing kfod at location {0}
-
Cause: Failed to parse the output returned by executing kfod because the output string is null or has fewer rows than expected
- PRCT-01051: Failed to parse the output returned by kfod for node {0} when executing kfod at location {1}
-
Cause: Failed to parse the output returned by executing kfod on the specified node because the output string is null or has fewer rows than expected.
- PRCT-01052: Failed to parse output {0} returned by kfod when executing kfod at location {1}
-
Cause: Failed to parse the output returned by executing kfod because the output has fewer columns than expected.
- PRCT-01053: Failed to parse output {0} returned by kfod for node {1} when executing kfod at location {2}
-
Cause: Failed to parse the output returned by executing kfod on the specified node because the output has fewer columns than expected.
- PRCT-01054: Fail to retrieve ASM active version for local node
-
Cause: Failed to get the active version of ASM by executing 'kfod nohdr=true op=version hostlist=hostlist'.
- PRCT-01055: Fail to retrieve ASM active version for node {0}. kfod execution failed at location {1}. Detailed error:\n{2}
-
Cause: Failed to get the active version of ASM by executing 'kfod nohdr=true op=version hostlist=hostlist' on the specified node.
- PRCT-01056: Fail to retrieve ASM instance type. kfod execution failed at location {0}. Detailed error:\n{1}
-
Cause: Failed to get the instance type for ASM instance by executing 'kfod nohdr=true op=version'.
- PRCT-01057: The value of ASM instance type {0} is not correct
-
Cause: The value of ASM instance type is invalid.
- PRCT-01058: Fail to check if ASM is running on node {0}. kfod execution failed at location {1}. Detailed error:\n{2}
-
Cause: Failed to check whether ASM is running by executing 'kfod nohdr=true op=insts hostlist=hostlist'.
- PRCT-01059: Fail to retrieve list of disk group names for node {0}. kfod execution failed at location {1}. Detailed error:\n{2}
-
Cause: Failed to get the diskgroup names by executing 'kfod nohdr=true op=groups hostlist=hostlist'.
- PRCT-01060: Fail to check if ASM is in rolling migration. kfod execution failed at location {1}. Detailed error:\n{2}
-
Cause: Failed to check whether ASM is in rolling migration by executing 'kfod nohdr=true op=rm'.
- PRCT-01061: Failed to verify ASM client credentials file "{0}"\n{1}
-
Cause: An attempt to verify that the ASM client credentials file specified is a valid credentials file failed.
- PRCT-01062: Failed to verify ASM client credentials.\n{0}
-
Cause: An attempt to verify the ASM credentials for this client cluster failed.
- PRCT-01063: Failed to get list of disks managed by ASM on node "{0}"\n{1}
-
Cause: An attempt to obtain the list of disks that are managed by ASM on the specified node failed.
- PRCT-01064: Failed to get ASM default disk discovery string \n {0}
-
Cause: An attempt to obtain the ASM default disk string failed.
- PRCT-01065: Failed to verify the size consistency of ASM disks on node "{0}". kfod execution failed at location "{1}". Detailed error:\n{2}
-
Cause: An attempt to verify the consistency of ASM disk sizes failed on the identified node with the indicated error message.
- PRCT-01100: Failed to retrieve ACFS active version for local node
-
Cause: Failed to execute acfsutil to retrieve the ACFS active version on the local node.
- PRCT-01101: Failed to retrieve ACFS active version for node {0}. acfsutil execution failed at file location {1}. Detailed error:\n{2}
-
Cause: Failed to execute acfsutil to retrieve the ACFS active version on the supplied node.
- PRCT-01102: Failed to parse output when executing acfsutil at file location {0}
-
Cause: Unable to parse output returned by acfsutil.
- PRCT-01103: Failed to parse the output for node {0} when executing acfsutil at file location {1}
-
Cause: Unable to parse output returned by acfsutil on the supplied node.
- PRCT-01104: Failed to parse output {0} when executing acfsutil at file location {1}
-
Cause: Unable to parse output returned by acfsutil at specified location.
- PRCT-01105: Failed to parse output {0} for node {1} when executing acfsutil at file location {2}
-
Cause: Unable to parse output returned by acfsutil at specified location on the supplied node.
- PRCT-01109: Failed to get diskgroup names for node {0}
-
Cause: Unable to parse disgkroup names returned by acfsutil on the supplied node.
- PRCT-01111: Received empty result while getting ACFS Mount Points on node {1}
-
Cause: The output returned by acfsutil is empty.
- PRCT-01114: Execution of acfsutil command failed on node {0} for location {1}
-
Cause: Failed to execute acfsutil on the supplied node at the specified location.
- PRCT-01115: Execution of acfsutil failed on node {0} with result {1}
-
Cause: Failed to execute acfsutil on the supplied node.
- PRCT-01116: Invalid partition path {0} specified to acfsutil on node {1}
-
Cause: The supplied path did not exist.
- PRCT-01117: Received empty result while getting ACFS Disk Groups on node {1}
-
Cause: The output returned by acfsutil is empty.
- PRCT-01118: Received empty result while getting total space at file location {0} on node {1}
-
Cause: The output returned by acfsutil is empty.
- PRCT-01119: Received empty result while getting free space at file location {0} on node {1}
-
Cause: The output returned by acfsutil is empty.
- PRCT-01120: A NULL path has been specified for the location on node {0}
-
Cause: A null path was provided for the location.
- PRCT-01121: Execution of acfsutil failed on local node with result {0}
-
Cause: Execution of acfsutil failed on the local node.
- PRCT-01122: Received empty result while getting mountpoint for path {0} on the local node
-
Cause: acfsutil returned an empty value when querying for the mountpoint of a specified path.
- PRCT-01123: The mountpoint is either set to null or empty
-
Cause: The supplied mountpoint is either an empty string or is set to null.
- PRCT-01124: Received empty result while getting volume device for mountpoint {0} on the local node
-
Cause: acfsutil returned an empty value when querying for the volume device of a specified mountpoint.
- PRCT-01125: The volume device is either set to null or empty
-
Cause: The supplied volume device is either an empty string or is set to null.
- PRCT-01126: Received empty result while getting mountpoint for volume device {0} on the local node
-
Cause: acfsutil returned an empty value when querying for the volume device of a specified mountpoint.
- PRCT-01127: Received empty result while getting all volume devices on the local node
-
Cause: No ACFS volume devices has been created.
- PRCT-01128: ACFS is not supported on this operating system
-
Cause: ACFS is not supported on the accompanying operating system.
- PRCT-01129: Execution of ACFS driver state check failed on local node with result {0}
-
Cause: Execution of ACFS driver state check failed on the local node
- PRCT-01130: Execution of advmutil failed on local node with result {0}
-
Cause: Execution of advmutil failed on the local node
- PRCT-01131: Failed to retrieve mount point for volume device {0}
-
Cause: No ACFS filesystem was mounted for the specified volume device.
- PRCT-01132: ACFS driver state check with "{0}" option on local node failed to display any output
-
Cause: No output was captured when executing ACFS driver state check with the specified option on the local node.
- PRCT-01133: ACFS driver state check with "{0}" option on node {1} failed to display any output
-
Cause: No output was captured when executing ACFS driver state check with the specified option on the specified node.
- PRCT-01134: Execution of ACFS driver state check failed on node {0} with result {1}
-
Cause: Execution of ACFS driver state check failed on the specified node.
- PRCT-01135: This platform does not support a default location for "{0}"
-
Cause: An attempt to run the 'acfsutil' command did not provide a location of this binary
- PRCT-01136: Invalid mount point
-
Cause: An internal error occurred.
- PRCT-01137: acfsutil command failed as the Snapshot {0} does not exist
-
Cause: The acfsutil command to delete the snapshot with the specified name failed as it does not exist.
- PRCT-01138: acfsutil command failed as the snapshot {0} already exists
-
Cause: The acfsutil command to create a snapshot failed because the snapshot with the specified name already existed.
- PRCT-01139: Execution of AFD driver state check failed on the local node with result {0}
-
Cause: Execution of ASM filter driver state check failed on the local node.
- PRCT-01140: Execution of AFD driver state check failed on node {0} with result {1}
-
Cause: Execution of ASM filter driver state check failed on the specified node.
- PRCT-01149: Failed to retrieve cluster name
-
Cause: The olsnodes command executed successfully, but there was no output.
- PRCT-01150: Failed to retrieve cluster name
-
Cause: Clusterware is not running.
- PRCT-01151: Failed to retrieve cluster nodes status
-
Cause: Clusterware is not running.
- PRCT-01152: Received empty result while getting cluster nodes Status Map
-
Cause: The olsnodes command executed successfully, but there was no output.
- PRCT-01153: Received empty result while getting a list of pinned and unpinned nodes in the cluster
-
Cause: The olsnodes command executed successfully, but there was no output.
- PRCT-01154: Failed to retrieve private host name for all cluster nodes. Detailed error:\n{0}
-
Cause: Clusterware is not running.
- PRCT-01155: Received empty result while getting the private interconnect for nodes in the cluster
-
Cause: The olsnodes command executed successfully, but there was no output.
- PRCT-01200: Failed to retrieve disk group name for volume device {0}. asmcmd execution failed at location {1}. Detailed error:\n{2}
-
Cause: Unable to retrieve the disk group name for the specified volume device
- PRCT-01201: Failed to retrieve volume name for volume device {0}. asmcmd execution failed at location {1}. Detailed error:\n{2}
-
Cause: Unable to retrieve the volume name for the specified volume device
- PRCT-01202: Failed to parse output returned by asmcmd when executing asmcmd at location {0}
-
Cause: Unable to parse output returned by asmcmd.
- PRCT-01203: Failed to parse the output returned by asmcmd for node {0} when executing asmcmd at location {1}
-
Cause: This is an internal error.
- PRCT-01204: Failed to find volume device {0}. asmcmd execution failed at location {1}. Detailed error:\n{2}
-
Cause: Volume device does not exist.
- PRCT-01205: Failed to parse output {0} returned by asmcmd when executing asmcmd at location {1}
-
Cause: Unable to parse the specified output returned by asmcmd.
- PRCT-01206: Failed to parse output {0} returned by asmcmd for node {1} when executing asmcmd at location {2}
-
Cause: Unable to parse the specified output returned by asmcmd on specified node.
- PRCT-01207: Failed to set the ORACLE_SID for running asmcmd from CRS home location {0}
-
Cause: Unable to retrieve the ASM instance name on the local node to generate the ORACLE_SID value.
- PRCT-01208: Failed to create volume {0}. asmcmd execution failed at location {1}. Detailed error:\n{2}
-
Cause: An attempt to execute asmcmd to create the volume device for the specified volume name failed.
- PRCT-01209: Diskgroup {0} does not have enough space. asmcmd execution failed at location {1}. Detailed error:\n{2}
-
Cause: Failed to execute asmcmd because the diskgroup does not have enough space for the specified operation.
- PRCT-01210: Disk group {0} does not exist. asmcmd execution failed at location {1}. Detailed error:\n{2}
-
Cause: An attempt to execute asmcmd to perform an operation with the disk group failed.
- PRCT-01211: Volume {0} is in use. asmcmd execution failed at location {1}. Detailed error:\n{2}
-
Cause: An attempt to execute asmcmd to create a volume with the specified volume name failed because this name is already being used by another volume.
- PRCT-01212: Failed to delete volume device {0}.asmcmd execution failed at location {1}. Detailed error:\n{2}
-
Cause: An attempt to execute asmcmd to delete the volume device for the specified volume name failed.
- PRCT-01213: Failed to get volume device for volume {0}.asmcmd execution failed at location {1}. Detailed error:\n{2}
-
Cause: An attempt to execute asmcmd to get the volume device for the specified volume name failed.
- PRCT-01214: Command 'asmcmd' could not be executed from directory {1}. Failed to retrieve discovery string for ASM instance. Detailed error:\n{2}
-
Cause: An attempt to retrieve the discovery string used by ASM instance failed.
- PRCT-01215: Command 'asmcmd' could not be executed from directory {1}. Failed to retrieve the list of disks from ASM instance. Detailed error:\n{2}
-
Cause: An attempt to retrieve the list of disks from ASM instance failed.
- PRCT-01217: Command 'asmcmd' could not be executed from directory {0}. Failed to resize volume {1}. Detailed error:\n{2}
-
Cause: An attempt to resize the volume failed.
- PRCT-01218: Command 'asmcmd' could not be executed from directory {1}. Failed to retrieve information of disk groups from ASM instance. Detailed error:\n{2}
-
Cause: An attempt to retrieve the list of disk groups from ASM instance failed.
- PRCT-01219: Command 'asmcmd spget' could not be executed from directory {0}. Failed to retrieve the ASM SPFILE location for ASM instance. Detailed error:\n{1}
-
Cause: An attempt to retrieve the SPFILE used by an ASM instance failed.
- PRCT-01220: Received empty result while getting the ASM SPFILE location for ASM instances using command 'asmcmd spget' from directory {0}
-
Cause: The indicated ASMCMD command executed successfully, but there was no output.
- PRCT-01221: failed to retrieve the ASM password file location for an ASM instance using command 'asmcmd pwget --asm' \n{0}
-
Cause: An attempt to retrieve the password file location for an ASM instance failed.
- PRCT-01222: Received empty result while getting the ASM password file location for an ASM instance using command 'asmcmd pwget --asm'
-
Cause: The asmcmd command executed successfully, but there was no output.
- PRCT-01223: failed to check whether the file "{0}" is on an ASM disk group \n{1}
-
Cause: An attempt to check whether the indicated file is on an ASM disk group failed.
- PRCT-01224: failed to retrieve the cluster state because the command 'asmcmd showclusterstate' can not be executed from directory {0}. Detailed error:\n{1}
-
Cause: An attempt to retrieve the cluster state failed.
- PRCT-01225: failed to verify Oracle Automatic Storage Management (Oracle ASM) user credentials using the command 'asmcmd credverify'. Detailed error:\n{0}
-
Cause: An attempt to verify Oracle ASM user credentials failed.
- PRCT-01300: oifcfg execution failed. Detailed error:\n{0}
-
Cause: Failed to execute the oifcfg command for the local node. See the accompanying error message for further details.
- PRCT-01301: oifcfg execution failed on node {0}. Detailed error:\n{1}
-
Cause: Failed to execute the oifcfg command for the remote node. See the accompanying error message for further details.
- PRCT-01302: The specified address "{0}" has an invalid IP address format
-
Cause: The format of the subnet number and/or the subnet mask was an invalid IP address format.
- PRCT-01303: The oifcfg command returned as result the line "{0}" that has less than 4 fields
-
Cause: This is an internal error.
- PRCT-01304: The specified IPv6 prefix length "{0}" is not between 0 and 128
-
Cause: The IPv6 prefix length was either not an integer or was out of the allowed range.
- PRCT-01305: The specified interface name "{0}" does not match the existing network interface name "{1}"
-
Cause: The interface name did not match the existing network interface name.
- PRCT-01306: Setting the address type to "ipv4" is an not allowed because the existing network address type is "ipv6"
-
Cause: An attempt to change the address type from 'ipv6' to 'ipv4' directly was rejected, because the address type must first be changed to 'both', then to 'ipv4'.
- PRCT-01307: Setting the address type to "ipv6" is an not allowed because the existing network address type is "ipv4"
-
Cause: An attempt to change the address type from 'ipv4' to 'ipv6' directly was rejected, because the address type must first be changed to 'both', then to 'ipv6'.
- PRCT-01308: Modifying the VIP is not allowed because the VIP name "{0}" resolved to both IPv4 and IPv6 addresses
-
Cause: The existing VIP name maps to both IPv4 and IPv6 addresses and the user tried to modify one of them.
- PRCT-01309: The USR_ORA_AUTO_VALUE attribute value "{0}" does not include both an IPv4 and an IPv6 value
-
Cause: Expected both an IPv4 value and an IPv6 value to coexist.
- PRCT-01400: getcrshome execution failed. Detailed error:\n{0}
-
Cause: Failed to execute the getcrshome command. See the accompanying error message for further details.
- PRCT-01401: getcrshome execution failed on node {0}. Detailed error:\n{1}
-
Cause: Failed to execute the getcrshome command. See the accompanying error message for further details.
- PRCT-01402: Attempt to retrieve version of SRVCTL from Oracle Home {0} failed.\n{1}
-
Cause: Failed to execute the 'srvctl -V' command. See the accompanying error message for further details.
- PRCT-01403: Failed to parse output returned by srvctl -V when executing command at Oracle home {0}
-
Cause: Failed to parse the output returned by executing the command 'srvctl -V' because the output string is null or has unexpected result
- PRCT-01404: Attempt to retrieve version of SRVCTL on node {0} from Oracle Home {1} failed. Detailed error: \n {2}
-
Cause: Failed to execute the command 'srvctl -V' command. See the accompanying error message for further details.
- PRCT-01405: Failed to parse output returned by srvctl -V when executing command at node {0} and Oracle home {1}
-
Cause: Failed to parse the output returned by executing the command 'srvctl -V' at specified node and because the output string is null or has unexpected result
- PRCT-01406: Oracle Home location: {0} does not contain {1}
-
Cause: The current Oracle Home directory does not contain the specified utility.
- PRCT-01407: failed to execute the olsnodes command to retrieve active node roles. Detailed error:\n{0}
-
Cause: An attempt to execute the command 'olsnodes -a' failed.
- PRCT-01408: Encountered unexpected output during the olsnodes command execution to retrieve active node roles
-
Cause: An attempt to execute olsnodes -a command failed.
- PRCT-01409: Received empty result while getting the active node roles for nodes in the cluster
-
Cause: The olsnodes command executed successfully, but there was no output.
- PRCT-01410: Failed to execute the crsctl command to retrieve configured node roles. Detailed error:\n{0}
-
Cause: An attempt to execute crsctl get node role config -all command failed.
- PRCT-01411: Encountered unexpected output during the crsctl command execution to retrieve configured node roles
-
Cause: An attempt to execute crsctl get node role config -all command failed.
- PRCT-01412: Received empty result while getting the configured node roles for nodes in the cluster
-
Cause: The crsctl command executed successfully, but there was no output.
- PRCT-01413: Failed to retrieve the configured node role of the node {0}
-
Cause: An attempt to execute crsctl get node role config -node command failed.
- PRCT-01414: Execution of the command {0} on the local node failed
-
Cause: An attempt to clone an Oracle Home using the given command failed.
- PRCT-01415: More than one ACFS resource was found for the mount point path {0}
-
Cause: When looking up the ACFS resource for a mount point, more than one resource was found.
- PRCT-01416: Unable to validate the interface type for subnet "{0}"
-
Cause: An attempt to validate the interface type for the given subnet failed.
- PRCT-01417: Failed to retrieve administrator groups. 'osdbagrp' execution failed at location {0}. Detailed error:\n{1}
-
Cause: During retrieval of administrator group, execution of the 'osdbagrp' command to retrieve administrator OS group names failed.
- PRCT-01418: Failed to modify the VIP for node {0} because the specified VIP name "{1}" does not resolve to both an IPv4 and IPv6 address, which is required by the network, because it has both IPv4 and IPv6 subnets
-
Cause: Both IPv4 and IPv6 configured VIP addresses existed, but the specified VIP name did not resolve to both IPv4 and IPv6 addresses.
- PRCT-01419: Failed to modify the VIP for node {0} as the specified VIP name "{1}" does not resolved to an IPv4 address
-
Cause: An IPv4 configured VIP address existed, but the specified VIP name did not resolve to an IPv4 address.
- PRCT-01420: Failed to modify the VIP for node {0} as the specified VIP name "{1}" does not resolved to an IPv6 address
-
Cause: An IPv6 configured VIP address existed, but the specified VIP name did not resolve to an IPv6 address.
- PRCT-01421: Failed to modify the VIP for node {0} because the specified VIP name or address "{1}" does not resolve to an IPv4 address
-
Cause: The configured VIP name resolved to an IPv4 address, but the specified VIP name or IP address did not resolve to an IPv4 address.
- PRCT-01422: Failed to modify the VIP for node {0} because the specified VIP name or address "{1}" does not resolve to an IPv6 address
-
Cause: The configured VIP name resolved to an IPv6 address, but the specified VIP name or IP address did not resolve to an IPv6 address.
- PRCT-01423: Failed to copy the directory contents from {0} to {1} on node {2}. Detailed error:\n{2}
-
Cause: An attempt to execute srvmhelper to copy the directory contents failed.
- PRCT-01424: Rapid Home Provisioning credentials creation failed while executing the Management Database configuration assistant on node {0}.
-
Cause: An attempt to execute the Management Database configuration assistant to create the Rapid Home Provisioning credentials failed.
- PRCT-01425: The specified VIP name "{0}" does not resolve to an IPv4 address
-
Cause: The configured VIP name resolved to an IPv4 address, but the specified VIP name did not resolve to a single IPv4 address.
- PRCT-01426: The specified VIP name "{0}" resolves to multiple addresses
-
Cause: The specified VIP name resolved to more than one IPv4 or IPv6 address.
- PRCT-01427: Failed to create the NFS resource on mount path "{0}". Detailed error:\n{1}
-
Cause: An attempt to create the NFS resource failed.
- PRCT-01428: Failed to execute Management Database configuration assistant for user "{0}" on node "{1}". Detailed error:\n{2}
-
Cause: An attempt to run Management Database configuration assistant failed.
- PRCT-01429: Failed to create wallet for Rapid Home Provisioning for user "{0}". Detailed error:\n{1}
-
Cause: An attempt to create the wallet for Rapid Home Provisioning failed.
- PRCT-01430: Failed to retrieve the Oracle ASM Dynamic Volume Manager compatibility attribute for disk group {0}. asmcmd execution failed at location {1}. Detailed error:\n{2}
-
Cause: An attempt to retrieve the 'compatible.advm' attribute for the specified disk group failed.
- PRCT-01431: The Oracle ASM Dynamic Volume Manager compatibility attribute is not set for disk group {0}.
-
Cause: An attempt to execute 'asmcmd' against the specified disk group failed because the command requires the retrieval of the 'compatible.advm' attribute which has not been set for that disk group.
- PRCT-01432: Failed to modify the VIP for node {0} because the specified VIP address "{1}" is not an IPv4 address
-
Cause: An attempt to modify a node VIP failed because the specified address was not of type IPv4 as required by the configured VIP.
- PRCT-01433: Failed to modify the VIP for node {0} because the specified VIP address "{1}" is not an IPv6 address
-
Cause: An attempt to modify a node VIP failed because the specified address was not of type IPv6 as required by the configured VIP.
- PRCT-01434: Failed to modify the VIP because the specified VIP name "{0}" does not resolve to an IPv4 address as required by network {1}
-
Cause: The configured network had an IPv4 subnet, but the specified VIP name or IP address did not resolve to an IPv4 address.
- PRCT-01435: Failed to modify the VIP because the specified VIP name "{0}" does not resolve to an IPv6 address as required by network {1}
-
Cause: The configured network had an IPv6 subnet, but the specified VIP name or IP address did not resolve to an IPv6 address.
- PRCT-01436: Volume {0} does not exist for disk group {1}. Detailed error:\n{2}
-
Cause: An attempt to execute 'asmcmd' to delete the volume for the disk group failed.
- PRCT-01437: Execution of the 'opatch lspatches -oh' command failed on local node with result {0}
-
Cause: Execution of the 'opatch lspatches -oh' failed on the local node.
- PRCT-01438: Failed to get the difference between the patches installed in {0} and {1} Oracle homes. Detailed error:\n{2}
-
Cause: An attempt to get the difference between the patches installed in the Oracle homes failed.
- PRCT-01439: Failed to create the directory {0} in nodes {1}. Detailed error:\n{2}
-
Cause: An attempt to execute srvmhelper to create the directory failed. Specifics of failure shown in appended error message.
- PRCT-01440: Failed to determine if database is administrator-managed\n{1}
-
Cause: An attempt to execute an internal command to determine if the database is administrator-managed failed. Specifics of the failure are shown in the appended error message.
- PRCT-01441: Failed to retrieve configured nodes for an administrator-managed database\n{1}
-
Cause: An attempt to execute an internal command to retrieve configured nodes for an administrator-managed database failed. Specifics of the failure are shown in the appended error message.
- PRCT-01442: Failed to execute srvmhelper command because command {0} does not exist
-
Cause: The srvmhelper script did not exist or was not accessible to the invoking user.
- PRCT-01443: Setting of password for the Rapid Home Provisioning (RHP) user failed while executing the Management Database configuration assistant on node {0}.\n{1}
-
Cause: An attempt to execute the Management Database configuration assistant to set the RHP user's password failed.
- PRCT-01444: Attempt to retrieve version of SQL*Plus from Oracle home {0} failed. Detailed error: \n {1}
-
Cause: An attempt to execute the 'sqlplus -V' command failed. See the accompanying error message for further details.
- PRCT-01445: Failed to parse output returned by sqlplus -V when executing command at Oracle home {0}. Detailed error: \n {1}
-
Cause: An attempt to parse the output returned by executing the command 'sqlplus -V' failed because the output string is null or has unexpected results.
- PRCT-01446: Attempt to retrieve version of SQL*Plus on node {0} from Oracle home {1} failed. Detailed error: \n {2}
-
Cause: An attempt to execute the 'sqlplus -V' command failed. See the accompanying error message for further details.
- PRCT-01447: Failed to parse output returned by sqlplus -V when executing command at node {0} and Oracle home {1}. Detailed error: \n {2}
-
Cause: An attempt to parse the output returned by executing the command 'sqlplus -V' at specified node failed because the output string is null or has unexpected results.
- PRCT-01448: Oracle home location: {0} does not contain {1}
-
Cause: The current Oracle home directory did not contain the specified utility.
- PRCT-01449: Execution of command 'orabase' failed. Detailed error:\n{0}
-
Cause: Execution of the 'orabase' command failed. See the accompanying error message for further details.
- PRCT-01450: The ORACLE_BASE registry key {0} has an empty value on node {1}.
-
Cause: The ORACLE_BASE registry key did not exist or its value was null.
- PRCT-01451: Error accessing file 'oracle.key'
-
Cause: An attempt to access the 'oracle.key' file to determine the location of registry containing ORACLE_BASE failed.
- PRCT-01452: Execution of the command 'opatch lsinventory -patch -oh' failed on local node with result {0}.
-
Cause: Execution of the command 'opatch lsinventory -patch -oh' failed on the local node. Details reported in accompanying messages.
- PRCT-01453: failed to get ASM properties from ASM client data file {0} \n{1}
-
Cause: An attempt to execute 'kfod op=credverify wrap=ASM client data file' to obtain the ASM properties failed.
- PRCT-01454: Resetting of the Rapid Home Provisioning repository failed while executing the Management Database configuration assistant on node {0}.\n{1}
-
Cause: An attempt to execute the Management Database configuration assistant to delete the repository contents failed.
- PRCT-01456: failed to execute 'asmcmd' command to obtain the client clusters
-
Cause: An attempt to execute the command 'asmcmd lscc --suppressheader' to obtain the client clusters failed.
- PRCT-01457: failed to retrieve cluster GUID for this cluster
-
Cause: An attempt to execute the command 'crsctl get css cluster guid' to obtain the GUID of this cluster failed.
- PRCT-01458: failed to get the disk group of management database \n{0}
-
Cause: An attempt to retrieve the disk group failed because execution of 'crsctl stat res ora.mgmtdb -p' completed with errors.
- PRCT-01459: Request is unsupported for version {0}.
-
Cause: An attempt to retrieve disk group failed because the version is earlier than 12.1.
- PRCT-01460: failed to execute command 'oradnfs isdnfsenabled' on the local node, detailed error:\n{0}
-
Cause: An attempt to verify that DNFS is enabled failed on the local node. See the accompanying error messages for further details.
- PRCT-01461: Failed to retrieve the value of attribute {1} for ASM disk group {0}. Execution of command '{2}' failed. Detailed error:\n{3}
-
Cause: An attempt to retrieve the value of the indicated attribute for the specified disk group failed.
- PRCT-01462: Failed to retrieve the attribute values for ASM disk group {0}. Execution of command '{1}' failed. Detailed error:\n{2}
-
Cause: An attempt to retrieve the attribute values for the specified disk group failed.
- PRCT-01463: Failed to execute command {0} to obtain the volume information. Detailed error: \n{1}
-
Cause: A requested operation that required obtaining volume information failed in the execution of the command 'asmcmd --nocp volinfo --all'. The accompanying message provides further details.
- PRCT-01464: No volume device information retrieved by executing command {0}.
-
Cause: A requested operation attempted to obtain volume information using the command 'asmcmd --nocp volinfo --all' and found no existing volumes.
- PRCT-01465: There are no Oracle ACFS file systems mounted.
-
Cause: An attempt to retrieve the Oracle Automatic Storage Management Cluster File System (Oracle ACFS) information for a specific mount point failed because there were no Oracle ACFS file systems mounted in the current cluster environment.
- PRCT-01466: Failed to determine if the cluster is configured to support leaf nodes. Detailed error:\n{0}
-
Cause: An attempt to run an internal command to determine if the cluster was configured to support leaf nodes failed. Specifics of the failure are shown in the following error message.
- PRCT-01467: failed to retrieve the attribute values for server pools\n{0}
-
Cause: An attempt to retrieve the attribute values for the server pools failed.
- PRCT-01468: invalid request for Oracle Grid Infrastructure Management Repository (GIMR) server
-
Cause: An attempt to retrieve GIMR client properties failed because it was executed on a GIMR server.
- PRCT-01469: Execution of command {0} completed successfully with warnings.
-
Cause: The indicated command completed with warnings. The accompanying messages provide more details.
- PRCT-01470: failed to reset the Rapid Home Provisioning (RHP) repository\n{0}
-
Cause: An attempt to reset the RHP repository failed. The accompanying error messages provide detailed failure information.
- PRCT-01471: failed to identify administrator-managed databases running on node "{0}"
-
Cause: An attempt to execute an internal command to identify administrator-managed databases running on the indicated node failed. The accompanying error messages provide more details.
- PRCT-01472: Volume device {0} does not exist.
-
Cause: An attempt to check if the specified volume device path was configured as an accelerator volume failed because the specified volume device path did not exist.
- PRCT-01473: Volume device {0} is not formatted as an Oracle ACFS.
-
Cause: An attempt to check if the specified volume device path was configured as an accelerator volume was rejected because the specified volume device was not formatted as Oracle Automatic Storage Management Cluster File Systems (Oracle ACFS).
- PRCT-01474: failed to run '{0}' on node {1}.\n{2}
-
Cause: An attempt to execute the specified command failed. The accompanying error messages provide more details.
- PRCT-01475: utility {1} not found in Oracle home path {0}
-
Cause: The install operation could not complete because it could not invoke the indicated utility in the Oracle home displayed in the message.
- PRCT-01476: Oracle ASM Filter Driver (ASMFD) driver state check with '{0}' option on the local node failed to display any output.
-
Cause: No output was captured when executing the Oracle ASM Filter Driver (ASMFD) driver state check with the indicated option on the local node. This is an internal error.
- PRCT-01477: Oracle ASM Filter Driver (ASMFD) driver state check with option '{0}' on node {1} failed to display any output.
-
Cause: No output was captured when executing an Oracle ASM Filter Driver (ASMFD) driver state check with the indicated option on the specified node. This is an internal error.
- PRCT-01478: failed to retrieve the active servers in server pool {0}\n{1}
-
Cause: An attempt to retrieve the active servers from the specified server pool failed. Accompanying messages provide detailed failure information.
- PRCT-01479: failed to retrieve administrator groups on node "{0}"\n{1}
-
Cause: The execution of the 'osdbagrp' command to retrieve the administrator operating system group names failed. Accompanying messages provide detailed failure information.
- PRCT-01480: failed to retrieve list of disk group names by executing 'kfod' on host {0}\n{1}
-
Cause: An attempt to retrieve the list of disk group names by executing 'kfod disks=all op=disks dscvgroup=TRUE asm_diskstring=<discovery_string>' failed. Accompanying error messages provide failure details.
- PRCT-01481: failed to retrieve the running nodes for the ACFS associated to disk group {0} and volume name {1}
-
Cause: An attempt to execute an internal command to retrieve the running nodes for an ACFS associated to the specified disk group and volume name failed. The accompanying error messages provide more details.
- PRCT-01482: failed to retrieve the running nodes for the ACFS associated to volume device {0}
-
Cause: An attempt to execute an internal command to retrieve the running nodes for an ACFS associated to the specified volume device failed. The accompanying error messages provide more details.
- PRCT-01483: failed to check if the ACFS associated to volume device {0} is node-local configured
-
Cause: An attempt to execute an internal command to check if the ACFS associated to the specified volume device was node-local configured failed. The accompanying error messages provide more details.
- PRCT-01484: failed to start remote execution server on node {0}
-
Cause: An attempt to start the required remote execution server on the indicated node failed. Detailed failure information is supplied by the accompanying messages.
- PRCT-01485: Execution of a Data Pump tool failed.\n{0}
-
Cause: An attempt to execute the 'expdp' or 'impdp' tool to export or import a schema failed. Accompanying messages provide detailed failure information.
- PRCT-01486: Execution of command '{0}' from Oracle Home {1} failed.\n{2}
-
Cause: An attempt to execute the specified SRVCTL command failed. Accompanying messages provide detailed failure information.
- PRCT-01487: failed to retrieve historical node list from Oracle Clusterware
-
Cause: An attempt to include historical Leaf Nodes with the command 'olsnodes -f' failed because the historical Leaf Nodes could not be retrieved from Oracle Clusterware.
- PRCT-01488: failed to create directory {0}\n{1}
-
Cause: An attempt to create the specified directory failed. Accompanying messages provide detailed failure information.
- PRCT-01489: failure to retrieve the cluster Single Client Access Name for network {0}\n{1}
-
Cause: An attempt to execute an internal command to retrieve the cluster Single Client Access Name failed. Specifics of the failure are shown in the appended error message.
- PRCT-01490: check that Rapid Home Provisioning (RHP) was configured failed
-
Cause: An attempt to execute an internal command to check whether RHP was configured failed. The accompanying error messages provide more details.
- PRCT-01491: Unable to retrieve list of disk group names. Execution failure in kfod at location {1}.\n{2}
-
Cause: An attempt to retrieve the disk group names by executing 'kfod nohdr=true op=groups' failed. The accompanying error messages provide detailed failure information.
- PRCT-01492: error signal "{0}" received, indicating segmentation fault (core dumped)
-
Cause: An internal error occurred.
- PRCT-01493: Execution of 'opatch query -is_rolling_patch' command failed.\n{0}
-
Cause: An attempt to determine if a patch was a rolling patch by executing 'opatch query -is_rolling_patch' failed. The accompanying messages provide detailed failure information.
- PRCT-01494: failed to remove {0}\n{1}
-
Cause: An attempt to remove the specified file or directory failed. Accompanying messages provide detailed failure information.
- PRCT-01495: failed to add cluster certificate to the trust store
-
Cause: An attempt to add an rhpclient failed because an error occurred while adding the cluster certificate to the trust store. The accompanying messages provide detailed failure information.
- PRCT-01496: failed to retrieve the cluster upgrade state
-
Cause: An attempt to retrieve the cluster upgrade state failed on the local node. The accompanying messages provide detailed failure information.
- PRCT-01497: failed to retrieve the cluster active patch level
-
Cause: An attempt to retrieve the cluster active patch level failed on the local node. The accompanying messages provide detailed failure information.
- PRCT-01498: failed to retrieve the cluster software patch level on node "{0}"
-
Cause: An attempt to retrieve the cluster software patch level of the indicated node failed. The accompanying messages provide detailed failure information.
- PRCT-01499: failed to create a DHCP proxy server resource
-
Cause: An attempt to configure the cluster to add a DHCP proxy server failed. The accompanying messages provide detailed failure information.
- PRCT-01500: There are no Oracle ACFS file systems on mount point {0}.
-
Cause: An attempt to retrieve the Oracle Automatic Storage Management Cluster File System (Oracle ACFS) information for the specified mount point failed because there was no Oracle ACFS file system mounted on the specified mount point.
- PRCT-01501: There are no Oracle ACFS file systems on mount point {0} in node {1}.
-
Cause: An attempt to retrieve the Oracle Automatic Storage Management Cluster File System (Oracle ACFS) information for the specified mount point on the specified node failed because there was no Oracle ACFS file system mounted there.
- PRCT-01502: Failed to retrieve the volume device for mountpoint {0}
-
Cause: An attempt to execute an internal command to retrieve the volume device for a mountpoint failed. The accompanying error messages provide detailed failure information.
- PRCT-01503: failed to verify that a VIP can be configured for network {0}\n{1}
-
Cause: An attempt to execute an internal command to validate whether a virtual IP address can be configured for the specified network resource failed. Specifics of the failure are shown in the accompanying error messages.
- PRCT-01504: invalid file path {0}
-
Cause: A requested operation was rejected because the indicated path did not exist.
- PRCT-01505: Failed to start resource after GIMR upgrade. Details:\n{0}
-
Cause: An attempt to execute an internal command to start the indicated resource failed after a Grid Infrastructure Management Repository (GIMR) upgrade. The accompanying messages provide detailed failure information.
- PRCT-01506: Failed to create a wallet for user "{0}" on path "{1}". Details:\n{2}
-
Cause: An attempt to execute an internal command to create a wallet file failed. The accompanying messages provide detailed failure information.
- PRCT-01507: Failed to add a certificate for a wallet using user "{0}" on path "{1}". Details:\n{2}
-
Cause: An attempt to execute an internal command to add a certificate in a wallet failed. The accompanying messages provide detailed failure information.
- PRCT-01508: Check whether group "{0}" exists failed.
-
Cause: An attempted operation failed because it required a check on the existence of the indicated group, and the internal command to perform the check failed. The accompanying error messages provide more details.
- PRCT-01509: failed to get the path of directory {0} from pluggable database {2} of container database {1}\n{3}
-
Cause: An attempted operation failed because it required retrieving the indicated directory's path, and the internal command to retrieve the path failed. The accompanying error messages provide more details.
- PRCT-01510: failed to parse the output returned by sqlplus to get the path of directory {0} from pluggable database {2} of container database {1}\n{3}
-
Cause: An attempted operation failed because it required retrieving the indicated directory's path, and the internal command to retrieve the path failed while parsing the output because it was null or had unexpected results. The accompanying error messages provide more details.
- PRCT-01511: failed to copy file {0} to destination {1}\n{2}
-
Cause: An attempted operation failed because it required copying the indicated file to the indicated destination, and the internal command to copy the file failed. The accompanying messages provide detailed failure information.
- PRCT-01512: failed to retrieve composite version from node "{0}"
-
Cause: An attempt to retrieve the composite version using the command 'oraversion -compositeVersion' failed. The accompanying messages provide detailed failure information.
- PRCT-01513: Execution of command {0} to obtain disk usage information failed. \n{1}
-
Cause: An attempt to retrieve the disk usage for a resource failed. The accompanying error messages provide more details.
- PRCT-01514: Disk group {0} does not have enough space to resize the volume to {1}GB. Execution of asmcmd at location {2} failed. Detailed error:\n{3}
-
Cause: An attempt to resize the specified volume was rejected because the indicated disk group was too small.
- PRCT-01515: failed to execute the command 'oradnfs mkdir' on the local node
-
Cause: An attempt to create an Oracle Direct NFS (dNFS) directory on the local node failed. The accompanying message provides detailed failure information.
- PRCT-01516: The dNFS operation '{0}' is not supported on this platform.
-
Cause: An attempt to execute an Oracle Direct NFS (dNFS) operation was rejected because the indicated command was not supported for the current operating system platform.
- PRCT-01517: failed to create a network resource for the SCAN "{0}" because the node name "{1}" does not resolve to any addresses of type {2}
-
Cause: The indicated node name address did not match the IP address type of the Single Client Access Name (SCAN) contained in the credentials file.
- PRCT-01518: failed to retrieve base version from node "{0}"
-
Cause: An attempt to retrieve the base version using the command 'oraversion -baseVersion' failed. The accompanying messages provide detailed failure information.
- PRCT-01519: failed to retrieve an Oracle Clusterware release patch version
-
Cause: An attempt to retrieve an Oracle Clusterware release patch version failed on the local node. The accompanying messages provide detailed failure information.
- PRCT-01520: ASM volume device {0} does not exist.
-
Cause: An operation that required obtaining volume information failed because the specified volume device path did not exist.
- PRCT-01525: Execution of command '{0}' from Oracle home {1} failed.\n{2}
-
Cause: An attempt to execute the specified CLUVFY command failed. Accompanying messages provide detailed failure information.
- PRCT-01532: failed to remove an Oracle Direct NFS (dNFS) file or directory "{0}".\n{1}
-
Cause: The command 'oradnfs rm' failed to remove the indicated Oracle Direct NFS (dNFS) path. The accompanying message provides detailed failure information.
- PRCT-01534: Execution of command '{0}' from home '{1}' failed.\n{2}
-
Cause: An attempt to execute the specified command failed. Accompanying messages provide detailed failure information.
- PRCT-01535: failed to retrieve CSS misscount\n{0}
-
Cause: An attempt to retrieve the CSS misscount using the command 'crsctl get css misscount' failed. The accompanying messages provide detailed failure information.
- PRCT-01536: Directory '{0}' is not writable
-
Cause: Write permissions were not granted to the specified directory on the local node.
- PRCT-01537: Execution of the command 'opatch lsinventory -oh -xml' failed on local node: {0}
-
Cause: Execution of the command 'opatch lsinventory -oh -xml' failed on the local node. Details reported in accompanying messages.
- PRCT-01538: Creation of the Grid Infrastructure Management Repository failed while executing the Management Database configuration assistant on node {0}.\n{1}
-
Cause: An attempt to execute the Management Database configuration assistant to create the GIMR failed.
- PRCT-01539: failed to create the diskgroup for this cluster
-
Cause: An attempt to create the diskgroup for the clusterware configuration failed.
- PRCT-01543: volume "{0}" is already attached
-
Cause: An attempt to attach a volume failed because the indicated volume is already attached.
- PRCT-01544: volume "{0}" is not attached
-
Cause: An attempt to detach a volume failed because the indicated volume is not attached.
- PRCT-01546: volume "{0}" is still attached
-
Cause: An attempt to remove a volume failed because the indicated volume is still attached.
- PRCT-01551: The volume for the specified device "{0}" does not exist
-
Cause: There was no volume attached for the specified device.
- PRCT-01557: failed to get the tablespace name of table {0} from schema {1} in pluggable database {2} of container database {3}\n{4}
-
Cause: An attempted operation failed because it required retrieving the tablespace of the specified table and the internal command to retrieve the name failed. The accompanying error messages provide more details.
- PRCT-01558: failed to get the size of tablespace {0} from pluggable database {1} of container database {2}\n{3}
-
Cause: An attempted operation failed because it required retrieving the specified tablespace size and the internal command to retrieve the size failed. The accompanying error messages provide more details.
- PRCT-01559: failed to get the free space in tablespace {0} from pluggable database {1} of container database {2}\n{3}
-
Cause: An attempted operation failed because it required retrieving the free space in the specified tablespace and the internal command to retrieve the free space failed. The accompanying error messages provide more details.
- PRCT-01560: Application of the datapatch on the GIMR failed while executing the Management Database Configuration Assistant on node {0}.\n{1}
-
Cause: An attempt to execute the Management Database Configuration Assistant to apply datapatch on the Grid Infrastructure Management Repository (GIMR) failed.
- PRCT-01561: failed to retrieve configured sites in cluster\n{0}
-
Cause: An attempt to retrieve the configured sites in cluster failed. The accompanying messages provide detailed failure information.
- PRCT-01562: The startup of instances "{0}" for database "{1}" are still in progress
-
Cause: The startup of specified database is not completed yet because one or more instances are still starting and the timeout has been reached.
- PRCT-01564: attached volume "{0}" does not exist
-
Cause: An attempt to retrieve the information of the indicated volume failed because there was no volume attached for the specified name.
- PRCT-01566: failed to recreate credentials XML file {0}\n{1}
-
Cause: Failed to generate credentials XML file by executing 'kfod op=credstoxml wrap=<credential_xml_file>'.
- PRCT-01567: Execution of "opatch version" command failed.\n{0}
-
Cause: An attempt to determine the version of OPatch failed. The accompanying messages provide detailed failure information.
- PRCT-01568: failed to retrieve the volume information of the device "{0}"
-
Cause: An attempt to retrieve the volume information of the specified device path using the command 'edvutil volinfo' failed. The accompanying messages provide detailed failure information.
- PRCT-01569: copied file "{0}" is empty
-
Cause: An attempt to copy the specified file failed.