57 CLSD-01001 to CLSD-02009

CLSD-01001: The OCR was formatted using version number.: Cause: Successfully formatted the OCR location(s).; Action: None

CLSD-01002: The OCR was restored from string.: Cause: The OCR was successfully restored from a backup file as requested by the user.; Action: None

CLSD-01003: The OCR format was downgraded to version number.: Cause: The OCR was successfully downgraded to an earlier block format as requested by the user.; Action: None

CLSD-01004: The OCR was imported from string.: Cause: Successfully imported the OCR contents from a file as requested by the user.; Action: None

CLSD-01005: The OCR upgrade was completed. Version has changed from number to number. Details in string.: Cause: The OCR was successfully upgraded to a newer block format.; Action: None

CLSD-01006: The OCR location string is inaccessible. Details in string.: Cause: An error occurred while accessing the OCR.; Action: Use the ocrcheck command to validate the accessibility of the device and its block integrity. Check that the OCR location in question has the correct permissions. Determine whether this behavior is limited to one node or whether it occurs across all of the nodes in the cluster. Use the ocrconfig command with the -replace option to replace the OCR location.

CLSD-01007: The OCR/OCR mirror location was replaced by string.: Cause: The OCR location was successfully replaced as requested by the user.; Action: None

CLSD-01008: Node string is not responding to OCR requests. Details in string.: Cause: Error in communicating to the OCR server on a peer node. This OCR did not receive a notification regarding its peer's death within the specified time.; Action: Contact Oracle Customer Support.

CLSD-01009: The OCR configuration is invalid. Details in string.: Cause: The OCR configuration on this node does not match the OCR configuration on the other nodes in the cluster.; Action: Determine the OCR configuration on the other nodes in the cluster on which Oracle Clusterware is running by using the ocrcheck command. Run the ocrconfig command with the -repair option to correct the OCR configuration on this node.

CLSD-01010: The OCR mirror location string was removed.: Cause: The OCR location was successfully removed as requested by the user.; Action: None

CLSD-01011: OCR cannot determine that the OCR content contains the latest updates. Details in string.: Cause: The OCR could not be started. The OCR location configured on this node does not have the necessary votes and might not have the latest updates.; Action: Ensure that the other nodes in the cluster have the same OCR location configured. If the configuration on the other nodes in the cluster does not match, then run the ocrconfig command with the -repair option to correct the configuration on this node. If the configurations on all of the nodes match, use the ocrdump command to ensure that the existing OCR location has the latest updates. Run the ocrconfig command with the -overwrite option to correct the problem. If the se procedures do not correct the problem, then contact Oracle Customer Support.

CLSD-01012: The OCR service started on node string.: Cause: The OCR was successfully started.; Action: None

CLSD-01013: The OCR at string was successfully formatted using version number. Ignore earlier CRS-1006 messages if any.: Cause: Successfully formatted the OCR location(s).; Action: Ignore earlier CRS-1006 messages if any.

CLSD-01201: CRSD started on node string.: Cause: CRSD has started, possibly due to a CRS start, or a node reboot or a CRSD restart.; Action: None Required. You can run the command 'crsctl check crsd' to validate the health of the CRSD

CLSD-01202: CRSD aborted on node string. Error [string]. Details in string.: Cause: Fatal Internal Error. Check the CRSD log file to determine the cause.; Action: Determine whether the CRSD gets auto-started.

CLSD-01203: Failover failed for the CRS resource string. Details in string.: Cause: Failover failed due to an internal error. Examine the contents of the CRSD log file to determine the cause.; Action: None

CLSD-01204: Recovering CRS resources for node string.: Cause: CRS resources are being recovered, possibly because the cluster node is starting up online.; Action: Check the status of the resources using the crs_stat command.

CLSD-01205: Auto-start failed for the CRS resource string. Details in string.: Cause: This message comes up when the auto-start for the resource has failed during a reboot of the cluster node.; Action: Start the resources using the crs_start command.

CLSD-01206: Resource string went into an UNKNOWN state. Force stop the resource using the crs_stop -f command and restart string.: Cause: Resource went into an UNKNOWN state because the check or the stop; Action: Force stop the resource using the crs_stop -f command and restart the resource

CLSD-01207: There are no more restart attempts left for resource string. Restart the resource manually using the crs_start command.: Cause: The Oracle Clusterware is no longer attempting to restart the resource because the resource has failed and the Oracle Clusterware has exhausted the maximum number of restart attempts.; Action: Use the crs_start command to restart the resouce manually.

CLSD-01401: EVMD started on node string.: Cause: EVMD has started either because of a CRS start, a node reboot, or an EVMD restart.; Action: None required. You can run the 'crsctl check evmd' command to validate the health of EVMD.

CLSD-01402: EVMD aborted on node string. Error [string]. Details in string.: Cause: EVMD has aborted due to an internal error. Check the EVMD log file to determine the cause.; Action: Determine whether the EVMD is auto-started

CLSD-01601: CSSD Reconfiguration complete. Active nodes are string.: Cause: A node joined or left the cluster; Action: None

CLSD-01602: CSSD aborted on node string. Error [string]. Details in string.: Cause: The CSS daemon aborted on the listed node with the listed return code; Action: Collect the CSS daemon logs from all nodes and any CSS daemon core files and contact Oracle Support

CLSD-01603: CSSD on node string shutdown by user.: Cause: The CSS daemon on the listed node was terminated by a user; Action: None

CLSD-01604: CSSD voting file is offline: string. Details in string.: Cause: The listed voting file became unusable on the local node; Action: Verify that the filesystem containing the listed voting file is available on the local node

CLSD-01605: CSSD voting file is online: string. Details in string.: Cause: The CSS daemon has detected a valid configured voting file; Action: None

CLSD-01606: CSSD Insufficient voting files available [string of string]. Details in string.: Cause: The number of voting files has decreased to a number of files that is insufficient.; Action: Locate previous 1604 messages and take action as indicated for message 1604

CLSD-01607: CSSD evicting node string. Details in string.: Cause: The local node is evicting the indicated node; Action: Collect the CSS daemon logs from all nodes and any CSS daemon core files and contact Oracle Support

CLSD-01608: CSSD Evicted by node string. Details in string.: Cause: The local node was evicted by the indicated node; Action: Collect the CSS daemon logs from all nodes and any CSS daemon core files and contact Oracle Support

CLSD-01609: CSSD detected a network split. Details in string.: Cause: Heartbeat messages between one or more nodes were not received and one or more nodes were evicted from the cluster to preserve data integrity.; Action: Verify all network connections between cluster nodes and repair any problematic connections. If there do not appear to be any network problems,
1. collect the CSS daemon logs, system messages and any CSS daemon core files from allnodes and

2. contact Oracle Support.

CLSD-01610: node string (number) at 90% heartbeat fatal, eviction in number.number seconds: Cause: Did not receive heartbeat messages from the node. This could be due network problems or failure of listed node.; Action: Check if the private interconnect network used by cluster is functioning properly, including all the cables, network cards, switches/routers etc.. between this node and listed node. Correct any problems discovered.

CLSD-01611: node string (number) at 75% heartbeat fatal, eviction in number.number seconds: Cause: Did not receive heartbeat messages from the node. This could be due to network problems or failure of the listed node.; Action: Check if the private interconnect network used by cluster is functioning properly, including all the cables, network cards, switches/routers etc.. between this node and listed node. Correct any problems discovered.

CLSD-01612: node string (number) at 50% heartbeat fatal, eviction in number.number seconds: Cause: Did not receive heartbeat messages from the node. This could be due to to network problems or failure of listed node.; Action: Check if the private interconnect network used by cluster is functioning properly, including all the cables, network cards, switches/routers etc.. between this node and listed node. Correct any problems discovered.

CLSD-01613: voting device hang at 90% fatal, termination in number ms, disk (number/string): Cause: Voting device I/O has not completed for a long time. This could be due some error with the device voting file is on or in some element in the path of the I/O to the device.; Action: Verify if the device is working properly including all the I/O paths. Voting file listed will be considered inactive in the number of secs specified. Failure of a majority of devices would result in node reboot.

CLSD-01614: voting device hang at 75% fatal, termination in number ms, disk (number/string): Cause: Voting device I/O has not completed for a long time. This could be due some error with the device voting file is on or in some element in the path of the I/O to the device.; Action: Verify if the device is working properly including all the I/O paths. Voting file listed will be considered inactive in the number of secs specified. Failure of a majority of devices would result in node reboot.

CLSD-01615: voting device hang at 50% fatal, termination in number ms, disk (number/string): Cause: Voting device I/O has not completed for a long time. This could be due some error with the device voting file is on or in some element in the path of the I/O to the device.; Action: Verify if the device is working properly including all the I/O paths. Voting file listed will be considered inactive in the number of secs specified. Failure of a majority of devices would result in node reboot.

CLSD-02001: memory allocation error when initiating the connection: Cause: failed to allocate memory for the connection with the target process; Action: None

CLSD-02002: connection by user string to string refused: Cause: User command cannot connect to the target process.; Action: The user may not have sufficient privilege to connect.

CLSD-02003: error number encountered when connecting to string: Cause: Connection to the target process failed.; Action: Examine whether the connection is made properly. Retry again at a later time if necessary.

CLSD-02004: error number encountered when sending messages to string: Cause: User command cannot communicate with the target process properly.; Action: Retry again at a later time.

CLSD-02005: timed out when waiting for response from number: Cause: the target process does not return acknowledgement in time.; Action: Retry again at a later time.

CLSD-02006: failed to get response from number: Cause: the target process failed to return acknowledgement.; Action: Retry again at a later time.

CLSD-02007: invalid component key name <string> used: Cause: the given component key name could not be recognized.; Action: re-run the command with a valid component key name.

CLSD-02008: invalid message type <number> used: Cause: an unrecognized message type was sent.; Action: Retry with a valid command again.

CLSD-02009: unable to get authentication for user string: Cause: current user was not authenticated for connection.; Action: Log in as another user and try again.