Skip Headers
Oracle® Real Application Clusters Administration and Deployment Guide
11g Release 1 (11.1)
Part Number B28254-01
Go to Documentation Home
Home		 Go to Book List
Book List		 Go to Table of Contents
Contents		 Go to Index
Index		 Go to Master Index
Master Index		 Go to Feedback page
Contact Us
Go to previous page
Previous		 Go to next page
Next
View PDF

C Oracle Real Application Clusters Tools Messages

This appendix describes the Oracle Real Application Clusters (Oracle RAC) management tools messages. The messages in this appendix appear alphabetically by group. The topics in this appendix are:

See Also:

Oracle Database Platform Guide for Microsoft Windows for Windows messages and for all other messages refer search online at

http://tahiti.oracle.com

Overview of Messages Specific to Oracle Real Application Clusters

Oracle RAC messages use the same ORA prefix and reside in the same e*.msg files as single-instance Oracle database messages. Additionally, some Oracle RAC messages are issued by the single-instance Oracle database. These messages appear online by way of a Tahiti error message search as described in the Oracle database documentation in the Preface of this book under the heading "Related Documents".

Prefixes and Message Codes for Oracle Real Application Clusters Messages

Message prefixes indicate where to find information about the messages in this chapter. In addition, the prefixes indicate which Oracle RAC component issued the messages.

Types of Oracle Real Application Clusters Messages and Related Files

The Oracle RAC high availability and cluster database management tools use the following syntax for internal messages:

PRKx-0000: Cause description "variable" text {variable} text {variable}

A message might appear as follows:

PRKC-1022 "Could not get "node name" for node {0} in {1}"

The variables in the previous example represent numbers, names, and character strings for objects in the physical or logical cluster and the cluster database. you can ignore empty variables.

PRKA—Cluster Node Applications Messages

PRKA-2001: GSD already exists
Cause: An attempt was made to create the Global Services Daemon (GSD) application while there is a running GSD application.
Action: Stop and remove the running GSD and create the GSD application again using the 'srvctl add nodeapps' command.
PRKA-2002: Listener already exists
Cause: An attempt was made to create a listener application while there is a running listener application.
Action: Stop and remove the running listener and create the listener application again using the 'srvctl add nodeapps' command.
PRKA-2003: EM Agent already exists
Cause: An attempt was made to create an Agent application while there is a running Agent application.
Action: Stop and remove the running Agent and create the Agent application again using the 'srvctl add nodeapps' command.
PRKA-2004: No database found for the cluster.
Cause:
Action:
PRKA-2005: Netmasks are different for starting and ending IP addresses
Cause: Invalid range of VIP addresses specified for the cluster.
Action: Check if the starting and ending addresses in the VIP range belong to the same netmask.
PRKA-2006: Invalid VIP address range
Cause: Invalid range of VIP addresses specified for the cluster.
Action: Check if the starting address is less than ending address.
PRKA-2007: Empty VIP address range
Cause: Invalid range of VIP addresses specified for the cluster.
Action: Enter valid non-null VIP address range.
PRKA-2008: No VIP address is available in the VIP pool
Cause: No IP addresses are available for use in the range of IP addresses that you specified earlier.
Action: Check the VIP address pool to ensure that you are using valid VIP addresses.
PRKA-2009: VIP address is not found
Cause: IP address is not found.
Action: Enter valid VIP address.
PRKA-2010: VIP address already exists
Cause: An attempt was made to create a Virtual IP while there is a running Virtual IP application.
Action: Stop and remove the running Virtual IP application and create the Virtual IP application using the 'srvctl add nodeapps' command.
PRKA-2011: Remote command failed - not used?
Cause: The command failed to execute on remote node.
Action: Check the command for syntax and semantics and reissue the command.
PRKA-2012: Failed to get the VIP address range configuration from the OCR
Cause: There might not be any IP address ranges in the OCR or it is possible that an OCR error occurred while retrieving the VIP address range.
Action: Refer to the OCR logs for detailed error information.
PRKA-2013: Failed to add the VIP address range configuration to the OCR
Cause: An OCR error occurred while adding the VIP address range into the OCR.
Action: Refer to the OCR logs for detailed error information.
PRKA-2014: Failed to remove the VIP address range configuration from the OCR
Cause: An OCR error occurred while adding the VIP address range into the OCR.
Action: Refer to the OCR logs for detailed error information.
PRKA-2015: Invalid node name
Cause: The node name that you entered does not belong to the cluster.
Action: Enter a node that belongs to the cluster.
PRKA-2016: Invalid listener name
Cause: The listener name entered is invalid.
Action: Correct the listener name.
PRKA-2017: There are no IP addresses in the specified range. Make sure to specify the correct range for the IP addresses.
Cause:
Action: Specify valid range for IP addresses.
PRKA-2018: Virtual IP can only be created or removed by the system privilege user.
Cause: Only users with administrative privileges can configure Virtual IPs on the system.
Action: Verify the privileges of the user who is attempting to create or remove the VIP address.
PRKA-2019: Error executing command \"{0}\". File is missing.
Cause:
Action:

PRKC—Cluster Command Messages

PRKC-1023: Invalid IP address format: {0}
Cause: The given IP address does not adhere to the IP address format standard.
Action: Use the correct IP address format.
PRKC-1024: Invalid netmask: {0}
Cause: The given netmask format does not adhere to the format standard.
Action: Change the netmask format to a valid netmask format.
PRKC-1025: Failed to create a file in directory {0}
Cause: Might be due to insufficient permission or due to insufficient disk space.
Action: Check the permission on the directory and available space.
PRKC-1026: Failed doing I/O to file {0}
Cause: Might be due to insufficient permission or due to insufficient disk space or network issue.
Action: Check the permission on the directory and available space. Make sure the storage medium is accessible.
PRKC-1027: Error checking existence of file {0} on {1}
Cause: Might be due to an improper user equivalence configuration or due to insufficient permissions on the parent directory.
Action: Verify that user equivalence is correctly configured and that the directory has read and execute permissions.
PRKC-1028: Error checking write permission for directory {0} on {1}
Cause: Might be due to an improper user equivalence configuration or due to insufficient permissions on the parent directory.
Action: Verify that user equivalence is correctly configured and that the directory has read and execute permissions.
PRKC-1029: Failed to get modification time for file {0} on node {1}, [2]
Cause: Might be due to an improper user equivalence configuration or due to insufficient permissions on the parent directory.
Action: Verify that user equivalence is correctly configured and that the directory has read and execute permissions.
PRKC-1030: Error checking accessibility for node {0}, {1}
Cause: Might be due to a network issue or to an improper user equivalence setup.
Action: Check node reachability between the local and the remote nodes and make sure user equivalence is correctly configured.
PRKC-1031: Error checking free space for {0} on {1}
Cause: Might be due to a network issue or to an improper user equivalence setup.
Action: Check node reachability between the local and the remote nodes and make sure that user equivalence is correctly configured.
PRKC-1032: Directory {0} does not exist
Cause: The specified directory does not exist.
Action: Make sure that the specified directory exists. Use an absolute path for the directory.
PRKC-1033: Executable {0} does not exist
Cause: The specified executable does not exist.
Action: Verify the existence of the executable before retrying.
PRKC-1034: No local node name found for host {0}
Cause: The local node may not be part of the cluster or an error may have occurred while retrieving the local node name.
Action: Check CRS logs in ORA_CRS_HOME/log/<hostname> and OCR logs in ORA_CRS_HOME/srvm/log.
PRKC-1035: Node names for this cluster could not be retrieved
Cause: An error occurred while retrieving node names from the cluster.
Action: Check CRS logs in ORA_CRS_HOME/log/<hostname> and OCR logs in ORA_CRS_HOME/srvm/log.
PRKC-1036: CRS_HOME name passed to the method was null
Cause: The CRS home name cannot be null.
Action: Pass non-null CRS_HOME to the method.
PRKC-1037: Error removing files listed in {0} from node {1}
Cause: Might be due to an improper user equivalence configuration or due to insufficient permissions.
Action: Verify that user equivalence is correctly configured and that the mentioned files have the correct permissions.
PRKC-1038: Error copying files listed in {0} to node {1}
Cause: Might be due to an improper user equivalence configuration or due to insufficient permissions.
Action: Verify that user equivalence is correctly configured and that the mentioned files have the correct permissions.
PRKC-1039: Error creating directories listed in {0} on node {1}
Cause: Might be due to an improper user equivalence configuration or due to insufficient permissions.
Action: Verify that user equivalence is correctly configured and that the mentioned files have the correct permissions.
PRKC-1040: Remote Shell is not known yet.
Cause: User equivalence is not yet configured.
Action: Configure user equivalence.
PRKC-1041: Remote Copy command is not known yet.
Cause: User equivalence is not yet configured.
Action: Configure user equivalence.
PRKC-1042: The Remote Shell {0} requested by client is not recognized
Cause: The system does not recognize the given remote shell command.
Action: Use ssh or rsh as the remote shell.
PRKC-1043: The Remote Copy command {0} requested by client is not recognized
Cause: The system does not recognize the given remote copy command.
Action: Use scp or rcp for remote copy.
PRKC-1044: Failed to check remote command execution setup for node {0} using shells {1} and {2}
Cause: Could not find the remote shell commands {1} and {2} on node {0}.
Action: Configure user equivalence. Use environment variables to pass remote shell commands.
PRKC-1045: Node name is null
Cause: Node name received is null.
Action: Pass non-null node name to method/command.
PRKC-1046: The file list passed to the method was null
Cause: The list of files obtained is null.
Action: Pass non-null file list to method.
PRKC-1047: The directory list passed to the method was null
Cause: The list of directories obtained is null.
Action: Pass non-null directory list to method.
PRKC-1048: {0} is not supported on Windows platform
Cause: Unsupported operation.
Action: Do not attempt {0} on Windows.
PRKC-1049: CRS is not supported in version {0}. It is supported from version {1} onwards
Cause: Unsupported operation.
Action: Upgrade to version {1} before attempting CRS commands.
PRKC-1050: EVM is not supported in version {0}. It is supported from version {1} onwards
Cause: Unsupported operation.
Action: Upgrade to version {1} before attempting to use EVM.
PRKC-1051: Invalid data to set for registry key {0}.
Cause: Data validation failed for registry operation.
Action: Check data passed as value for registry key {0}.
PRKC-1052: Invalid data type for registry key {0}.
Cause: Data validation failed for registry key {0}.
Action: Check data type of value for registry key {0}.
PRKC-1053: Error returned from node {0} is \"{1}\"
Cause:
Action: Contact your customer support representative.
PRKC-1054: Node {0} is not accessible
Cause: Might be due to a network issue or due to an improper user equivalence configuration.
Action: Contact your network or system administrator to verify connectivity and the health of node {0}.
PRKC-1055: Directory name passed was null
Cause:
Action: Ensure non-null directory name is passed to command.
PRKC-1056: Failed to get the hostname for node {0}
Cause: Unable to fetch the hostname.
Action: Check hostname of node {0}.
PRKC-1057: The computername and hostname do not match for node {0}. Make sure that they match.
Cause:
Action: Contact your network or computer administrator to reconfigure the computer name and/or the hostname before re-attempting the operation.
PRKC-1058: The hostname registry key {0} has an empty value on node {1}
Cause: Null value was passed for the registry key {0}.
Action: Contact your customer service representative.
PRKC-1059: The computername registry key {0} has an empty value on node {1}
Cause: Null value was passed for the registry key {0}.
Action: Contact your customer service representative.
PRKC-1060: Cluster misconfigured on node \"{0}\", \"{1}\" property in {2} does not match with configured data in Oracle Cluster Registry
Cause: Improper setup for the cluster.
Action: Contact your customer service representative.
PRKC-1061: Failed to list contents of the directory {0}
Cause: Might be due to insufficient permission.
Action: Check the permission and the contents of directory {0}.
PRKC-1062: Node list is null
Cause: The node list is null.
Action: Pass non-null node list to method/command.
PRKC-1063: Node list {0} contained {1} nodes, minimum number of nodes required is {2}
Cause:
Action: Modify nodelist to contain appropriate number of nodes before retrying method/command.
PRKC-1064: Node list {0} contained {1} nodes whereas the cluster has {2} nodes
Cause: The node list that is configured for the cluster does not match the given node list.
Action: Modify the nodelist to contain {2} nodes.
PRKC-1065: Nodes {0} do not belong to this cluster
Cause: The provided nodes are not configured for the cluster.
Action: Remove the invalid nodes that do not belong to cluster.
PRKC-1066: Failed to retrieve node number for node \"{0}\
Cause: Cluster was not properly setup.
Action: Check CRS logs for detailed error information.
PRKC-1067: File name is null
Cause:
Action: Change file name to non-null value and retry method invocation.
PRKC-1068: Failed to get private interconnect node name for node {0}, {1}
Cause: Cluster was not properly setup.
Action: Check logs for detailed error information.
PRKC-1069: Failed to get sub keys of \"{0}\" registry key, {1}
Cause: Either the parent or the sub-key does not exist.
Action: Contact your customer service representative.
PRKC-1070: Failed to get sub keys of \"{0}\" registry key on node \"{1}\", {2}
Cause: Either the parent or the sub-key does not exist.
Action: Contact your customer service representative.
PRKC-1071: Nodes \"{0}\" did not respond to ping in \"{1}\" seconds, {2}
Cause: The node might be down or there could be a network outage.
Action: Contact your network administrator to verify connectivity between the specified nodes.
PRKC-1072: Invalid node \"{0}\" specified for checking the result of operation
Cause: Node name validation for the operation failed.
Action: Check the value of node {0}. Specify valid values for the nodes.
PRKC-1073: Failed to transfer directory \"{0}\" to any of the given nodes \"{1}\". {2}
Cause: Could not copy the directory \"{0}\" to any of the given nodes \"{1}\".
Action: Verify that user equivalence is properly configured. Check the log files for details.
PRKC-1074: Error on node {0}:{1}
Cause:
Action: Contact your customer support representative.
PRKC-1075: User equivalence does not exist with nodes \"{0}\", {1}
Cause: User equivalence was not configured.
Action: Contact your system administrator to verify user equivalence between the specified nodes.
PRKC-1076: Oracle home is null
Cause:
Action: Contact your customer support representative.
PRKC-1077: List file {0} has the following invalid files:{1}
Cause: Filename validation failed for the given files.
Action: Remove invalid entries from list file.
PRKC-1078: Failed to transfer directories listed in \"{0}\" to any of the given nodes \"{1}\": {2}
Cause: Could not copy the directory \"{0}\" to any of the given nodes \"{1}\".
Action: Verify that user equivalence is properly configured. Check the log files for details.
PRKC-1079: {0} is not contained within an Oracle home
Cause:
Action: Use {0} contained within an Oracle home.
PRKC-1080: Failed to transfer file \"{0}\" to any of the given nodes \"{1}\". {2}
Cause: Could not copy the file \"{0}\" to any of the given nodes \"{1}\".
Action: Verify that user equivalence is properly configured. Check the log files for details.
PRKC-1081: Failed to transfer listed files in \"{0}\" to any of the given nodes \"{1}\". {2}
Cause: Could not copy the files \"{0}\" to any of the given nodes \"{1}\".
Action: Verify that user equivalence is properly configured. Check the log files for details.
PRKC-1082: Failed to create listed directory in \"{0}\" to any of the given nodes \"{1}\". {2}
Cause: Could not create the directory \"{0}\" to any of the given nodes \"{1}\".
Action: Verify that user equivalence is properly configured. Verify the permissions for the parent directory on the given nodes.
PRKC-1083: Failed to remove listed directory in \"{0}\" to any of the given nodes \"{1}\". {2}
Cause: Could not remove the directory \"{0}\" to any of the given nodes \"{1}\".
Action: Verify that user equivalence is properly configured. Verify the permissions for the parent directory on the given nodes.
PRKC-1084: Failed to create path \"{0}\" in any of the given nodes \"{1}\". {2}
Cause: Could not create the path \"{0}\" to any of the given nodes \"{1}\".
Action: Verify that user equivalence is properly configured. Verify the permissions for the parent directory on the given nodes.
PRKC-1085: Failed to retrieve Oracle private name for node \"{0}\"
Cause: Cluster is not properly configured.
Action: Check whether node {0} is part of the cluster. If so, contact your customer support representative. If not, correct node name.
PRKC-1086: Unknown path type \"{0}\" specified for path \"{1}\" existence check
Cause: Unknown path type.
Action: Specify a valid path type for the path existence check.
PRKC-1087: Failed to retrieve virtual IP for node \"{0}\"
Cause: Cluster is not properly configured.
Action: Check whether node {0} is part of the cluster. If so, contact your customer support representative. If not, correct node name.
PRKC-1088: Failed to recursively list files from the directories specified in file: {0}
Cause: File access issue.
Action: Verify that the files exist and make sure that the files permissions are correct.
PRKC-1089: List file {0} is empty
Cause: An empty list file was passed to a transfer/copy command.
Action: Edit the contents of the list file before reattempting the command.
PRKC-1090: Failed to update environment on nodes \"{0}\", {1}
Cause: Might be due to improper privilege.
Action: Check user privilege on nodes \"{0}\".
PRKC-1091: The include list file passed is null
Cause:
Action: Pass non-null include file list to retry command/method.
PRKC-1092: Failed to retrieve the location of votedisks: {0}
Cause: Node name passed to command is not part of cluster.
Action: Invalid node name passed to command. Use a name for a node that is part of the cluster.
PRKC-1093: Failed to retrieve the version of crs software on node \"{0}\" : {1}
Cause: Cluster is not setup properly.
Action: Contact your customer support representative.
PRKC-1094: Failed to retrieve the active version of crs: {0}
Cause: Cluster is not setup properly.
Action: Contact your customer support representative.
PRKC-1095: OLE initialization or OCX load error while registering OCX library on nodes \"{0}\", {1}
Cause: Cluster is not setup properly.
Action: Contact your customer support representative.
PRKC-1096: Failed to do node reboot on nodes \"{0}\", {1}
Cause: Cluster is not setup properly.
Action: Contact your customer support representative.
PRKC-1097: PRKC- The file, \"{0}\" is not an OCX
Cause: Cluster is not setup properly.
Action: Contact your customer support representative.
PRKC-1098: Failed to create new listfile with proper UNC path from the path specified in file: {0}
Cause: Internal error.
Action: Contact your customer support representative.
PRKC-1099: The host names or IP addresses passed as an argument are null
Cause:
Action: Pass non-null arguments for hostnames or IP addresses.
PRKC-1100: The network port {0} is already in use
Cause: Preoccupied network port {0}.
Action: Free port {0} for use by CRS infrastructure.
PRKC-1101: The network port {0} is not available for use.
Cause: The port {0} might be used by another application.
Action: Make port {0} available for use.
PRKC-1102: CSS is not configured with local-only OCR on node \"{0}\"
Cause: CSS is not configured to run in a stand alone environment.
Action: Follow the documentation to setup CSS properly.
PRKC-1102: CSS is not configured with local-only OCR on node \"{0}\"
Cause: CSS is not configured to run in a standalone environment.
Action: Follow the documentation to setup CSS properly.
PRKC-1103: Failed to check CSS status for any of the given nodes \"{0}\", {1}
Cause: CSS might be down. User equivalence might not be set or there could be a network issue.
Action: Check the logs to see details.
PRKC-1104: Property, \"{0}\" is not found in file \"{1}\"
Cause: File \"{1}\" does not contain the property \"{0}\".
Action: Check the file '{1}'.
PRKC-1105: Failed to retrieve the local CSS home for node \"{0}\"
Cause: Cluster is not setup properly.
Action: Contact your customer support representative.
PRKC-1106: Failed to remove file \"{0}\" on node \"{1}\", {2}
Cause: Could not remove the file \"{0}\" on node \"{1}\".
Action: Verify that user equivalence is properly configured. Verify the permissions for the parent directory as well as for the file on the given nodes.
PRKC-1107: Failed to create symbolic link from file \"{0}\" to \"{1}\" on node \"{2}\", {3}
Cause: Could not create symbolic link.
Action: Verify that user equivalence is properly configured. Verify the permissions for the parent directory as well as for the file on the given nodes.
PRKC-1108: Failed to copy file \"{0}\" on node \"{1}\" to file \"{2}\" on node \"{3}\", {4}
Cause: Could not copy the file \"{0}\" on node \"{1}\".
Action: Verify that user equivalence is properly configured. Verify the permissions for the parent directory as well as for the file on the given nodes.
PRKC-1109: Failed to move file \"{0}\" to file \"{1}\" on node \"{2}\", {3}
Cause: Could not move the file \"{0}\" to file \"{1}\" on node \"{2}\".
Action: Verify that user equivalence is properly configured. Verify the permissions for the parent directory as well as for the file on the given nodes.
PRKC-1110: Failed to create directory \"{0}\" on node \"{1}\", {2}
Cause: Could not create the directory \"{0}\" on node \"{1}\".
Action: Verify that user equivalence is properly configured. Check the log files for details.
PRKC-1111: Failed to remove directory \"{0}\" on node \"{1}\", {2}
Cause: Could not remove the directory \"{0}\" on node \"{1}\".
Action: Verify that user equivalence is properly configured. Check the log files for details.
PRKC-1112: Failed to list contents of directory \"{0}\" on node \"{1}\", {2}
Cause: Could not read the directory \"{0}\" on node \"{1}\".
Action: Verify that user equivalence is properly configured. Check the log files for details.
PRKC-1113: Directory \"{0}\" does not exist on node \"{1}\"
Cause: The mentioned directory does not exist.
Action: Check for existence of directory {0}. Use absolute path for the directory.
PRKC-1114: Registry key name is null
Cause:
Action: Correct registry key name passed to command.
PRKC-1115: Registry subkey name is null
Cause:
Action: Correct registry subkey name passed to command.
PRKC-1116: Failed to create registry subkey \"{0}\" under key \"{1}\" on node \"{2}\", [3]
Cause: Registry operation failed.
Action: See logs for detail.
PRKC-1117: Failed to delete registry subkey \"{0}\" under key \"{1}\" on node \"{2}\", [3]
Cause: Registry operation failed.
Action: See logs for detail.
PRKC-1118: Failed to check existence of registry key \"{0}\" on node \"{1}\", [2]
Cause: Registry operation failed.
Action: See logs for detail.
PRKC-1119: Failed to set data for value \"{0}\" of registry key \"{1}\" on node \"{2}\", [3]
Cause: Registry operation failed.
Action: See logs for detail.
PRKC-1120: Failed to retrieve data for value \"{0}\" of registry key \"{1}\" on node \"{2}\", [3]
Cause: Registry operation failed.
Action: See logs for detail.
PRKC-1121: Failed to delete value \"{0}\" of registry key \"{1}\" on node \"{2}\", [3]
Cause: Registry operation failed.
Action: See logs for detail.
PRKC-1122: Service name is null
Cause: Empty service name provided.
Action: Reattempt the command with a non-null service name.
PRKC-1123: Failed to create service \"{0}\" on node \"{1}\", [2]
Cause:
Action: Please refer to logs for detailed error information.
PRKC-1124: Failed to create service dependency between services \"{0}\" and \"{1}\" on node \"{2}\", [3]
Cause:
Action: Please refer to logs for detailed error information.
PRKC-1125: Failed to start service \"{0}\" on node \"{1}\", [2]
Cause:
Action: Please refer to logs for detailed error information.
PRKC-1126: Failed to stop service \"{0}\" on node \"{1}\", [2]
Cause:
Action: Please refer to logs for detailed error information.
PRKC-1127:Failed to delete service \"{0}\" on node \"{1}\", [2]
Cause:
Action: Please refer to logs for detailed error information.
PRKC-1128: Invalid Interface type {0} is specified as an argument.
Cause:
Action: Correct interface type before retrying command.
PRKC-1129: Invalid IP address type {0} is specified as an argument.
Cause:
Action: Change IP address type before reattempting command.
PRKC-1130: Version argument is null.
Cause:
Action: Correct version argument and retry method invocation.
PRKC-1131: Failed to set user permissions on path {0} on nodes {1}, [{2}]
Cause: Might be due to improper user equivalence setup.
Action: Verify that user equivalence is correctly configured.
PRKC-1132: Failed to set administrator permissions on path {0} on nodes {1}, [{2}]
Cause: Might be due to improper user equivalence setup.
Action: Verify that user equivalence is correctly configured.
PRKC-1133: Names of services on which this service \"{0}\" is dependent on is null.
Cause:
Action: Invalid dependency list passed to method. Correct dependency list and retry command.
PRKC-1134: Failed to remove service dependency between services \"{0}\" and \"{1}\" on node \"{2}\", [3]
Cause:
Action: Refer to logs for detailed error information.
PRKC-1135: Registry key name {0} is not valid, it must be fully defined registry key path
Cause: Invalid registry key format.
Action: Provide valid registry key path.

PRKD—Global Services Daemon Messages

PRKD-3000: Failed to initialize and register with clusterware
Cause: This can occur if cluster synchronization services was not functioning properly.
Action: Check the state of your clusterware by running olsnodes from ORA_CRS_HOME/bin. It should list the nodes in the cluster.
PRKD-3001: Ready to receive client requests
Cause: Global Services Daemon is ready.
Action: No action needed at this time.

PRKE—Global Services Daemon Controller Utility Messages

PRKE-1008: Failed to get list of active nodes from clusterware
Cause: Not operating in cluster mode, failure to load srvm libraries, failure to initialize clusterware context.
Action: Verify the health of the Oracle Clusterware by running the "lsnodes" command to obtain a list of the active nodes in the cluster. Also verify the presence of the SRVM libraries in the load library path. If the active node list is correct and the SRVM libraries are in the load path, then contact your customer support representative.
PRKE-1009: Failed to start GSD on local node
Cause: GSD is already running on the local node, or GSD could not be started because of some other reason.
Action: Run "srvctl status" to check if a daemon is already running on the local node. If a daemon is not running on local node, please contact your customer support representative to check for the other reasons for failure.
PRKE-1010: Failed to stop GSD on local node
Cause: GSD is not running on the local node, or GSD could not shutdown gracefully.
Action: Run "srvctl status" to check if a GSD is running on the local node. If a GSD is running, please contact your customer support representative to check for other reasons for failure.
PRKE-1011: Failed to get status of GSD on local node
Cause: Failure to get the list of active nodes from the cluster, or failure to query the list of live daemons from the clusterware.
Action: Run "lsnodes" to check the health of the clusterware. If the clusterware is working fine, check for the presence of srvm libraries in the load library path. If the libraries are present, please contact your customer support representative for further assistance.

PRKH—Server Manager (SRVM) Messages

PRKH-1000: Unable to load the SRVM HAS shared library
Cause: The system cannot find, or load the srvm has shared library.
Action: Check your system's library load path. Verify that the library exists, and that the libraries it depends on are readable and are in the load path.
PRKH-1001: HASContext Internal Error
Cause: An unexpected internal error has occurred while attempting to communicate with CRS.
Action: Contact Oracle support.
PRKH-1002: Internal HASContext Error: JNI Native Call Failure
Cause: An unexpected internal error has occurred while executing native code from java.
Action: Contact Oracle support.
PRKH-1003: Failed to allocate memory in native layer:
Cause: The SRVM framework was unable to allocate memory.
Action: Your system is running low on memory. Check the memory and swap space, resolve the problem and retry.
PRKH-1004: Failed to execute remote join cluster alias {0} for nodes:
Cause: Unable to execute a join cluster alias operation on another node.
Action: Check the failed nodes. Verify that the system can execute remote commands on those nodes. Check the cluster alias and its related functionality.
PRKH-1005: Failed to execute remote leave cluster alias {0} for nodes:
Cause: Unable to execute a leave cluster alias operation on another node.
Action: Check the failed nodes. Verify that the system can execute remote commands on those nodes. Check the cluster alias and its related functionality.
PRKH-1006: The following nodes are either not active or not configured:
Cause: The system was unable to find a node requested.
Action: Please check the node list supplied and verify that the node is available and configured.
PRKH-1007: Exception Caused by:
Cause: The current exception was caused by another earlier exception.
Action: Examine all of the nested exceptions to determine the root cause of the error.
PRKH-1008: Internal HASContext Error: Argument {0} must be set.
Cause: Internal software error.
Action: Contact Oracle support.
PRKH-1009: CRS HOME must be defined in the environment or in the Oracle Cluster Registry
Cause: The system is unable to determine the ORA_CRS_HOME for this CRS installation.
Action: Check that the Oracle Cluster Registry is properly configured and available to this node.
PRKH-1010: Unable to communicate with CRS services
Cause: The system is unable to communicate with the Oracle Clusterware services.
Action: Check that all of the CRS daemons are running and are properly configured. Verify that the current program is attempting to communicate with the correct CRS daemons.
PRKH-1011: Process does not have sufficient privileges to perform the requested operation. {0}
Cause: The user running the current operation is not permitted to execute a given operation.
Action: Check other messages in the error stack to determine which operation failed. Verify that you are running the operation as the correct user.
PRKH-1012: Unable to find or resolve user {0}
Cause: The system was unable to find the user name supplied.
Action: Check the username and try again.
PRKH-1013: The oracle home {0} does not exist
Cause: The system was unable to find the oracle home supplied.
Action: Check the full path of the oracle home and try again.

PRKI—Cluster Pre-Install Messages

PRKI-2059 Unable to copy files to the nodes
Cause: Lack of permission to create destination file or copy file to the destination location.
Action: Verify permission to create the destination file. Also, please make sure that the destination file is not currently in use.
PRKI-2060 Unable to create service on the nodes
Cause: Lack of permission to create the service, or service already exists.
Action: Verify that you have the permission to create a service on the destination node or nodes. Also, verify that the service does not already exist.
PRKI-2061 Unable to start service on the nodes
Cause: Service is not created, service is already running, service marked for deletion, service could not be started properly.
Action: Try to start the service manually from the service control panel and check the Windows Error message that it gives.
PRKI-2061 Unable to start service on the nodes
Cause: This could be because of several possible problems: the service is not created, the service is already running, the service is marked for deletion, or the service could not be started properly.
Action: Try to start the service manually from the service control panel and check the Windows error message that it gives.
PRKI-2064 Unable to update registry entries on the nodes
Cause: Lack of permission to modify registry entries on the nodes, error while updating the registries.
Action: Verify permission to modify registry entries.
PRKI-2066 Unable to find an Oracle disk partition. Please exit from the wizard, create Oracle partitions and try again.
Cause: Absence of Oracle disk partition, failure to load OLM dll.
Action: Verify that OLM dll (oobjlib.dll) is present in the load path. Also, verify that the Oracle disk partitions are present by going to the Disk Administrator and looking for the partitions.
PRKI-2114 Cannot collect and verify hardware information for all the nodes. Press abort to exit the wizard or ignore to continue.
Cause: Failure to connect to the remote nodes while adding a node to a cluster. Failure to collect VIA information if VIA was chosen.
Action: If you are trying to add a node to an existing cluster, then attempt to map a drive letter to a drive on each of the remote nodes (using commands such as "net use"). Also, verify that the you have permission to start a temporary service on the remote nodes to collect VIA information, in case your system uses VIA.
PRKI-2116 Cannot connect to remote drive on node {0}
Cause: Failure to connect to remote node.
Action: Try to map a driver letter from the local node to the remote node using commands such as "net use."
PRKI-2119 Unable to delete files on {0}. Install may not succeed if files are not deleted
Cause: Files that you are trying to delete do not exist or are currently being used.
Action: If the files you are trying to delete do not exist, ignore this error. If the files you are trying to delete are currently being used, then stop the processes that are using the files and retry.
PRKI-2120 Unable to delete service {0} on {1}. Install may not succeed if services are not deleted
Cause: Service does not exist, or service could not be deleted.
Action: Check the service control panel to see if the service exists. If the service does not exist, ignore this error. If the service exists, try to delete it from the command line using utilities like "net" and "sc." If this fails, check the Windows error message returned by these commands.

PRKN—Server Manager (SRVM) System Library Messages

PRKN-1008: Unable to load the shared library "{0}" or a dependent library, from {1}={2} [{3}]
Cause: The SRVM framework was unable to load a shared library to perform native operations.
Action: Make sure that the library in question is installed and in a location where it can be loaded. Check the environment setting that determines shared library loading on your platform.
PRKN-1009: Native System Internal Error
Cause: An unexpected internal error occurred while attempting to execute a native operation from Java.
Action: Contact Oracle Support.
PRKN-1010: This system is not properly configured as a cluster
Cause: SRVM was unable to find the system libraries which are required in order to use the system as a cluster.
Action: Verify that the Oracle Clusterware installation succeeded and attempt to execute the 'srvctl status' command to obtain more diagnostic information.
PRKN-1011: Failed to retrieve value for "{0}" under registry key "{1}" on node "{2}", {3}
Cause: There was a problem accessing the Windows registry key.
Action: Open the Windows Registry editor on the node and verify that the Registry key exists and that it contains the subkey.

PRKO—Server Control (SRVCTL) Utility Messages

PRKO-2001: "Invalid command line syntax"
Cause: An invalid SRVCTL command line was entered.
Action: Use -h SRVCTL command line option to find out the correct command line syntax and re-enter the command.
PRKO-2002: "Invalid command line option: "
Cause: An invalid SRVCTL command line option was entered.
Action: Use -h SRVCTL command line option to find out the correct command line syntax and re-enter the command.
PRKO-2003: "Invalid command line option value: "
Cause: An invalid SRVCTL command line option value was entered.
Action: Use -h SRVCTL command line option to find out the correct command line syntax and re-enter the command.
PRKO-2004: "Repetition of command line option: "
Cause: Duplicate SRVCTL command line option was entered.
Action: Eliminate the duplicate and re-enter the command.
PRKO-2005: "Application error: Failure in getting Cluster Database Configuration for: "
Cause: An error occurred when getting Cluster Database configuration for the named database.
Action: Make sure that the database has been configured in Cluster Database Configuration Repository; make sure that GSDs are running on each node in the cluster.
PRKO-2005: "Application error: Failure in getting Cluster Database Configuration for: "
Cause: An error occurred when getting Cluster Database configuration for the named database.
Action: Verify that the database has been configured in the Oracle Cluster Registry; make sure that the GSDs are running on each node in the cluster.
PRKO-2006: "Invalid node name: "
Cause: An invalid node name was entered.
Action: Use the correct node name. A valid node name should match the output from 'lsnodes' and must not contain domain name.
PRKO-2007: "Invalid instance name: "
Cause: An invalid instance name was entered.
Action: Use the correct instance name for the database. Run the 'srvctl config database -d <db_name>' command to identify all instances of the database in the Oracle Cluster Registry.
PRKO-2008: "Invalid connect string: "
Cause: An invalid connect string was entered.
Action: Use the correct connect string syntax: <user>/<password>[ as <role>].
PRKO-2009: "Invalid name/value string: "
Cause: An invalid environment name/value pair was entered during SRVCTL setenv command.
Action: Make sure that the correct name/value string format is used: <name>=<value>.
PRKO-2010: "Error in adding instance to node: "
Cause: An error occurred when adding instance to the Oracle Cluster Registry.
Action: Use the 'srvctl config database -d <db_name>' command to check if the database has been configured in the Oracle Cluster Registry; make sure that the GSDs are running on each node in the cluster.
PRKO-2011: "Error in removing instance: "
Cause: An error occurred when removing an instance from the Oracle Cluster Registry.
Action: Use the 'srvctl config database -d <db_name>' command to check if the database and instance have been configured in the Oracle Cluster Registry; make sure that the GSDs are running on each node in the cluster.
PRKO-2012: "Error in moving instance to node: "
Cause: An error occurred when changing the instance and node mapping in the Oracle Cluster Registry.
Action: Use the 'srvctl config database -d <db_name>' command to check if the database and instance have been configured in the Oracle Cluster Registry; make sure that the GSDs are running on each node in the cluster.
PRKO-2013: "Error in setting env: "
Cause: An error occurred when setting environment variables for a database or an instance.
Action: Use 'srvctl config database -d <db_name>' command to check if the database and/or the instance have been configured in the Oracle Cluster Registry; make sure that the GSDs are running on each node in the cluster.
PRKO-2014: "Error in unsetting env: "
Cause: An error occurred when unsetting environment variables for a database or an instance.
Action: Use the 'srvctl getenv' command to check if the environment variable exists for the database or instance; make sure that the database and/or the instance have been configured in the Oracle Cluster Registry; make sure that the GSDs are running on each node in the cluster.
PRKO-2015: "Error in checking condition of instance on node: "
Cause: Could not get status information of an instance.
Action: Use the 'srvctl config database -d <db_name>' command to check if the instance has been configured in the Oracle Cluster Registry; make sure that the GSDs are running on each node in the cluster.
PRKO-2016: "Error in checking condition of listener on node: "
Cause: Could not get status information of a listener.
Action: Check if the listener has been configured in the listener configuration file and if the database instance on the node is listed in SID_NAME in the listener configuration; make sure that GSDs are running on each node in the cluster.
PRKO-2017: "Service {0} is not supported on instance {1}."
Cause: The named instance is not configured in the service configuration.
Action: In service related operations, make sure that you operate on the instances that are configured for the service.
PRKO-2019: Cannot change management policy when database is disabled. Either remove -y option or enable database before before running this command
Cause: The database resource attributes cannot be changed when it is in online state.
Action: Stop the database using the 'srvctl stop database' command and then re-run the command to change the policy.
PRKO-2101: "Instance is disabled: "
Cause: The instance is disabled and cannot be started.
Action: Enable the instance before starting.
PRKO-2102: "Service {0} is not supported on instance {1}."
Cause: The named instance is not configured in the service configuration.
Action: In service related operations, make sure you operate on the instances that are configured for the service.
PRKO-2104: "Error in checking condition of service: "
Cause: There is a problem with the CRS daemon, or the service resource is in an unknown state.
Action: Check whether the daemon is up and listening to the port that SRVCTL is communicating with. Check the service resource status.
PRKO-2105: "Error in checking condition of VIP on node: "
Cause: There is a problem with the CRS daemon, or the VIP resource is in an unknown state.
Action: Check whether the daemon is up and listening to the port that SRVCTL is communicating with. Check the VIP resource status.
PRKO-2106: "Error in checking condition of GSD on node: "
Cause: There is a problem with the CRS daemon, or the VIP resource is in an unknown state.
Action: Check whether the daemon is up and listening to the port that SRVCTL is communicating with. Check the VIP resource status.
PRKO-2108: "Node applications are still running on node: "
Cause: Node applications are running on the node.
Action: Stop the node applications before removing them.
PRKO-2109: "Invalid address string: "
Cause: Invalid address string.
Action: Use the correct format for address string.
PRKO-2112: "Some or all node applications are not removed successfully onnode: "
Cause: There was a problem when removing the node applications.
Action: Details of the problem are given in the text.
PRKO-2113: "Instance {0} is already a preferred instance for service {1}."
Cause: The instance is configured as a preferred instance for the service.
Action: Pick another instance to configure.
PRKO-2114: "Instance {0} is already an available instance for service {1}."
Cause: The instance is configured as an available instance for the service.
Action: Select another instance to configure.
PRKO-2115: "Cannot remove node-level applications on node {0}, because alistener application exists. Remove the listener application first, thenre-run this command."
Cause: A listener application exists.
Action: Remove the listener application first, then re-run this command.
PRKO-2116: "Error in checking condition of ONS daemon on node: "
Cause: There is a problem with the CRS daemon, or the ONS resource is in an unknown state.
Action: Check if the daemon is up and listening to the port that SRVCTL is communicating with. Check the ONS resource status.
PRKO-2117: "This command should be executed as the system privilege user."
Cause: User did not login as the system privilege user.
Action: Login as system privilege user and re-try.
PRKO-2118: "Error in checking condition of ASM instance {0} on node {1}."
Cause: There is a problem with the CRS daemon, or the ASM resource is in an unknown state.
Action: Check if the daemon is up and listening to the port that SRVCTL is communicating with. Check the ASM resource status.
PRKO-2119: "Error in checking enable/disable status of ASM instance {0} onnode {1}."
Cause: There was some problem when checking the status of the ASM instance.
Action: Make sure that the Oracle Cluster Registry is functioning and that the CRS daemon is running.
PRKO-2120: "The internal database service {0} cannot be managed with srvctl."
Cause: The internal database service is not supposed to be a highly available service.
Action: Do not operate on the internal database service.

PRKP—Cluster Database Management Messages

PRKP-1000 "Cannot retrive configuration for cluster database {0}"
Cause: The cluster database configuration cannot be retrieved from the repository. This can occur either because the database was never registered, or because the repository itself has not been created.
Action: Check if the database has been configured by printing a list of all cluster databases using 'srvctl config'. If the repository has not been created, use 'srvconfig -init' to create it.
PRKP-1001 "Error starting instance {0} on node {1}"
Cause: The instance could not be started using the SQL*Plus startup command.
Action: Try starting the named instance manually using SQL*Plus to see why it failed.
PRKP-1002 "Error stopping instance {0} on node {1}"
Cause: The SQL*Plus shutdown command returned an error while stopping the instance.
Action: Try stopping the named instance manually using SQL*Plus to see why it failed.
PRKP-1003 "Startup operation partially failed"
Cause: Some components of the cluster database could not be started.
Action: See earlier error message for details.
PRKP-1004 "Shutdown operation partially failed"
Cause: Some components of the cluster database reported errors while being stopped.
Action: See earlier error messages for details.
PRKP-1005 "Failed to start up cluster database {0}"
Cause: The cluster database could not be started.
Action: See earlier error messages for details.
PRKP-1006 "Failed to shut down cluster database {0}"
Cause: The cluster database reported errors while being shut down.
Action: See earlier error messages for details.
PRKP-1007 "Failed to start all the listeners associated with all the instances of cluster database {0}"
Cause:
Action: Contact your customer support representative.
PRKP-1008 "Failed to start listeners associated with instance {0} on node {1}"
Cause:
Action: Contact your customer support representative.
PRKP-1009 "Failed to stop all the listeners associated with all the instances of cluster database {0}"
Cause: Either the listener name associated with an instance could not be determined, or "lsnrctl stop" failed for a listener.
Action: Verify that listener.ora contains a SID_LIST entry for each instance of the named database, and that the lsnrctl stop command succeeds for those listeners.
PRKP-1010 "Failed to stop all the listeners associated with instance {0} on node{1}"
Cause: Either the listener name associated with an instance could not be determined, or "lsnrctl stop" failed for a listener.
Action: Verify that listener.ora contains a SID_LIST entry for each instance of the named database, and that the lsnrctl stop command succeeds for those listeners.
PRKP-1011 "Failed to get all the listeners associated with instance {0} on node{1}"
Cause: The listener name associated with an instance could not be determined.
Action: Ensure that listener.ora contains a SID_LIST entry for the named instance.
PRKP-1012 "Invalid environment variable {0} setting for cluster database {1}"
Cause: The argument to the -t option is not of the form <name>=<value> or it contains special characters.
Action: Ensure that the -t option has an argument of the form <name>=<value>. Enclose the argument to the -t flag in quotes.
PRKP-1013 "{0}: undefined environment variable for cluster database {1}"
Cause: The named environment variable is not defined for the named cluster database.
Action: Set a value for the variable with "srvctl set env."
PRKP-1014 "{0}: undefined environment variable for instance {1} of cluster database {2}"
Cause: The named environment variable is not defined for the given instance.
Action: Set a value for the variable with "srvctl set env."
PRKP-1015 "{0}: undefined environment variable"
Cause: The named environment variable is not defined.
Action: Set a value for the named environment variable with "srvctl set env."
PRKP-1016 "Database {0} already enabled"
Cause: An attempt was made to enable a database that is already enabled.
Action: No action required.
PRKP-1017 "Instance {0} already enabled."
Cause: An attempt was made to enable an instance that is already enabled.
Action: No action required.
PRKP-1018 "Service {0} already enabled."
Cause: An attempt was made to enable a service that is already enabled.
Action: No action required.
PRKP-1019 "Database {0} already disabled."
Cause: An attempt was made to disable a database that is already disabled.
Action: No action required.
PRKP-1020 "Instance {0} already disabled."
Cause: An attempt was made to disable an instance that is already disabled.
Action: No action required.
PRKP-1021 "Service {0} already disabled."
Cause: An attempt was made to disable a service that is already disabled.
Action: No action required.
PRKP-1022 "The database {0} is still running."
Cause: An attempt was made to delete a database that is still running.
Action: Stop the database using 'srvctl stop database' before deleting the database.
PRKP-1023 "The instance {0} is still running."
Cause: An attempt was made to delete an instance that is still running.
Action: Stop the instance using 'srvctl stop instance' before deleting the instance.
PRKP-1024 "The service {0} is still running."
Cause: An attempt was made to delete a service that is still running.
Action: Stop the service using 'srvctl stop service' before deleting the service.
PRKP-1025 "The service {0} does not exist."
Cause: An attempt was made to operate on a non-configured service.
Action: Check if the service is configured through 'srvctl status service'.
PRKP-1026 "No instance found for database {0}."
Cause: An attempt was made to operate on a non-configured instance.
Action:
PRKP-1027 "Instance {0} is not found for database {1}."
Cause: An attempt was made to operate on a non-configured instance.
Action: Check if the instance is configured through 'srvctl config instance'.
PRKP-1028 "No preferred instance(s) for service {0}."
Cause: An attempt was made to create a service without preferred instances.
Action: Supply preferred instances for the service through 'srvctl create service'.
PRKP-1029 "Failed to register the service {0}."
Cause: Internal error.
Action: Contact support.
PRKP-1030 "Failed to start the service {0}."
Cause: Internal error.
Action: Contact support.
PRKP-1031 "Failed to stop the service {0}."
Cause: Internal error.
Action: Contact support.
PRKP-1032 "Cannot start the disabled service {0}."
Cause: Internal error.
Action: Contact support.
PRKP-1033 "Cannot relocate service {0} from instance {1} to instance {2}."
Cause: Internal error.
Action: Contact support.
PRKP-1034 "{0}: undefined environment variable for node {1}."
Cause: Internal error.
Action: Contact support.
PRKP-1035 "Invalid environment variable {0} setting for node {1}."
Cause:
Action: Contact support.
PRKP-1036 "Failed to unregister HA resource {0}."
Cause:
Action: Contact support.
PRKP-1037 "Failed to create cluster database {0}."
Cause:
Action: Contact support.
PRKP-1038 "Invalid instance {0} specified for the Service {1}."
Cause:
Action: Contact support.
PRKP-1039 "operation result is null"
Cause:
Action: Contact support.
PRKP-1041: "Failed to reload all the listeners associated with cluster database {0}"
Cause:
Action: Refer to CRS logs for detailed error information.
PRKP-1042: "Failed to reload all the listeners associated with instance {0} on node{1}"
Cause:
Action: Refer to CRS logs for detailed error information.
PRKP-1043: "Failed to reload listeners on node {0}"
Cause:
Action: Refer to CRS logs for detailed error information.
PRKP-1044 "Failed to enable the database {0}."
Cause:
Action: Contact support.
PRKP-1045 "Failed to disable the database {0}."
Cause:
Action: Contact support.
PRKP-1046 "Failed to enable the instance {0}."
Cause:
Action: Contact support.
PRKP-1048 "Failed to change configuration for service {0}."
Cause:
Action: Contact support.
PRKP-1049 "{0}: undefined environment variable for service {1} of cluster database {2}"
Cause: The environment variable is not defined for the service.
Action: No action required.
PRKP-1050 "Failed to remove the service {0}."
Cause: There was a problem while executing the crs_unregister command.
Action: Verify whether the crs_unregister command succeeds in unregistering a CRS resource.
PRKP-1051 "Failed to remove the service {0} on instance {1}."
Cause: There was a problem while executing the crs_unregister command.
Action: Verify whether the crs_unregister command succeeds in unregistering a CRS resource.
PRKP-1052 "Failed to enable the service {0}."
Cause: There was a problem while executing the crs_register command.
Action: Verify whether the crs_register command succeeds in registering a CRS resource.
PRKP-1053 "Failed to disable the service {0}."
Cause: There was a problem while executing the crs_register command.
Action: Verify whether the crs_register command succeeds in registering a CRS resource.
PRKP-1054 "Failed to enable the service {0} on instance {1}."
Cause: There was a problem while executing the crs_register command.
Action: Verify whether the crs_register command succeeds in registering a CRS resource.
PRKP-1055 "Failed to disable the service {0} on instance {1}."
Cause: There was a problem while executing the crs_register command.
Action: Verify whether the crs_register command succeeds in registering a CRS resource.
PRKP-1056 "Failed to get the status of the resource {0}."
Cause: There was a problem while executing the crs_stat command.
Action: Verify whether the crs_stat command gives the status of the CRS resources registered.
PRKP-1057 "Failed to set the environment for service {0}."
Cause: There was a problem while accessing the OCR.
Action: Check whether the OCR is accessible by executing a srvctl config command.
PRKP-1058 "Failed to unset the environment for service {0}."
Cause: There was a problem while accessing the OCR.
Action: Check whether the OCR is accessible by executing the srvctl config command.
PRKP-1059 "Failed to get the environment for service {0}."
Cause: There was a problem while accessing the OCR.
Action: Check whether the OCR is accessible by executing the srvctl config command.
PRKP-1060 "Failed to get CRS home."
Cause: Internal error.
Action: Contact support.
PRKP-1061 "Failed to modify the database {0}. "
Cause: Internal error.
Action: Contact support.
PRKP-1062 "Service {0} is already running."
Cause: Attempted to start a service that is already running.
Action: None required.
PRKP-1063 "Service {0} is already stopped."
Cause: Attempted to stop a service that is already stopped.
Action: None required.
PRKP-1064 "Service {0} is already running on instance {1}."
Cause: Attempted to start a service on an instance where it is already running.
Action: None required.
PRKP-1065 "Service {0} is already stopped on instance {1}."
Cause: Attempted to stop a service on an instance where it is already stopped.
Action: None required.
PRKP-1066 "Instance {0} is not an available instance for service {1}."
Cause:
Action: Contact support.
PRKP-1067 "Instance {0} is the last available instance for service {1}. Try modify service instead."
Cause:
Action: Contact support.
PRKP-1068 "Cannot stop the critical instance {0} in critical standby database {1} because it would result in a shutdown of the primary database."
Cause: Attempted to stop the critical instance in a critical standby database while the primary database is running.
Action: Do not stop the critical instance in a critical standby database while the primary database is running.
PRKP-1069 "Failed to change domain of the database {0} to {1}, because this domain name is already used by service {2} configured under the database."
Cause: Attempted to change the database domain when there are services configured with this domain.
Action: Do not change the database domain when there are services configured with that domain.
PRKP-1070 "Service name {0} contains illegal characters."
Cause: Invalid characters have been specified in the service name given.
Action: Supply a name for the service with the character set [a-zA-Z0-9_.].
PRKP-1071: "Database unique name or instance name {0} contains illegal characters {1}."},
Cause:
Action: Correct db/instance name before retrying method/command.
PRKP-1072 "Failed to create service {0} for database {1}, because the specified service domain name is the same as the database domain {2}."
Cause:
Action:
PRKP-1073 "Cannot create database {0} because a database named {1} already exists."
Cause: Attempted to create a database that already exists.
Action: Choose a different name for the database being created.
PRKP-1074 "Failed to relocate a service resource to instance {0} during modifying service configuration for service {1}."
Cause: Internal error.
Action: Contact support.
PRKP-1075 "Instance {0} is the last preferred instance for service {1}."
Cause: Internal error.
Action: Contact support
PRKP-1076: Instance name passed to the method is null
Cause: The Oracle instance SID that you are passing to this API cannot be null.
Action: Make sure that the Oracle instance is configure before this call. Check client specific error message for details.
PRKP-1077: Oracle home is null for the cluster database {0}
Cause: Oracle home specified cannot be null.
Action: Make sure Oracle home is properly set. Check client specific error message for more details.
PRKP-1078: Failed to retrieve \"{0}\" attribute value from \"{1}\" file, {2}"
Cause: An error occurred while retrieving CRS attribute value because of some CRS/OCR error.
Action: Refer to CRS or OCR logs in CRS home/log/<hostname> for detailed error information.
PRKP-1079: Cannot start service {0} on disabled database {1}
Cause: Service cannot be started on a database which is already disabled.
Action: Enable the database using 'srvctl enable database' before re-attempting command.
PRKP-1080: "Cannot start service {0} on disabled instance {1}."
Cause: Service cannot be started in an instance which is already disabled.
Action: Enable the instance using 'srvctl enable instance' before attempting to start the service.
PRKP-1081: Database name passed to the method is null
Cause: The database name cannot be null to perform the operation.
Action: Verify the database name that you are using and retry the command
PRKP-1082: Instance \"{0}\" does not exist in database \"{1}\"
Cause: The configuration information for this instance may not exist in the OCR, or the instance was never configured.
Action: Verify the instance name that you are using before retrying the command. Alternatively, verify the instances that are configured with a database by running the command 'srvctl config database -d <database>'.
PRKP-1083: The service {0} already exists.
Cause: You cannot have multiple database services with same name.
Action: Make sure you use unique service names for each database.
PRKP-1084: Database \"{0}\" cannot have more than \"{1}\" services
Cause: The database supports only 115 user services. You cannot configure more than 115 services.
Action: If you must add this service, then remove some of the unused services using the command 'srvctl removes services' before adding any new services.

PRKR—Cluster Registry Messages

PRKR-1001 "cluster database {0} does not exist"
Cause: The cluster database was never configured in the OCR.
Action: Check if the database has been configured by printing a list of all cluster databases using 'srvctl config'.
PRKR-1002 "cluster database {0} already exists"
Cause: An attempt was made to configure a cluster database that already exists in the OCR.
Action: Check if the database has already been configured by printing a list of all cluster databases using 'srvctl config'.
PRKR-1003 "instance {0} does not exist"
Cause: The named instance is not configured in the OCR.
Action: Use srvctl options to check if the instance was configured in the OCR.
PRKR-1004 "instance {0} already exists"
Cause: The named instance is already configured in the OCR.
Action: Use srvctl options to check if the instance has already been configured in the OCR.
PRKR-1005 "adding of cluster database {0} configuration failed, {1}"
Cause: An error occurred while attempting to add the cluster database configuration information to the OCR.
Action: Verify whether the OCR is accessible by using an 'ocrcheck' or 'srvctl config' command.
PRKR-1006 "deleting of cluster database {0} configuration failed, {1}"
Cause: Same as PRKR-1005.
Action: See earlier error messages.
PRKR-1007 "getting of cluster database {0} configuration failed, {1}"
Cause: Same as PRKR-1005.
Action: See earlier error messages.
PRKR-1008 "adding of instance {0} on node {1} to cluster database {2} failed, {3}"
Cause: Same as PRKR-1005.
Action: See earlier error messages.
PRKR-1009 "deleting of instance {0} from cluster database {1} failed, {2}"
Cause: Same as PRKR-1005.
Action: See earlier error messages.
PRKR-1010 "moving of instance {0} to node {1} of cluster database {2} failed, {3}"
Cause: Same as PRKR-1005.
Action: See earlier error messages.
PRKR-1011 "renaming of instance {0} to instance {1} of cluster database {2} failed, {3}"
Cause: Same as PRKR-1005.
Action: See earlier error messages.
PRKR-1016 "reading of cluster database {0} configuration failed, {1}, {2}"
Cause: Same as PRKR-1005.
Action: See earlier error messages.
PRKR-1017 "writing of cluster database {0} configuration failed, {1}, {2}"
Cause: Same as PRKR-1005.
Action: See earlier error messages.
PRKR-1018 "reading of directory failed, {0}, {1}"
Cause: Internal error.
Action: Contact your customer support representative.
PRKR-1019 "writing of directory failed, {0}, {1}"
Cause: Internal error.
Action: Contact your customer support representative.
PRKR-1020 "reading of version information failed, {0}, {1}"
Cause: Same as PRKR-1005.
Action: See earlier error messages.
PRKR-1021 "writing of version information failed, {0}, {1}"
Cause: Same as PRKR-1005.
Action: See earlier error messages.
PRKR-1022 "raw device {0} contains incompatible version, {1} != {2}"
Cause: An attempt was made to use an incompatible version of the OCR.
Action: Contact your customer support representative.
PRKR-1023 "file {0} does not exist"
Cause: The named file did not exist.
Action: Check if the file exists.
PRKR-1024 "file {0} does not have {1} permissions"
Cause: The named file did not have the specified permission.
Action: Try changing the permission on the file to the specified permission.
PRKR-1025 "file {0} does not contain property {1}"
Cause: The file did not contain the specified property.
Action: Contact your customer support representative.
PRKR-1026 "property {0} not set in file {1}"
Cause: The file did not contain the specified property.
Action: Contact your customer support representative.
PRKR-1027 "failed to retrieve list of cluster databases"
Cause: Same as PRKR-1005.
Action: See earlier error messages.
PRKR-1028 "raw device {0} is invalid\n[HINT: initialize raw device by using \"srvconfig\" tool]"
Cause: The cluster registry was never initialized.
Action: Use srvconfig -init to initialize the cluster registry.
PRKR-1038 "invalid argument {0} specified to -init option"
Cause:
Action:
PRKR-1039 "invalid option {0} specified"
Cause: The specified option was invalid.
Action: Check usage.
PRKR-1040 "missing <file> argument for {0} option"
Cause: The specified option was invalid for srvconfig.
Action: Check usage for details.
PRKR-1045 "raw device version \"{0}\""
Cause: Attempted to retrieve the version of the cluster registry.
Action: No action is required.
PRKR-1046 "srvconfig detected valid raw device \"{0}\"\n[HINT: please specify -init -f option to forcefully initialize it]"
Cause: A valid cluster registry was detected.
Action: No action is required.
PRKR-1047 "raw device {0} is in use by daemon(s) on node(s) {1}"
Cause: An attempt was made to initialize the OCR while the Global Services Daemons were up on one or more nodes in the cluster.
Action: Stop all of the Global Services Daemons on all of the nodes in the cluster by running the 'srvctl stop' command on every node. Try the 'srvconfig -init' operation again.
PRKR-1050 "file {0} creation in {1} directory failed, check permissions, etc."
Cause: Attempted to create a file in a directory which did not exist or which d id not have the right permissions.
Action: Create the directory if it did not exist or change the permission of the directory.
PRKR-1051 "file {0} does not contain an entry for dbname {1}"
Cause: Internal error.
Action: Contact your customer support representative.
PRKR-1052 "file name {0} is not of <cluster database name>.conf form"
Cause: An attempt was made to register a cluster database in the OCR and the file argument passed was not of the <cluster database name>.conf form.
Action: Refer to the usage of the srvconfig command for more information.
PRKR-1053 "invalid range {0} specified in node_list = {1}"
Cause:
Action: Contact your customer support representative.
PRKR-1054 "invalid parameter {0} specified in inst_oracle_sid = {1}"
Cause: Extra number of arguments provided to srvconfig.
Action: See usage of srvconfig for details.
PRKR-1055 "invalid extra arguments {0} specified to {1} option"
Cause: Provided invalid arguments to srvconfig.
Action: See usage of srvconfig for details.
PRKR-1056 "invalid registry entry {0} found, should be of form {1}"
Cause: Detected an invalid registry entry while attempting to add a 8.1.7 or earlier version of Oracle Parallel Server in the OCR.
Action: Contact your customer support representative.
PRKR-1057 "environment variable does not exist"
Cause: Attempted to retrieve non existing environment variable.
Action: Set the environment variable.
PRKR-1058 "Service {0} does not exist in cluster database {1}."
Cause: The named service is not configured in the OCR.
Action: Use srvctl options to check whether the service was configured in the OCR.
PRKR-1059 "Node {0} does not exist."
Cause: Node applications for the named node are not configured in the OCR.
Action: Use srvctl options to check whether the node applications were configured for the given node in the OCR.
PRKR-1060 "Failed to add configuration for node {0}"
Cause:
Action: Contact your customer support representative.
PRKR-1061 "Failed to run remote command to get node configuration for node {0}"
Cause: An internal error occurred while retrieving the configuration for the given node.
Action: Contact your customer support representative.
PRKR-1062 "Failed to find configuration for node {0}"
Cause:
Action: Contact your customer support representative.
PRKR-1063 "VIP {0} is already existing"
Cause:
Action: Contact your customer support representative.
PRKR-1064 "SRVM configuration operation failed due to Oracle Cluster Registry error :"
Cause: Error occurred while accessing the Oracle Cluster Registry.
Action: Contact your customer support representative.
PRKR-1066 "cluster database domain does not match"
Cause:
Action: Contact your customer support representative.
PRKR-1067 "Failed to get environment for cluster database {0}, {1}"
Cause: Unable to retrieve the environment configuration for the given cluster database from the OCR.
Action: Use the ocrdump utility to check whether the environment was configured for the given cluster database in the OCR.
PRKR-1068 "Failed to get environment for instance {1} of cluster database {0}, {2}"
Cause: Unable to retrieve the environment configuration for the given instance from the OCR.
Action: Use ocrdump to check if environment was configured for the given instance in the OCR.
PRKR-1069 "Failed to set environment for cluster database {0}, {1}"
Cause: Unable to update the environment configuration for the given cluster database in the OCR.
Action: Contact your customer support representative.
PRKR-1070 "Failed to set environment for instance {1} of cluster database {0}, {2}"
Cause: Unable to update the environment configuration for the given instance to the OCR.
Action: Contact your customer support representative.
PRKR-1071 "Failed to unset environment for cluster database {0}, {1}"
Cause: Unable to update the environment configuration for the given cluster database in the OCR.
Action: Contact your customer support representative.
PRKR-1072 "Failed to unset environment for instance {1} of cluster database {0}, {2}"
Cause: Unable to update the environment configuration for the given instance in the OCR.
Action: Contact your customer support representative.
PRKR-1073 "\n########## Configuration of nodeapps follows ##########\n"
Cause:
Action: Contact your customer support representative.
PRKR-1074 "\n########## Configuration of vip_range follows ##########\n"
Cause:
Action: Contact your customer support representative.
PRKR-1075 "Insufficient privileges for doing this operation"
Cause: User did not have sufficient privileges when running this command.
Action: Execute this command as a privileged user.
PRKR-1076 "This command cannot run when the Oracle RAC daemons (crsd, evmd, ocssd) are running. Make sure the daemons are not running before invoking this command"
Cause: The Oracle RAC daemons were running when this command was invoked.
Action: Make sure that the Oracle RAC daemons have been stopped before running this command.
PRKR-1077 "One or more arguments passed to the function are not valid"
Cause: One or more invalid arguments were passed to the given method.
Action: Contact your customer support representative.
PRKR-1078 "Database {0} cannot be administered using current version of srvctl. Instead run srvctl from {1}"
Cause: Using incorrect SRVCTL version.
Action: Contact your customer support representative.
PRKR-1079 "Failed to initialize the Oracle Cluster Registry"
Cause: Failed to initialize the Oracle Cluster Registry.
Action: Contact your customer support representative.

PRKS—Automatic Storage Management Messages

PRKS-1000: "ASM instance "{0}" already exists on node "{1}"
Cause: An attempt was made to add configuration information for an ASM instance on the node where it already exists.
Action: Check whether the ASM instance was configured on the node using 'srvctl config asm -n <node>' before adding the configuration for it.
PRKS-1001: ASM instance "{0}" does not exist on node "{1}"
Cause: The configuration for the ASM instance does not exist on the node.
Action: Check whether the ASM instance was configured on the node using 'srvctl config asm -n <node>' before performing the operation.
PRKS-1002: Failed to create CRS profile for ASM instance "{0}" on node "{1}", [{2}]
Cause: 'crs_stat -p' command failed for the ASM instance resource on the node.
Action: Contact Oracle Support.
PRKS-1003: Failed to register CRS resource for ASM instance "{0}" on node "{1}", [{2}]
Cause: crs_register command failed for ASM instance resource on the node.
Action: Contact Oracle Support.
PRKS-1004: Failed to unregister CRS resource for ASM instance "{0}" on node "{1}", [{2}]" }
Cause: A crs_unregister command failed for the ASM instance resource on the node.
Action: Check if there is a database instance that is dependent upon the ASM instance on the node by running the command crs_stat -p ora.<db>.<inst>.inst and see if ASM instance resource name appears in the required resources for the database instance. Remove the database instance's required resource dependency on the ASM instance by running a 'srvctl modify asm' command before retrying this operation.
PRKS-1005: Failed to create CRS resource for ASM instance "{0}" on node "{1}", [{2}]
Cause: crs_register command failed for the ASM instance resource on the node.
Action: Contact Oracle Support.
PRKS-1006: ASM instance "{0}" is already running on node "{1}".
Cause: An attempt was made to start a running ASM instance on the node.
Action: None.
PRKS-1007: ASM instance "{0}" is still running on node "{1}".
Cause: An attempt was made to remove the configuration for a running ASM instance on the node.
Action: Stop the ASM instance using 'srvctl stop asm -n <node> -i <inst>' command before performing the remove operation.
PRKS-1008: ASM instance "{0}" is not running on node "{1}".
Cause: An attempt was made to stop a non-running ASM instance on the node.
Action: None.
PRKS-1009: Failed to start ASM instance "{0}" on node "{1}", [{2}]
Cause: crs_start failed for the ASM instance resource on the node, may be due to invalid startup credentials or missing parameter file.
Action: Check if VIP resource is online on the node and then try to startup the ASM instance using SQL*Plus to get more diagnostic information.
PRKS-1010: Failed to start ASM instances "{0}" on node "{1}", [{2}]
Cause: See above.
Action: See above.
PRKS-1011: Failed to check status of ASM instance "{0}" on node "{1}", [{2}]
Cause: crs_stat failed for the ASM instance resource on the node.
Action: Contact Oracle Support.
PRKS-1012: Failed to stop ASM instance "{0}" on node "{1}", [{2}]"
Cause: The crs_stop command failed for the ASM instances on the node. This may be due to a CRS resource dependency or because the user has invalid credentials for stopping ASM instances.
Action: Determine whether there are database instances that depend on the ASM instance on the node by running the crs_stat -p ora.<db>.<inst>.inst command. If ASM instance resource names appear in the required resources for the database instance, then stop the database instances first using the 'srvctl stop instance' command. Do this before retrying the ASM instance stop operation or try to stop the ASM instance using SQL*Plus to obtain more diagnostic information.
PRKS-1013: Failed to stop ASM instances "{0}" on node "{1}", [{2}]"
Cause: See above.
Action: See above.
PRKS-1014: Failed to enable CRS resource for ASM instance "{0}" on node "{1}", [{2}]
Cause: Failed to set the enable flag of the ASM instance configuration in the OCR.
Action: Verify that the OCR is accessible by running the 'srvctl config ' command.
PRKS-1015: Failed to enable CRS resources for ASM instances "{0}" on node "{1}", [{2}]"
Cause: See above for each ASM instance.
Action: Check whether the OCR is accessible by running the 'srvctl config ' command.
PRKS-1016: Failed to disable CRS resource for ASM instance "{0}" on node "{1}", [{2}]"
Cause: Failed to reset the enable flag of the ASM instance configuration in the OCR.
Action: Verify that the OCR is accessible by running the 'srvctl config ' command.
PRKS-1017: Failed to disable CRS resources for ASM instances "{0}" on node "{1}", [{2}]"
Cause: See above for each ASM instance.
Action: Verify that the OCR is accessible by running the 'srvctl config ' command.
PRKS-1019: Cannot create CRS dependency between database instance "{0}" configured on node "{1}" and ASM instance "{2}" configured on node "{3}".
Cause: An attempt was made to create a CRS dependency between a database instance and an ASM instance that is configured on a different node.
Action: Make sure that the database instance and the ASM instance are on the same node before creating a CRS dependency between them.
PRKS-1020: Failed to create CRS dependency between database instance "{0}" and ASM instance "{1}", [{2}]
Cause: 'crs_register -u' failed to create CRS dependency between the database instance and the ASM instance on the node.
Action: Contact Oracle support.
PRKS-1021: Failed to remove CRS dependency between database instance "{0}" and ASM instance "{1}", [{2}]
Cause: 'crs_register -u' command failed to remove CRS dependency between the database instance and the ASM instance on the node.
Action: Contact Oracle Support.
PRKS-1022: Failed to remove CRS dependency between database instance "{0}" and ASM instances "{1}", [{2}]
Cause: See above.
Action: See above.
PRKS-1023: Failed to remove CRS resource for ASM instance "{0}" on node "{1}", [{2}]
Cause: crs_unregister command failed to unregister CRS resource for the ASM instances on the node.
Action: Contact Oracle Support.
PRKS-1026: ASM Configuration for node "{0}" does not exist in cluster registry."
Cause: An attempt was made to retrieve names of ASM instances configured on the node without configuring any ASM instance on it.
Action: First configure ASM instance using 'srvctl add asm' on the node command before executing the get configuration operation.
PRKS-1027: Configuration for ASM instance "{0}" does not exist in cluster registry."
Cause: An attempt was made to retrieve node name for a given ASM instance name which is not configured on any cluster nodes.
Action: First configure ASM instance using 'srvctl add asm' command before executing the get configuration operation.
PRKS-1028: Configuration for ASM instance "{0}" on node "{1}" does not exist in cluster registry.
Cause: An attempt was made to retrieve configuration for the ASM instance on the node name where it was not configured.
Action: Use 'srvctl config asm -n <node>' command to determine the ASM instance names configured on it and then pass one of these names as "-i <inst>" argument to 'srvctl config asm' command.
PRKS-1029: Client version "{0}" is not compatible with ASM instance configuration version "{1}" in cluster registry.
Cause: Version of the client that tried to retrieve ASM instance configuration is not compatible with ASM instance configuration version.
Action: Make sure client version is compatible with ASM instance configuration version before accessing it.
PRKS-1030: Failed to add configuration for ASM instance "{0}" on node "{1}" in cluster registry, [{2}]
Cause: Failed to add the configuration information for the ASM instance in the OCR.
Action: Verify that the OCR is accessible by executing 'srvctl config ' command.
PRKS-1031: "Failed to retrieve configuration for ASM instance "{0}" on node "{1}" from cluster registry, [{2}]
Cause: Failed to retrieve the configuration information for the ASM instance from the OCR.
Action: Verify that the OCR is accessible by executing 'srvctl config ' command.
PRKS-1032: Failed to modify configuration for ASM instance "{0}" on node "{1}" in cluster registry, [{2}]
Cause: Failed to modify the configuration information for the ASM instance on the node in the OCR.
Action: Verify that the OCR is accessible by executing 'srvctl config ' command.
PRKS-1033: Failed to remove configuration for ASM instance "{0}" on node "{1}" from cluster registry, [{2}]
Cause: Failed to remove the configuration information for the ASM instance from the OCR.
Action: Verify that the OCR is accessible by executing 'srvctl config ' command.
PRKS-1034: Failed to remove configuration for ASM instances "{0}" on node "{1}" from cluster registry, [{2}]"
Cause: See above.
Action: See above.
PRKS-1035: Failed to retrieve ORACLE_HOME value for ASM instance "{0}" on node "{1}" from cluster registry, [{2}]
Cause: Failed to retrieve the ORACLE_HOME from the ASM instance configuration in the OCR.
Action: Verify that the OCR is accessible by executing 'srvctl config ' command.
PRKS-1036: VIP resource for ASM instance node "{0}" does not exist."
Cause: The VIP resource for the node does not exist; it is a required resource for the ASM instance configuration on the node.
Action: Configure the VIP resource for the node using the 'srvctl add nodeapps' command as a privileged user before adding configuration for the ASM instance.
PRKS-1037: Failed to check existence of VIP resource for ASM instance node "{0}", [{1}]
Cause: 'crs_stat ora.<node>.vip' failed to check status of the VIP resource for the node.
Action: Contact Oracle Support.

PRKU—Command-Line Parser Utility Messages

PRKU-1000: "Exception Caused by: "
Cause: The current exception was caused by another earlier exception.
Action: Examine all of the nested exceptions to determine the root cause of the error.
PRKU-1001: "The parameter {0} is required."
Cause: The parameter specified is required by a command line utility.
Action: Supply the parameter specified.
PRKU-1002: "Unexpected argument {0}."
Cause: The argument specified is not needed or not understood by this utility.
Action: Verify the arguments on the command you are executing.
PRKU-1003: "The parameter {0} requires an argument."
Cause: The parameter specified must be accompanied by an argument.
Action: Verify the arguments on the command you are executing.

PRKV—Virtual IP Configuration Assistant Messages

PRKV-1013 "A network interface is required"
Cause: You did not provide a network interface for configuring the virtual IP address.
Action: When running VIPCA in GUI mode, select a suitable network interface from the list. When running VIPCA in silent mode, provide a suitable interface using the '-interfaces' option.
PRKV-1014 "Enter a valid IP address for the node \"{0}\"."
Cause: You did not enter an IP address to be configured as a virtual IP for the node.
Action: Enter an unused IP address to be used for configuring the virtual IP address.
PRKV-1015 "Enter a valid subnet mask for the IP address \"{0}\"."
Cause: You did not enter an IP netmask for the IP address.
Action: Enter a netmask for the IP address.
PRKV-1016 "IP address \"{0}\" is invalid. Enter a valid IP address."
Cause: IP address entered is invalid.
Action: Enter a valid IP address in standard IEEE format.
PRKV-1017 "IP address \"{0}\" does not exist. Enter a valid IP address."
Cause: IP address cannot be resolved in the network.
Action: Add an IP address in DNS or /etc/hosts so it can be resolved.
PRKV-1018 "IP address \"{0}\" has invalid format. Enter a valid IP address."
Cause: IP address is not in standard IEEE format.
Action: Enter a valid IP address in IEEE format.
PRKV-1019 "Netmask entered \"{0}\" has invalid format. Enter a valid netmask."
Cause: Netmask entered in not in standard IEEE format.
Action: Enter a valid IP netmask in IEEE format.
PRKV-1039 "IP address \"{0}\" has already been used. Enter an unused IP address."
Cause: The IP address entered is already used by another node as a virtual IP address.
Action: Enter an unused IP address.
PRKV-1059: "Invalid node name \"{0}\" entered in an input argument."
Cause: The IP address entered is already used by another node as a virtual IP address.
Action: Enter an unused IP address.
PRKV-1060: "Virtual IP address is not entered for node \"{0}\". Enter a valid virtual IP address."
Cause:
Action: Enter a valid virtual IP address for node {0} before re-attempting the command.
PRKV-1061 "Invalid IP address \"{0}\" entered in an input argument."
Cause:
Action: Enter valid IP address in place of {0} before reattempting command.
PRKV-1062 "Invalid netmask \"{0}\" entered in an invalid argument."
Cause:
Action: Enter valid netmask in place of {0} before reattempting command.
PRKV-1063 "Insufficient privileges."
Cause:
Action: Contact your system administrator to grant the appropriate privileges to you so that you can perform the required operations.
PRKV-1064 "Failed to obtain handle to CRS.
Cause:
Action: Refer to CRS logs for detailed error information.
PRKV-1065 "Host IP address \"{0}\" cannot be used as virtual IP for the node \"{1}\". Enter a different IP address.
Cause:
Action: Change IP address {0} before reattempting command.
PRKV-1066 "Host IP address \"{0}\" of cluster node \"{1}\" cannot be used as virtual IP for the node \"{2}\". Enter a different IP address."
Cause:
Action: Change IP address {0} before reattempting command.
PRKV-1070: Different interface names entered as an input for each node. Specify same set of interfaces for each node in the cluster.
Cause: The nodes in a cluster should use the same set of public interfaces for configuring a Virtual IP.
Action: Make sure that you have public interfaces on each node of the cluster and that their names and subnets match.
PRKV-1072: Invalid syntax used for option \"nodevips\". Check usage (vipca -help) for proper syntax.
Cause: The syntax argument value specified for option "nodevips" is invalid.
Action: Run "vipca -help" to see the syntax in which nodevips option value should be specified.
PRKV-1073: "Node names \"{0}\" are duplicated in an input argument."
Cause: The node names entered as input to the VIPCA command line should be unique.
Action: Remove duplicate node names from VIPCA command line and rerun the command.
PRKV-1073: "Node names \"{0}\" are duplicated in an input argument."
Cause: The node names that you enter as input to the VIPCA command line should be unique.
Action: Remove duplicate node names from the VIPCA command line and rerun the command.
PRKV-1074: The given interface(s), \"{0}\" is not public. Public interfaces should be used to configure virtual Ips.
Cause: The interface that you have specified as input is not a public interface. The Oracle Clusterware uses public interfaces for configuring VIPs.
Action: Find a public interface on your system with a name and subnet that matches all of the nodes of the cluster and specify this interface as an argument to VIPCA.
Go to previous page
Previous		 Go to next page
Next
Go to Documentation Home
Home		 Go to Book List
Book List		 Go to Table of Contents
Contents		 Go to Index
Index		 Go to Master Index
Master Index		 Go to Feedback page
Contact Us