CLST-01101: assigning default private interconnect name string for node string
Cause: A private interconnect name was not specified. The node name was used as a default instead.
Action: Verify that the node name refers to IP addresses on the private interconnect. Using a non-private network can cause performance and stability issues.
CLST-01102: assigning default host name string for node string
Cause: A host name for the node was not specified. The node name was used as a default instead.
Action: If the node name is not equal to the host name, the host name must be supplied to clscfg. Failure to do so will cause the Cluster Ready Services daemons not to function.
CLST-01103: existing configuration version (string) detected
Cause: An existing configuration was detected.
Action: Informational message only. No action is required. clscfg will not modify the existing configuration unless explicitly requested with the -force flag.
CLST-01104: successfully determined required configuration for all components
Cause: clscfg was able to determine the proper configuration requirements.
Action: Informational message only. No action is required. clscfg will attempt to write the configuration next.
CLST-01105: An existing configuration was detected. It was not overwritten.
Cause: An existing configuration was detected, and clscfg chose not to overwrite it.
Action: This message may be ignored if it is seen as part of starting any node other than the first one. The -force option can be used to override this decision, but if it is used when there are active cluster members, failure CLSS-0101 and data integrity issues are likely.
CLST-01301: successfully deleted string of string configuration values
Cause: clscfg completed a portion of the delete operation.
Action: Informational message only. No action is required. If some of the values were not deleted, another error message should be visible with more information.
CLST-01302: successfully deleted string of string configuration keys
Cause: clscfg completed a portion of the delete operation.
Action: Informational message only. No action is required. If some of the keys were not deleted, another error message should be visible with more information.
CLST-01303: successfully rolled back delete operation
Cause: The delete node operation failed, but the configuration was properly restored to its original state.
Action: Informational message only. No action is required.
CLST-01304: node deletion successful
Cause: The delete node operation succeeded.
Action: Informational message only. No action is required.
CLST-01401: formatting voting device: string
Cause: clscfg started formatting the voting device.
Action: Informational message only. No action is required.
CLST-01501: tried to delete key string but it was not there
Cause: clscfg attempted to delete a key as part of a delete operation, but it had already been deleted.
Action: Informational message only. No action is required. This might be an indication of corrupted configuration, or a previous delete operation that did not complete.
CLST-01901: configuring TCP ports string, string, string, and string
Cause: The specified ports were configured for use with the Cluster Ready Services Daemons.
Action: Informational message only. No action is required. To change the ports used, specify 4 alternate ports with "-t". Example: -t 1001,1002,1003,1004
CLST-01902: configuring node: node number string, node name string
Cause: This node configuration was requested.
Action: Informational message only. No action is required. To alter the list of nodes re-run the install and specify a different set of nodes, or make use of the add and delete node install options after the current install is complete.
CLST-01903: configuring node: host name string, private interconnect name string
Cause: This node configuration was requested.
Action: Informational message only. No action is required. To alter the list of nodes re-run the install and specify a different set of nodes, or make use of the add and delete node install options after the current install is complete.
CLST-01904: creating configuration with user (string) and group (string)
Cause: The configuration was set up with the specified user and group.
Action: Informational message only. No action is required. Some configuration information will only be accessible to members of the specified group. Note: On Windows platforms the group may be blank.
Action: The -force parameter will cause clscfg to overwrite the existing configuration. If used while a Cluster Ready Services cluster is actively running, this can cause instability and data integrity exposures.
CLST-02101: Too many nodes were specified. limit is string
Cause: Too many nodes were specified on command line.
Action: Retry the operation with a smaller number of simultaneous changes.
CLST-02102: Node string specified is out of range. Maximum node number is string.
Cause: A node was specified with node number out of range.
Action: Retry the operation with a smaller node number.
CLST-02103: Unable to parse TCP port options specified.
Cause: Arguments to the -t flag were not valid port numbers, or some number other than 4 ports were supplied.
Action: Correct the arguments to the -t flag and rerun the operation.
CLST-02104: TCP port string is out of bounds.
Cause: The TCP port specified was not a valid port number.
Action: Specify an another port. Usually TCP ports need to be between 1001 and 65,535.
CLST-02105: missing required parameter -l with language ID information
Cause: The -l parameter was required for the requested operation.
Action: Supply the -l parameter with the proper language ID.
CLST-02106: missing required parameter -o with path to ORA_CRS_HOME
Cause: The -o parameter was required for the requested operation.
Action: Supply the -o parameter with the proper path.
CLST-02107: failure configuring component string
Cause: The Oracle Cluster Repository configuration for the specified component was unsuccessful.
Action: Look for other error information and contact Oracle support.
CLST-02108: missing required parameter -q with path to the voting device
Cause: The -q parameter was required for the requested operation.
Action: Supply the -q parameter with a valid path for the voting device.
CLST-02109: missing required parameter -c with a cluster name
Cause: The -c parameter was required for the requested operation.
Action: Supply the -c parameter with a name for the cluster.
CLST-02110: missing required parameter -nn with the list of nodenames
Cause: The -nn parameter was required for the requested operation.
Action: Supply a list of node names with the format: nodenameA,nodenumA,nodenameB,nodenumB,...
CLST-02201: node string already exists in the configuration with node number string
Cause: A node name specified for the add node operation conflicted with the existing configuration.
Action: Choose an alternate node to add to the cluster, or give the new node a unique name, or delete the previous node, then retry.
CLST-02202: private interconnect name string is already assigned to node number string
Cause: The private interconnect name specified for the add node operation conflicted with the existing configuration.
Action: Choose an alternate node to add to the cluster, or give the new node a unique name, or delete the previous node, then retry.
CLST-02203: Host name string is already assigned to node number string.
Cause: The host name specified for the add node operation conflicted with the existing configuration.
Action: Choose an alternate node to add to the cluster, or give the new node a unique name, or delete the previous node, then retry.
CLST-02204: Node number string is already assigned to node string.
Cause: The node number specified for the add node operation conflicted with the existing configuration.
Action: Chose an alternate node to add to the cluster, or give the new node a unique node number, or delete the previous node, then retry.
CLST-02301: failure string validating configuration of node string
Cause: clscfg was unable to validate existing configuration of the specified node.
Action: Validate the integrity of the Cluster Ready Services install on the local node, or choose another node to delete.
CLST-02302: failure string validating configuration of private interconnect name string
Cause: clscfg was unable to validate existing configuration of the specified node.
Action: Validate the integrity of the Cluster Ready Services install on the local node, or choose another node to delete.
CLST-02303: failure string validating configuration of node with host name string
Cause: clscfg was unable to validate existing configuration of the specified node.
Action: Validate the integrity of the Cluster Ready Services install on the local node, or choose another node to delete.
CLST-02304: node name string for node string does not match existing node name string
Cause: The node name specified in a delete operation did not match the existing configuration.
Action: Specify the correct information describing the node you intend to delete, then retry.
CLST-02305: node number string for node string does not match existing node number string
Cause: The node number specified in a delete operation did not match the existing configuration.
Action: Specify the correct information describing the node you intend to delete, then retry.
CLST-02306: private interconnect name string for node string does not match string
Cause: The private interconnect name specified in a delete operation did not match the existing configuration.
Action: Specify the correct information describing the node you intend to delete, then retry.
CLST-02307: host name string for node string does not match existing host name string
Cause: The host name specified in a delete operation did not match the existing configuration.
Action: Specify the correct information describing the node you intend to delete, then retry.
CLST-02308: concurrent node deletion suspected when deleting key string
Cause: A key being deleted by the current operation was deleted by another process during the small amount of time between opening it for deletion and actually deleting it. An attempt to execute multiple separate delete operations may have occurred, and may have corrupted the configuration.
Action: Verify the integrity of the Oracle Cluster Repository, and restore from backup if necessary. If only one clscfg process was active on the cluster this may be ignored.
CLST-02309: failure updating the configuration in node deletion
Cause: clscfg was unable to modify the existing configuration for node deletion. The existing configuration was probably not harmed.
Action: Verify the integrity of the Cluster Ready Services install on the local node, and retry.
CLST-02310: CSS daemon refused node deletion, status string. attempting rollback
Cause: Cluster Synchronization Services daemon refused the node deletion.
Action: One or more of the designated nodes may still be active. clscfg will now attempt to roll back the deletion process. The Cluster Ready Services daemons must be shut down on a node before any attempt to remove them from the configuration. More information on why the attempt was refused may be available in the Cluster Synchronization Service logfile.
CLST-02311: failure rolling back node deletion. configuration irrecoverable
Cause: clscfg attempted to roll back the deletion process after a failure and was unable to do so. Configuration was partially deleted and left in an inconsistent state.
Action: Shut down the cluster and restore the Oracle Cluster Repository from backup.
CLST-02312: failed to completely delete node configuration
Cause: The node deletion was mostly successful, and should be functional in this state. Some portions of the configuration were not successfully deleted.
Action: This can be ignored. The safer choice is to restore the Oracle Cluster Repository from backup, and attempt the delete again. Adding any of the deleted nodes back to the configuration in the future may fail if this is ignored.
CLST-02401: failure string querying maximum configurable node number
Cause: clscfg was unable to determine the legitimate range of node numbers.
Action: Verify the integrity of the Cluster Ready Services install on the local node.
CLST-02402: failure string querying existing configured node list
Cause: clscfg was unable to retrieve the list of currently configured nodes.
Action: Verify the integrity of the Cluster Ready Services install on the local node.
CLST-02403: failure string querying the maximum node name size
Cause: clscfg was unable to determine the size of the largest node name.
Action: Verify the integrity of the Cluster Ready Services install on the local node.
CLST-02404: failure string querying the cluster name
Cause: clscfg was unable to determine the existing cluster name.
Action: Verify the integrity of the Cluster Ready Services install on the local node.
CLST-02405: failure formatting voting device (string) at [string] [string] [string]
Cause: clscfg failed to format the voting device.
Action: Verify the path and permissions set on the voting device.
CLST-02501: failure string opening configuration for write operation
Cause: clscfg was attempting to open the current configuration for write access.
Action: Verify the integrity of the Oracle Cluster Repository. Shut down the cluster and restore OCR from backup if necessary.
CLST-02502: failure string writing new configuration
Cause: clscfg was attempting to write new configuration data.
Action: Verify the integrity of the Oracle Cluster Repository. Shut down the cluster and restore OCR from backup if necessary.
CLST-02503: failure string opening configuration for delete operation
Cause: clscfg received an error while attempting to delete part of the existing configuration.
Action: Verify the integrity of the Oracle Cluster Repository. Shut down the cluster and restore OCR from backup if necessary.
CLST-02504: failure string writing configuration to disk
Cause: clscfg received a failure writing information to the Oracle Cluster Repository.
Action: Verify the settings for the Oracle Cluster Repository and retry.
CLST-02901: The number of Oracle Cluster Repository keys exceeds limit of string.
Cause: clscfg ran out of internal space for keys during install.
Action: Re-run the install and specify a smaller list of nodes. When that completes, use the add node option to add the remaining nodes.
CLST-02902: The number of Oracle Cluster Repository keys exceeds limit of string.
Cause: clscfg ran out of internal space for keys during delete node.
Action: Re-run the delete node operation and delete fewer nodes at once.
CLST-02903: unable to allocate string bytes of memory at location: string
Cause: clscfg was unable to allocate enough memory to service the request.
Action: Ensure that the specified amount of memory will be available and retry the operation.
CLST-02904: failure string in SCLS API at string
Cause: clscfg was unable to query for information about the system setup.
Action: Contact Oracle support with the additional information printed just after this message.
CLST-02905: add, install, delete, concepts, and local are mutually exclusive
Cause: clscfg was run with two different mode flags. All mode flags are mutually exclusive.
Action: Correct the command line and try again.
CLST-02906: Clustername should be between 1 and string letters.
Cause: cluster name supplied with -c argument was the wrong size.
Action: Supply an alternate cluster name of an appropriate length.
CLST-02907: unknown parameter string supplied
Cause: An unknown parameter was passed to clscfg.
Action: Use "clscfg -help" or "clscfg -concepts" for more information.
CLST-02908: unable to determine local hostname
Cause: clscfg was unable to determine the local hostname.
Action: Verify the operating system host name configuration.
CLST-02909: The requested operation requires High Availability privileges.
Cause: The current user did not have High Availability privileges.
Action: Log in as a different user and retry the operation.
CLST-02910: Failure string contacting the CRS daemon.
Cause: clscfg was unable to communicate with the CRS daemon.
Action: The requested operation must be performed from an active cluster node. Validate the pre-existing installation on the local machine, or perform the operation from another node.
CLST-02911: failure string contacting the CSS daemon
Cause: clscfg was unable to communicate with the CSS daemon.
Action: The requested operation must be performed from an active cluster node. Validate the pre-existing installation on the local machine, or perform the operation from another node.