Skip Headers
Oracle® Database Error Messages
12c Release 1 (12.1)

E49325-05
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

88 PRCT-01000 to PRCT-01454

PRCT-01000: File path is null
Cause: The supplied path is set to null.
Action: Oracle internal error. Contact Oracle Support Services..
PRCT-01001: Node name is null
Cause: The supplied node name is set to null.
Action: Oracle internal error. Contact Oracle Support Services.
PRCT-01003: Failed to run "{0}" on node "{1}"
Cause: Failed to execute the specified command on the specified node.
Action: Oracle internal error. Contact Oracle Support Services.
PRCT-01004: Directory name passed was null
Cause: The supplied directory name is set to null.
Action: Oracle internal error. Contact Oracle Support Services.
PRCT-01005: Directory {0} does not exist
Cause: The supplied directory path does not exist.
Action: Oracle internal error. Contact Oracle Support Services.
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.
Action: Execute the command 'olsnodes -c' from the specified node and check the output of the command. Fix the problem according to the error message given in the command output.
PRCT-01007: Failed to retrieve local node name
Cause: Underlying call failed to get the local hostname.
Action: Please check the accompanying error message.
PRCT-01008: Failed to retrieve node names
Cause: Failed to get the node names using the command 'olsnodes'.
Action: Execute the command 'olsnodes' and check the output of the command. Fix the problem according to the error message given in the command output.
PRCT-01009: crsctl execution failed. Detailed error: {0}
Cause: Failed to execute crsctl command.
Action: Examine the accompanying error message for details.
PRCT-01010: crsctl execution failed on node {0}. Detailed error: {1}
Cause: Failed to execute crsctl command on the specified node.
Action: Examine the accompanying error message for details.
PRCT-01011: Failed to run "{0}". Detailed error: {1}
Cause: Failed to execute the specified command on the local node.
Action: Execute the specified command from the console and check the result. Fix the problem according to the error message given in the command output.
PRCT-01012: Invalid file path {0}
Cause: The supplied path does not exist.
Action: Oracle internal error. Contact Oracle Support Services.
PRCT-01013: Failed to start remote execution server on local node.
Cause: A remote execution server is required on this platform, but an attempt to start one on this node failed. This message is accompanied by other(s) providing details on the failure.
Action: Correct the problem indicated by the accompanying error messages. On Windows systems, make sure that the current user has authority to remove and create directories and files in the Temp directory and to create and delete registry entries.
PRCT-01014: Internal error: {0}
Cause: An internal error occurred. The included value is an internal identifier.
Action: Oracle internal error. Contact Oracle Support Services.
PRCT-01015: Version supplied is null
Cause: The supplied version was set to null.
Action: Oracle internal error. Contact Oracle Support Services.
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
Action: This is an internal error. Contact Oracle Support Services.
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.
Action: This is an internal error. Contact Oracle Support Services.
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.
Action: This is an internal error. Contact Oracle Support Services.
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.
Action: This is an internal error. Contact Oracle Support Services.
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>'.
Action: This is an internal error. Contact Oracle Support Services.
PRCT-01055: Fail to retrieve ASM active version for node {0}. kfod execution failed at location {1}. Detailed error: {2}
Cause: Failed to get the active version of ASM by executing 'kfod nohdr=true op=version hostlist=<hostlist>' on the specified node.
Action: Examine the accompanying error messages for details.
PRCT-01056: Fail to retrieve ASM instance type. kfod execution failed at location {0}. Detailed error: {1}
Cause: Failed to get the instance type for ASM instance by executing 'kfod nohdr=true op=version'.
Action: Examine the accompanying error messages for details.
PRCT-01057: The value of ASM instance type {0} is not correct
Cause: The value of ASM instance type is invalid.
Action: The instance type of ASM can only be YES or NO.
PRCT-01058: Fail to check if ASM is running on node {0}. kfod execution failed at location {1}. Detailed error: {2}
Cause: Failed to check whether ASM is running by executing 'kfod nohdr=true op=insts hostlist=<hostlist>'.
Action: Examine the accompanying error messages for details.
PRCT-01059: Fail to retrieve list of disk group names for node {0}. kfod execution failed at location {1}. Detailed error: {2}
Cause: Failed to get the diskgroup names by executing 'kfod nohdr=true op=groups hostlist=<hostlist>'.
Action: Examine the accompanying error messages for details.
PRCT-01060: Fail to check if ASM is in rolling migration. kfod execution failed at location {1}. Detailed error: {2}
Cause: Failed to check whether ASM is in rolling migration by executing 'kfod nohdr=true op=rm'.
Action: Examine the accompanying error messages for details.
PRCT-01061: Failed to verify ASM client credentials file "{0}" {1}
Cause: An attempt to verify that the ASM client credentials file specified is a valid credentials file failed.
Action: Examine the accompanying error messages for details.
PRCT-01062: Failed to verify ASM client credentials. {0}
Cause: An attempt to verify the ASM credentials for this client cluster failed.
Action: Examine the accompanying error messages for details.
PRCT-01063: Failed to get list of disks managed by ASM on node "{0}" {1}
Cause: An attempt to obtain the list of disks that are managed by ASM on the specified node failed.
Action: Examine the accompanying error messages for details.
PRCT-01064: Failed to get ASM default disk discovery string {0}
Cause: An attempt to obtain the ASM default disk string failed.
Action: Examine the accompanying error messages for details.
PRCT-01065: Failed to verify the size consistency of ASM disks on node "{0}". kfod execution failed at location "{1}". Detailed error: {2}
Cause: An attempt to verify the consistency of ASM disk sizes failed on the identified node with the indicated error message.
Action: Examine the accompanying error messages for details.
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.
Action: Review the accompanying error messages that provides the details of why acfsutil execution failed. Resolve the reported problem and retry.
PRCT-01101: Failed to retrieve ACFS active version for node {0}. acfsutil execution failed at file location {1}. Detailed error: {2}
Cause: Failed to execute acfsutil to retrieve the ACFS active version on the supplied node.
Action: Review the accompanying error messages that provides the details of why acfsutil execution failed. Resolve the reported problem and retry.
PRCT-01102: Failed to parse output when executing acfsutil at file location {0}
Cause: Unable to parse output returned by acfsutil.
Action: Oracle internal error. Contact Oracle Support Services.
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.
Action: Oracle internal error. Contact Oracle Support Services.
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.
Action: Oracle internal error. Contact Oracle Support Services.
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.
Action: Oracle internal error. Contact Oracle Support Services.
PRCT-01109: Failed to get diskgroup names for node {0}
Cause: Unable to parse disgkroup names returned by acfsutil on the supplied node.
Action: Oracle internal error. Contact Oracle Support Services.
PRCT-01111: Received empty result while getting ACFS Mount Points on node {1}
Cause: The output returned by acfsutil is empty.
Action: Oracle internal error. Contact Oracle Support Services.
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.
Action: Review the accompanying error messages that provides the details of why acfsutil execution failed. Resolve the reported problem and retry.
PRCT-01115: Execution of acfsutil failed on node {0} with result {1}
Cause: Failed to execute acfsutil on the supplied node.
Action: Review the accompanying error messages that provides the details of why acfsutil execution failed. Resolve the reported problem and retry.
PRCT-01116: Invalid partition path {0} specified to acfsutil on node {1}
Cause: The supplied path did not exist.
Action: Supply a valid partition path and retry.
PRCT-01117: Received empty result while getting ACFS Disk Groups on node {1}
Cause: The output returned by acfsutil is empty.
Action: Oracle internal error. Contact Oracle Support Services.
PRCT-01118: Received empty result while getting total space at file location {0} on node {1}
Cause: The output returned by acfsutil is empty.
Action: Oracle internal error. Contact Oracle Support Services.
PRCT-01119: Received empty result while getting free space at file location {0} on node {1}
Cause: The output returned by acfsutil is empty.
Action: Oracle internal error. Contact Oracle Support Services.
PRCT-01120: A NULL path has been specified for the location on node {0}
Cause: A null path was provided for the location.
Action: Oracle internal error. Contact Oracle Support Services.
PRCT-01121: Execution of acfsutil failed on local node with result {0}
Cause: Execution of acfsutil failed on the local node.
Action: Review the accompanying error messages that provides the details of why acfsutil execution failed. Resolve the reported problem and retry.
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.
Action: Oracle internal error. Contact Oracle Support Services.
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.
Action: Oracle internal error. Contact Oracle Support Services.
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.
Action: Oracle internal error. Contact Oracle Support Services.
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.
Action: Oracle internal error. Contact Oracle Support Services.
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.
Action: Oracle internal error. Contact Oracle Support Services.
PRCT-01127: Received empty result while getting all volume devices on the local node
Cause: No ACFS volume devices has been created.
Action: Use usmca to create ACFS volume devices.
PRCT-01128: ACFS is not supported on this operating system
Cause: ACFS is not supported on the accompanying operating system.
Action: Run srvctl filesystem command on a supported 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
Action: Review the accompanying error messages that provides the details of why ACFS driver state check execution failed. Resolve the reported problem and retry.
PRCT-01130: Execution of advmutil failed on local node with result {0}
Cause: Execution of advmutil failed on the local node
Action: Review the accompanying error messages that provides the details of why advmutil execution failed. Resolve the reported problem and retry.
PRCT-01131: Failed to retrieve mount point for volume device {0}
Cause: No ACFS filesystem was mounted for the specified volume device.
Action: Mount the filesystem and retry.
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.
Action: Internal error. Contact Oracle Support Services.
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.
Action: Internal error. Contact Oracle Support Services.
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.
Action: Review the accompanying error messages that provides the details of why ACFS driver state check execution failed. Resolve the reported problem and retry.
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
Action: Internal error. Contact Oracle Support Services.
PRCT-01136: Invalid mount point
Cause: An internal error occurred.
Action: Contact Oracle Support Services.
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.
Action: Create the snapshot with the specified name and retry the operation.
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.
Action: Retry the operation with a different snapshot name.
PRCT-01149: Failed to retrieve cluster name
Cause: The olsnodes command executed successfully, but there was no output.
Action: This is an internal error. Contact Oracle Support Services.
PRCT-01150: Failed to retrieve cluster name
Cause: Clusterware is not running.
Action: Make sure the clusterware is running.
PRCT-01151: Failed to retrieve cluster nodes status
Cause: Clusterware is not running.
Action: Make sure the clusterware is running.
PRCT-01152: Received empty result while getting cluster nodes Status Map
Cause: The olsnodes command executed successfully, but there was no output.
Action: This is an internal error. Contact Oracle Support Services.
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.
Action: This is an internal error. Contact Oracle Support Services.
PRCT-01154: Failed to retrieve private host name for all cluster nodes. Detailed error: {0}
Cause: Clusterware is not running.
Action: Make sure the clusterware is 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.
Action: This is an internal error. Contact Oracle Support Services.
PRCT-01200: Failed to retrieve disk group name for volume device {0}. asmcmd execution failed at location {1}. Detailed error: {2}
Cause: Unable to retrieve the disk group name for the specified volume device
Action: Check that ASM instance is running on the local node.
PRCT-01201: Failed to retrieve volume name for volume device {0}. asmcmd execution failed at location {1}. Detailed error: {2}
Cause: Unable to retrieve the volume name for the specified volume device
Action: Check that ASM instance is running on the local node.
PRCT-01202: Failed to parse output returned by asmcmd when executing asmcmd at location {0}
Cause: Unable to parse output returned by asmcmd.
Action: Oracle internal error. Contact Oracle Support Services.
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.
Action: Contact Oracle Support Services.
PRCT-01204: Failed to find volume device {0}. asmcmd execution failed at location {1}. Detailed error: {2}
Cause: Volume device does not exist.
Action: Create the volume device using asm tools.
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.
Action: Oracle internal error. Contact Oracle Support Services.
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.
Action: Oracle internal error. Contact Oracle Support Services.
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.
Action: Use crsctl to make sure that the CRS stack is up; use the command 'srvctl status asm' to make sure that the ASM resource is running on the local node.
PRCT-01208: Failed to create volume {0}. asmcmd execution failed at location {1}. Detailed error: {2}
Cause: An attempt to execute asmcmd to create the volume device for the specified volume name failed.
Action: Review the accompanying error messages that provide the details of why asmcmd execution failed. Resolve the reported problem and retry.
PRCT-01209: Diskgroup {0} does not have enough space. asmcmd execution failed at location {1}. Detailed error: {2}
Cause: Failed to execute asmcmd because the diskgroup does not have enough space for the specified operation.
Action: Add more disks to the diskgroup and re-try the operation.
PRCT-01210: Disk group {0} does not exist. asmcmd execution failed at location {1}. Detailed error: {2}
Cause: An attempt to execute asmcmd to perform an operation with the disk group failed.
Action: Review the accompanying error messages that provide the details of why asmcmd execution failed. Resolve the reported problem and retry.
PRCT-01211: Volume {0} is in use. asmcmd execution failed at location {1}. Detailed error: {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.
Action: Retry the operation with a different volume name.
PRCT-01212: Failed to delete volume device {0}.asmcmd execution failed at location {1}. Detailed error: {2}
Cause: An attempt to execute asmcmd to delete the volume device for the specified volume name failed.
Action: Review the accompanying error messages that provide the details of why asmcmd execution failed. Resolve the reported problem and retry.
PRCT-01213: Failed to get volume device for volume {0}.asmcmd execution failed at location {1}. Detailed error: {2}
Cause: An attempt to execute asmcmd to get the volume device for the specified volume name failed.
Action: Review the accompanying error messages that provide the details of why asmcmd execution failed. Resolve the reported problem and retry.
PRCT-01214: Command 'asmcmd' could not be executed from directory {1}. Failed to retrieve discovery string for ASM instance. Detailed error: {2}
Cause: An attempt to retrieve the discovery string used by ASM instance failed.
Action: Look at the accompanying messages and respond accordingly.
PRCT-01215: Command 'asmcmd' could not be executed from directory {1}. Failed to retrieve the list of disks from ASM instance. Detailed error: {2}
Cause: An attempt to retrieve the list of disks from ASM instance failed.
Action: Look at the accompanying messages and respond accordingly.
PRCT-01217: Command 'asmcmd' could not be executed from directory {0}. Failed to resize volume {1}. Detailed error: {2}
Cause: An attempt to resize the volume failed.
Action: Review the accompanying error messages that provide the details of the failure. Resolve the reported problem and retry.
PRCT-01218: Command 'asmcmd' could not be executed from directory {1}. Failed to retrieve information of disk groups from ASM instance. Detailed error: {2}
Cause: An attempt to retrieve the list of disk groups from ASM instance failed.
Action: Look at the accompanying messages and respond accordingly.
PRCT-01219: Command 'asmcmd spget' could not be executed from directory {0}. Failed to retrieve the ASM SPFILE location for ASM instance. Detailed error: {1}
Cause: An attempt to retrieve the SPFILE used by an ASM instance failed.
Action: Look at the accompanying messages and respond accordingly.
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.
Action: This is an internal error. Contact Oracle Support Services.
PRCT-01300: oifcfg execution failed. Detailed error: {0}
Cause: Failed to execute the oifcfg command for the local node. See the accompanying error message for further details.
Action: Try to execute the oifcfg command manually.
PRCT-01301: oifcfg execution failed on node {0}. Detailed error: {1}
Cause: Failed to execute the oifcfg command for the remote node. See the accompanying error message for further details.
Action: Try to execute the oifcfg command manually.
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.
Action: Make sure that both the subnet number and the subnet mask have a valid 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.
Action: Contact Oracle Support Services.
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.
Action: Make sure that the IPv6 prefix length is an integer from 0 to 128.
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.
Action: Either omit the interface name or make sure it is the same as the existing one for this network.
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'.
Action: Use the command 'srvctl modify network' to change the network type to 'both' by adding an IPv4 subnet, then retry the command.
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'.
Action: Use the command 'srvctl modify network' to change the network type to 'both' by adding an IPv6 subnet, then retry the command.
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.
Action: Remove the VIP resource, issue the command 'srvctl add vip' providing either the IPv4 or IPv6 address the VIP name resolves to and then rerun the 'srvctl modify vip' command.
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.
Action: Internal error. Contact Oracle Support Services.
PRCT-01400: getcrshome execution failed. Detailed error: {0}
Cause: Failed to execute the getcrshome command. See the accompanying error message for further details.
Action: Try to execute the getcrshome command manually.
PRCT-01401: getcrshome execution failed on node {0}. Detailed error: {1}
Cause: Failed to execute the getcrshome command. See the accompanying error message for further details.
Action: Try to execute the getcrshome command manually.
PRCT-01402: Attempt to retrieve version of SRVCTL from Oracle Home {0} failed. Detailed error: {1}
Cause: Failed to execute the 'srvctl -V' command. See the accompanying error message for further details.
Action: Verify that the 'bin' directory under the indicated oracle home contains the 'srvctl' binary, and verify execution of the command 'srvctl -V' manually on that oracle home.
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
Action: Verify execution of the command 'srvctl -V' manually at oracle home or Contact Oracle Support Services.
PRCT-01404: Attempt to retrieve version of SRVCTL on node {0} from Oracle Home {1} failed. Detailed error: {2}
Cause: Failed to execute the command 'srvctl -V' command. See the accompanying error message for further details.
Action: Verify that the 'bin' directory in specified node under the indicated oracle home contains the 'srvctl' binary, and verify execution of the command 'srvctl -V' manually on that oracle home.
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
Action: Verify execution of the command 'srvctl -V' manually at given node and oracle home or Contact Oracle Support Services.
PRCT-01406: Oracle Home location: {0} does not contain {1}
Cause: The current Oracle Home directory does not contain the specified utility.
Action: Provide the correct Oracle Home directory.
PRCT-01407: failed to execute the olsnodes command to retrieve active node roles. Detailed error: {0}
Cause: An attempt to execute the command 'olsnodes -a' failed.
Action: Check the accompanying error messages.
PRCT-01408: Encountered unexpected output during the olsnodes command execution to retrieve active node roles
Cause: An attempt to execute olsnodes -a command failed.
Action: Check the accompanying error messages.
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.
Action: This is an internal error. Contact Oracle Support Services.
PRCT-01410: Failed to execute the crsctl command to retrieve configured node roles. Detailed error: {0}
Cause: An attempt to execute crsctl get node role config -all command failed.
Action: Check the accompanying error messages.
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.
Action: Check the accompanying error messages.
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.
Action: This is an internal error. Contact Oracle Support Services.
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.
Action: Check the accompanying error messages.
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.
Action: Check the accompanying error messages.
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.
Action: Remove all but one of the ACFS resources that contains the duplicate mount point path.
PRCT-01416: Unable to validate the interface type for subnet "{0}"
Cause: An attempt to validate the interface type for the given subnet failed.
Action: Check the accompanying error messages.
PRCT-01417: Failed to retrieve administrator groups. 'osdbagrp' execution failed at location {0}. Detailed error: {1}
Cause: During retrieval of administrator group, execution of the 'osdbagrp' command to retrieve administrator OS group names failed.
Action: Examine the accompanying error messages for details.
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.
Action: Ensure that the specifed VIP name resolves 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.
Action: Make sure that the specified VIP name resolves 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.
Action: Make sure that the specified VIP name resolves 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.
Action: Make sure that the specified VIP name or address resolves 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.
Action: Make sure that the specified VIP name or address resolves to an IPv6 address.
PRCT-01423: Failed to copy the directory contents from {0} to {1} on node {2}. Detailed error: {2}
Cause: An attempt to execute srvmhelper to copy the directory contents failed.
Action: Examine the accompanying error messages.
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.
Action: Examine the accompanying error messages for details.
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.
Action: Specify a VIP name that resolves to a single IPv4 address. Use 'nslookup <vipname>' to display the addresses to which the VIP name resolves.
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.
Action: Specify a VIP name that resolves to one address. Use 'nslookup <vipname>' to display the addresses to which the VIP name resolves.
PRCT-01427: Failed to create the NFS resource on mount path "{0}". Detailed error: {1}
Cause: An attempt to create the NFS resource failed.
Action: Examine the accompanying error messages.
PRCT-01428: Failed to execute Management Database configuration assistant for user "{0}" on node "{1}". Detailed error: {2}
Cause: An attempt to run Management Database configuration assistant failed.
Action: Examine the accompanying error messages.
PRCT-01429: Failed to create wallet for Rapid Home Provisioning for user "{0}". Detailed error: {1}
Cause: An attempt to create the wallet for Rapid Home Provisioning failed.
Action: Examine the accompanying error messages.
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: {2}
Cause: An attempt to retrieve the 'compatible.advm' attribute for the specified disk group failed.
Action: Examine the accompanying error messages for details and take appropiate corrective action.
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.
Action: Set the 'compatible.advm' attribute for the specified disk group to a version above 11.2.0.3 with the ASM Configuration Assistant (asmca) and retry adding a Rapid Home Provisioning Server using 'srvctl add rhpserver' command.
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.
Action: Retry the command making sure that the specified VIP address is an IPv4 address.
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.
Action: Retry the command making sure that the specified VIP address is an IPv6 address.
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.
Action: Make sure that the specified VIP name or address resolves 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.
Action: Make sure that the specified VIP name or address resolves to an IPv6 address.
PRCT-01436: Volume {0} does not exist for disk group {1}. Detailed error: {2}
Cause: An attempt to execute 'asmcmd' to delete the volume for the disk group failed.
Action: Review the accompanying error messages that provide the details of why ASMCMD execution failed. Resolve the reported problem and retry.
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.
Action: Review the accompanying error messages that provide the details of why the 'opatch lspatches -oh' execution failed. Resolve the reported problem and retry.
PRCT-01438: Failed to get the difference between the patches installed in {0} and {1} Oracle homes. Detailed error: {2}
Cause: An attempt to get the difference between the patches installed in the Oracle homes failed.
Action: Examine the accompanying error messages.
PRCT-01439: Failed to create the directory {0} in nodes {1}. Detailed error: {2}
Cause: An attempt to execute srvmhelper to create the directory failed. Specifics of failure shown in appended error message.
Action: Examine the accompanying error messages for details. Resolve the problems reported and retry.
PRCT-01440: Failed to determine if database is administrator-managed {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.
Action: Examine the accompanying error messages for details. Resolve the problems reported and retry.
PRCT-01441: Failed to retrieve configured nodes for an administrator-managed database {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.
Action: Examine the accompanying error messages for details. Resolve the problems reported and retry.
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.
Action: Check whether the specified srvmhelper script exists. Also, check whether the user has execute permission on the srvmhelper script.
PRCT-01443: Setting of password for user GHSUSER failed while executing the Management Database configuration assistant on node {0}.
Cause: An attempt to execute the Management Database configuration assistant to set GHSUSER's password failed.
Action: Examine the accompanying error messages for details.
PRCT-01444: Attempt to retrieve version of SQL*Plus from Oracle home {0} failed. Detailed error: {1}
Cause: An attempt to execute the 'sqlplus -V' command failed. See the accompanying error message for further details.
Action: Verify that the 'bin' directory under the indicated Oracle home contains the 'sqlplus' binary, and verify execution of the command 'sqlplus -V' manually on that Oracle home.
PRCT-01445: Failed to parse output returned by sqlplus -V when executing command at Oracle home {0}. Detailed error: {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.
Action: Verify execution of the command 'sqlplus -V' manually at the Oracle home or contact Oracle Support Services.
PRCT-01446: Attempt to retrieve version of SQL*Plus on node {0} from Oracle home {1} failed. Detailed error: {2}
Cause: An attempt to execute the 'sqlplus -V' command failed. See the accompanying error message for further details.
Action: Verify that the 'bin' directory in the specified node under the indicated Oracle home contains the 'sqlplus' binary, and verify execution of the command 'sqlplus -V' manually on that Oracle home.
PRCT-01447: Failed to parse output returned by sqlplus -V when executing command at node {0} and Oracle home {1}. Detailed error: {1}
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.
Action: Verify execution of the command 'sqlplus -V' manually at the given node and Oracle home or contact Oracle Support Services.
PRCT-01448: Oracle home location: {0} does not contain {1}
Cause: The current Oracle home directory did not contain the specified utility.
Action: Provide the correct Oracle home directory.
PRCT-01449: Execution of command 'orabase' failed. Detailed error: {0}
Cause: Execution of the 'orabase' command failed. See the accompanying error message for further details.
Action: Correct the problem indicated by the accompanying message.
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.
Action: Clone the existing ORACLE_HOME to re-create the registry entries using the command 'clone.pl'.
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.
Action: Clone the existing ORACLE_HOME to re-create the 'oracle.key' file using the command 'clone.pl'.
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.
Action: Review the accompanying error messages that provide the details of why the 'opatch lsinventory -patch -oh' execution failed. Resolve the reported problem and retry executing the command.
PRCT-01453: Failed to execute the crsctl command to retrieve cluster GUID. Detailed error: {0}
Cause: An attempt to execute the command 'crsctl get css clusterguid' failed.
Action: Examine the accompanying error messages, resolve reported problems and retry executing the command.
PRCT-01454: Received empty result while getting the cluster GUID
Cause: The crsctl command executed successfully, but there was no output.
Action: This is an internal error. Contact Oracle Support Services.