18 CLST-01101 to CLST-03203
- 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.
- 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.
- CLST-01103: existing configuration version (string) detected
-
Cause: An existing configuration was detected.
- CLST-01104: successfully determined required configuration for all components
-
Cause: clscfg was able to determine the proper configuration requirements.
- CLST-01105: An existing configuration was detected. It was not overwritten.
-
Cause: An existing configuration was detected, and clscfg chose not to overwrite it.
- CLST-01301: successfully deleted string of string configuration values
-
Cause: clscfg completed a portion of the delete operation.
- CLST-01302: successfully deleted string of string configuration keys
-
Cause: clscfg completed a portion of the delete operation.
- CLST-01303: successfully rolled back delete operation
-
Cause: The delete node operation failed, but the configuration was properly restored to its original state.
- CLST-01304: node deletion successful
-
Cause: The delete node operation succeeded.
- CLST-01401: formatting voting device: string
-
Cause: clscfg started formatting the voting device.
- 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.
- CLST-01901: configuring TCP ports string, string, string, and string
-
Cause: The specified ports were configured for use with the Cluster Ready Services Daemons.
- CLST-01902: configuring node: node number string, node name string
-
Cause: This node configuration was requested.
- CLST-01903: configuring node: host name string, private interconnect name string
-
Cause: This node configuration was requested.
- CLST-01904: creating configuration with user (string) and group (string)
-
Cause: The configuration was set up with the specified user and group.
- CLST-01999: Warning: -force specified. Overwriting existing configuration.
-
Cause: The -force parameter was supplied.
- CLST-02101: Too many nodes were specified. limit is string
-
Cause: Too many nodes were specified on command line.
- 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.
- 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.
- CLST-02104: TCP port string is out of bounds.
-
Cause: The TCP port specified was not a valid port number.
- CLST-02105: missing required parameter -l with language ID information
-
Cause: The -l parameter was required for the requested operation.
- CLST-02106: missing required parameter -o with path to ORA_CRS_HOME
-
Cause: The -o parameter was required for the requested operation.
- CLST-02107: failure configuring component string
-
Cause: The Oracle Cluster Repository configuration for the specified component was unsuccessful.
- CLST-02108: missing required parameter -q with path to the voting device
-
Cause: The -q parameter was required for the requested operation.
- CLST-02109: missing required parameter -c with a cluster name
-
Cause: The -c parameter was required for the requested operation.
- CLST-02110: missing required parameter -nn with the list of nodenames
-
Cause: The -nn parameter was required for the requested operation.
- 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.
- 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.
- 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.
- 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.
- CLST-02301: failure string validating configuration of node string
-
Cause: clscfg was unable to validate existing configuration of the specified node.
- CLST-02302: failure string validating configuration of private interconnect name string
-
Cause: clscfg was unable to validate existing configuration of the specified node.
- CLST-02303: failure string validating configuration of node with host name string
-
Cause: clscfg was unable to validate existing configuration of the specified node.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- CLST-02310: CSS daemon refused node deletion, status string. attempting rollback
-
Cause: Cluster Synchronization Services daemon refused the node deletion.
- 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.
- 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.
- CLST-02401: failure string querying maximum configurable node number
-
Cause: clscfg was unable to determine the legitimate range of node numbers.
- CLST-02402: failure string querying existing configured node list
-
Cause: clscfg was unable to retrieve the list of currently configured nodes.
- CLST-02403: failure string querying the maximum node name size
-
Cause: clscfg was unable to determine the size of the largest node name.
- CLST-02404: failure string querying the cluster name
-
Cause: clscfg was unable to determine the existing cluster name.
- CLST-02405: failure formatting voting device (string) at [string] [string] [string]
-
Cause: clscfg failed to format the voting device.
- CLST-02501: failure string opening configuration for write operation
-
Cause: clscfg was attempting to open the current configuration for write access.
- CLST-02502: failure string writing new configuration
-
Cause: clscfg was attempting to write new configuration data.
- CLST-02503: failure string opening configuration for delete operation
-
Cause: clscfg received an error while attempting to delete part of the existing configuration.
- CLST-02504: failure string writing configuration to disk
-
Cause: clscfg received a failure writing information to the Oracle Cluster Repository.
- CLST-02901: The number of Oracle Cluster Repository keys exceeds limit of string.
-
Cause: clscfg ran out of internal space for keys during install.
- 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.
- CLST-02903: unable to allocate string bytes of memory at location: string
-
Cause: clscfg was unable to allocate enough memory to service the request.
- CLST-02904: failure string in SCLS API at string
-
Cause: clscfg was unable to query for information about the system setup.
- 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.
- CLST-02906: Clustername should be between 1 and string letters.
-
Cause: cluster name supplied with -c argument was the wrong size.
- CLST-02907: unknown parameter string supplied
-
Cause: An unknown parameter was passed to clscfg.
- CLST-02908: unable to determine local hostname
-
Cause: clscfg was unable to determine the local hostname.
- CLST-02909: The requested operation requires High Availability privileges.
-
Cause: The current user did not have High Availability privileges.
- CLST-02910: Failure string contacting the CRS daemon.
-
Cause: clscfg was unable to communicate with the CRS daemon.
- CLST-02911: failure string contacting the CSS daemon
-
Cause: clscfg was unable to communicate with the CSS daemon.
- CLST-02999: Untranslated failure: [string] [string] [string] [string] [string] [string]
-
Cause: A failure with no translation occurred.
- CLST-03100: See the documentation for usage information.
-
Cause: Incorrect or insufficient arguments were passed to crsuser.
- CLST-03101: Enter the password for user string.
-
Cause: crsuser requires the password to register the user.
- CLST-03102: Operation successful.
-
Cause: The operation succeeded.
- CLST-03200: internal error: [string] [string] [string] [string] [string]
-
Cause: A failure with no translation occurred.
- CLST-03201: unexpected argument: string
-
Cause: crsuser failed to parse the arguments, or an unknown argument was passed.
- CLST-03202: Memory allocation failure for string bytes.
-
Cause: crsuser was unable to allocate memory.
- CLST-03203: insufficient privileges for action: string
-
Cause: The current user did not have sufficient privileges.