Skip Headers
Oracle® Clusterware Administration and Deployment Guide
11g Release 1 (11.1)

B28255-07
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

H Oracle Clusterware Alert Messages

This appendix describes the Oracle Clusterware messages that are returned in the Oracle Clusterware alert log.

See Also:

Oracle Database Platform Guide for Microsoft Windows for Windows messages and for all other messages search online at

http://tahiti.oracle.com

CRS--0600: [%s] Error [%s]. Details in %s.
Cause: None
Action: None
CRS-1001 The OCR was formatted using version %d.
Cause: Successfully formatted the OCR location(s).
Action: None
CRS-1002 The OCR was restored from %s.
Cause: The OCR was successfully restored from a backup file as requested by the user.
Action: None
CRS-1003 The OCR format was downgraded to version %d.
Cause: The OCR was successfully downgraded to an earlier block format as requested by the user.
Action: None
CRS-1004 The OCR was imported from %s.
Cause: Successfully imported the OCR contents from a file as requested by the user.
Action: None
CRS-1005 The OCR upgrade was completed. Version has changed from %d to %d. Details in %s.
Cause: The OCR was successfully upgraded to a newer block format.
Action: None
CRS-1006 The OCR location %s is inaccessible. Details in %s.
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.
CRS-1007 The OCR/OCR mirror location was replaced by %s.
Cause: The OCR location was successfully replaced as requested by the user.
Action: None
CRS-1008 Node %s is not responding to OCR requests. Details in %s.
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 Support.
CRS-1009 The OCR configuration is invalid. Details in %s.
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.
CRS-1010 The OCR mirror location %s was removed.
Cause: The OCR location was successfully removed as requested by the user.
Action: None
CRS-1011 OCR cannot determine that the OCR content contains the latest updates. Details in %s.
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 Support Services.

CRS-1012 The OCR service started on node %s.
Cause: The OCR was successfully started.
Action: None
CRS-1013 The OCR at %s was successfully formatted using version %d. Ignore earlier CRS-1006 messages if any.
Cause: Successfully formatted the OCR location(s).
Action: Ignore earlier CRS-1006 messages if any.
CRS-1201 CRSD started on node %s.
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
CRS-1202 CRSD aborted on node %s. Error [%s]. Details in %s.
Cause: Fatal Internal Error. Check the CRSD log file to determine the cause.
Action: Determine whether the CRSD gets auto-started.
CRS-1203 Failover failed for the CRS resource %s. Details in %s.
Cause: Failover failed due to an internal error. Examine the contents of the CRSD log file to determine the cause.
Action: None
CRS-1204 Recovering CRS resources for node %s.
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.
CRS-1205 Auto-start failed for the CRS resource %s. Details in %s.
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.
CRS-1206 Resource %s went into an UNKNOWN state. Force stop the resource using the crs_stop -f command and restart %s.
Cause: Resource went into an UNKNOWN state because the check or the stop action on the resource failed.
Action: Force stop the resource using the crs_stop -f command and restart the resource
CRS-1207 There are no more restart attempts left for resource %s. 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 resource manually.
CRS-1401 EVMD started on node %s.
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.
CRS-1402 EVMD aborted on node %s. Error [%s]. Details in %s.
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.
CRS-1601 CSSD Reconfiguration complete. Active nodes are %s.
Cause: A node joined or left the cluster
Action: None
CRS-1602 CSSD aborted on node %s. Error [%s]. Details in %s.
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
CRS-1603 CSSD on node %s shutdown by user.
Cause: The CSS daemon on the listed node was terminated by a user
Action: None
CRS-1604 CSSD voting file is offline: %s. Details in %s.
Cause: The listed voting file became unusable on the local node
Action: Verify that the file system containing the listed voting file is available on the local node
CRS-1605 CSSD voting file is online: %s. Details in %s.
Cause: The CSS daemon has detected a valid configured voting file
Action: None
CRS-1606 CSSD Insufficient voting files available [%s of %s]. Details in %s.
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
CRS-1607 CSSD evicting node %s. Details in %s.
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
CRS-1608 CSSD Evicted by node %s. Details in %s.
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
CRS-1609 CSSD detected a network split. Details in %s.
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 all nodes

2. Contact Oracle Support

CRS-1610 node %s (%d) at 90%% heartbeat fatal, eviction in %d.%03d 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 and so on between this node and listed node. Correct any problems discovered.
CRS-1611 node %s (%d) at 75%% heartbeat fatal, eviction in %d.%03d 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 and so on between this node and listed node. Correct any problems discovered.
CRS-1612 node %s (%d) at 50%% heartbeat fatal, eviction in %d.%03d seconds
Cause: Did not receive heartbeat messages from the node. This could be due 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 and so on between this node and listed node. Correct any problems discovered.
CRS-1613 voting device hang at 90%% fatal, termination in %u ms, disk (%d/%s)
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 seconds specified. Failure of a majority of devices would result in node reboot.
CRS-1614 voting device hang at 75%% fatal, termination in %u ms, disk (%d/%s)
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 seconds specified. Failure of a majority of devices would result in node reboot.
CRS-1615 voting device hang at 50%% fatal, termination in %u ms, disk (%d/%s)
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 seconds specified. Failure of a majority of devices would result in node reboot.
CRS-1801 Cluster %s configured with nodes %s.
Cause: None
Action: None
CRS-1802 Node %s added to cluster.
Cause: None
Action: None
CRS-1803 Node %s deleted from cluster.
Cause: None
Action: None
CRS-1804 Node %s upgraded to version %s.
Cause: None
Action: None
CRS-1901 CRS service setting (%s) is changed from [%s] to [%s].
Cause: None
Action: None
CRS-2001 memory allocation error when initiating the connection failed to allocate memory for the connection with the target process
Cause: Failed to allocate memory for the connection with the target process.
Action: None.
CRS-2002 connection by user %s to %s refused
Cause: User command cannot connect to the target process.
Action: The user may not have sufficient privilege to connect.
CRS-2003 error %d encountered when connecting to %s
Cause: Connection to the target process failed.
Action: Examine whether the connection is made properly. Retry again at a later time if necessary.
CRS-2004 error %d encountered when sending messages to %s
Cause: User command cannot communicate with the target process properly.
Action: Retry again at a later time.
CRS-2005 timed out when waiting for response from %d
Cause: The target process does not return acknowledgment in time.
Action: Retry again at a later time.
CRS-2006 failed to get response from %d
Cause: The target process failed to return acknowledgement.
Action: Retry again at a later time.
CRS-2007 invalid component key name <%s> used
Cause: The given component key name could not be recognized.
Action: re-run the command with a valid component key name.
CRS-2008 invalid message type <%d> used
Cause: An unrecognized message type was sent.
Action: Retry with a valid command again.
CRS-2009 unable to get authentication for user %s
Cause: Current user was not authenticated for connection.
Action: Log in as another user and try again.