59 CLSS-00001 to CLSS-03202

CLSS-00001: skgxn not active: Cause: The skgxn service is required, but is not active; Action: Verify that the clusterware skgxn is active and restart it if necessary

CLSS-00002: unable to determine local node number. type string: Cause: Either the skgxn service is unavailable, or the OCR configuration is incomplete/inaccurate.; Action: Verify that the clusterware skgxn is active and restart it if necessary. Additionally validate that the clusterware installation was successful, and that the local node was entered in the node listings.

CLSS-00003: unable to determine cluster name. type string: Cause: Name of the cluster cannot be determined from configuration.; Action: Verify that the clusterware installation was successful and that the OCR registry is available.

CLSS-00004: unable to allocate memory resources: Cause: Memory allocation routines failed.; Action: Validate that the system has sufficient memory resources to use the product.

CLSS-00099: logfile open failed for string, err string: Cause: The log file could not be opened, with error type err; Action: Verify that the log directory specified during installation exists and that the ocssd executable has permission to create a file in that directory

CLSS-00100: configuration data access failed for key string: Cause: Access of the configuration data indicated by key failed with error code error; Action: Verify that the clusterware installation was successful and that the OCR registry is accessible

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.; Action: Verify that the local and remote nodes are accessing the same Oracle Cluster Repository.

CLSS-00102: initialization failure: [string] [string] [string] [string] [string] [string]: Cause: A general initialization failure occurred.; Action: Contact Oracle Customer Service for more information.

CLSS-00103: unable to read configuration information for node string: Cause: Incomplete configuration information for the specified node was found.; Action: Validate the integrity of the Oracle Cluster Repository, restoring it from backup if necessary.

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; Action: Verify that the clusterware installation was successful and that the node has not been added since installation

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; Action: Report this error to the vendor who supplied the skgxn

CLSS-02000: reconfiguration successful, incarnation string with string nodes: Cause: A rconfiguration has completed successfully; Action: None

CLSS-02001: local node number string, master node number string: Cause: Informational message regarding this incarnation; Action: None

CLSS-02200: Received node deletion request for active node string.: Cause: User attempted to delete a node from the configuration before shutting it down.; Action: Shut down the specified node and retry the node deletion.

CLSS-02201: endpoint already in use: string: Cause: The specified endpoint is already in use. Another process is using the endpoint.; Action: Shut down the other process, and retry the startup attempt.

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.; Action: Contact the disk hardware vendor for information on improving the availability of the disk.

CLSS-02203: unable to access voting device: string: Cause: The CSS daemon received a failure using the voting device.; Action: Examine the permissions on the voting device. If this failure occurred later than boot time, then access to the voting device was lost.

CLSS-02204: voting device not configured. [string] [string]: Cause: A voting device was not supplied during configuration.; Action: The voting device assists in ensuring data integrity and is required by the CSS daemon. Configure a voting device and restart the cluster.

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.; Action: Verify the stability of the private network between the local node and the specified remote node.

CLSS-02206: local node evicted by vendor node monitor: Cause: The Operating System vendor's node monitor evicted the local node.; Action: Examine the vendor node monitor's logs for relevant information.

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.; Action: Examine the vendor node monitor's logs for relevant information.

CLSS-03000: reconfiguration successful, incarnation string with string nodes: Cause: A rconfiguration has completed successfully; Action: None

CLSS-03001: local node number string, master node number string: Cause: Informational message regarding this incarnation; Action: None

CLSS-03200: timed out waiting on nested reconfiguration: Cause: The current reconfiguration hung. A network failure may have \ occurred.; Action: The local node will terminate itself to cause remote nodes to enter a nested reconfiguration. This may allow the cluster to continue operation.

CLSS-03201: An attempt to begin a nested reconfiguration failed.: Cause: unable to cancel previous reconfiguration to begin a new one; Action: None

CLSS-03202: out of sync with master: [string] [string] [string] [string]: Cause: Consistency checks between the local node and the master failed.; Action: The local daemon will terminate itself to ensure that the surviving cluster is all properly coordinated.