CLSMDNS-00000: no error
Cause: A command completely successfully.
Action: No action is needed.
CLSMDNS-00001: GIPC endpoint creation failed.
Cause: An attempt to create a GIPC endpoint for use multicast operations failed.
Action: Examine the accompanying error (if any) and the log file for details as to
why the operation failed.
CLSMDNS-00002: bind failed.
Cause: An attempt to bind an address to a GIPC endpoint failed.
Action: Examine the accompanying error (if any) and the log file for details as to
why the operation failed.
CLSMDNS-00003: address creation failed.
Cause: An attempt to create a GIPC address failed.
Action: Examine the accompanying error (if any) and the log file for details as to
why the operation failed.
CLSMDNS-00004: attribute setting failed.
Cause: An attempt to set an attribute on a GIPC endpoint or address failed.
Action: Examine the accompanying error (if any) and the log file for details as to
why the operation failed.
CLSMDNS-00005: interface registration failed.
Cause: The registration of an interface with mDNS failed.
Action: Examine the accompanying error (if any) and the log file for details as to
why the operation failed.
CLSMDNS-00006: failed to get name server list.
Cause: An attempt to get the list of available name servers failed.
Action: Examine the accompanying error (if any) and the log file for details as to
why the operation failed.
CLSMDNS-00007: mDNS initialization failed.
Cause: The initialization of the mDNS subsystem failed.
Action: Examine the accompanying error (if any) and the log file for details as to
why the operation failed.
58-2 Oracle Database Error Messages
CLSMDNS-00008: start of host query failed.
Cause: The query for hosts from mDNS failed to start.
Action: Examine the accompanying error (if any) and the log file for details as to
why the operation failed.
CLSMDNS-00009: stop of host query failed.
Cause: Termination of the query for hosts from mDNS failed.
Action: Examine the accompanying error (if any) and the log file for details as to
why the operation failed.
CLSMDNS-00010: Initialization of name server name retrieval failed.
Cause: The initialization of the retrieval of the names of the name servers used by
multicast DNS failed.
Action: Examine the accompanying messages(s) that detail the platform error(s)
for details about the exception.
CLSMDNS-00011: retrieval of name server name failed.
Cause: The retrieval of the name of a name server to be used by multicast DNS
failed.
Action: Examine the accompanying messages(s) that detail the platform error(s)
for details about the exception.
CLSMDNS-00012: no name servers found.
Cause: No name servers were found that could be used by multicast DNS.
Action: Check the system configuration and ensure that or more DNS name
servers are configured, operating and accessible.
CLSMDNS-00013: Send of response to DNS server failed.
Cause: An attempt to send a response to a query from the DNS server failed.
Action: Examine accompanying exceptions for details about the exact error.
CLSMDNS-00015: invalid record type: number
Cause: The DNS server sent a record whose type is unknown.
Action: This is a warning message which can be ignored because the error should
occur very infrequently. If the error occurs frequently, Oracle Customer Support
should be contacted.
CLSMDNS-02000: unknown error.
Cause: An unknown error occurred. This error can occur when the multicast DNS
server is not running.
Action: If the multicast server is not running, start it and try the operation again.
If it is running, this is an internal error and Oracle Customer Support should be
contacted with details about how and when the error occurred.
CLSMDNS-02001: no such name exists.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
CLSMDNS-02002: memory allocation failure.
Cause: The allocation of process memory failed.
CLSMDNS-00000 to CLSMDNS-02255 58-3
Action: If memory is low on the system, terminate other processes and/or threads
and try the operation again. Otherwise, this is an internal error and Oracle
Customer Support should be contacted.
CLSMDNS-02003: invalid parameter.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
CLSMDNS-02004: invalid reference.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
CLSMDNS-02005: invalid state.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
CLSMDNS-02006: invalid flags.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
CLSMDNS-02007: operation is unsupported.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
CLSMDNS-02008: uninitialized.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
CLSMDNS-02009: no cache.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
CLSMDNS-02010: record or service is already registered.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
CLSMDNS-02011: name conflict found.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
CLSMDNS-02012: Invalid.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
CLSMDNS-02013: Firewall.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
CLSMDNS-02014: Incompatible.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
58-4 Oracle Database Error Messages
CLSMDNS-02015: invalid interface.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
CLSMDNS-02016: Refused.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
CLSMDNS-02017: no such record.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
CLSMDNS-02018: no authentication.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
CLSMDNS-02019: no such key.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
CLSMDNS-02020: error occurred while passing through NAT.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
CLSMDNS-02021: double NAT encountered.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
CLSMDNS-02022: invalid time.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
CLSMDNS-02023: invalid signature.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
CLSMDNS-02024: invalid key.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
CLSMDNS-02025: transient error.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
CLSMDNS-02250: connection pending.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
CLSMDNS-02251: connection failed.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
CLSMDNS-00000 to CLSMDNS-02255 58-5
CLSMDNS-02252: connection established.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
CLSMDNS-02253: more memory needed for cache.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
CLSMDNS-02254: configuration changed.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
CLSMDNS-02255: memory free needed.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
58-6 Oracle Database Error Messages
59
CLSR-00001 to CLSR-06507 59-1
CLSR-00001 to CLSR-06507 9 5
CLSR-00001: Oracle error number encountered
Cause: Oracle-related error is encountered.
Action: Check alert log and trace file for more detail.
CLSR-00002: Oracle error encountered while executing string
Cause: Oracle-related error is encountered while executing a request.
Action: Check alert log for more detail.
CLSR-00003: ORACLE_HOME environment variable not set
Cause: ORACLE_HOME environment variable is not set.
Action: Make sure that the ORACLE_HOME environment variable has been
properly set and exported.
CLSR-00004: Error encountered at string, category=number, operation=string, OS
error=number
Cause: Operating system error occurred.
Action: Check for the error message for more detail.
CLSR-00005: Error encountered during memory allocation
Cause: System memory is insufficient.
Action: Check the availability of memory in the system before retrying.
CLSR-00006: Error encountered when writing file string
Cause: Error when writing file.
Action: Check the permission of the file and the existence of its path.
CLSR-00007: Error encountered when reading file string
Cause: Error when reading file.
Action: Check the permission and existence of the file.
CLSR-00501: Error number encountered when connecting to EVM daemon
Cause: Error encountered when connecting to EVM daemon.
Action: Check status of EVM daemon and log file for detail.
CLSR-00502: Error number encountered when subscribing an EVM event
Cause: Error encountered when subscribing an EVM event.
Action: Contact customer support.
CLSR-00503: Error number encountered when creating an EVM event
59-2 Oracle Database Error Messages
Cause: Error encountered when creating an EVM event.
Action: Contact customer support.
CLSR-00504: Error number encountered when posting an EVM event
Cause: Error encountered when posting an EVM event.
Action: Contact customer support.
CLSR-00505: Empty event type is specified
Cause: Empty event type is specified.
Action: Try again with a valid event type.
CLSR-00506: Unmatched resource name prefix string is specified
Cause: Specified resource name prefix does not match as required.
Action: Try again with a valid resource name prefix.
CLSR-00507: The length of the facility name string exceeds the limit (number)
Cause: The given facility name is too long.
Action: Try again with a short facility name.
CLSR-00508: Invalid message number number
Cause: An incorrect message number is specified.
Action: Try again with a correct message number.
CLSR-00509: Unable to initialize NLS
Cause: Failed to initialize callback structure for NLS.
Action: Contact customer support.
CLSR-00510: Unable to load NLS data
Cause: Failed to initialize NLS data loading.
Action: Not action required as default data loading will be used.
CLSR-00511: Error number encountered when handling incoming EVM message
Cause: Error encountered when handling incoming EVM message.
Action: Check log file for detail.
CLSR-00512: Invalid CAA trigger event type [string]
Cause: Invalid CAA trigger event type is specified.
Action: Try again with a valid type.
CLSR-00513: Message file is not found
Cause: The requested OCI message file is not found.
Action: Check if the message file is properly installed.
CLSR-00514: Unable to locate PMON [pid=string]
Cause: Cannot find PMON with this pid.
Action: Check the existence of PMON.
CLSR-00515: A service member is already running on this node
Cause: There is a service member of the same service running on this node.
Action: No action required as the service member will try to start on another
node.
CLSR-00001 to CLSR-06507 59-3
CLSR-00516: No service provider found at this node
Cause: No suitable service provider is found on this node.
Action: No action required as the service member will try to start on another
node.
CLSR-00517: Failed to register a service name
Cause: The requested service name cannot be registered.
Action: Check log file for detail.
CLSR-00518: Failed to register a preconnect service name
Cause: The requested preconnect service name cannot be registered.
Action: Check log file for detail.
CLSR-00519: No instance found
Cause: No instance is found running for the database resource.
Action: No action required as the database resource will fail itself.
CLSR-00520: No service member found
Cause: No service member is found running for the composite service resource.
Action: No action required as the composite service resource will fail itself.
CLSR-00521: Event string is rejected by EVM daemon
Cause: No template has been registered for the event or caller is not authorized to
post the event.
Action: Check if there is a template registered for this event and the authority of
posting this event.
CLSR-00522: Resource string is not registered
Cause: CRS resource is not registered.
Action: Register the CRS resource.
CLSR-00523: Resource string is not enabled
Cause: CRS resource is not enabled.
Action: Enable the CRS resource.
CLSR-00524: Resource string is stopping, resource string cannot start
Cause: Resource cannot start because its composite resource is stopping.
Action: Retry to start the resource when its composite resource is not stopping.
CLSR-00525: prsr initialization failed
Cause: See the related error message.
Action: Run crs_stat to make sure CSS and OCR working properly.
CLSR-00526: Failed to retrieve database configuration in OCR
Cause: See the related error message.
Action: Run crs_stat to make sure CSS and OCR working properly and database
configuration in ocr is initialized.
CLSR-00527: OCR operation failed
Cause: See related error messages about the OCR operation.
Action: Fix the related error. Then try again.
59-4 Oracle Database Error Messages
CLSR-00528: RACGONS: host and port number already configured in OCR
Cause: host and port number already configured in OCR.
Action: None
CLSR-00529: RACGONS: host and port number to be removed does not exist
Cause: host and port number to be removed is not configured in OCR.
Action: None
CLSR-00530: Can not get user name
Cause: Error caused by OSD layer.
Action: Contact Oracle support.
CLSR-00531: Can not get primary group name
Cause: There is no primary group for this OS.
Action: Not faital. None.
CLSR-01001: Unsupported open mode number is specified
Cause: Unsupported open mode is specified for mounting database.
Action: Retry again with a valid open mode.
CLSR-01002: Unable to process instance startup
Cause: ORACLE_HOME environment variable not set.
Action: Make sure that the ORACLE_HOME environment variable has been
properly set and exported.
CLSR-01003: Error number encountered during mounting database
Cause: Unexpected error occurs when mounting database.
Action: Check current status of database before retrying.
CLSR-01004: Failed to mount database
Cause: Database cannot be mounted by an instance.
Action: Check alert log for error detail.
CLSR-01005: Error number encountered during altering database open mode
Cause: Unexpected error occurs when altering database open mode.
Action: Check current database status.
CLSR-01006: Unable to process instance shutdown
Cause: ORACLE_HOME environment variable not set.
Action: Make sure that the ORACLE_HOME environment variable has been
properly set and exported.
CLSR-01007: Connection to database was not established
Cause: Connection to database is failed to establish.
Action: Make sure connection and environment are properly set up.
CLSR-01008: Error number encountered during querying for PMON status
Cause: Unexpected error encountered when querying v$process for PMON.
Action: Check alert log and connection to database.
CLSR-01009: database management module failed to start
CLSR-00001 to CLSR-06507 59-5
Cause: Error encountered during initializing database management module.
Action: Check previous error message for detail.
CLSR-01010: Unable to record PMON pid to string
Cause: Failed to write os pid for PMON to file.
Action: Check file system for disk space and access privilege.
CLSR-01011: Invalid instance startup mode [string] is specified
Cause: Invalid startup mode is specified.
Action: Retry again with a valid startup mode.
CLSR-01012: Invalid instance stop mode [string] is specified
Cause: Invalid stop mode is specified.
Action: Retry again with a vaild stop mode.
CLSR-06500: Invalid input arguments
Cause: Invalid input arguments are specified.
Action: Retry again with a valid argument.
CLSR-06501: Exceeds maximum number of arguments
Cause: Too many input arguments are specified.
Action: Retry again with correct number of arguments.
CLSR-06502: Failed to connect to database 'string' as user 'string'
Cause: Failed to connect to database.
Action: Check database and log file for details.
CLSR-06503: Service name already registered
Cause: Requested service name has been registered by another service.
Action: Choose another service name and retry registration again.
CLSR-06504: Service name not in SERVICE_NAMES
Cause: Requested service name is not registered.
Action: Make sure the correct service name is specified in the request.
CLSR-06505: SERVICE_NAMES found null and fixed
Cause: SERVICE_NAMES parameter becomes null after the delete operation.
Action: Not action required as SERVICE_NAMES is set to default value.
CLSR-06506: Error number encountered when executing string
Cause: Error occurred when executing the SQL statement.
Action: Check alert log for more detail.
CLSR-06507: Cannot add to SERVICE_NAMES, SERVICE_NAMES will be too long
Cause: Adding the service name will exceed the limit of SERVICE_NAMES.
Action: Change the configuration to avoid SERVICE_NAMES becomes too long.
59-6 Oracle Database Error Messages
60
CLSS-00001 to CLSS-03202 60-1
CLSS-00001 to CLSS-03202 0 6
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]
60-2 Oracle Database Error Messages
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-00001 to CLSS-03202 60-3
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.
60-4 Oracle Database Error Messages
61
CLST-01101 to CLST-03203 61-1
CLST-01101 to CLST-03203 1 6
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.
Action: Verify that the node name refers to IP addresses on the private
interconnect. Using a non-private network can cause performance and stability
issues.
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.
Action: If the node name is not equal to the host name, the host name must be
supplied to clscfg. Failure to do so will cause the Cluster Ready Services daemons
not to function.
CLST-01103: existing configuration version (string) detected
Cause: An existing configuration was detected.
Action: Informational message only. No action is required. clscfg will not modify
the existing configuration unless explicitly requested with the -force flag.
CLST-01104: successfully determined required configuration for all components
Cause: clscfg was able to determine the proper configuration requirements.
Action: Informational message only. No action is required. clscfg will attempt to
write the configuration next.
CLST-01105: An existing configuration was detected. It was not overwritten.
Cause: An existing configuration was detected, and clscfg chose not to overwrite
it.
Action: This message may be ignored if it is seen as part of starting any node
other than the first one. The -force option can be used to override this decision, but
if it is used when there are active cluster members, failure CLSS-0101 and data
integrity issues are likely.
CLST-01301: successfully deleted string of string configuration values
Cause: clscfg completed a portion of the delete operation.
Action: Informational message only. No action is required. If some of the values
were not deleted, another error message should be visible with more information.
CLST-01302: successfully deleted string of string configuration keys
Cause: clscfg completed a portion of the delete operation.
61-2 Oracle Database Error Messages
Action: Informational message only. No action is required. If some of the keys
were not deleted, another error message should be visible with more information.
CLST-01303: successfully rolled back delete operation
Cause: The delete node operation failed, but the configuration was properly
restored to its original state.
Action: Informational message only. No action is required.
CLST-01304: node deletion successful
Cause: The delete node operation succeeded.
Action: Informational message only. No action is required.
CLST-01401: formatting voting device: string
Cause: clscfg started formatting the voting device.
Action: Informational message only. No action is required.
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.
Action: Informational message only. No action is required. This might be an
indication of corrupted configuration, or a previous delete operation that did not
complete.
CLST-01901: configuring TCP ports string, string, string, and string
Cause: The specified ports were configured for use with the Cluster Ready
Services Daemons.
Action: Informational message only. No action is required. To change the ports
used, specify 4 alternate ports with "-t". Example: -t 1001,1002,1003,1004
CLST-01902: configuring node: node number string, node name string
Cause: This node configuration was requested.
Action: Informational message only. No action is required. To alter the list of
nodes re-run the install and specify a different set of nodes, or make use of the add
and delete node install options after the current install is complete.
CLST-01903: configuring node: host name string, private interconnect name string
Cause: This node configuration was requested.
Action: Informational message only. No action is required. To alter the list of
nodes re-run the install and specify a different set of nodes, or make use of the add
and delete node install options after the current install is complete.
CLST-01904: creating configuration with user (string) and group (string)
Cause: The configuration was set up with the specified user and group.
Action: Informational message only. No action is required. Some configuration
information will only be accessible to members of the specified group. Note: On
Windows platforms the group may be blank.
CLST-01999: Warning: -force specified. Overwriting existing configuration.
Cause: The -force parameter was supplied.
Action: The -force parameter will cause clscfg to overwrite the existing
configuration. If used while a Cluster Ready Services cluster is actively running,
this can cause instability and data integrity exposures.
CLST-01101 to CLST-03203 61-3
CLST-02101: Too many nodes were specified. limit is string
Cause: Too many nodes were specified on command line.
Action: Retry the operation with a smaller number of simultaneous changes.
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.
Action: Retry the operation with a smaller node number.
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.
Action: Correct the arguments to the -t flag and rerun the operation.
CLST-02104: TCP port string is out of bounds.
Cause: The TCP port specified was not a valid port number.
Action: Specify an another port. Usually TCP ports need to be between 1001 and
65,535.
CLST-02105: missing required parameter -l with language ID information
Cause: The -l parameter was required for the requested operation.
Action: Supply the -l parameter with the proper language ID.
CLST-02106: missing required parameter -o with path to ORA_CRS_HOME
Cause: The -o parameter was required for the requested operation.
Action: Supply the -o parameter with the proper path.
CLST-02107: failure configuring component string
Cause: The Oracle Cluster Repository configuration for the specified component
was unsuccessful.
Action: Look for other error information and contact Oracle support.
CLST-02108: missing required parameter -q with path to the voting device
Cause: The -q parameter was required for the requested operation.
Action: Supply the -q parameter with a valid path for the voting device.
CLST-02109: missing required parameter -c with a cluster name
Cause: The -c parameter was required for the requested operation.
Action: Supply the -c parameter with a name for the cluster.
CLST-02110: missing required parameter -nn with the list of nodenames
Cause: The -nn parameter was required for the requested operation.
Action: Supply a list of node names with the format:
nodenameA,nodenumA,nodenameB,nodenumB,...
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.
Action: Choose an alternate node to add to the cluster, or give the new node a
unique name, or delete the previous node, then retry.
61-4 Oracle Database Error Messages
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.
Action: Choose an alternate node to add to the cluster, or give the new node a
unique name, or delete the previous node, then retry.
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.
Action: Choose an alternate node to add to the cluster, or give the new node a
unique name, or delete the previous node, then retry.
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.
Action: Chose an alternate node to add to the cluster, or give the new node a
unique node number, or delete the previous node, then retry.
CLST-02301: failure string validating configuration of node string
Cause: clscfg was unable to validate existing configuration of the specified node.
Action: Validate the integrity of the Cluster Ready Services install on the local
node, or choose another node to delete.
CLST-02302: failure string validating configuration of private interconnect name
string
Cause: clscfg was unable to validate existing configuration of the specified node.
Action: Validate the integrity of the Cluster Ready Services install on the local
node, or choose another node to delete.
CLST-02303: failure string validating configuration of node with host name string
Cause: clscfg was unable to validate existing configuration of the specified node.
Action: Validate the integrity of the Cluster Ready Services install on the local
node, or choose another node to delete.
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.
Action: Specify the correct information describing the node you intend to delete,
then retry.
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.
Action: Specify the correct information describing the node you intend to delete,
then retry.
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-01101 to CLST-03203 61-5
Action: Specify the correct information describing the node you intend to delete,
then retry.
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.
Action: Specify the correct information describing the node you intend to delete,
then retry.
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.
Action: Verify the integrity of the Oracle Cluster Repository, and restore from
backup if necessary. If only one clscfg process was active on the cluster this may be
ignored.
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.
Action: Verify the integrity of the Cluster Ready Services install on the local node,
and retry.
CLST-02310: CSS daemon refused node deletion, status string. attempting rollback
Cause: Cluster Synchronization Services daemon refused the node deletion.
Action: One or more of the designated nodes may still be active. clscfg will now
attempt to roll back the deletion process. The Cluster Ready Services daemons
must be shut down on a node before any attempt to remove them from the
configuration. More information on why the attempt was refused may be available
in the Cluster Synchronization Service logfile.
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.
Action: Shut down the cluster and restore the Oracle Cluster Repository from
backup.
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.
Action: This can be ignored. The safer choice is to restore the Oracle Cluster
Repository from backup, and attempt the delete again. Adding any of the deleted
nodes back to the configuration in the future may fail if this is ignored.
CLST-02401: failure string querying maximum configurable node number
Cause: clscfg was unable to determine the legitimate range of node numbers.
Action: Verify the integrity of the Cluster Ready Services install on the local node.
CLST-02402: failure string querying existing configured node list
Cause: clscfg was unable to retrieve the list of currently configured nodes.
61-6 Oracle Database Error Messages
Action: Verify the integrity of the Cluster Ready Services install on the local node.
CLST-02403: failure string querying the maximum node name size
Cause: clscfg was unable to determine the size of the largest node name.
Action: Verify the integrity of the Cluster Ready Services install on the local node.
CLST-02404: failure string querying the cluster name
Cause: clscfg was unable to determine the existing cluster name.
Action: Verify the integrity of the Cluster Ready Services install on the local node.
CLST-02405: failure formatting voting device (string) at [string] [string] [string]
Cause: clscfg failed to format the voting device.
Action: Verify the path and permissions set on the voting device.
CLST-02501: failure string opening configuration for write operation
Cause: clscfg was attempting to open the current configuration for write access.
Action: Verify the integrity of the Oracle Cluster Repository. Shut down the
cluster and restore OCR from backup if necessary.
CLST-02502: failure string writing new configuration
Cause: clscfg was attempting to write new configuration data.
Action: Verify the integrity of the Oracle Cluster Repository. Shut down the
cluster and restore OCR from backup if necessary.
CLST-02503: failure string opening configuration for delete operation
Cause: clscfg received an error while attempting to delete part of the existing
configuration.
Action: Verify the integrity of the Oracle Cluster Repository. Shut down the
cluster and restore OCR from backup if necessary.
CLST-02504: failure string writing configuration to disk
Cause: clscfg received a failure writing information to the Oracle Cluster
Repository.
Action: Verify the settings for the Oracle Cluster Repository and retry.
CLST-02901: The number of Oracle Cluster Repository keys exceeds limit of string.
Cause: clscfg ran out of internal space for keys during install.
Action: Re-run the install and specify a smaller list of nodes. When that
completes, use the add node option to add the remaining nodes.
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.
Action: Re-run the delete node operation and delete fewer nodes at once.
CLST-02903: unable to allocate string bytes of memory at location: string
Cause: clscfg was unable to allocate enough memory to service the request.
Action: Ensure that the specified amount of memory will be available and retry
the operation.
CLST-02904: failure string in SCLS API at string
Cause: clscfg was unable to query for information about the system setup.
CLST-01101 to CLST-03203 61-7
Action: Contact Oracle support with the additional information printed just after
this message.
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.
Action: Correct the command line and try again.
CLST-02906: Clustername should be between 1 and string letters.
Cause: cluster name supplied with -c argument was the wrong size.
Action: Supply an alternate cluster name of an appropriate length.
CLST-02907: unknown parameter string supplied
Cause: An unknown parameter was passed to clscfg.
Action: Use "clscfg -help" or "clscfg -concepts" for more information.
CLST-02908: unable to determine local hostname
Cause: clscfg was unable to determine the local hostname.
Action: Verify the operating system host name configuration.
CLST-02909: The requested operation requires High Availability privileges.
Cause: The current user did not have High Availability privileges.
Action: Log in as a different user and retry the operation.
CLST-02910: Failure string contacting the CRS daemon.
Cause: clscfg was unable to communicate with the CRS daemon.
Action: The requested operation must be performed from an active cluster node.
Validate the pre-existing installation on the local machine, or perform the
operation from another node.
CLST-02911: failure string contacting the CSS daemon
Cause: clscfg was unable to communicate with the CSS daemon.
Action: The requested operation must be performed from an active cluster node.
Validate the pre-existing installation on the local machine, or perform the
operation from another node.
CLST-02999: Untranslated failure: [string] [string] [string] [string] [string] [string]
Cause: A failure with no translation occurred.
Action: Contact Oracle Customer Support for more information.
CLST-03100: See the documentation for usage information.
Cause: Incorrect or insufficient arguments were passed to crsuser.
Action: Read documentation for instructions on how to use this tool.
CLST-03101: Enter the password for user string.
Cause: crsuser requires the password to register the user.
Action: Enter the requested password.
CLST-03102: Operation successful.
Cause: The operation succeeded.
Action: None
61-8 Oracle Database Error Messages
CLST-03200: internal error: [string] [string] [string] [string] [string]
Cause: A failure with no translation occurred.
Action: Contact Oracle Customer support for more information.
CLST-03201: unexpected argument: string
Cause: crsuser failed to parse the arguments, or an unknown argument was
passed.
Action: Supply the correct arguments and try again.
CLST-03202: Memory allocation failure for string bytes.
Cause: crsuser was unable to allocate memory.
Action: Free up some system memory and try again.
CLST-03203: insufficient privileges for action: string
Cause: The current user did not have sufficient privileges.
Action: Log in as another user and try again.
62
CLSU-00100 to CLSU-00912 62-1
CLSU-00100 to CLSU-00912 2 6
CLSU-00100: operating system function: string failed with error data: string
Cause: A call to an Operating System dependent service or function returned an
error indication. The message includes the name of the function and the returned
error data. The latter varies by platform but typically is numeric; on most
platforms it is the value of C "errno" after the failing call.
Action: This error normally is accompanied by other (higher-level) messages
describing the operation that is affected by the failure. It may also include one or
more of messages 101, 103, and 104 providing additional error details. All of the
messages should be examined to assess the error, which may have a very ordinary
cause and correction, such as an input file failing to open because the supplied
name was misspelled.
CLSU-00101: operating system error message: string
Cause: This message accompanies message 100 above when the Operating System
dependent error data can be converted into a text message. On most Oracle
platforms the message is a text representation of the C "errno" value reported in
message 100.
Action: See message 100.
CLSU-00102: operating system interface detected an error
Cause: This message is issued instead of messages 100-101 when a "logical" error
condition (rather than failure of an Operating System function call) is detected at
an Operating System specific interface. The error condition is further described by
accompanying message(s), including 103 and 104.
Action: This error normally is accompanied by other (higher-level) messages
describing the operation that is affected by the failure. In most cases it will also
include messages 103 and 104, providing additional details about the error. All of
the messages should be examined to assess the error, which may have a very
ordinary cause and correction, such as a missing required environment variable.
CLSU-00103: error location: string
Cause: This message accompanies message 100, 102, or 105 and identifies a
location in Oracle program code that encountered the error.
Action: See message 100, 102, or 105. This information normally is useful only
when reporting the error condition to Oracle as a potential code bug.
CLSU-00104: additional error information: string
Cause: This message accompanies message 100, 102, or 105 and supplies
additional information related to the error condition. A single error may include
multiple lines of additional information.
62-2 Oracle Database Error Messages
Action: See message 100, 102, or 105.
CLSU-00105: operating system interface has reported an internal failure
Cause: This message indicates that an Operating System dependent interface
within Oracle code has detected internal corruption or some other evidence of
internal program failure.
Action: This message may be accompanied by other (higher-level) messages
indicating the product operation that was affected by the failure. It may also be
accompanied by either or both of messages 103 and 104. All situations reporting
this condition should be referred to Oracle Support for resolution.
CLSU-00106: An improper operating system error display was attempted
Cause: During processing of an error condition, an attempt was made to format
or display Operating System dependent error data, but the error data structure
was found to indicate "no error".
Action: This error should be reported to Oracle Support for resolution.
CLSU-00200: **** Error stack contains number records, newest first:
Cause: The collection of errors about to be presented contains this many following
records.
Action: This and the following data should be reported to Oracle Support for
resolution.
CLSU-00201: **** Error stack end ****
Cause: This marks the end of a collection of errors
Action: The preceding data should be reported to Oracle Support for resolution.
CLSU-00210: CLSUUS test msg 0
Cause: A message for testing, should never be seen in the field.
Action: Report to Oracle Support.
CLSU-00211: CLSUUS test msg 1:string
Cause: A message for testing, should never be seen in the field.
Action: Report to Oracle Support.
CLSU-00212: CLSUUS test msg 2:string 2:string
Cause: A message for testing, should never be seen in the field.
Action: Report to Oracle Support.
CLSU-00213: CLSUUS test msg 3:string 2:string 3:string
Cause: A message for testing, should never be seen in the field.
Action: Report to Oracle Support.
CLSU-00214: CLSUUS test msg 4:string 2:string 3:string 4:string
Cause: A message for testing, should never be seen in the field.
Action: Report to Oracle Support.
CLSU-00215: CLSUUS test msg 5:string 2:string 3:string 4:string 5:string
Cause: A message for testing, should never be seen in the field.
Action: Report to Oracle Support.
CLSU-00216: CLSUUS test msg 6:string 2:string 3:string 4:string 5:string 6:string
CLSU-00100 to CLSU-00912 62-3
Cause: A message for testing, should never be seen in the field.
Action: Report to Oracle Support.
CLSU-00217: CLSUUS test msg 7:string 2:string 3:string 4:string 5:string 6:string
7:string
Cause: A message for testing, should never be seen in the field.
Action: Report to Oracle Support.
CLSU-00218: CLSUUS test msg 8:string 2:string 3:string 4:string 5:string 6:string
7:string 8:string
Cause: A message for testing, should never be seen in the field.
Action: Report to Oracle Support.
CLSU-00220: clsem FATAL exception: string
Cause: Something unrecoverable happened in CLSEM.
Action: Report to Oracle Support.
CLSU-00221: ERROR printed by clsecho: string
Cause: An error printed by clsecho
Action: Report to Oracle Support.
CLSU-00222: WARNING printed by clsecho: string
Cause: A warning
Action: Note the text
CLSU-00223: Info printed by clsecho: string
Cause: Information printed by clsecho
Action: Report to Oracle Support.
CLSU-00910: Named exception string string string string
Cause: Program raised an exception that does not have its own message
Action: Report to Oracle Support.
CLSU-00911: Signal string received
Cause: Program received on OS signal reported as an exception
Action: Report to Oracle Support
CLSU-00912: Operating system error: string
Cause: One or more operating system-specific errors were noticed
Action: Examine the message(s) for more information.
62-4 Oracle Database Error Messages
63
CLSW-00001 to CLSW-01000 63-1
CLSW-00001 to CLSW-01000 3 6
CLSW-00001: Cluster Wallet operation failed
Cause: This is generic internal error for Cluster Wallet.
Action: Contact Oracle Customer Support.
CLSW-00002: Out of heap memory.
Cause: The program ran out of heap memory.
Action: Retry the operation when more memory is available.
CLSW-00003: Error in the cluster registry (OCR) layer. [number] [string]
Cause: An error occurred in the cluster registry layer while performing a cluster
wallet operation.
Action: Ensure correct operation of cluster registry by inspecting ocr error (oerr
proc <ocrerror>), by using ocrcheck and ocrdump, and retry the operation.
CLSW-00004: Error in the network security layer. [number] [string]
Cause: An error occurred in the network security layer while performing a cluster
wallet operation.
Action: Inspect the network security error (oerr ora <nzerr>), and take corrective
action to ensure correct operation.
CLSW-00005: Cannot perform cluster wallet operation because one of the
parameters is NULL.
Cause: Program tried a cluster wallet operation using a NULL parameter.
Action: Check the parameters, and retry the operation.
CLSW-00006: Cannot perform cluster wallet operation because the context is
invalid.
Cause: The cluster wallet context passed was invalid.
Action: Intialize the cluster wallet and retry the operation.
CLSW-00007: Cannot perform cluster wallet operation because one of the
parameters is invalid. [number] [string]
Cause: Program tried a cluster wallet operation using an invalid parameter.
Action: Check the parameters, and retry the operation.
CLSW-00008: The cluster wallet to be created already exists.
Cause: The program tried to create a cluster wallet that already exists.
Action: Retry the operation after unsetting the CLSW_FLAGS_WALLET_CREATE
63-2 Oracle Database Error Messages
CLSW-00009: The cluster wallet to be operated on does not exist.
Cause: Program tried to access a cluster wallet which does not exist.
Action: Check to see if the cluster wallet exists and try the operation
CLSW-00010: Error in the NLS services.
Cause: An error occurred in the NLS services while performing a cluster wallet
operation.
Action: Check to see if the message file exists in $ORACLE_
HOME/has/mesg/clsw*.msb
CLSW-00011: Cannot perform cluster wallet operation because data stored in the
registry is invalid.
Cause: The data stored in the registry cannot be converted to a wallet.
Action: Delete the registry key associated with the wallet and recreate the wallet.
CLSW-00012: User is not authorized to perform the cluster wallet operation.
[number] [string]
Cause: Program tried an operation on a cluster wallet for which it does not have
permission.
Action: Check to see if program is run as the correct user.
CLSW-00013: Error in the clusterware operating system (SCLS) services. [string]
Cause: An error occurred in the SCLS services while performing a cluster wallet
operation.
Action: Check to see if NIS/LDAP on Unix and Active Directory Service on
Windows has been correctly configured.
CLSW-00014: Wallet type 'string' is not supported on this operating system.
Cause: The program tried a cluster wallet operation using a wallet type that is not
supported on current operating system.
Action: This is an internal error. Contact oracle support services.
CLSW-00015: Alias 'string' already exists in wallet type 'string'.
Cause: A request to add the specified alias to the wallet failed because the alias
already existed in the wallet.
Action: Add an alias that does not already exist in the wallet. The password for an
alias that already exists can be modified using the command 'crsctl modify wallet'.
CLSW-00016: Alias 'string' was not found in wallet type 'string'.
Cause: A request to modify the specified alias in the wallet failed because the alias
did not exist in the wallet.
Action: Ensure that the alias exists in the wallet type specified. A new alias can be
added to a wallet type using the command 'crsctl add wallet'.
CLSW-01000: Enter Password:
Cause: This is a prompt to user to enter password.
Action: Enter password.
64
CRS-00001 to CRS-29006 64-1
CRS-00001 to CRS-29006 4 6
CRS-00001: Message ID string-number not found.
Cause: The messsage for the given message id is not found in any language.
Action: Make sure the product is setup correctly on the system.
CRS-00002: string:Internal list corruption. trace file: "string"
Cause: An internal error was detected during trace file flush processing.
Action: Contact Oracle Support Services.
CRS-00003: An error occurred while attempting to open file "string". Additional
diagnostics: string
Cause: An error was encountered while attempting to open the specified file.
Action: Examine the additional diagnostics, if available, and attempt to correct
any file system environmental problems if indicated. Otherwise, contact Oracle
Support Services.
CRS-00004: logging terminated for the process. log file: "string"
Cause: One or more file system errors were encountered which caused logging to
be terminated for this process.
Action: Examine preceding Alert log messages for details on the error or errors
that occurred. Restart the process to reenable logging.
CRS-00005: file "string" deleted after close failure
Cause: This message is informational. An attempt to close the specified file failed.
The contents of the file after a close error are undefined. The file has been
successfully deleted. Log data are lost.
Action: None
CRS-00006: file rotation processing continues for file: "string"
Cause: This message is informational and indicates only that a preceding error
was not sufficiently severe to terminate file rotation which might otherwise be the
case.
Action: None
CRS-00007: failed to open new log file "string\
Cause: The file system encountered an error while attempting to open the
specified file during log file rotation. Log data are lost.
Action: Review the preceding Alert log message CRS-0011 and attempt to resolve
any file system environmental problems indicated. Otherwise, contact Oracle
Support Services.
64-2 Oracle Database Error Messages
CRS-00008: opened new file "string" after close failure
Cause: This message is informational. Log data are lost.
Action: None
CRS-00009: file "string" reopened
Cause: An error was encountered during rotation processing so that file rotation
could not proceed. The original file, which had been closed, was successfully
reopened.
Action: Review Alert log messages that precede this message that identify the file
system error or errors encountered. If the additional diagnostic data in a preceding
alert log message indicate a file system environmental problem, attempt to correct
it. Otherwise contact Oracle Support Services.
CRS-00011: An error occurred while attempting to close file "string" during file
rotation. Additional diagnostics: string
Cause: An error was encountered when attempting to close the specified file.
Action: Examine the additional diagnostics, if any, and attempt to correct any file
system environmental problems if indicated. Otherwise, contact Oracle Support
Services.
CRS-00012: An error occurred while attempting to rename file "string" to "string"
during file rotation. Additional diagnostics: string
Cause: An error was encountered when attempting to rename the source file to
the destination file.
Action: Examine the additional diagnostics, if any, and attempt to correct any file
system environmental problems if indicated. Otherwise, contact Oracle Support
Services.
CRS-00013: An error occurred while attempting to check for the existence of file
"string" during file rotation. Additional diagnostics: string
Cause: An error was encountered while attempting to determine if the specified
file existed.
Action: Examine the additional diagnostics, if any, and attempt to correct any file
system environmental problems if indicated. Otherwise, contact Oracle Support
Services.
CRS-00014: An error occurred while attempting to delete file "string" during file
rotation. Additional diagnostics: string
Cause: An error was encountered while attempting to delete the specified file.
Action: Examine the additional diagnostics, if any, and attempt to correct any file
system environmental problems if indicated. Otherwise, contact Oracle Support
Services.
CRS-00015: An error occurred while attempting to flush file "string" during file
rotation. Additional diagnostics: string
Cause: An error was encountered while an attempting to flush the specified file.
Action: Examine the additional diagnostics, if any, and attempt to correct any file
system environmental problems if indicated. Otherwise, contact Oracle Support
Services.
CRS-00016: An error occurred while attempting to free the file name object for file
"string" during file rotation. Additional diagnostics: string
CRS-00001 to CRS-29006 64-3
Cause: An error was encountered while attempting to free the file name object for
the specified file.
Action: Examine the additional diagnostics, if any, and attempt to correct any file
system environmental problems if indicated. Otherwise, contact Oracle Support
Services.
CRS-00017: An error occurred while attempting to create a file name object for file
"string" during file rotation. Additional diagnostics: string
Cause: An error was encountered while attempting to create a file name object for
the specified file.
Action: Examine the additional diagnostics, if any, and attempt to correct any file
system environmental problems if indicated. Otherwise, contact Oracle Support
Services.
CRS-00018: An error occurred while attempting to reopen file "string" during file
rotation. Additional diagnostics: string
Cause: An error was encountered while attempting to reopen the specified file.
Action: Examine the additional diagnostics, if any, and attempt to correct any file
system environmental problems if indicated. Otherwise, contact Oracle Support
Services.
CRS-00019: Log file rotation terminated. log file: "string"
Cause: One or more file system errors were encountered which caused log file
rotation to be terminated for the process. Although log file rotation has been
terminated, logging continues.
Action: Review Alert log messages that precede this alert log message that
identify the file system error or errors encountered. If the additional diagnostic
data in a preceding alert log message indicate a file system environmental
problem, attempt to correct it. Otherwise contact Oracle Support Services. To
reenable file rotation the process must be restarted.
CRS-00020: An error occurred while attempting to create a file name object for file
"string" during file open processing. Additional diagnostics: string
Cause: An error was encountered while attempting to create a file name object for
the specified file.
Action: Examine the additional diagnostics, if any, and attempt to correct any file
system environmental problems if indicated. Otherwise, contact Oracle Support
Services.
CRS-00021: An error occurred while attempting to check for the existence of file
"string" during file open processing. Additional diagnostics: string
Cause: An error was encountered while attempting to determine if the specified
file existed.
Action: Examine the additional diagnostics, if any, and attempt to correct any file
system environmental problems if indicated. Otherwise, contact Oracle Support
Services.
CRS-00022: An error occurred while attempting to change access permissions and
privileges for file "string" during file open processing. Additional diagnostics:
string
Cause: An error was encountered while attempting to change access permissions
and privileges for the specified file.
64-4 Oracle Database Error Messages
Action: Examine the additional diagnostics, if any, and attempt to correct any file
system environmental problems if indicated. Otherwise, contact Oracle Support
Services.
CRS-00023: An error occurred while attempting to create default permissions for
file "string" during file open processing. Additional diagnostics: string
Cause: An error was encountered while attempting to create default file
permissions for the specified file.
Action: Examine the additional diagnostics, if any, and attempt to correct any file
system environmental problems if indicated. Otherwise, contact Oracle Support
Services.
CRS-00024: An error occurred while attempting to create a file name object for file
"string" during file open processing. Additional diagnostics: string
Cause: An error was encountered while attempting to create a file name object for
the specified file.
Action: Examine the additional diagnostics, if any, and attempt to correct any file
system environmental problems if indicated. Otherwise, contact Oracle Support
Services.
CRS-00025: An error occurred while attempting to create a file object for file
"string" during file open processing. Additional diagnostics: string
Cause: An error was encountered while attempting to create a file object for the
specified file.
Action: Examine the additional diagnostics, if any, and attempt to correct any file
system environmental problems if indicated. Otherwise, contact Oracle Support
Services.
CRS-00026: failed to create one or more file name objects to rename "string" to
"string" during file rotation processing
Cause: An error was encountered while attempting to create one of more file
name objects for the specified files.
Action: Contact Oracle Support Services.
CRS-00027: An error occurred while attempting to determine the size of file "string"
during file open processing. Additional diagnostics: string
Cause: An error was encountered while attempting to determine the size of the
specified file.
Action: Examine the additional diagnostics, if any, and attempt to correct any file
system environmental problems if indicated. Otherwise, contact Oracle Support
Services.
CRS-00028: An error occurred while attempting to write the banner for file "string".
Additional diagnostics: string
Cause: An error was encountered while attempting to write the banner record to
the specified file.
Action: Examine the additional diagnostics, if any, and attempt to correct any file
system environmental problems if indicated. Otherwise, contact Oracle Support
Services.
CRS-00029: An error occurred while attempting to flush file "string" after the
banner record was written. Additional diagnostics: string
CRS-00001 to CRS-29006 64-5
Cause: An error was encountered while attempting to flush the specified file after
writing the banner record.
Action: Examine the additional diagnostics, if any, and attempt to correct any file
system environmental problems if indicated. Otherwise, contact Oracle Support
Services.
CRS-00030: An invalid file type was encountered while attempting to perform file
synchronization. Additional diagnostics: string ftype: number
Cause: An invalid file type specification was encountered by file synchronization
services.
Action: Contact Oracle Support Services.
CRS-00031: An error occurred while attempting to flush file "string" during file
synchronization processing. Additional diagnostics: string
Cause: An error was encountered while attempting to flush the specified file
during file synchronization processing.
Action: Examine the additional diagnostics, if any, and attempt to correct any file
system environmental problems if indicated. Otherwise, contact Oracle Support
Services.
CRS-00032: An error occurred while attempting to create a file object for file
"string" during generate-file-name processing. Additional diagnostics: string
Cause: An error was encountered while attempting to create a file object for the
specified file.
Action: Examine the additional diagnostics, if any, and attempt to correct any file
system environmental problems if indicated. Otherwise, contact Oracle Support
Services.
CRS-00033: An error occurred while attempting to create a file object for file
"string" during generate-file-name processing. Additional diagnostics: string
Cause: An error was encountered while attempting to create a file object for the
specified file.
Action: Examine the additional diagnostics, if any, and attempt to correct any file
system environmental problems if indicated. Otherwise, contact Oracle Support
Services.
CRS-00034: An error occurred while attempting to open file "string" during
generate-file-name processing. Additional diagnostics: string
Cause: An error was encountered while attempting to open the specified file.
Action: Examine the additional diagnostics, if any, and attempt to correct any file
system environmental problems if indicated. Otherwise, contact Oracle Support
Services.
CRS-00035: An invalid pointer to an internal control structure was encountered
while attempting to open a log file. Additional diagnostics: string
Cause: An invalid pointer was encountered when attempting to open a file.
Logging is disabled for the process.
Action: Contact Oracle Support Services.
CRS-00036: An error occurred while attempting to open file "string".
Cause: An error was encountered while attempting to open the specified file.
64-6 Oracle Database Error Messages
Action: Review preceding Alert log messages and attempt to resolve any file
system environmental problems indicated. Otherwise, contact Oracle Support
Services
CRS-00037: An error occurred while attempting to write to file "string". Additional
diagnostics: string
Cause: An error was encountered while attempting to write to the specified file.
Logging is disabled for the process.
Action: Review preceding Alert log messages and attempt to resolve any file
system environmental problems indicated. Otherwise, contact Oracle Support
Services
CRS-00038: An invalid pointer to an internal control structure was encountered
while attempting to open a trace file. Additional diagnostics: string
Cause: An invalid pointer was encountered when attempting to open a trace file.
Tracing is disabled for the process.
Action: Contact Oracle Support Services.
CRS-00039: An error occurred while attempting to open trace file "string".
Cause: An error was encountered while attempting to open the specified file.
Tracing is disabled for the process.
Action: Review preceding Alert log messages and attempt to resolve any file
system environmental problems indicated. Otherwise, contact Oracle Support
Services
CRS-00040: Trace logging terminated for the process. trace file: "string"
Cause: One or more file system errors were encountered which caused tracing to
be terminated for this process.
Action: Examine preceding Alert log messages for details on the error or errors
that occurred. Restart the process to reenable logging.
CRS-00041: Trace file rotation terminated for the process. Trace file: "string"
Cause: One or more file system errors were encountered which caused trace file
rotation to be terminated for the process. Although trace file rotation has been
terminated, tracing continues.
Action: Review Alert log messages that precede this alert log message that
identify the file system error or errors encountered. If the additional diagnostic
data in a preceding alert log message indicate a file system environmental
problem, attempt to correct it. Otherwise contact Oracle Support Services. To
reenable trace file rotation the process must be restarted.
CRS-00184: Cannot communicate with the CRS daemon.
Cause: The CRS daemon on the local node is either not running or there was an
internal communication error with the CRS daemon.
Action: Check if the CRS daemon process is running on the local node.
CRS-00210: Could not find resource 'string'.
Cause: An attempt was made to operate on a resource that is not registered.
Action: Ensure that the resource name is specified correctly using the command
'crsctl status resource'.
CRS-00211: Resource 'string' has already been registered.
Cause: An attempt was made to register a resource that is already registered.
CRS-00001 to CRS-29006 64-7
Action: Ensure that the resource name is specified correctly and retry the
command.
CRS-00213: Could not register resource 'string'.
Cause: There was an internal error while registering the resource.
Action: Check the CRS daemon log file.
CRS-00214: Could not unregister resource 'string'.
Cause: There was an internal error while unregistering the resource.
Action: Check the CRS daemon log file.
CRS-00215: Could not start resource 'string'.
Cause: There was an internal error while starting the resource.
Action: Check the CRS daemon log file.
CRS-00216: Could not stop resource 'string'.
Cause: There was an internal error while stopping the resource.
Action: Check the CRS daemon log file.
CRS-00217: Could not relocate resource 'string'.
Cause: There was an internal error while relocating the resource.
Action: Check the CRS daemon log file.
CRS-00218: Could not restart the resource 'string' on the original node.
Cause: There was an internal error while restarting the resource.
Action: Check the CRS daemon log file.
CRS-00219: Could not update resource 'string'.
Cause: There was an internal error while updating the resource.
Action: Check the CRS daemon log file.
CRS-00220: Resource 'string' has invalid resource profile.
Cause: Invalid attributes in the resource profile.
Action: Run the command 'crsctl status type' to identify the invalid attributes.
Modify these attributes using the command 'crsctl modify type'.
CRS-00221: Resource 'string''s action script cannot be found.
Cause: The action script has been deleted from the file system.
Action: Run 'crsctl status resource -p' to determine the action script location, and
check for its existence.
CRS-00223: Resource 'string' has placement error.
Cause: Based on the placement policy for the resource, there was no available host
to which the resourse could failover or start.
Action: Check the target host for the resource and restart the resource using the
'crsctl start resource' command.
CRS-00230: Member 'string' is not in the cluster.
Cause: The hostname was not found in the cluster.
Action: Check the hostnames in the cluster.
CRS-00232: Cluster member is down. Cannot perform operation.
64-8 Oracle Database Error Messages
Cause: The node on which CRS is attempting to start the resource is down.
Action: Start the node and retry the operation.
CRS-00233: Resource or relatives are currently involved with another operation.
Cause: Another CRS daemon was operating on the same resource.
Action: Wait for a minute and try the command or operation again.
CRS-00253: CRS configuration error, the CRS default directory is not set in Oracle
Cluster Registry.
Cause: The Oracle Cluster Registry key which contains the user default CRS key
is not initialised.
Action: Check the CRS configuration. If necessary reinstall CRS.
CRS-00254: authorization failure
Cause: The user permissions were insufficient to operate on the resource.
Action: Check the permissions associated with the resource using 'crsctl getperm
resource' and set the appropriate user permissions using 'crsctl setperm resource'.
CRS-00255: CRSD is not running in privileged mode. Insufficient permissions to
run this command.
Cause: The CRS daemon was not running as the privileged user.
Action: Check if the CRS daemon is running as root (UNIX) or Administrator
(Windows).
CRS-00256: Username conflicts with the owner of the resource.
Cause: An attempt was made to give separate user level permissions for the
owner of the resource.
Action: Check the owner of the resource and the user being given permissions.
CRS-00257: Groupname conflicts with the primary group of the resource.
Cause: An attempt was made to give separate group level permissions for the
primary group of the resource.
Action: Check the primary group of the resource and the group being given
permissions.
CRS-00258: Invalid ACL string format.
Cause: An invalid permission string (ACL) was supplied.
Action: Check the syntax of the permission string (ACL).
CRS-00259: Owner of the resource does not belong to the group.
Cause: The owner of the resource does not belong to the expected group.
Action: If this resource is owned by the root user, check if the root user belongs to
the dba group.
CRS-00271: CRSD shutdown is already in progress.
Cause: crsctl stop command is issued before waiting for a prior stop command to
finish.
Action: Wait for the currently running shutdown command to complete before
issuing subsequent command.
CRS-00272: This command remains for backward compatibility only
Cause: A deprecated command was issued.
CRS-00001 to CRS-29006 64-9
Action: For all new use cases, use the replacement.
CRS-00273: This command is deprecated and has been replaced by 'string'
Cause: A deprecated command was issued.
Action: For all new use cases, use the replacement.
CRS-00274: This command is deprecated and its functionality incorporated into
'string'
Cause: A deprecated command was issued.
Action: For all new use cases, use the replacement.
CRS-00275: This command is not supported in Oracle Restart environment.
Cause: One of the "crs_" commands was issued in an Oracle Restart environment.
Action: Use the corresponding crsctl command.
CRS-00402: Could not make safe directory('string')
Cause: Unable to create safe directory.
Action: Check if you have proper permissions and sufficient space on the disk to
create the directory.
CRS-00403: Could not change working directory to safe directory('string')
Cause: Unable to change directory to safe directory.
Action: Check if safe directory exists and if you have proper permissions.
CRS-00406: Could not create lock directory ('string')
Cause: Unable to create lock directory.
Action: Check if you have proper permissions and sufficient space on the disk to
create the directory.
CRS-00407: Another CRSD may be running, could not obtain lock file 'string'.
Cause: Unable to obtain lock file as another CRSD may be running.
Action: Stop the existing CRSD before attempting to start CRSD again.
CRS-00413: Could not initialize the Cluster Synchronization Services context
Cause: Unable to communicate with the cluster services.
Action: Verify that the Cluster Synchronization Services Daemon is properly
configured and is running.
CRS-00414: Could not establish Event Manager connection
Cause: Unable to communicate with Event Manager daemon.
Action: Run the 'crsctl check evmd' command to determine whether Event
Manager daemon is properly configured and is running.
CRS-00451: CRS configuration error, unable to initialize Oracle Cluster Registry.
Cause: The Oracle Cluster Registry that contains information about the CRS
configuration is unavailable.
Action: Check the OCR configuration using the ocrcheck utility and resolve any
issues it reports. If the problem persists, contact Oracle Support Services.
CRS-00452: CRS configuration error, unable to find CRSD Connection Information
in Oracle Cluster Registry.
64-10 Oracle Database Error Messages
Cause: The Oracle Cluster Registry key which contains the user default CRSD
connection is not initialized.
Action: Check the OCR configuration using the ocrcheck utility and resolve any
issues it reports. If the problem persists, contact Oracle Support Services.
CRS-00453: CRS configuration error, unable to find Instance Information in Oracle
Cluster Registry.
Cause: The Oracle Cluster Registry key which contains the Instance's information
is not initialized.
Action: Check the OCR configuration using the ocrcheck utility and resolve any
issues it reports. If the problem persists, contact Oracle Support Services.
CRS-00471: Node number is not found
Cause: Cluster Synchronization Services is unable to retrieve the node name.
Action: Verify your cluster installation, including any vendor cluster ware. If
necessary reinstall the cluster.
CRS-00472: Node name is not found
Cause: Cluster Services is unable to retrieve the node name.
Action: Verify your cluster installation, including any vendor cluster ware. If
necessary reinstall the cluster.
CRS-00602: Encountered operating system error 'string' while authenticating user
'string'. Details at string in string.
Cause: The operating system experienced an error when Clusterware
authenticated the specified user.
Action: Verify that the authentication service in your environment is functioning
correctly. If the problem persists, contact Oracle Support Services.
CRS-00700: Oracle High Availability Service aborted due to failure to allocate
memory. Details at string in string.
Cause: Memory allocation failed.
Action: Restart Cluster Ready Service using 'crsctl stop crs -f' followed by 'crsctl
start crs'. If the problem persists, contact Oracle Support Services.
CRS-00701: Oracle High Availability Service aborted due to failure to obtain
identity of the running process. Details at string in string.
Cause: Failed to retrieve user id.
Action: Check <crs_home> owner and restart Cluster Ready Service using 'crsctl
stop crs -f' followed by 'crsctl start crs'. If the problem persists, contact Oracle
Support Services.
CRS-00702: Oracle High Availability Service aborted due to failure to run as
privileged user. Details at string in string.
Cause: Oracle High Availability Service was not running as privileged user.
Action: On Unix, restart Cluster Ready Service as privileged user using 'crsctl
stop crs -f' followed by 'crsctl start crs'. On Windows, check the privileges of the
Oracle High Availability Service and restart Cluster Ready Service using 'crsctl
stop crs -f' followed by 'crsctl start crs' If the problem persists, contact Oracle
Support Services.
CRS-00703: Oracle High Availability Service aborted due to failure to initialize the
communication context. Details at string in string.
CRS-00001 to CRS-29006 64-11
Cause: The network layer initialization failed.
Action: Restart Cluster Ready Service using 'crsctl stop crs -f' followed by 'crsctl
start crs'. If the problem persists, contact Oracle Support Services.
CRS-00704: Oracle High Availability Service aborted due to Oracle Local Registry
error [string]. Details at string in string.
Cause: Oracle Local Registry aborted with an error. Look at the associated error
message to determine the underlying issue.
Action: Solve the underlying issue and restart Cluster Ready Service using 'crsctl
stop crs -f' followed by 'crsctl start crs'. If the problem persists, contact Oracle
Support Services.
CRS-00708: Oracle High Availability Service aborted due to failure to retrieve
ORA_CRS_HOME environment variable. Details at string in string.
Cause: An environment variable required by Oracle High Availability Service
failed to be set at initialization.
Action: Run 'rootcrs.pl -unlock' followed by 'rootcrs.pl -patch' and restart Cluster
Ready Service using 'crsctl stop crs -f' followed by 'crsctl start crs'. If the problem
persists, contact Oracle Support Services.
CRS-00709: Oracle High Availability Service aborted due to failure to initialize
ORA_CRS_HOME path. Details at string in string.
Cause: Oracle High Availability Service ORA_CRS_HOME path could not be
initialized.
Action: Check for execute permissions on the Grid Infrastructure home or <crs_
home> and restart Cluster Ready Service using 'crsctl stop crs -f' followed by
'crsctl start crs'. If the problem persists, contact Oracle Support Services.
CRS-00712: Oracle High Availability Service aborted due to failure to initialize the
network layer with error [number]. Details at string in string.
Cause: The network layer initialization failed.
Action: Restart Cluster Ready Service using 'crsctl stop crs -f' followed by 'crsctl
start crs'. If the problem persists, contact Oracle Support Services.
CRS-00713: An error occurred initializing the Reboot Advisory Monitor: error code
[number]. Details at string in string.
Cause: An error occurred initializing the Reboot Advisory Monitor component of
Oracle High Availability Service. This error is not fatal; Oracle High Availability
Service processing continues.
Action: Examine the Clusterware alert log for messages providing details of the
error. If the error is correctable, do so and then restart Cluster Ready Service using
'crsctl stop crs -f' followed by 'crsctl start crs'. If no messages are found or you do
not understand how to correct the problem, contact Oracle Support Services.
CRS-00714: Oracle Clusterware Release number.number.number.number.number.
Cause: The Oracle High Availability Services Daemon (OHASD) was started as
part of a general start of the Oracle Clusterware stack on this node.
Action: None
CRS-00715: Oracle High Availability Service has timed out waiting for init.ohasd to
be started.
Cause: The Oracle High Availability Service requires that initd start init.ohasd to
successfully initialize.
64-12 Oracle Database Error Messages
Action: 1. Check the run level to ensure that you are in the correct runlevel using
cluvfy ("cluvfy stage -pre crsinst -n <nodelist>"); 2. If the run level is correct,
diagnose the reason for init.d not starting init.ohasd.
CRS-00800: Cluster Ready Service aborted due to failure to allocate memory.
Details at string in string.
Cause: Memory allocation failed.
Action: Restart Cluster Ready Service using 'crsctl stop crs -f' followed by 'crsctl
start crs'. If the problem persists, contact Oracle Support Services.
CRS-00801: Cluster Ready Service aborted due to failure to obtain identity of the
running process. Details at string in string.
Cause: Failed to retrieve user id.
Action: Check <crs_home> owner and restart Cluster Ready Service using 'crsctl
stop crs -f' followed by 'crsctl start crs'. If the problem persists, contact Oracle
Support Services.
CRS-00802: Cluster Ready Service aborted due to failure to run as privileged user.
Details at string in string.
Cause: Cluster Ready Service was not running as privileged user.
Action: On Unix, restart Cluster Ready Service as privileged user using 'crsctl
stop crs -f' followed by 'crsctl start crs'. On Windows, check the privileges of the
Oracle High Availability Service and restart Cluster Ready Service using 'crsctl
stop crs -f' followed by 'crsctl start crs' If the problem persists, contact Oracle
Support Services.
CRS-00803: Cluster Ready Service aborted due to failure to initialize the
communication context. Details at string in string.
Cause: The network layer initialization failed.
Action: Restart Cluster Ready Service using 'crsctl stop crs -f' followed by 'crsctl
start crs'. If the problem persists, contact Oracle Support Services.
CRS-00804: Cluster Ready Service aborted due to Oracle Cluster Registry error
[string]. Details at string in string.
Cause: Oracle Cluster Registry aborted with an error. Look at the associated error
message to determine the underlying issue.
Action: Solve the underlying issue and restart Cluster Ready Service using 'crsctl
stop crs -f' followed by 'crsctl start crs'. If the problem persists, contact Oracle
Support Services.
CRS-00805: Cluster Ready Service aborted due to failure to communicate with
Cluster Synchronization Service with error [number]. Details at string in string.
Cause: The Cluster Synchronization Service is unreachable.
Action: Restart Cluster Ready Service using 'crsctl stop crs -f' followed by 'crsctl
start crs'. If the problem persists, contact Oracle Support Services.
CRS-00806: Cluster Ready Service aborted due to failure to retrieve the local node
name. Details at string in string.
Cause: The Cluster Synchronization Service node name is not accessible.
Action: Restart Cluster Ready Service using 'crsctl stop crs -f' followed by 'crsctl
start crs'. If the problem persists, contact Oracle Support Services.
CRS-00001 to CRS-29006 64-13
CRS-00807: Cluster Ready Service aborted due to failure to check version
compatibility. Details at string in string.
Cause: Oracle Cluster Registry content is not compatible with this version of
Cluster Ready Service.
Action: Start the correct version of Cluster Ready Service. If the problem persists,
contact Oracle Support Services.
CRS-00808: Cluster Ready Service aborted due to failure to retrieve ORA_CRS_
HOME environment variable. Details at string in string.
Cause: An environment variable required by Cluster Ready Service failed to be
set at initialization.
Action: Run 'rootcrs.pl -unlock' followed by 'rootcrs.pl -patch' and restart Cluster
Ready Service using 'crsctl stop crs -f' followed by 'crsctl start crs'. If the problem
persists, contact Oracle Support Services.
CRS-00809: Cluster Ready Service aborted due to failure to initialize ORA_CRS_
HOME path. Details at string in string.
Cause: Cluster Ready Service ORA_CRS_HOME path could not be initialized.
Action: Check for execute permissions on the Grid Infrastructure home or <crs_
home> and restart Cluster Ready Service using 'crsctl stop crs -f' followed by
'crsctl start crs'. If the problem persists, contact Oracle Support Services.
CRS-00810: Cluster Ready Service aborted due to failure to communicate with
Event Management Service with error [number]. Details at string in string.
Cause: The Event Management Service is unreachable.
Action: Restart Cluster Ready Service using 'crsctl stop crs -f' followed by 'crsctl
start crs'. If the problem persists, contact Oracle Support Services.
CRS-00811: Cluster Ready Service aborted due to failure to build dependency
graph. Details at string in string.
Cause: There exists inconsistencies in the resources dependencies.
Action: Check the resources dependencies and restart Cluster Ready Service
using 'crsctl stop crs -f' followed by 'crsctl start crs'. If the problem persists, contact
Oracle Support Services.
CRS-00812: Cluster Ready Service aborted due to failure to initialize the network
layer with error [number]. Details at string in string.
Cause: The network layer initialization failed.
Action: Restart Cluster Ready Service using 'crsctl stop crs -f' followed by 'crsctl
start crs'. If the problem persists, contact Oracle Support Services.
CRS-00813: Cluster Ready Service aborted due to failure to initialize the network
layer with error [string]. Details at string in string.
Cause: The network layer initialization failed.
Action: Restart Cluster Ready Service using 'crsctl stop crs -f' followed by 'crsctl
start crs'. If the problem persists, contact Oracle Support Services.
CRS-00814: Cluster Ready Service aborted due to failure to start thread with error
[number]. Details at string in string.
Cause: Thread creation failed.
Action: Restart Cluster Ready Service using 'crsctl stop crs -f' followed by 'crsctl
start crs'. If the problem persists, contact Oracle Support Services.
64-14 Oracle Database Error Messages
CRS-01001: The OCR was formatted using version number.
Cause: Successfully formatted the OCR location(s).
Action: None
CRS-01002: The OCR was restored from file string.
Cause: The OCR was successfully restored from a backup file as requested by the
user.
Action: None
CRS-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
CRS-01004: The OCR was imported from string.
Cause: Successfully imported the OCR contents from a file.
Action: None
CRS-01005: The Oracle Clusterware upgrade was completed. Version has changed
from [number, string] to [number, string]. Details in string.
Cause: The Oracle Clusterware was successfully upgraded to a version.
Action: None
CRS-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.
CRS-01007: The OCR/OCR mirror location was replaced by string.
Cause: The OCR location was successfully replaced as requested by the user.
Action: None
CRS-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 Support Services.
CRS-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.
CRS-01010: The OCR mirror location string was removed.
Cause: The OCR location was successfully removed as requested by the user.
Action: None
CRS-00001 to CRS-29006 64-15
CRS-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
Support Services.
CRS-01012: The OCR service started on node string.
Cause: The OCR was successfully started.
Action: None
CRS-01013: The OCR location in an ASM disk group is inaccessible. Details in
string.
Cause: An error occurred while accessing the OCR file in an ASM disk group.
Action: Use the 'asmcmd' command to verify if the ASM instance is active. If the
ASM instance aborted, it will be restarted automatically. Use 'ocrcheck -config' to
discover the OCR locations configured, and verify using 'asmcmd' that the disk
group in question is mounted. Mount the disk group if it is not mounted. Validate
if the behavior is limited to one node or whether it occurs across all of the nodes in
the cluster. If nothing works, use the 'ocrconfig' command with the '-replace' or
'-delete' option to replace or remove the OCR location.
CRS-01014: Failed to import Oracle Cluster Registry from file string
Cause: Unable to read data from the import file and import to the cluster registry
Action: Check availability of the cluster registry and the details of the failure from
the log file
CRS-01015: A request to terminate the Cluster Ready Service on node string
completed successfully. Details at string in string.
Cause: The Cluster Ready Service on the above listed node did not respond to an
earlier request within the specified time. The Cluster Ready Service will be
terminated to prevent any possible cluster hangs.
Action: Check the Oracle Clusterware alert log on the listed node for any
problems. Check for any reason that might not allow the Cluster Ready Service to
run optimally on the listed node. Verify network accessibility to the listed node
from other nodes in the cluster. If the problem persists, contact Oracle Support
Services.
CRS-01016: The Cluster Ready Service on this node terminated because it detected
a failure while upgrading the Oracle Cluster Registry format. Details at string in
string.
Cause: The Cluster Ready Service on the node coordinating the upgrade of the
Oracle Cluster Registry format terminated.
Action: The Oracle Cluster Registry format upgrade will be completed by another
node in the cluster. The Cluster Ready Service on the node listed above will be
automatically restarted, and will be able to function as soon as the upgrade
completes. If the problem persists, contact Oracle Support Services.
64-16 Oracle Database Error Messages
CRS-01017: The Cluster Ready Service on this node terminated because it was
unable to open the import file while upgrading the Oracle
Cause: A command completely successfully.
Action: No action is needed.
CLSMDNS-00001: GIPC endpoint creation failed.
Cause: An attempt to create a GIPC endpoint for use multicast operations failed.
Action: Examine the accompanying error (if any) and the log file for details as to
why the operation failed.
CLSMDNS-00002: bind failed.
Cause: An attempt to bind an address to a GIPC endpoint failed.
Action: Examine the accompanying error (if any) and the log file for details as to
why the operation failed.
CLSMDNS-00003: address creation failed.
Cause: An attempt to create a GIPC address failed.
Action: Examine the accompanying error (if any) and the log file for details as to
why the operation failed.
CLSMDNS-00004: attribute setting failed.
Cause: An attempt to set an attribute on a GIPC endpoint or address failed.
Action: Examine the accompanying error (if any) and the log file for details as to
why the operation failed.
CLSMDNS-00005: interface registration failed.
Cause: The registration of an interface with mDNS failed.
Action: Examine the accompanying error (if any) and the log file for details as to
why the operation failed.
CLSMDNS-00006: failed to get name server list.
Cause: An attempt to get the list of available name servers failed.
Action: Examine the accompanying error (if any) and the log file for details as to
why the operation failed.
CLSMDNS-00007: mDNS initialization failed.
Cause: The initialization of the mDNS subsystem failed.
Action: Examine the accompanying error (if any) and the log file for details as to
why the operation failed.
58-2 Oracle Database Error Messages
CLSMDNS-00008: start of host query failed.
Cause: The query for hosts from mDNS failed to start.
Action: Examine the accompanying error (if any) and the log file for details as to
why the operation failed.
CLSMDNS-00009: stop of host query failed.
Cause: Termination of the query for hosts from mDNS failed.
Action: Examine the accompanying error (if any) and the log file for details as to
why the operation failed.
CLSMDNS-00010: Initialization of name server name retrieval failed.
Cause: The initialization of the retrieval of the names of the name servers used by
multicast DNS failed.
Action: Examine the accompanying messages(s) that detail the platform error(s)
for details about the exception.
CLSMDNS-00011: retrieval of name server name failed.
Cause: The retrieval of the name of a name server to be used by multicast DNS
failed.
Action: Examine the accompanying messages(s) that detail the platform error(s)
for details about the exception.
CLSMDNS-00012: no name servers found.
Cause: No name servers were found that could be used by multicast DNS.
Action: Check the system configuration and ensure that or more DNS name
servers are configured, operating and accessible.
CLSMDNS-00013: Send of response to DNS server failed.
Cause: An attempt to send a response to a query from the DNS server failed.
Action: Examine accompanying exceptions for details about the exact error.
CLSMDNS-00015: invalid record type: number
Cause: The DNS server sent a record whose type is unknown.
Action: This is a warning message which can be ignored because the error should
occur very infrequently. If the error occurs frequently, Oracle Customer Support
should be contacted.
CLSMDNS-02000: unknown error.
Cause: An unknown error occurred. This error can occur when the multicast DNS
server is not running.
Action: If the multicast server is not running, start it and try the operation again.
If it is running, this is an internal error and Oracle Customer Support should be
contacted with details about how and when the error occurred.
CLSMDNS-02001: no such name exists.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
CLSMDNS-02002: memory allocation failure.
Cause: The allocation of process memory failed.
CLSMDNS-00000 to CLSMDNS-02255 58-3
Action: If memory is low on the system, terminate other processes and/or threads
and try the operation again. Otherwise, this is an internal error and Oracle
Customer Support should be contacted.
CLSMDNS-02003: invalid parameter.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
CLSMDNS-02004: invalid reference.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
CLSMDNS-02005: invalid state.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
CLSMDNS-02006: invalid flags.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
CLSMDNS-02007: operation is unsupported.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
CLSMDNS-02008: uninitialized.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
CLSMDNS-02009: no cache.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
CLSMDNS-02010: record or service is already registered.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
CLSMDNS-02011: name conflict found.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
CLSMDNS-02012: Invalid.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
CLSMDNS-02013: Firewall.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
CLSMDNS-02014: Incompatible.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
58-4 Oracle Database Error Messages
CLSMDNS-02015: invalid interface.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
CLSMDNS-02016: Refused.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
CLSMDNS-02017: no such record.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
CLSMDNS-02018: no authentication.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
CLSMDNS-02019: no such key.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
CLSMDNS-02020: error occurred while passing through NAT.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
CLSMDNS-02021: double NAT encountered.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
CLSMDNS-02022: invalid time.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
CLSMDNS-02023: invalid signature.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
CLSMDNS-02024: invalid key.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
CLSMDNS-02025: transient error.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
CLSMDNS-02250: connection pending.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
CLSMDNS-02251: connection failed.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
CLSMDNS-00000 to CLSMDNS-02255 58-5
CLSMDNS-02252: connection established.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
CLSMDNS-02253: more memory needed for cache.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
CLSMDNS-02254: configuration changed.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
CLSMDNS-02255: memory free needed.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
58-6 Oracle Database Error Messages
59
CLSR-00001 to CLSR-06507 59-1
CLSR-00001 to CLSR-06507 9 5
CLSR-00001: Oracle error number encountered
Cause: Oracle-related error is encountered.
Action: Check alert log and trace file for more detail.
CLSR-00002: Oracle error encountered while executing string
Cause: Oracle-related error is encountered while executing a request.
Action: Check alert log for more detail.
CLSR-00003: ORACLE_HOME environment variable not set
Cause: ORACLE_HOME environment variable is not set.
Action: Make sure that the ORACLE_HOME environment variable has been
properly set and exported.
CLSR-00004: Error encountered at string, category=number, operation=string, OS
error=number
Cause: Operating system error occurred.
Action: Check for the error message for more detail.
CLSR-00005: Error encountered during memory allocation
Cause: System memory is insufficient.
Action: Check the availability of memory in the system before retrying.
CLSR-00006: Error encountered when writing file string
Cause: Error when writing file.
Action: Check the permission of the file and the existence of its path.
CLSR-00007: Error encountered when reading file string
Cause: Error when reading file.
Action: Check the permission and existence of the file.
CLSR-00501: Error number encountered when connecting to EVM daemon
Cause: Error encountered when connecting to EVM daemon.
Action: Check status of EVM daemon and log file for detail.
CLSR-00502: Error number encountered when subscribing an EVM event
Cause: Error encountered when subscribing an EVM event.
Action: Contact customer support.
CLSR-00503: Error number encountered when creating an EVM event
59-2 Oracle Database Error Messages
Cause: Error encountered when creating an EVM event.
Action: Contact customer support.
CLSR-00504: Error number encountered when posting an EVM event
Cause: Error encountered when posting an EVM event.
Action: Contact customer support.
CLSR-00505: Empty event type is specified
Cause: Empty event type is specified.
Action: Try again with a valid event type.
CLSR-00506: Unmatched resource name prefix string is specified
Cause: Specified resource name prefix does not match as required.
Action: Try again with a valid resource name prefix.
CLSR-00507: The length of the facility name string exceeds the limit (number)
Cause: The given facility name is too long.
Action: Try again with a short facility name.
CLSR-00508: Invalid message number number
Cause: An incorrect message number is specified.
Action: Try again with a correct message number.
CLSR-00509: Unable to initialize NLS
Cause: Failed to initialize callback structure for NLS.
Action: Contact customer support.
CLSR-00510: Unable to load NLS data
Cause: Failed to initialize NLS data loading.
Action: Not action required as default data loading will be used.
CLSR-00511: Error number encountered when handling incoming EVM message
Cause: Error encountered when handling incoming EVM message.
Action: Check log file for detail.
CLSR-00512: Invalid CAA trigger event type [string]
Cause: Invalid CAA trigger event type is specified.
Action: Try again with a valid type.
CLSR-00513: Message file is not found
Cause: The requested OCI message file is not found.
Action: Check if the message file is properly installed.
CLSR-00514: Unable to locate PMON [pid=string]
Cause: Cannot find PMON with this pid.
Action: Check the existence of PMON.
CLSR-00515: A service member is already running on this node
Cause: There is a service member of the same service running on this node.
Action: No action required as the service member will try to start on another
node.
CLSR-00001 to CLSR-06507 59-3
CLSR-00516: No service provider found at this node
Cause: No suitable service provider is found on this node.
Action: No action required as the service member will try to start on another
node.
CLSR-00517: Failed to register a service name
Cause: The requested service name cannot be registered.
Action: Check log file for detail.
CLSR-00518: Failed to register a preconnect service name
Cause: The requested preconnect service name cannot be registered.
Action: Check log file for detail.
CLSR-00519: No instance found
Cause: No instance is found running for the database resource.
Action: No action required as the database resource will fail itself.
CLSR-00520: No service member found
Cause: No service member is found running for the composite service resource.
Action: No action required as the composite service resource will fail itself.
CLSR-00521: Event string is rejected by EVM daemon
Cause: No template has been registered for the event or caller is not authorized to
post the event.
Action: Check if there is a template registered for this event and the authority of
posting this event.
CLSR-00522: Resource string is not registered
Cause: CRS resource is not registered.
Action: Register the CRS resource.
CLSR-00523: Resource string is not enabled
Cause: CRS resource is not enabled.
Action: Enable the CRS resource.
CLSR-00524: Resource string is stopping, resource string cannot start
Cause: Resource cannot start because its composite resource is stopping.
Action: Retry to start the resource when its composite resource is not stopping.
CLSR-00525: prsr initialization failed
Cause: See the related error message.
Action: Run crs_stat to make sure CSS and OCR working properly.
CLSR-00526: Failed to retrieve database configuration in OCR
Cause: See the related error message.
Action: Run crs_stat to make sure CSS and OCR working properly and database
configuration in ocr is initialized.
CLSR-00527: OCR operation failed
Cause: See related error messages about the OCR operation.
Action: Fix the related error. Then try again.
59-4 Oracle Database Error Messages
CLSR-00528: RACGONS: host and port number already configured in OCR
Cause: host and port number already configured in OCR.
Action: None
CLSR-00529: RACGONS: host and port number to be removed does not exist
Cause: host and port number to be removed is not configured in OCR.
Action: None
CLSR-00530: Can not get user name
Cause: Error caused by OSD layer.
Action: Contact Oracle support.
CLSR-00531: Can not get primary group name
Cause: There is no primary group for this OS.
Action: Not faital. None.
CLSR-01001: Unsupported open mode number is specified
Cause: Unsupported open mode is specified for mounting database.
Action: Retry again with a valid open mode.
CLSR-01002: Unable to process instance startup
Cause: ORACLE_HOME environment variable not set.
Action: Make sure that the ORACLE_HOME environment variable has been
properly set and exported.
CLSR-01003: Error number encountered during mounting database
Cause: Unexpected error occurs when mounting database.
Action: Check current status of database before retrying.
CLSR-01004: Failed to mount database
Cause: Database cannot be mounted by an instance.
Action: Check alert log for error detail.
CLSR-01005: Error number encountered during altering database open mode
Cause: Unexpected error occurs when altering database open mode.
Action: Check current database status.
CLSR-01006: Unable to process instance shutdown
Cause: ORACLE_HOME environment variable not set.
Action: Make sure that the ORACLE_HOME environment variable has been
properly set and exported.
CLSR-01007: Connection to database was not established
Cause: Connection to database is failed to establish.
Action: Make sure connection and environment are properly set up.
CLSR-01008: Error number encountered during querying for PMON status
Cause: Unexpected error encountered when querying v$process for PMON.
Action: Check alert log and connection to database.
CLSR-01009: database management module failed to start
CLSR-00001 to CLSR-06507 59-5
Cause: Error encountered during initializing database management module.
Action: Check previous error message for detail.
CLSR-01010: Unable to record PMON pid to string
Cause: Failed to write os pid for PMON to file.
Action: Check file system for disk space and access privilege.
CLSR-01011: Invalid instance startup mode [string] is specified
Cause: Invalid startup mode is specified.
Action: Retry again with a valid startup mode.
CLSR-01012: Invalid instance stop mode [string] is specified
Cause: Invalid stop mode is specified.
Action: Retry again with a vaild stop mode.
CLSR-06500: Invalid input arguments
Cause: Invalid input arguments are specified.
Action: Retry again with a valid argument.
CLSR-06501: Exceeds maximum number of arguments
Cause: Too many input arguments are specified.
Action: Retry again with correct number of arguments.
CLSR-06502: Failed to connect to database 'string' as user 'string'
Cause: Failed to connect to database.
Action: Check database and log file for details.
CLSR-06503: Service name already registered
Cause: Requested service name has been registered by another service.
Action: Choose another service name and retry registration again.
CLSR-06504: Service name not in SERVICE_NAMES
Cause: Requested service name is not registered.
Action: Make sure the correct service name is specified in the request.
CLSR-06505: SERVICE_NAMES found null and fixed
Cause: SERVICE_NAMES parameter becomes null after the delete operation.
Action: Not action required as SERVICE_NAMES is set to default value.
CLSR-06506: Error number encountered when executing string
Cause: Error occurred when executing the SQL statement.
Action: Check alert log for more detail.
CLSR-06507: Cannot add to SERVICE_NAMES, SERVICE_NAMES will be too long
Cause: Adding the service name will exceed the limit of SERVICE_NAMES.
Action: Change the configuration to avoid SERVICE_NAMES becomes too long.
59-6 Oracle Database Error Messages
60
CLSS-00001 to CLSS-03202 60-1
CLSS-00001 to CLSS-03202 0 6
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]
60-2 Oracle Database Error Messages
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-00001 to CLSS-03202 60-3
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.
60-4 Oracle Database Error Messages
61
CLST-01101 to CLST-03203 61-1
CLST-01101 to CLST-03203 1 6
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.
Action: Verify that the node name refers to IP addresses on the private
interconnect. Using a non-private network can cause performance and stability
issues.
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.
Action: If the node name is not equal to the host name, the host name must be
supplied to clscfg. Failure to do so will cause the Cluster Ready Services daemons
not to function.
CLST-01103: existing configuration version (string) detected
Cause: An existing configuration was detected.
Action: Informational message only. No action is required. clscfg will not modify
the existing configuration unless explicitly requested with the -force flag.
CLST-01104: successfully determined required configuration for all components
Cause: clscfg was able to determine the proper configuration requirements.
Action: Informational message only. No action is required. clscfg will attempt to
write the configuration next.
CLST-01105: An existing configuration was detected. It was not overwritten.
Cause: An existing configuration was detected, and clscfg chose not to overwrite
it.
Action: This message may be ignored if it is seen as part of starting any node
other than the first one. The -force option can be used to override this decision, but
if it is used when there are active cluster members, failure CLSS-0101 and data
integrity issues are likely.
CLST-01301: successfully deleted string of string configuration values
Cause: clscfg completed a portion of the delete operation.
Action: Informational message only. No action is required. If some of the values
were not deleted, another error message should be visible with more information.
CLST-01302: successfully deleted string of string configuration keys
Cause: clscfg completed a portion of the delete operation.
61-2 Oracle Database Error Messages
Action: Informational message only. No action is required. If some of the keys
were not deleted, another error message should be visible with more information.
CLST-01303: successfully rolled back delete operation
Cause: The delete node operation failed, but the configuration was properly
restored to its original state.
Action: Informational message only. No action is required.
CLST-01304: node deletion successful
Cause: The delete node operation succeeded.
Action: Informational message only. No action is required.
CLST-01401: formatting voting device: string
Cause: clscfg started formatting the voting device.
Action: Informational message only. No action is required.
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.
Action: Informational message only. No action is required. This might be an
indication of corrupted configuration, or a previous delete operation that did not
complete.
CLST-01901: configuring TCP ports string, string, string, and string
Cause: The specified ports were configured for use with the Cluster Ready
Services Daemons.
Action: Informational message only. No action is required. To change the ports
used, specify 4 alternate ports with "-t". Example: -t 1001,1002,1003,1004
CLST-01902: configuring node: node number string, node name string
Cause: This node configuration was requested.
Action: Informational message only. No action is required. To alter the list of
nodes re-run the install and specify a different set of nodes, or make use of the add
and delete node install options after the current install is complete.
CLST-01903: configuring node: host name string, private interconnect name string
Cause: This node configuration was requested.
Action: Informational message only. No action is required. To alter the list of
nodes re-run the install and specify a different set of nodes, or make use of the add
and delete node install options after the current install is complete.
CLST-01904: creating configuration with user (string) and group (string)
Cause: The configuration was set up with the specified user and group.
Action: Informational message only. No action is required. Some configuration
information will only be accessible to members of the specified group. Note: On
Windows platforms the group may be blank.
CLST-01999: Warning: -force specified. Overwriting existing configuration.
Cause: The -force parameter was supplied.
Action: The -force parameter will cause clscfg to overwrite the existing
configuration. If used while a Cluster Ready Services cluster is actively running,
this can cause instability and data integrity exposures.
CLST-01101 to CLST-03203 61-3
CLST-02101: Too many nodes were specified. limit is string
Cause: Too many nodes were specified on command line.
Action: Retry the operation with a smaller number of simultaneous changes.
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.
Action: Retry the operation with a smaller node number.
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.
Action: Correct the arguments to the -t flag and rerun the operation.
CLST-02104: TCP port string is out of bounds.
Cause: The TCP port specified was not a valid port number.
Action: Specify an another port. Usually TCP ports need to be between 1001 and
65,535.
CLST-02105: missing required parameter -l with language ID information
Cause: The -l parameter was required for the requested operation.
Action: Supply the -l parameter with the proper language ID.
CLST-02106: missing required parameter -o with path to ORA_CRS_HOME
Cause: The -o parameter was required for the requested operation.
Action: Supply the -o parameter with the proper path.
CLST-02107: failure configuring component string
Cause: The Oracle Cluster Repository configuration for the specified component
was unsuccessful.
Action: Look for other error information and contact Oracle support.
CLST-02108: missing required parameter -q with path to the voting device
Cause: The -q parameter was required for the requested operation.
Action: Supply the -q parameter with a valid path for the voting device.
CLST-02109: missing required parameter -c with a cluster name
Cause: The -c parameter was required for the requested operation.
Action: Supply the -c parameter with a name for the cluster.
CLST-02110: missing required parameter -nn with the list of nodenames
Cause: The -nn parameter was required for the requested operation.
Action: Supply a list of node names with the format:
nodenameA,nodenumA,nodenameB,nodenumB,...
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.
Action: Choose an alternate node to add to the cluster, or give the new node a
unique name, or delete the previous node, then retry.
61-4 Oracle Database Error Messages
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.
Action: Choose an alternate node to add to the cluster, or give the new node a
unique name, or delete the previous node, then retry.
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.
Action: Choose an alternate node to add to the cluster, or give the new node a
unique name, or delete the previous node, then retry.
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.
Action: Chose an alternate node to add to the cluster, or give the new node a
unique node number, or delete the previous node, then retry.
CLST-02301: failure string validating configuration of node string
Cause: clscfg was unable to validate existing configuration of the specified node.
Action: Validate the integrity of the Cluster Ready Services install on the local
node, or choose another node to delete.
CLST-02302: failure string validating configuration of private interconnect name
string
Cause: clscfg was unable to validate existing configuration of the specified node.
Action: Validate the integrity of the Cluster Ready Services install on the local
node, or choose another node to delete.
CLST-02303: failure string validating configuration of node with host name string
Cause: clscfg was unable to validate existing configuration of the specified node.
Action: Validate the integrity of the Cluster Ready Services install on the local
node, or choose another node to delete.
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.
Action: Specify the correct information describing the node you intend to delete,
then retry.
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.
Action: Specify the correct information describing the node you intend to delete,
then retry.
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-01101 to CLST-03203 61-5
Action: Specify the correct information describing the node you intend to delete,
then retry.
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.
Action: Specify the correct information describing the node you intend to delete,
then retry.
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.
Action: Verify the integrity of the Oracle Cluster Repository, and restore from
backup if necessary. If only one clscfg process was active on the cluster this may be
ignored.
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.
Action: Verify the integrity of the Cluster Ready Services install on the local node,
and retry.
CLST-02310: CSS daemon refused node deletion, status string. attempting rollback
Cause: Cluster Synchronization Services daemon refused the node deletion.
Action: One or more of the designated nodes may still be active. clscfg will now
attempt to roll back the deletion process. The Cluster Ready Services daemons
must be shut down on a node before any attempt to remove them from the
configuration. More information on why the attempt was refused may be available
in the Cluster Synchronization Service logfile.
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.
Action: Shut down the cluster and restore the Oracle Cluster Repository from
backup.
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.
Action: This can be ignored. The safer choice is to restore the Oracle Cluster
Repository from backup, and attempt the delete again. Adding any of the deleted
nodes back to the configuration in the future may fail if this is ignored.
CLST-02401: failure string querying maximum configurable node number
Cause: clscfg was unable to determine the legitimate range of node numbers.
Action: Verify the integrity of the Cluster Ready Services install on the local node.
CLST-02402: failure string querying existing configured node list
Cause: clscfg was unable to retrieve the list of currently configured nodes.
61-6 Oracle Database Error Messages
Action: Verify the integrity of the Cluster Ready Services install on the local node.
CLST-02403: failure string querying the maximum node name size
Cause: clscfg was unable to determine the size of the largest node name.
Action: Verify the integrity of the Cluster Ready Services install on the local node.
CLST-02404: failure string querying the cluster name
Cause: clscfg was unable to determine the existing cluster name.
Action: Verify the integrity of the Cluster Ready Services install on the local node.
CLST-02405: failure formatting voting device (string) at [string] [string] [string]
Cause: clscfg failed to format the voting device.
Action: Verify the path and permissions set on the voting device.
CLST-02501: failure string opening configuration for write operation
Cause: clscfg was attempting to open the current configuration for write access.
Action: Verify the integrity of the Oracle Cluster Repository. Shut down the
cluster and restore OCR from backup if necessary.
CLST-02502: failure string writing new configuration
Cause: clscfg was attempting to write new configuration data.
Action: Verify the integrity of the Oracle Cluster Repository. Shut down the
cluster and restore OCR from backup if necessary.
CLST-02503: failure string opening configuration for delete operation
Cause: clscfg received an error while attempting to delete part of the existing
configuration.
Action: Verify the integrity of the Oracle Cluster Repository. Shut down the
cluster and restore OCR from backup if necessary.
CLST-02504: failure string writing configuration to disk
Cause: clscfg received a failure writing information to the Oracle Cluster
Repository.
Action: Verify the settings for the Oracle Cluster Repository and retry.
CLST-02901: The number of Oracle Cluster Repository keys exceeds limit of string.
Cause: clscfg ran out of internal space for keys during install.
Action: Re-run the install and specify a smaller list of nodes. When that
completes, use the add node option to add the remaining nodes.
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.
Action: Re-run the delete node operation and delete fewer nodes at once.
CLST-02903: unable to allocate string bytes of memory at location: string
Cause: clscfg was unable to allocate enough memory to service the request.
Action: Ensure that the specified amount of memory will be available and retry
the operation.
CLST-02904: failure string in SCLS API at string
Cause: clscfg was unable to query for information about the system setup.
CLST-01101 to CLST-03203 61-7
Action: Contact Oracle support with the additional information printed just after
this message.
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.
Action: Correct the command line and try again.
CLST-02906: Clustername should be between 1 and string letters.
Cause: cluster name supplied with -c argument was the wrong size.
Action: Supply an alternate cluster name of an appropriate length.
CLST-02907: unknown parameter string supplied
Cause: An unknown parameter was passed to clscfg.
Action: Use "clscfg -help" or "clscfg -concepts" for more information.
CLST-02908: unable to determine local hostname
Cause: clscfg was unable to determine the local hostname.
Action: Verify the operating system host name configuration.
CLST-02909: The requested operation requires High Availability privileges.
Cause: The current user did not have High Availability privileges.
Action: Log in as a different user and retry the operation.
CLST-02910: Failure string contacting the CRS daemon.
Cause: clscfg was unable to communicate with the CRS daemon.
Action: The requested operation must be performed from an active cluster node.
Validate the pre-existing installation on the local machine, or perform the
operation from another node.
CLST-02911: failure string contacting the CSS daemon
Cause: clscfg was unable to communicate with the CSS daemon.
Action: The requested operation must be performed from an active cluster node.
Validate the pre-existing installation on the local machine, or perform the
operation from another node.
CLST-02999: Untranslated failure: [string] [string] [string] [string] [string] [string]
Cause: A failure with no translation occurred.
Action: Contact Oracle Customer Support for more information.
CLST-03100: See the documentation for usage information.
Cause: Incorrect or insufficient arguments were passed to crsuser.
Action: Read documentation for instructions on how to use this tool.
CLST-03101: Enter the password for user string.
Cause: crsuser requires the password to register the user.
Action: Enter the requested password.
CLST-03102: Operation successful.
Cause: The operation succeeded.
Action: None
61-8 Oracle Database Error Messages
CLST-03200: internal error: [string] [string] [string] [string] [string]
Cause: A failure with no translation occurred.
Action: Contact Oracle Customer support for more information.
CLST-03201: unexpected argument: string
Cause: crsuser failed to parse the arguments, or an unknown argument was
passed.
Action: Supply the correct arguments and try again.
CLST-03202: Memory allocation failure for string bytes.
Cause: crsuser was unable to allocate memory.
Action: Free up some system memory and try again.
CLST-03203: insufficient privileges for action: string
Cause: The current user did not have sufficient privileges.
Action: Log in as another user and try again.
62
CLSU-00100 to CLSU-00912 62-1
CLSU-00100 to CLSU-00912 2 6
CLSU-00100: operating system function: string failed with error data: string
Cause: A call to an Operating System dependent service or function returned an
error indication. The message includes the name of the function and the returned
error data. The latter varies by platform but typically is numeric; on most
platforms it is the value of C "errno" after the failing call.
Action: This error normally is accompanied by other (higher-level) messages
describing the operation that is affected by the failure. It may also include one or
more of messages 101, 103, and 104 providing additional error details. All of the
messages should be examined to assess the error, which may have a very ordinary
cause and correction, such as an input file failing to open because the supplied
name was misspelled.
CLSU-00101: operating system error message: string
Cause: This message accompanies message 100 above when the Operating System
dependent error data can be converted into a text message. On most Oracle
platforms the message is a text representation of the C "errno" value reported in
message 100.
Action: See message 100.
CLSU-00102: operating system interface detected an error
Cause: This message is issued instead of messages 100-101 when a "logical" error
condition (rather than failure of an Operating System function call) is detected at
an Operating System specific interface. The error condition is further described by
accompanying message(s), including 103 and 104.
Action: This error normally is accompanied by other (higher-level) messages
describing the operation that is affected by the failure. In most cases it will also
include messages 103 and 104, providing additional details about the error. All of
the messages should be examined to assess the error, which may have a very
ordinary cause and correction, such as a missing required environment variable.
CLSU-00103: error location: string
Cause: This message accompanies message 100, 102, or 105 and identifies a
location in Oracle program code that encountered the error.
Action: See message 100, 102, or 105. This information normally is useful only
when reporting the error condition to Oracle as a potential code bug.
CLSU-00104: additional error information: string
Cause: This message accompanies message 100, 102, or 105 and supplies
additional information related to the error condition. A single error may include
multiple lines of additional information.
62-2 Oracle Database Error Messages
Action: See message 100, 102, or 105.
CLSU-00105: operating system interface has reported an internal failure
Cause: This message indicates that an Operating System dependent interface
within Oracle code has detected internal corruption or some other evidence of
internal program failure.
Action: This message may be accompanied by other (higher-level) messages
indicating the product operation that was affected by the failure. It may also be
accompanied by either or both of messages 103 and 104. All situations reporting
this condition should be referred to Oracle Support for resolution.
CLSU-00106: An improper operating system error display was attempted
Cause: During processing of an error condition, an attempt was made to format
or display Operating System dependent error data, but the error data structure
was found to indicate "no error".
Action: This error should be reported to Oracle Support for resolution.
CLSU-00200: **** Error stack contains number records, newest first:
Cause: The collection of errors about to be presented contains this many following
records.
Action: This and the following data should be reported to Oracle Support for
resolution.
CLSU-00201: **** Error stack end ****
Cause: This marks the end of a collection of errors
Action: The preceding data should be reported to Oracle Support for resolution.
CLSU-00210: CLSUUS test msg 0
Cause: A message for testing, should never be seen in the field.
Action: Report to Oracle Support.
CLSU-00211: CLSUUS test msg 1:string
Cause: A message for testing, should never be seen in the field.
Action: Report to Oracle Support.
CLSU-00212: CLSUUS test msg 2:string 2:string
Cause: A message for testing, should never be seen in the field.
Action: Report to Oracle Support.
CLSU-00213: CLSUUS test msg 3:string 2:string 3:string
Cause: A message for testing, should never be seen in the field.
Action: Report to Oracle Support.
CLSU-00214: CLSUUS test msg 4:string 2:string 3:string 4:string
Cause: A message for testing, should never be seen in the field.
Action: Report to Oracle Support.
CLSU-00215: CLSUUS test msg 5:string 2:string 3:string 4:string 5:string
Cause: A message for testing, should never be seen in the field.
Action: Report to Oracle Support.
CLSU-00216: CLSUUS test msg 6:string 2:string 3:string 4:string 5:string 6:string
CLSU-00100 to CLSU-00912 62-3
Cause: A message for testing, should never be seen in the field.
Action: Report to Oracle Support.
CLSU-00217: CLSUUS test msg 7:string 2:string 3:string 4:string 5:string 6:string
7:string
Cause: A message for testing, should never be seen in the field.
Action: Report to Oracle Support.
CLSU-00218: CLSUUS test msg 8:string 2:string 3:string 4:string 5:string 6:string
7:string 8:string
Cause: A message for testing, should never be seen in the field.
Action: Report to Oracle Support.
CLSU-00220: clsem FATAL exception: string
Cause: Something unrecoverable happened in CLSEM.
Action: Report to Oracle Support.
CLSU-00221: ERROR printed by clsecho: string
Cause: An error printed by clsecho
Action: Report to Oracle Support.
CLSU-00222: WARNING printed by clsecho: string
Cause: A warning
Action: Note the text
CLSU-00223: Info printed by clsecho: string
Cause: Information printed by clsecho
Action: Report to Oracle Support.
CLSU-00910: Named exception string string string string
Cause: Program raised an exception that does not have its own message
Action: Report to Oracle Support.
CLSU-00911: Signal string received
Cause: Program received on OS signal reported as an exception
Action: Report to Oracle Support
CLSU-00912: Operating system error: string
Cause: One or more operating system-specific errors were noticed
Action: Examine the message(s) for more information.
62-4 Oracle Database Error Messages
63
CLSW-00001 to CLSW-01000 63-1
CLSW-00001 to CLSW-01000 3 6
CLSW-00001: Cluster Wallet operation failed
Cause: This is generic internal error for Cluster Wallet.
Action: Contact Oracle Customer Support.
CLSW-00002: Out of heap memory.
Cause: The program ran out of heap memory.
Action: Retry the operation when more memory is available.
CLSW-00003: Error in the cluster registry (OCR) layer. [number] [string]
Cause: An error occurred in the cluster registry layer while performing a cluster
wallet operation.
Action: Ensure correct operation of cluster registry by inspecting ocr error (oerr
proc <ocrerror>), by using ocrcheck and ocrdump, and retry the operation.
CLSW-00004: Error in the network security layer. [number] [string]
Cause: An error occurred in the network security layer while performing a cluster
wallet operation.
Action: Inspect the network security error (oerr ora <nzerr>), and take corrective
action to ensure correct operation.
CLSW-00005: Cannot perform cluster wallet operation because one of the
parameters is NULL.
Cause: Program tried a cluster wallet operation using a NULL parameter.
Action: Check the parameters, and retry the operation.
CLSW-00006: Cannot perform cluster wallet operation because the context is
invalid.
Cause: The cluster wallet context passed was invalid.
Action: Intialize the cluster wallet and retry the operation.
CLSW-00007: Cannot perform cluster wallet operation because one of the
parameters is invalid. [number] [string]
Cause: Program tried a cluster wallet operation using an invalid parameter.
Action: Check the parameters, and retry the operation.
CLSW-00008: The cluster wallet to be created already exists.
Cause: The program tried to create a cluster wallet that already exists.
Action: Retry the operation after unsetting the CLSW_FLAGS_WALLET_CREATE
63-2 Oracle Database Error Messages
CLSW-00009: The cluster wallet to be operated on does not exist.
Cause: Program tried to access a cluster wallet which does not exist.
Action: Check to see if the cluster wallet exists and try the operation
CLSW-00010: Error in the NLS services.
Cause: An error occurred in the NLS services while performing a cluster wallet
operation.
Action: Check to see if the message file exists in $ORACLE_
HOME/has/mesg/clsw*.msb
CLSW-00011: Cannot perform cluster wallet operation because data stored in the
registry is invalid.
Cause: The data stored in the registry cannot be converted to a wallet.
Action: Delete the registry key associated with the wallet and recreate the wallet.
CLSW-00012: User is not authorized to perform the cluster wallet operation.
[number] [string]
Cause: Program tried an operation on a cluster wallet for which it does not have
permission.
Action: Check to see if program is run as the correct user.
CLSW-00013: Error in the clusterware operating system (SCLS) services. [string]
Cause: An error occurred in the SCLS services while performing a cluster wallet
operation.
Action: Check to see if NIS/LDAP on Unix and Active Directory Service on
Windows has been correctly configured.
CLSW-00014: Wallet type 'string' is not supported on this operating system.
Cause: The program tried a cluster wallet operation using a wallet type that is not
supported on current operating system.
Action: This is an internal error. Contact oracle support services.
CLSW-00015: Alias 'string' already exists in wallet type 'string'.
Cause: A request to add the specified alias to the wallet failed because the alias
already existed in the wallet.
Action: Add an alias that does not already exist in the wallet. The password for an
alias that already exists can be modified using the command 'crsctl modify wallet'.
CLSW-00016: Alias 'string' was not found in wallet type 'string'.
Cause: A request to modify the specified alias in the wallet failed because the alias
did not exist in the wallet.
Action: Ensure that the alias exists in the wallet type specified. A new alias can be
added to a wallet type using the command 'crsctl add wallet'.
CLSW-01000: Enter Password:
Cause: This is a prompt to user to enter password.
Action: Enter password.
64
CRS-00001 to CRS-29006 64-1
CRS-00001 to CRS-29006 4 6
CRS-00001: Message ID string-number not found.
Cause: The messsage for the given message id is not found in any language.
Action: Make sure the product is setup correctly on the system.
CRS-00002: string:Internal list corruption. trace file: "string"
Cause: An internal error was detected during trace file flush processing.
Action: Contact Oracle Support Services.
CRS-00003: An error occurred while attempting to open file "string". Additional
diagnostics: string
Cause: An error was encountered while attempting to open the specified file.
Action: Examine the additional diagnostics, if available, and attempt to correct
any file system environmental problems if indicated. Otherwise, contact Oracle
Support Services.
CRS-00004: logging terminated for the process. log file: "string"
Cause: One or more file system errors were encountered which caused logging to
be terminated for this process.
Action: Examine preceding Alert log messages for details on the error or errors
that occurred. Restart the process to reenable logging.
CRS-00005: file "string" deleted after close failure
Cause: This message is informational. An attempt to close the specified file failed.
The contents of the file after a close error are undefined. The file has been
successfully deleted. Log data are lost.
Action: None
CRS-00006: file rotation processing continues for file: "string"
Cause: This message is informational and indicates only that a preceding error
was not sufficiently severe to terminate file rotation which might otherwise be the
case.
Action: None
CRS-00007: failed to open new log file "string\
Cause: The file system encountered an error while attempting to open the
specified file during log file rotation. Log data are lost.
Action: Review the preceding Alert log message CRS-0011 and attempt to resolve
any file system environmental problems indicated. Otherwise, contact Oracle
Support Services.
64-2 Oracle Database Error Messages
CRS-00008: opened new file "string" after close failure
Cause: This message is informational. Log data are lost.
Action: None
CRS-00009: file "string" reopened
Cause: An error was encountered during rotation processing so that file rotation
could not proceed. The original file, which had been closed, was successfully
reopened.
Action: Review Alert log messages that precede this message that identify the file
system error or errors encountered. If the additional diagnostic data in a preceding
alert log message indicate a file system environmental problem, attempt to correct
it. Otherwise contact Oracle Support Services.
CRS-00011: An error occurred while attempting to close file "string" during file
rotation. Additional diagnostics: string
Cause: An error was encountered when attempting to close the specified file.
Action: Examine the additional diagnostics, if any, and attempt to correct any file
system environmental problems if indicated. Otherwise, contact Oracle Support
Services.
CRS-00012: An error occurred while attempting to rename file "string" to "string"
during file rotation. Additional diagnostics: string
Cause: An error was encountered when attempting to rename the source file to
the destination file.
Action: Examine the additional diagnostics, if any, and attempt to correct any file
system environmental problems if indicated. Otherwise, contact Oracle Support
Services.
CRS-00013: An error occurred while attempting to check for the existence of file
"string" during file rotation. Additional diagnostics: string
Cause: An error was encountered while attempting to determine if the specified
file existed.
Action: Examine the additional diagnostics, if any, and attempt to correct any file
system environmental problems if indicated. Otherwise, contact Oracle Support
Services.
CRS-00014: An error occurred while attempting to delete file "string" during file
rotation. Additional diagnostics: string
Cause: An error was encountered while attempting to delete the specified file.
Action: Examine the additional diagnostics, if any, and attempt to correct any file
system environmental problems if indicated. Otherwise, contact Oracle Support
Services.
CRS-00015: An error occurred while attempting to flush file "string" during file
rotation. Additional diagnostics: string
Cause: An error was encountered while an attempting to flush the specified file.
Action: Examine the additional diagnostics, if any, and attempt to correct any file
system environmental problems if indicated. Otherwise, contact Oracle Support
Services.
CRS-00016: An error occurred while attempting to free the file name object for file
"string" during file rotation. Additional diagnostics: string
CRS-00001 to CRS-29006 64-3
Cause: An error was encountered while attempting to free the file name object for
the specified file.
Action: Examine the additional diagnostics, if any, and attempt to correct any file
system environmental problems if indicated. Otherwise, contact Oracle Support
Services.
CRS-00017: An error occurred while attempting to create a file name object for file
"string" during file rotation. Additional diagnostics: string
Cause: An error was encountered while attempting to create a file name object for
the specified file.
Action: Examine the additional diagnostics, if any, and attempt to correct any file
system environmental problems if indicated. Otherwise, contact Oracle Support
Services.
CRS-00018: An error occurred while attempting to reopen file "string" during file
rotation. Additional diagnostics: string
Cause: An error was encountered while attempting to reopen the specified file.
Action: Examine the additional diagnostics, if any, and attempt to correct any file
system environmental problems if indicated. Otherwise, contact Oracle Support
Services.
CRS-00019: Log file rotation terminated. log file: "string"
Cause: One or more file system errors were encountered which caused log file
rotation to be terminated for the process. Although log file rotation has been
terminated, logging continues.
Action: Review Alert log messages that precede this alert log message that
identify the file system error or errors encountered. If the additional diagnostic
data in a preceding alert log message indicate a file system environmental
problem, attempt to correct it. Otherwise contact Oracle Support Services. To
reenable file rotation the process must be restarted.
CRS-00020: An error occurred while attempting to create a file name object for file
"string" during file open processing. Additional diagnostics: string
Cause: An error was encountered while attempting to create a file name object for
the specified file.
Action: Examine the additional diagnostics, if any, and attempt to correct any file
system environmental problems if indicated. Otherwise, contact Oracle Support
Services.
CRS-00021: An error occurred while attempting to check for the existence of file
"string" during file open processing. Additional diagnostics: string
Cause: An error was encountered while attempting to determine if the specified
file existed.
Action: Examine the additional diagnostics, if any, and attempt to correct any file
system environmental problems if indicated. Otherwise, contact Oracle Support
Services.
CRS-00022: An error occurred while attempting to change access permissions and
privileges for file "string" during file open processing. Additional diagnostics:
string
Cause: An error was encountered while attempting to change access permissions
and privileges for the specified file.
64-4 Oracle Database Error Messages
Action: Examine the additional diagnostics, if any, and attempt to correct any file
system environmental problems if indicated. Otherwise, contact Oracle Support
Services.
CRS-00023: An error occurred while attempting to create default permissions for
file "string" during file open processing. Additional diagnostics: string
Cause: An error was encountered while attempting to create default file
permissions for the specified file.
Action: Examine the additional diagnostics, if any, and attempt to correct any file
system environmental problems if indicated. Otherwise, contact Oracle Support
Services.
CRS-00024: An error occurred while attempting to create a file name object for file
"string" during file open processing. Additional diagnostics: string
Cause: An error was encountered while attempting to create a file name object for
the specified file.
Action: Examine the additional diagnostics, if any, and attempt to correct any file
system environmental problems if indicated. Otherwise, contact Oracle Support
Services.
CRS-00025: An error occurred while attempting to create a file object for file
"string" during file open processing. Additional diagnostics: string
Cause: An error was encountered while attempting to create a file object for the
specified file.
Action: Examine the additional diagnostics, if any, and attempt to correct any file
system environmental problems if indicated. Otherwise, contact Oracle Support
Services.
CRS-00026: failed to create one or more file name objects to rename "string" to
"string" during file rotation processing
Cause: An error was encountered while attempting to create one of more file
name objects for the specified files.
Action: Contact Oracle Support Services.
CRS-00027: An error occurred while attempting to determine the size of file "string"
during file open processing. Additional diagnostics: string
Cause: An error was encountered while attempting to determine the size of the
specified file.
Action: Examine the additional diagnostics, if any, and attempt to correct any file
system environmental problems if indicated. Otherwise, contact Oracle Support
Services.
CRS-00028: An error occurred while attempting to write the banner for file "string".
Additional diagnostics: string
Cause: An error was encountered while attempting to write the banner record to
the specified file.
Action: Examine the additional diagnostics, if any, and attempt to correct any file
system environmental problems if indicated. Otherwise, contact Oracle Support
Services.
CRS-00029: An error occurred while attempting to flush file "string" after the
banner record was written. Additional diagnostics: string
CRS-00001 to CRS-29006 64-5
Cause: An error was encountered while attempting to flush the specified file after
writing the banner record.
Action: Examine the additional diagnostics, if any, and attempt to correct any file
system environmental problems if indicated. Otherwise, contact Oracle Support
Services.
CRS-00030: An invalid file type was encountered while attempting to perform file
synchronization. Additional diagnostics: string ftype: number
Cause: An invalid file type specification was encountered by file synchronization
services.
Action: Contact Oracle Support Services.
CRS-00031: An error occurred while attempting to flush file "string" during file
synchronization processing. Additional diagnostics: string
Cause: An error was encountered while attempting to flush the specified file
during file synchronization processing.
Action: Examine the additional diagnostics, if any, and attempt to correct any file
system environmental problems if indicated. Otherwise, contact Oracle Support
Services.
CRS-00032: An error occurred while attempting to create a file object for file
"string" during generate-file-name processing. Additional diagnostics: string
Cause: An error was encountered while attempting to create a file object for the
specified file.
Action: Examine the additional diagnostics, if any, and attempt to correct any file
system environmental problems if indicated. Otherwise, contact Oracle Support
Services.
CRS-00033: An error occurred while attempting to create a file object for file
"string" during generate-file-name processing. Additional diagnostics: string
Cause: An error was encountered while attempting to create a file object for the
specified file.
Action: Examine the additional diagnostics, if any, and attempt to correct any file
system environmental problems if indicated. Otherwise, contact Oracle Support
Services.
CRS-00034: An error occurred while attempting to open file "string" during
generate-file-name processing. Additional diagnostics: string
Cause: An error was encountered while attempting to open the specified file.
Action: Examine the additional diagnostics, if any, and attempt to correct any file
system environmental problems if indicated. Otherwise, contact Oracle Support
Services.
CRS-00035: An invalid pointer to an internal control structure was encountered
while attempting to open a log file. Additional diagnostics: string
Cause: An invalid pointer was encountered when attempting to open a file.
Logging is disabled for the process.
Action: Contact Oracle Support Services.
CRS-00036: An error occurred while attempting to open file "string".
Cause: An error was encountered while attempting to open the specified file.
64-6 Oracle Database Error Messages
Action: Review preceding Alert log messages and attempt to resolve any file
system environmental problems indicated. Otherwise, contact Oracle Support
Services
CRS-00037: An error occurred while attempting to write to file "string". Additional
diagnostics: string
Cause: An error was encountered while attempting to write to the specified file.
Logging is disabled for the process.
Action: Review preceding Alert log messages and attempt to resolve any file
system environmental problems indicated. Otherwise, contact Oracle Support
Services
CRS-00038: An invalid pointer to an internal control structure was encountered
while attempting to open a trace file. Additional diagnostics: string
Cause: An invalid pointer was encountered when attempting to open a trace file.
Tracing is disabled for the process.
Action: Contact Oracle Support Services.
CRS-00039: An error occurred while attempting to open trace file "string".
Cause: An error was encountered while attempting to open the specified file.
Tracing is disabled for the process.
Action: Review preceding Alert log messages and attempt to resolve any file
system environmental problems indicated. Otherwise, contact Oracle Support
Services
CRS-00040: Trace logging terminated for the process. trace file: "string"
Cause: One or more file system errors were encountered which caused tracing to
be terminated for this process.
Action: Examine preceding Alert log messages for details on the error or errors
that occurred. Restart the process to reenable logging.
CRS-00041: Trace file rotation terminated for the process. Trace file: "string"
Cause: One or more file system errors were encountered which caused trace file
rotation to be terminated for the process. Although trace file rotation has been
terminated, tracing continues.
Action: Review Alert log messages that precede this alert log message that
identify the file system error or errors encountered. If the additional diagnostic
data in a preceding alert log message indicate a file system environmental
problem, attempt to correct it. Otherwise contact Oracle Support Services. To
reenable trace file rotation the process must be restarted.
CRS-00184: Cannot communicate with the CRS daemon.
Cause: The CRS daemon on the local node is either not running or there was an
internal communication error with the CRS daemon.
Action: Check if the CRS daemon process is running on the local node.
CRS-00210: Could not find resource 'string'.
Cause: An attempt was made to operate on a resource that is not registered.
Action: Ensure that the resource name is specified correctly using the command
'crsctl status resource'.
CRS-00211: Resource 'string' has already been registered.
Cause: An attempt was made to register a resource that is already registered.
CRS-00001 to CRS-29006 64-7
Action: Ensure that the resource name is specified correctly and retry the
command.
CRS-00213: Could not register resource 'string'.
Cause: There was an internal error while registering the resource.
Action: Check the CRS daemon log file.
CRS-00214: Could not unregister resource 'string'.
Cause: There was an internal error while unregistering the resource.
Action: Check the CRS daemon log file.
CRS-00215: Could not start resource 'string'.
Cause: There was an internal error while starting the resource.
Action: Check the CRS daemon log file.
CRS-00216: Could not stop resource 'string'.
Cause: There was an internal error while stopping the resource.
Action: Check the CRS daemon log file.
CRS-00217: Could not relocate resource 'string'.
Cause: There was an internal error while relocating the resource.
Action: Check the CRS daemon log file.
CRS-00218: Could not restart the resource 'string' on the original node.
Cause: There was an internal error while restarting the resource.
Action: Check the CRS daemon log file.
CRS-00219: Could not update resource 'string'.
Cause: There was an internal error while updating the resource.
Action: Check the CRS daemon log file.
CRS-00220: Resource 'string' has invalid resource profile.
Cause: Invalid attributes in the resource profile.
Action: Run the command 'crsctl status type' to identify the invalid attributes.
Modify these attributes using the command 'crsctl modify type'.
CRS-00221: Resource 'string''s action script cannot be found.
Cause: The action script has been deleted from the file system.
Action: Run 'crsctl status resource -p' to determine the action script location, and
check for its existence.
CRS-00223: Resource 'string' has placement error.
Cause: Based on the placement policy for the resource, there was no available host
to which the resourse could failover or start.
Action: Check the target host for the resource and restart the resource using the
'crsctl start resource' command.
CRS-00230: Member 'string' is not in the cluster.
Cause: The hostname was not found in the cluster.
Action: Check the hostnames in the cluster.
CRS-00232: Cluster member is down. Cannot perform operation.
64-8 Oracle Database Error Messages
Cause: The node on which CRS is attempting to start the resource is down.
Action: Start the node and retry the operation.
CRS-00233: Resource or relatives are currently involved with another operation.
Cause: Another CRS daemon was operating on the same resource.
Action: Wait for a minute and try the command or operation again.
CRS-00253: CRS configuration error, the CRS default directory is not set in Oracle
Cluster Registry.
Cause: The Oracle Cluster Registry key which contains the user default CRS key
is not initialised.
Action: Check the CRS configuration. If necessary reinstall CRS.
CRS-00254: authorization failure
Cause: The user permissions were insufficient to operate on the resource.
Action: Check the permissions associated with the resource using 'crsctl getperm
resource' and set the appropriate user permissions using 'crsctl setperm resource'.
CRS-00255: CRSD is not running in privileged mode. Insufficient permissions to
run this command.
Cause: The CRS daemon was not running as the privileged user.
Action: Check if the CRS daemon is running as root (UNIX) or Administrator
(Windows).
CRS-00256: Username conflicts with the owner of the resource.
Cause: An attempt was made to give separate user level permissions for the
owner of the resource.
Action: Check the owner of the resource and the user being given permissions.
CRS-00257: Groupname conflicts with the primary group of the resource.
Cause: An attempt was made to give separate group level permissions for the
primary group of the resource.
Action: Check the primary group of the resource and the group being given
permissions.
CRS-00258: Invalid ACL string format.
Cause: An invalid permission string (ACL) was supplied.
Action: Check the syntax of the permission string (ACL).
CRS-00259: Owner of the resource does not belong to the group.
Cause: The owner of the resource does not belong to the expected group.
Action: If this resource is owned by the root user, check if the root user belongs to
the dba group.
CRS-00271: CRSD shutdown is already in progress.
Cause: crsctl stop command is issued before waiting for a prior stop command to
finish.
Action: Wait for the currently running shutdown command to complete before
issuing subsequent command.
CRS-00272: This command remains for backward compatibility only
Cause: A deprecated command was issued.
CRS-00001 to CRS-29006 64-9
Action: For all new use cases, use the replacement.
CRS-00273: This command is deprecated and has been replaced by 'string'
Cause: A deprecated command was issued.
Action: For all new use cases, use the replacement.
CRS-00274: This command is deprecated and its functionality incorporated into
'string'
Cause: A deprecated command was issued.
Action: For all new use cases, use the replacement.
CRS-00275: This command is not supported in Oracle Restart environment.
Cause: One of the "crs_" commands was issued in an Oracle Restart environment.
Action: Use the corresponding crsctl command.
CRS-00402: Could not make safe directory('string')
Cause: Unable to create safe directory.
Action: Check if you have proper permissions and sufficient space on the disk to
create the directory.
CRS-00403: Could not change working directory to safe directory('string')
Cause: Unable to change directory to safe directory.
Action: Check if safe directory exists and if you have proper permissions.
CRS-00406: Could not create lock directory ('string')
Cause: Unable to create lock directory.
Action: Check if you have proper permissions and sufficient space on the disk to
create the directory.
CRS-00407: Another CRSD may be running, could not obtain lock file 'string'.
Cause: Unable to obtain lock file as another CRSD may be running.
Action: Stop the existing CRSD before attempting to start CRSD again.
CRS-00413: Could not initialize the Cluster Synchronization Services context
Cause: Unable to communicate with the cluster services.
Action: Verify that the Cluster Synchronization Services Daemon is properly
configured and is running.
CRS-00414: Could not establish Event Manager connection
Cause: Unable to communicate with Event Manager daemon.
Action: Run the 'crsctl check evmd' command to determine whether Event
Manager daemon is properly configured and is running.
CRS-00451: CRS configuration error, unable to initialize Oracle Cluster Registry.
Cause: The Oracle Cluster Registry that contains information about the CRS
configuration is unavailable.
Action: Check the OCR configuration using the ocrcheck utility and resolve any
issues it reports. If the problem persists, contact Oracle Support Services.
CRS-00452: CRS configuration error, unable to find CRSD Connection Information
in Oracle Cluster Registry.
64-10 Oracle Database Error Messages
Cause: The Oracle Cluster Registry key which contains the user default CRSD
connection is not initialized.
Action: Check the OCR configuration using the ocrcheck utility and resolve any
issues it reports. If the problem persists, contact Oracle Support Services.
CRS-00453: CRS configuration error, unable to find Instance Information in Oracle
Cluster Registry.
Cause: The Oracle Cluster Registry key which contains the Instance's information
is not initialized.
Action: Check the OCR configuration using the ocrcheck utility and resolve any
issues it reports. If the problem persists, contact Oracle Support Services.
CRS-00471: Node number is not found
Cause: Cluster Synchronization Services is unable to retrieve the node name.
Action: Verify your cluster installation, including any vendor cluster ware. If
necessary reinstall the cluster.
CRS-00472: Node name is not found
Cause: Cluster Services is unable to retrieve the node name.
Action: Verify your cluster installation, including any vendor cluster ware. If
necessary reinstall the cluster.
CRS-00602: Encountered operating system error 'string' while authenticating user
'string'. Details at string in string.
Cause: The operating system experienced an error when Clusterware
authenticated the specified user.
Action: Verify that the authentication service in your environment is functioning
correctly. If the problem persists, contact Oracle Support Services.
CRS-00700: Oracle High Availability Service aborted due to failure to allocate
memory. Details at string in string.
Cause: Memory allocation failed.
Action: Restart Cluster Ready Service using 'crsctl stop crs -f' followed by 'crsctl
start crs'. If the problem persists, contact Oracle Support Services.
CRS-00701: Oracle High Availability Service aborted due to failure to obtain
identity of the running process. Details at string in string.
Cause: Failed to retrieve user id.
Action: Check <crs_home> owner and restart Cluster Ready Service using 'crsctl
stop crs -f' followed by 'crsctl start crs'. If the problem persists, contact Oracle
Support Services.
CRS-00702: Oracle High Availability Service aborted due to failure to run as
privileged user. Details at string in string.
Cause: Oracle High Availability Service was not running as privileged user.
Action: On Unix, restart Cluster Ready Service as privileged user using 'crsctl
stop crs -f' followed by 'crsctl start crs'. On Windows, check the privileges of the
Oracle High Availability Service and restart Cluster Ready Service using 'crsctl
stop crs -f' followed by 'crsctl start crs' If the problem persists, contact Oracle
Support Services.
CRS-00703: Oracle High Availability Service aborted due to failure to initialize the
communication context. Details at string in string.
CRS-00001 to CRS-29006 64-11
Cause: The network layer initialization failed.
Action: Restart Cluster Ready Service using 'crsctl stop crs -f' followed by 'crsctl
start crs'. If the problem persists, contact Oracle Support Services.
CRS-00704: Oracle High Availability Service aborted due to Oracle Local Registry
error [string]. Details at string in string.
Cause: Oracle Local Registry aborted with an error. Look at the associated error
message to determine the underlying issue.
Action: Solve the underlying issue and restart Cluster Ready Service using 'crsctl
stop crs -f' followed by 'crsctl start crs'. If the problem persists, contact Oracle
Support Services.
CRS-00708: Oracle High Availability Service aborted due to failure to retrieve
ORA_CRS_HOME environment variable. Details at string in string.
Cause: An environment variable required by Oracle High Availability Service
failed to be set at initialization.
Action: Run 'rootcrs.pl -unlock' followed by 'rootcrs.pl -patch' and restart Cluster
Ready Service using 'crsctl stop crs -f' followed by 'crsctl start crs'. If the problem
persists, contact Oracle Support Services.
CRS-00709: Oracle High Availability Service aborted due to failure to initialize
ORA_CRS_HOME path. Details at string in string.
Cause: Oracle High Availability Service ORA_CRS_HOME path could not be
initialized.
Action: Check for execute permissions on the Grid Infrastructure home or <crs_
home> and restart Cluster Ready Service using 'crsctl stop crs -f' followed by
'crsctl start crs'. If the problem persists, contact Oracle Support Services.
CRS-00712: Oracle High Availability Service aborted due to failure to initialize the
network layer with error [number]. Details at string in string.
Cause: The network layer initialization failed.
Action: Restart Cluster Ready Service using 'crsctl stop crs -f' followed by 'crsctl
start crs'. If the problem persists, contact Oracle Support Services.
CRS-00713: An error occurred initializing the Reboot Advisory Monitor: error code
[number]. Details at string in string.
Cause: An error occurred initializing the Reboot Advisory Monitor component of
Oracle High Availability Service. This error is not fatal; Oracle High Availability
Service processing continues.
Action: Examine the Clusterware alert log for messages providing details of the
error. If the error is correctable, do so and then restart Cluster Ready Service using
'crsctl stop crs -f' followed by 'crsctl start crs'. If no messages are found or you do
not understand how to correct the problem, contact Oracle Support Services.
CRS-00714: Oracle Clusterware Release number.number.number.number.number.
Cause: The Oracle High Availability Services Daemon (OHASD) was started as
part of a general start of the Oracle Clusterware stack on this node.
Action: None
CRS-00715: Oracle High Availability Service has timed out waiting for init.ohasd to
be started.
Cause: The Oracle High Availability Service requires that initd start init.ohasd to
successfully initialize.
64-12 Oracle Database Error Messages
Action: 1. Check the run level to ensure that you are in the correct runlevel using
cluvfy ("cluvfy stage -pre crsinst -n <nodelist>"); 2. If the run level is correct,
diagnose the reason for init.d not starting init.ohasd.
CRS-00800: Cluster Ready Service aborted due to failure to allocate memory.
Details at string in string.
Cause: Memory allocation failed.
Action: Restart Cluster Ready Service using 'crsctl stop crs -f' followed by 'crsctl
start crs'. If the problem persists, contact Oracle Support Services.
CRS-00801: Cluster Ready Service aborted due to failure to obtain identity of the
running process. Details at string in string.
Cause: Failed to retrieve user id.
Action: Check <crs_home> owner and restart Cluster Ready Service using 'crsctl
stop crs -f' followed by 'crsctl start crs'. If the problem persists, contact Oracle
Support Services.
CRS-00802: Cluster Ready Service aborted due to failure to run as privileged user.
Details at string in string.
Cause: Cluster Ready Service was not running as privileged user.
Action: On Unix, restart Cluster Ready Service as privileged user using 'crsctl
stop crs -f' followed by 'crsctl start crs'. On Windows, check the privileges of the
Oracle High Availability Service and restart Cluster Ready Service using 'crsctl
stop crs -f' followed by 'crsctl start crs' If the problem persists, contact Oracle
Support Services.
CRS-00803: Cluster Ready Service aborted due to failure to initialize the
communication context. Details at string in string.
Cause: The network layer initialization failed.
Action: Restart Cluster Ready Service using 'crsctl stop crs -f' followed by 'crsctl
start crs'. If the problem persists, contact Oracle Support Services.
CRS-00804: Cluster Ready Service aborted due to Oracle Cluster Registry error
[string]. Details at string in string.
Cause: Oracle Cluster Registry aborted with an error. Look at the associated error
message to determine the underlying issue.
Action: Solve the underlying issue and restart Cluster Ready Service using 'crsctl
stop crs -f' followed by 'crsctl start crs'. If the problem persists, contact Oracle
Support Services.
CRS-00805: Cluster Ready Service aborted due to failure to communicate with
Cluster Synchronization Service with error [number]. Details at string in string.
Cause: The Cluster Synchronization Service is unreachable.
Action: Restart Cluster Ready Service using 'crsctl stop crs -f' followed by 'crsctl
start crs'. If the problem persists, contact Oracle Support Services.
CRS-00806: Cluster Ready Service aborted due to failure to retrieve the local node
name. Details at string in string.
Cause: The Cluster Synchronization Service node name is not accessible.
Action: Restart Cluster Ready Service using 'crsctl stop crs -f' followed by 'crsctl
start crs'. If the problem persists, contact Oracle Support Services.
CRS-00001 to CRS-29006 64-13
CRS-00807: Cluster Ready Service aborted due to failure to check version
compatibility. Details at string in string.
Cause: Oracle Cluster Registry content is not compatible with this version of
Cluster Ready Service.
Action: Start the correct version of Cluster Ready Service. If the problem persists,
contact Oracle Support Services.
CRS-00808: Cluster Ready Service aborted due to failure to retrieve ORA_CRS_
HOME environment variable. Details at string in string.
Cause: An environment variable required by Cluster Ready Service failed to be
set at initialization.
Action: Run 'rootcrs.pl -unlock' followed by 'rootcrs.pl -patch' and restart Cluster
Ready Service using 'crsctl stop crs -f' followed by 'crsctl start crs'. If the problem
persists, contact Oracle Support Services.
CRS-00809: Cluster Ready Service aborted due to failure to initialize ORA_CRS_
HOME path. Details at string in string.
Cause: Cluster Ready Service ORA_CRS_HOME path could not be initialized.
Action: Check for execute permissions on the Grid Infrastructure home or <crs_
home> and restart Cluster Ready Service using 'crsctl stop crs -f' followed by
'crsctl start crs'. If the problem persists, contact Oracle Support Services.
CRS-00810: Cluster Ready Service aborted due to failure to communicate with
Event Management Service with error [number]. Details at string in string.
Cause: The Event Management Service is unreachable.
Action: Restart Cluster Ready Service using 'crsctl stop crs -f' followed by 'crsctl
start crs'. If the problem persists, contact Oracle Support Services.
CRS-00811: Cluster Ready Service aborted due to failure to build dependency
graph. Details at string in string.
Cause: There exists inconsistencies in the resources dependencies.
Action: Check the resources dependencies and restart Cluster Ready Service
using 'crsctl stop crs -f' followed by 'crsctl start crs'. If the problem persists, contact
Oracle Support Services.
CRS-00812: Cluster Ready Service aborted due to failure to initialize the network
layer with error [number]. Details at string in string.
Cause: The network layer initialization failed.
Action: Restart Cluster Ready Service using 'crsctl stop crs -f' followed by 'crsctl
start crs'. If the problem persists, contact Oracle Support Services.
CRS-00813: Cluster Ready Service aborted due to failure to initialize the network
layer with error [string]. Details at string in string.
Cause: The network layer initialization failed.
Action: Restart Cluster Ready Service using 'crsctl stop crs -f' followed by 'crsctl
start crs'. If the problem persists, contact Oracle Support Services.
CRS-00814: Cluster Ready Service aborted due to failure to start thread with error
[number]. Details at string in string.
Cause: Thread creation failed.
Action: Restart Cluster Ready Service using 'crsctl stop crs -f' followed by 'crsctl
start crs'. If the problem persists, contact Oracle Support Services.
64-14 Oracle Database Error Messages
CRS-01001: The OCR was formatted using version number.
Cause: Successfully formatted the OCR location(s).
Action: None
CRS-01002: The OCR was restored from file string.
Cause: The OCR was successfully restored from a backup file as requested by the
user.
Action: None
CRS-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
CRS-01004: The OCR was imported from string.
Cause: Successfully imported the OCR contents from a file.
Action: None
CRS-01005: The Oracle Clusterware upgrade was completed. Version has changed
from [number, string] to [number, string]. Details in string.
Cause: The Oracle Clusterware was successfully upgraded to a version.
Action: None
CRS-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.
CRS-01007: The OCR/OCR mirror location was replaced by string.
Cause: The OCR location was successfully replaced as requested by the user.
Action: None
CRS-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 Support Services.
CRS-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.
CRS-01010: The OCR mirror location string was removed.
Cause: The OCR location was successfully removed as requested by the user.
Action: None
CRS-00001 to CRS-29006 64-15
CRS-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
Support Services.
CRS-01012: The OCR service started on node string.
Cause: The OCR was successfully started.
Action: None
CRS-01013: The OCR location in an ASM disk group is inaccessible. Details in
string.
Cause: An error occurred while accessing the OCR file in an ASM disk group.
Action: Use the 'asmcmd' command to verify if the ASM instance is active. If the
ASM instance aborted, it will be restarted automatically. Use 'ocrcheck -config' to
discover the OCR locations configured, and verify using 'asmcmd' that the disk
group in question is mounted. Mount the disk group if it is not mounted. Validate
if the behavior is limited to one node or whether it occurs across all of the nodes in
the cluster. If nothing works, use the 'ocrconfig' command with the '-replace' or
'-delete' option to replace or remove the OCR location.
CRS-01014: Failed to import Oracle Cluster Registry from file string
Cause: Unable to read data from the import file and import to the cluster registry
Action: Check availability of the cluster registry and the details of the failure from
the log file
CRS-01015: A request to terminate the Cluster Ready Service on node string
completed successfully. Details at string in string.
Cause: The Cluster Ready Service on the above listed node did not respond to an
earlier request within the specified time. The Cluster Ready Service will be
terminated to prevent any possible cluster hangs.
Action: Check the Oracle Clusterware alert log on the listed node for any
problems. Check for any reason that might not allow the Cluster Ready Service to
run optimally on the listed node. Verify network accessibility to the listed node
from other nodes in the cluster. If the problem persists, contact Oracle Support
Services.
CRS-01016: The Cluster Ready Service on this node terminated because it detected
a failure while upgrading the Oracle Cluster Registry format. Details at string in
string.
Cause: The Cluster Ready Service on the node coordinating the upgrade of the
Oracle Cluster Registry format terminated.
Action: The Oracle Cluster Registry format upgrade will be completed by another
node in the cluster. The Cluster Ready Service on the node listed above will be
automatically restarted, and will be able to function as soon as the upgrade
completes. If the problem persists, contact Oracle Support Services.
64-16 Oracle Database Error Messages
CRS-01017: The Cluster Ready Service on this node terminated because it was
unable to open the import file while upgrading the Oracle
再分享一下我老师大神的人工智能教程吧。零基础！通俗易懂！风趣幽默！还带黄段子！希望你也加入到我们人工智能的队伍中来！http://www.captainbed.net