17 CLSS-00001 to CLSS-03202
- CLSS-00001: skgxn not active
-
Cause: The skgxn service is required, but is not active
- CLSS-00002: unable to determine local node number. type string
-
Cause: Either the skgxn service is unavailable, or the OCR configuration is incomplete/inaccurate.
- CLSS-00003: unable to determine cluster name. type string
-
Cause: Name of the cluster cannot be determined from configuration.
- CLSS-00004: unable to allocate memory resources
-
Cause: Memory allocation routines failed.
- CLSS-00099: logfile open failed for string, err string
-
Cause: The log file could not be opened, with error type err
- CLSS-00100: configuration data access failed for key string
-
Cause: Access of the configuration data indicated by key failed with error code error
- CLSS-00101: Oracle Cluster Repository mismatch with node string. (string != string)
-
Cause: A remote node is accessing a different set of configuration. This situation can be caused by attempting to reinstall while there are active cluster nodes.
- CLSS-00102: initialization failure: [string] [string] [string] [string] [string] [string]
-
Cause: A general initialization failure occurred.
- CLSS-00103: unable to read configuration information for node string
-
Cause: Incomplete configuration information for the specified node was found.
- CLSS-00200: local node string not listed in configuration
-
Cause: The OCR configuration information does not list this node as a member of the cluster
- CLSS-01200: skgxn errror: category string, operation string, loc string
-
Cause: The skgxn service encountered an error, the information in the error message is vendor supplied diagnostic information
- CLSS-02000: reconfiguration successful, incarnation string with string nodes
-
Cause: A rconfiguration has completed successfully
- CLSS-02001: local node number string, master node number string
-
Cause: Informational message regarding this incarnation
- CLSS-02200: Received node deletion request for active node string.
-
Cause: User attempted to delete a node from the configuration before shutting it down.
- CLSS-02201: endpoint already in use: string
-
Cause: The specified endpoint is already in use. Another process is using the endpoint.
- CLSS-02202: voting device access took an excessive amount of time. (string sec)
-
Cause: A read or write to the voting device took an unacceptable amount of time.
- CLSS-02203: unable to access voting device: string
-
Cause: The CSS daemon received a failure using the voting device.
- CLSS-02204: voting device not configured. [string] [string]
-
Cause: A voting device was not supplied during configuration.
- CLSS-02205: remote node string signaled our eviction via voting device: cause string
-
Cause: A remote node of the cluster evicted the local node due to network failure or due to software failure in the local CSS daemon.
- CLSS-02206: local node evicted by vendor node monitor
-
Cause: The Operating System vendor's node monitor evicted the local node.
- CLSS-02207: error string getting status from vendor node monitor
-
Cause: The CSS daemon received a failure interacting with the vendor node monitor. The local node may have been evicted or the vendor node monitor may have been shut down.
- CLSS-03000: reconfiguration successful, incarnation string with string nodes
-
Cause: A rconfiguration has completed successfully
- CLSS-03001: local node number string, master node number string
-
Cause: Informational message regarding this incarnation
- CLSS-03200: timed out waiting on nested reconfiguration
-
Cause: The current reconfiguration hung. A network failure may have \ occurred.
- CLSS-03201: An attempt to begin a nested reconfiguration failed.
-
Cause: unable to cancel previous reconfiguration to begin a new one
- CLSS-03202: out of sync with master: [string] [string] [string] [string]
-
Cause: Consistency checks between the local node and the master failed.