12C ORA-错误汇总20

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 ), 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 ), 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 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 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 "); 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 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 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 Cluster Registry
format. Details at string in string.
Cause: There was a failure accessing the import file on this node. The Cluster
Ready Service on this node may not have been active during the Oracle Cluster
Registry format upgrade.
Action: The Oracle Cluster Registry format upgrade will be completed by another
node in the cluster. The Cluster Ready Service on this node will be automatically
restarted, and will be able to function as soon as the upgrade completes. If the
problem persists, contact Oracle Support Services.
CRS-01018: The Cluster Ready Service on this node terminated because the OCR
configuration on this node is invalid. Details at string in string.
Cause: The OCR configuration on this node did not match with the OCR
configuration on the other nodes in the cluster.
Action: The OCR configuration on this node is automatically repaired and the
Cluster Ready Service will be automatically restarted. If the problem persists,
contact Oracle Support Services.
CRS-01019: The OCR Service exited on host string. Details in string
Cause: The OCR Service exited due to an internal error.
Action: Determine whether the service has restarted. Collect Clusterware alert log
and the CRSD log indicated in the message and contact Oracle Support Services.
CRS-01020: The Oracle Cluster Registry has invalid contents. Details at string in
string.
Cause: Some of the Oracle Cluster Registry contents were invalid.
Action: Check the log file indicated in the message for more details. Use the
'ocrcheck' command to detect errors, and the 'ocrdump' command to review the
registry contents. If problems exist, the registry may need to be recovered or
restored. If the problem persists, contact Oracle Support Services.
CRS-01021: The Oracle Cluster Registry backup file in an ASM disk group is
inaccessible. Details in string.
Cause: Oracle Cluster Registry backup location did not exists, wasn't mounted
correctly, or did not have the required permissions.
Action: Ensure that the backup location exists, that it is mounted correctly and
visible to all nodes in the cluster, and that its permissions are correct. Check the
ASM entries in the alert log file for more details.
CRS-01022: The Oracle Clusterware was forcibly upgraded without upgrading
nodes string. Version has changed from [number, string] to [number, string].
Details in string.
Cause: Oracle Clusterware was forcibly upgraded when the above listed nodes
were not upgraded.
Action: Delete the above listed nodes using the procedure documented in the
Oracle Clusterware documentation. If the nodes later become accessible, they can
be added back into the cluster.
CRS-01024: The Cluster Ready Service on this node terminated because the ASM
instance was not active on this node. Details at string in string.
Cause: The Cluster Ready Service on the node terminated because the ASM
instance was no longer active.
CRS-00001 to CRS-29006 64-17
Action: The Cluster Ready Services on this node will be automatically restarted. If
the problem persists, contact Oracle Support Services.
CRS-01025: The Oracle Clusterware was upgraded to [string] on all nodes, but the
cluster operating version is still [string]. Details in [string].
Cause: The cluster upgrade did not complete because the root upgrade script
failed on the last node, the root upgrade script was interrupted by the user, or the
cluster upgrade is ongoing.
Action: Check the Oracle Clusterware alert log on all nodes for any problems.
Rerun the root upgrade script on the last node to completion, and ensure that the
cluster operating version has changed using the 'crsctl query crs activeversion'
command. If the problem persists, run diagcollection.pl and contact Oracle
Support Services.
CRS-01026: The Oracle Clusterware patch has completed. The patch level has
changed from [number] to [number]. Details in string.
Cause: The Oracle Clusterware was successfully patched.
Action: None
CRS-01027: The Oracle Cluster Registry (OCR) location in an ASM disk group
[string] does not have sufficient space. Details at string in string.
Cause: Unable to increase the size of OCR file in the above listed disk group as
the disk group was out of space.
Action: Delete unused files from the disk group or add additional disks to the
disk group. Refer to Oracle Clusterware administration documentation to know
about the space requirements for OCR in ASM disk group.
CRS-01028: The Oracle Cluster Registry backup location string is inaccessible from
node string. Details in string.
Cause: The backup location provided did not exist, was not mounted correctly, or
did not have the required permissions.
Action: Ensure that the backup location exists, that it is mounted correctly and
visible to all nodes in the cluster, and that the permissions are correct. If the
backup location is an ASM disk group, check the ASM entries in the alert log file
for more details.
CRS-01110: The Oracle Clusterware upgrade is in unknown state [number].
Cause: There was an internal error upgrading the Oracle Clusterware.
Action: Retry the 'crsctl set crs activeversion' command. If the problem persists,
contact Oracle Support Services.
CRS-01111: Error upgrading the Oracle Clusterware. Details [string].
Cause: There was an internal error upgrading the Oracle Clusterware.
Action: Verify using the 'crsctl check crs' command that the CRS Service running.
Retry the 'crsctl set crs activeversion' command. If the problem persists, contact
Oracle Support Services.
CRS-01112: Failed to set the Oracle Clusterware operating version string
Cause: There was an internal error upgrading the Oracle Clusterware.
Action: Retry the 'crsctl set crs activeversion' command. If the problem persists,
contact Oracle Support Services.
CRS-01114: Invalid active version [string] passed
64-18 Oracle Database Error Messages
Cause: An invalid active version was passed.
Action: Use the 'crsctl query crs softwareversion' command to retrieve a valid
active version.
CRS-01115: Oracle Clusterware has already been upgraded.
Cause: Oracle Clusterware is already running in highest possible operating
version.
Action: None
CRS-01116: Oracle Clusterware upgrade has been aborted.
Cause: One of the Oracle Clusterware components have failed to upgrade within
the expected time.
Action: Check the Oracle Clusterware alert log and the CRS daemon log for
additional information.
CRS-01117: Error upgrading the Oracle Clusterware.
Cause: An attempt was made to change the Oracle Clusterware operating version
before all nodes were upgraded.
Action: Run root.sh script on all nodes in the cluster. If the problem persists,
contact Oracle Support Services.
CRS-01119: Unable to complete Oracle Clusterware upgrade while nodes string
have not yet upgraded
Cause: An attempt was made to change the Oracle Clusterware operating version
before all known nodes had been upgraded. Note that some of the nodes listed in
the message may no longer be current or recent cluster members.
Action: Issue the 'olsnodes' command to list current and recent cluster members.
Any nodes listed in the error message, but not listed by 'olsnodes' have not been
active recently, and should be deleted using the procedure documented in the
Oracle Clusterware documentation. The currently or recently active cluster
members listed by 'olsnodes' should be upgraded, or, if no longer needed, deleted:
1) Run the rootupgrade.sh script on each node to be retained. 2) Delete nodes no
longer desired using the procedure documented in the Oracle Clusterware
documentation. Once all of the nodes listed in the message have been upgraded or
deleted, run the rootupgrade.sh script on an upgraded node to complete the
upgrade. If one or more nodes could not upgraded or deleted, forcibly upgrade
the cluster using the procedure documented in the Oracle Clusterware
documentation.
CRS-01121: Oracle Clusterware was forcibly upgraded without upgrading nodes
string.
Cause: Oracle Clusterware was forcibly upgraded when the above listed nodes
were not upgraded.
Action: Delete the above listed nodes using the procedure documented in the
Oracle Clusterware documentation. If the nodes later become accessible, they can
be added back into the cluster.
CRS-01124: Invalid active version [string] retrieved.
Cause: An invalid active version was retrieved from the configuration.
Action: Contact Oracle Support Services.
CRS-01129: Rejecting rolling upgrade mode change because Oracle ASM is in an
unexpected state.
CRS-00001 to CRS-29006 64-19
Cause: A request to reset rolling upgrade mode was rejected because Oracle ASM
was in an unexpected state.
Action: Retry the 'crsctl set crs activeversion' command. If the problem persists,
contact Oracle Support Services.
CRS-01130: Rejecting rolling upgrade mode change because Oracle IOServer is in
an unexpected state.
Cause: A request to reset rolling patch mode was rejected because Oracle
IOServer was in an unexpected state.
Action: Retry the 'crsctl set crs activeversion' command. If the problem persists,
contact Oracle Support Services.
CRS-01131: The cluster was successfully set to rolling upgrade mode.
Cause: A 'crsctl start rollingupgrade' command completed successfully.
Action: None
CRS-01132: The cluster is in rolling upgrade mode.
Cause: The cluster was already running in rolling upgrade mode.
Action: None
CRS-01133: There was an error setting Oracle Clusterware to rolling upgrade mode.
Cause: There was an error setting Oracle Clusterware to rolling upgrade mode.
Action: Verify using the 'crsctl check crs' command that the Cluster Ready
Services (CRS) is active, and inspect the accompanying Clusterware-specific error
messages to see if there is a correctable problem. If so, correct the problem and
retry the 'crsctl start rollingupgrade' command. If the problem persists, contact
Oracle Support Services.
CRS-01134: There was an error setting Oracle ASM to rolling upgrade mode.
Cause: There was an error setting Oracle ASM to rolling upgrade mode.
Action: Verify using the 'srvctl status asm' command that the Oracle ASM
instance is active, and inspect the accompanying ASM-specific error messages to
see if there is a correctable problem. If so, correct the problem and retry the 'crsctl
start rollingupgrade' command. If the problem persists, contact Oracle Support
Services.
CRS-01135: There was an error setting Oracle IOServer to rolling upgrade mode.
Cause: There was an error setting Oracle IOServer to rolling upgrade mode.
Action: Verify using the 'srvctl status ioserver' command that the Oracle IOServer
instance is active, and inspect the accompanying IOServer-specific error messages
to see if there is a correctable problem. If so, correct the problem and retry the
'crsctl start rollingupgrade' command. If the problem persists, contact Oracle
Support Services.
CRS-01136: Rejecting the rolling upgrade mode change because the cluster is being
patched.
Cause: The rolling upgrade mode change was rejected because the cluster was
being patched.
Action: Complete applying the patch on all nodes in the cluster before retrying
the 'crsctl start rollingupgrade' command.
CRS-01137: Rejecting the rolling upgrade mode change because the cluster was
forcibly upgraded.
64-20 Oracle Database Error Messages
Cause: The rolling upgrade mode change was rejected because the cluster was
forcibly upgraded.
Action: Delete the nodes that were not upgraded using the procedure
documented in the Oracle Clusterware documentation. Retry the 'crsctl start
rollingupgrade' command after completing the above steps.
CRS-01138: There was an error setting the cluster to rolling upgrade mode.
Cause: There was an internal error setting the cluster to rolling upgrade mode.
Action: Retry the 'crsctl start rollingupgrade' command. If the problem persists,
contact Oracle Support Services.
CRS-01139: Invalid version [string] passed
Cause: An invalid version was passed.
Action: Use the version returned by the 'crsctl query crs releaseversion' command
issued from the Oracle Grid Infrastructure home to which you are upgrading.
CRS-01140: The passed version [string] cannot be less than or equal to the release
version [string].
Cause: A version was passed that was less than or equal to the release version.
Action: Verify that the version of the Oracle Grid Infrastructure home to be
upgraded to is greater than the current Oracle Grid Infrastructure home.
CRS-01141: The passed version [string] cannot be less than or equal to the cluster
active version [string].
Cause: A version was passed that was less than or equal to the cluster active
version.
Action: Verify that the version of the Oracle Grid Infrastructure home to be
upgraded to is greater than the cluster active version.
CRS-01142: The cluster cannot be set to rolling upgrade mode because Oracle
Clusterware is not active on at least one remote node.
Cause: The cluster could not be set to rolling upgrade mode because Oracle
Clusterware was not active on any of the remote nodes.
Action: Start Oracle Clusterware on at least one remote node and retry the 'crsctl
start rollingupgrade' command, or retry upgrade using the non-rolling option.
CRS-01151: The cluster was successfully set to rolling patch mode.
Cause: A 'crsctl start rollingpatch' command completed successfully.
Action: None
CRS-01152: The cluster is in rolling patch mode.
Cause: The cluster was already running in rolling patch mode.
Action: None
CRS-01153: There was an error setting Oracle Clusterware to rolling patch mode.
Cause: There was an error setting Oracle Clusterware to rolling patch mode.
Action: Verify using the 'crsctl check crs' command that the Cluster Ready
Services (CRS) is active, and inspect the accompanying Clusterware-specific error
messages to see if there is a correctable problem. If so, correct the problem and
retry the 'crsctl start rollingpatch' command. If the problem persists, contact Oracle
Support Services.
CRS-00001 to CRS-29006 64-21
CRS-01154: There was an error setting Oracle ASM to rolling patch mode.
Cause: There was an error setting Oracle ASM to rolling patch mode.
Action: Verify using the 'srvctl status asm' command that the Oracle ASM
instance is active, and inspect the accompanying ASM-specific error messages to
see if there is a correctable problem. If so, correct the problem and retry the 'crsctl
start rollingpatch' command. If the problem persists, contact Oracle Support
Services.
CRS-01155: There was an error setting Oracle IOServer to rolling patch mode.
Cause: There was an error setting Oracle IOServer to rolling patch mode.
Action: Verify using the 'srvctl status ioserver' command that the Oracle IOServer
instance is active, and inspect the accompanying IOServer-specific error messages
to see if there is a correctable problem. If so, correct the problem and retry the
'crsctl start rollingpatch' command. If the problem persists, contact Oracle Support
Services.
CRS-01156: Rejecting the rolling patch mode change because the cluster is in the
middle of an upgrade.
Cause: The rolling patch mode change was rejected because the cluster was
undergoing an upgrade.
Action: None
CRS-01157: Rejecting the rolling patch mode change because the cluster was
forcibly upgraded.
Cause: The rolling patch mode change was rejected because the cluster was
forcibly upgraded.
Action: Delete the nodes that were not upgraded using the procedure
documented in the Oracle Clusterware documentation. Retry the 'crsctl start
rollingpatch' or 'crsctl stop rollingpatch' command after completing the above
steps.
CRS-01158: There was an error setting the cluster to rolling patch mode.
Cause: There was an internal error setting the cluster to rolling patch mode.
Action: Retry the 'crsctl start rolling patch' command. If the problem persists,
contact Oracle Support Services.
CRS-01159: The cluster cannot be set to rolling patch mode because Oracle
Clusterware is not active on at least one remote node.
Cause: The cluster could not be set to rolling patch mode because Oracle
Clusterware was not active on any of the remote nodes.
Action: Start Oracle Clusterware on at least one remote node and retry the 'crsctl
start rollingpatch' command, or retry patching using the non-rolling option.
CRS-01161: The cluster was successfully patched to patch level [number].
Cause: A 'crsctl stop rollingpatch' command completed successfully.
Action: None
CRS-01162: Rejecting rolling patch mode change because the patch level is not
consistent across all nodes in the cluster. The patch level on nodes string is not
the same as the expected patch level [number] found on nodes string.
Cause: The 'crsctl stop rollingpatch' command was rejected because all the nodes
in the cluster were not patched to the same patch level.
64-22 Oracle Database Error Messages
Action: Make sure all the nodes in the cluster have been patched to the same
patch level using the 'crsctl query crs softwarepatch ' command. Retry the
'crsctl stop rollingpatch' command after patching the required nodes.
CRS-01163: There was an error resetting Oracle Clusterware rolling patch mode.
Cause: There was an error resetting Oracle Clusterware rolling patch mode.
Action: Verify using the 'crsctl check crs' command that the Cluster Ready
Services (CRS) is active, and inspect the accompanying Clusterware-specific error
messages to see if there is a correctable problem. If so, correct the problem and
retry the 'crsctl stop rollingpatch' command. If the problem persists, contact Oracle
Support Services.
CRS-01164: There was an error resetting Oracle ASM rolling patch mode.
Cause: There was an error resetting Oracle ASM rolling patch mode.
Action: Verify using the 'srvctl status asm' command that the Oracle ASM
instance is active, and inspect the accompanying ASM-specific error messages to
see if there is a correctable problem. If so, correct the problem and retry the 'crsctl
stop rollingpatch' command. If the problem persists, contact Oracle Support
Services.
CRS-01165: There was an error resetting Oracle IOServer rolling patch mode.
Cause: There was an error resetting Oracle IOServer rolling patch mode.
Action: Verify using the 'srvctl status ioserver' command that the Oracle IOServer
instance is active, and inspect the accompanying IOServer-specific error messages
to see if there is a correctable problem. If so, correct the problem and retry the
'crsctl stop rollingpatch' command. If the problem persists, contact Oracle Support
Services.
CRS-01166: Rejecting rolling patch mode change because Oracle ASM is in [string]
state.
Cause: A request to reset rolling patch mode was rejected because Oracle ASM
was in an unexpected state.
Action: Retry the 'crsctl stop rollingpatch' command. If the problem persists,
contact Oracle Support Services.
CRS-01167: Rejecting rolling patch mode change because Oracle IOServer is in
[string] state.
Cause: A request to reset rolling patch mode was rejected because Oracle
IOServer was in an unexpected state.
Action: Retry the 'crsctl stop rollingpatch' command. If the problem persists,
contact Oracle Support Services.
CRS-01168: There was an error resetting the cluster rolling patch mode.
Cause: There was an internal error resetting the cluster rolling patch mode.
Action: Retry the 'crsctl stop rolling patch' command. If the problem persists,
contact Oracle Support Services.
CRS-01169: The cluster is consistent and the cluster active patch level is [number].
Cause: The cluster has already completed the rolling patch procedure.
Action: None
CRS-00001 to CRS-29006 64-23
CRS-01170: Rejecting rolling patch mode change because the patch has not been
applied yet. The software patch level [number] on this node is not the same as
the expected patch level [number].
Cause: The 'crsctl stop rollingpatch' command was rejected because the patch
level did not match with the configured software patch level.
Action: Complete applying the patch on this node, and verify the patch level
using the 'crsctl query crs softwarepatch ' command. Retry the 'crsctl stop
rollingpatch' command.
CRS-01171: Rejecting rolling patch mode change because the patch level is not
consistent across all nodes in the cluster. The patch level on nodes string is not
the same as the patch level [number] found on nodes string.
Cause: The 'crsctl stop rollingpatch' command was rejected because all the nodes
in the cluster were not patched to the same patch level.
Action: Verify the list of patches applied on a node by issuing the the 'crsctl query
crs releasepatch' command. Apply the requisite patches. Make sure all the nodes
in the cluster have been patched to the same patch level using the 'crsctl query crs
softwarepatch' command. Retry the 'crsctl stop rollingpatch' command after
patching the required nodes.
CRS-01181: There was an error retrieving the Oracle Clusterware release patch
level.
Cause: There was an internal error retrieving the Oracle Clusterware release patch
level.
Action: Contact Oracle Support Services.
CRS-01182: Oracle Clusterware release patch level is [number] and the complete list
of patches [string] have been applied on the local node.
Cause: None, this is an informational message.
Action: None
CRS-01183: Oracle Clusterware release patch level is [number] and an incomplete
list of patches [string] have been applied on the local node.
Cause: There was an error retrieving the complete list of patches.
Action: Contact Oracle Support Services.
CRS-01184: Oracle Clusterware release patch level is [number] and no patches have
been applied on the local node.
Cause: None, this is an informational message.
Action: None
CRS-01191: There was an error retrieving the Oracle Clusterware software patch
level.
Cause: There was an internal error retrieving the Oracle Clusterware software
patch level.
Action: Contact Oracle Support Services.
CRS-01192: Oracle Clusterware patch level on node string is [number].
Cause: None, this is an informational message.
Action: None
CRS-01201: CRSD started on node string.
64-24 Oracle Database Error Messages
Cause: CRSD has started, possibly due to a CRS start, or a node reboot or a CRSD
restart.
Action: None Required. You can run the command 'crsctl check crsd' to validate
the health of the CRSD.
CRS-01202: CRSD aborted on node string. Error [string]. Details in string.
Cause: Fatal Internal Error. Check the CRSD log file to determine the cause.
Action: Determine whether the CRSD gets auto-started.
CRS-01203: Failover failed for the CRS resource string. Details in string.
Cause: Failover failed due to an internal error. Examine the contents of the CRSD
log file to determine the cause.
Action: None
CRS-01204: Recovering CRS resources for node string.
Cause: CRS resources are being recovered, possibly because the cluster node is
starting up online.
Action: Check the status of the resources using the 'crsctl status resource'
command.
CRS-01205: Auto-start failed for the CRS resource string. Details in string.
Cause: This message comes up when the auto-start for the resource has failed
during a reboot of the cluster node.
Action: Start the resources using the 'crsctl start resource' command.
CRS-01206: Resource string is in the UNKNOWN state. Make sure the resource is
completely stopped, then use the 'crsctl stop -f' command.
Cause: Resource went into an unknown state because the check or the stop
Action: Make sure the resource is completely stopped, then use the 'crsctl stop -f'
command.
CRS-01207: There are no more restart attempts left for resource string. Restart the
resource manually using the crsctl command.
Cause: The Oracle Clusterware is no longer attempting to restart the resource
because the resource has failed and the Oracle Clusterware has exhausted the
maximum number of restart attempts.
Action: Use the 'crsctl start' command to restart the resource manually.
CRS-01208: Cluster Ready Service terminating, unable to start successfully. Details
at string in string.
Cause: Cluster Ready Service could not initialize successfully.
Action: Restart Cluster Ready Service using the command 'crsctl start
clusterware'. If the problem persists, contact Oracle Support Services.
CRS-01209: Cluster Ready Service terminating, failed to register with group 'string'.
Details at string in string.
Cause: Cluster Ready Service could not initialize successfully.
Action: Restart Cluster Ready Service using the command 'crsctl start
clusterware'. If the problem persists, contact Oracle Support Services.
CRS-01210: Cluster Ready Service failed to update group data. Details at string in
string.
CRS-00001 to CRS-29006 64-25
Cause: Cluster Ready Service failed to update the group private data with new
master.
Action: Restart Cluster Ready Service using the command 'crsctl start
clusterware'. If the problem persists, contact Oracle Support Services.
CRS-01211: Cluster Ready Service noticed abnormal termination by Cluster
Synchronization Service. Details at string in string.
Cause: Cluster Ready Service terminating due to abnormal termination of Cluster
Synchronization Service layer.
Action: Contact Oracle Support Services.
CRS-01212: Cluster Ready Service received invalid update for group private data.
Details at string in string.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
CRS-01213: Cluster Ready Service failed to retrieve user information. Details at
string in string.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
CRS-01214: Cluster Ready Service failed to initialize OLR context. Details at string
in string.
Cause: Cluster Ready Service unable to access local registry.
Action: Use the ocrcheck utility to detect errors in the OLR. If problems exist, the
registry may need to be recovered or restored.
CRS-01215: Cluster Ready Service could not get the local node number. Details at
string in string.
Cause: Cluster Ready Service could not retrieve the local node incarnation
number.
Action: Contact Oracle Support Services.
CRS-01216: Cluster Ready Service could not determine node list. Details at string in
string.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
CRS-01217: Cluster Ready Service unable to get node name. Details at string in
string.
Cause: Cluster Ready Service could not determine node name.
Action: Contact Oracle Support Services.
CRS-01218: Cluster Ready Service error during initialization. Details at string in
string.
Cause: Cluster Ready Service could not initialize underlying layers successfully.
Action: Contact Oracle Support Services.
CRS-01219: Cluster Synchronization Service not available. Details at string in
string.
Cause: Cluster Ready Service was unable to initialize access to CSS, which is
required.
64-26 Oracle Database Error Messages
Action: Contact Oracle Support Services.
CRS-01220: Cluster Ready Service could not retrieve local node number. Details at
string in string.
Cause: Cluster Ready Service could not retrieve node number for local node.
Action: Contact Oracle Support Services.
CRS-01221: Cluster Ready Service failed to retrieve local node name. Details at
string in string.
Cause: Cluster Ready Service could not retrieve node name.
Action: Contact Oracle Support Services.
CRS-01222: Cluster Ready Service failed to retrieve maximum group size. Details at
string in string.
Cause: Cluster Ready Service could not retrieve value for maximum group size.
Action: Contact Oracle Support Services.
CRS-01223: Cluster Ready Service error while reading cluster active version. Details
at string in string.
Cause: Could not retrieve cluster active version.
Action: Contact Oracle Support Services.
CRS-01224: Server authentication exception encountered, exception text is 'string'.
Details at string in string.
Cause: Cluster Ready Service encountered error while authenticating user.
Action: This is an internal error. Contact Oracle Support Services.
CRS-01225: Invalid identity exception encountered, exception text is 'string'. Details
at string in string.
Cause: Cluster Ready Service could not verify user identity.
Action: This is an internal error. Contact Oracle Support Services.
CRS-01226: Failed to create message to send to policy engine. Details at string in
string.
Cause: Cluster Ready Service encountered communication error.
Action: This is an internal error. Contact Oracle Support Services.
CRS-01227: Error during initialization of communication subsystem. Details at
string in string.
Cause: Cluster Ready Service encountered communication error during
initialization.
Action: This is an internal error. Contact Oracle Support Services.
CRS-01228: Error while setting up user interface server. Details at string in string.
Cause: Cluster Ready Service encountered communication error.
Action: This is an internal error. Contact Oracle Support Services.
CRS-01229: Error while listening for events. Details at string in string.
Cause: Cluster Ready Service encountered communication error.
Action: This is an internal error. Contact Oracle Support Services.
CRS-01231: Failed to open key 'string' in OCR. Details at string in string.
CRS-00001 to CRS-29006 64-27
Cause: This is an internal error.
Action: This is an internal error. Contact Oracle Support Services.
CRS-01232: Could not get security attribute for system key 'string' in OCR. Details
at string in string.
Cause: Encountered error while reading system key attributes in OCR.
Action: This is an internal error. Contact Oracle Support Services.
CRS-01233: Failed to initialize batch handler for OCR. Details at string in string.
Cause: Could not initialize batch handler for multiwrite in OCR.
Action: This is an internal error. Contact Oracle Support Services.
CRS-01234: Encountered error while setting key value for key 'string' in OCR.
Details at string in string.
Cause: Encountered an error while executing a batch write in OCR.
Action: This is an internal error. Contact Oracle Support Services.
CRS-01235: Error while executing batch for multi writes in OCR. Details at string in
string.
Cause: Encountered an error while executing a batch write in OCR.
Action: This is an internal error. Contact Oracle Support Services.
CRS-01236: Error enumerating subkeys for key 'string' in OCR. Details at string in
string.
Cause: Encountered an error while reading subkey values in OCR.
Action: This is an internal error. Contact Oracle Support Services.
CRS-01237: Failed to retrieve the maximum value supported in OCR. Details at
string in string.
Cause: Could not read the maximum value size from registry.
Action: This is an internal error. Contact Oracle Support Services.
CRS-01238: Failed to add a delete key operation for key 'string' to a batch in OCR.
Details at string in string.
Cause: Encountered internal error while deleting key in OCR.
Action: This is an internal error. Contact Oracle Support Services.
CRS-01239: Cluster Ready Service aborted due to an unexpected error [string].
Details at string in string.
Cause: This is an unexpected error. Look at the associated error message to fix the
underlying issue.
Action: If the problem persists, contact Oracle Support Services.
CRS-01301: Oracle High Availability Service started on node string.
Cause: Oracle High Availability Service has started, possibly due to a Clusterware
start, or a node reboot.
Action: None Required.
CRS-01302: Oracle High Availability Service aborted on node string. Error [string].
Details in string.
Cause: Fatal Internal Error. Check the Oracle High Availability Service log file to
determine the cause.
64-28 Oracle Database Error Messages
Action: Determine whether the Oracle High Availability Service gets auto-started.
CRS-01303: Failover failed for the OHAS resource string. Details in string.
Cause: Failover processing for the specified resource did not complete. Examine
the contents of the Oracle High Availability Service log file to determine the cause.
Action: None
CRS-01304: Recovering OHAS resources for node string.
Cause: Oracle High Availability Service resources are being recovered, possibly
because the cluster node is starting up online.
Action: Check the status of the resources using the crsctl command.
CRS-01305: Auto-start failed for the OHAS resource string. Details in string.
Cause: This message comes up when the auto-start for the resource has failed
during a reboot of the cluster node.
Action: Start the resources using the 'crsctl start resource' command.
CRS-01306: Resource string is in an unknown state. Make sure the resource is
completely stopped, then use the 'crsctl stop -f' command.
Cause: Resource went into an unknown state because the check or the stop
Action: Make sure the resource is completely stopped, then use the 'crsctl stop -f'
command.
CRS-01307: There are no more restart attempts left for resource string. Restart the
resource manually using the crsctl command.
Cause: The Oracle Clusterware is no longer attempting to restart the resource
because the resource has failed and the Oracle Clusterware has exhausted the
maximum number of restart attempts.
Action: Use the 'crsctl start resource' command to restart the resource manually.
CRS-01308: Oracle High Availability Service terminating, unable to start
successfully. Details at string in string.
Cause: Oracle High Availability Service could not initialize successfully.
Action: Restart your clusterware installation. If the problem persists, contact
Oracle Support Services.
CRS-01309: Oracle High Availability Service terminating, failed to register with
group 'string'. Details at string in string.
Cause: Oracle High Availability Service could not initialize successfully.
Action: Restart your clusterware installation. If the problem persists, contact
Oracle Support Services.
CRS-01310: Oracle High Availability Service failed to update group data. Details at
string in string.
Cause: Oracle High Availability Service failed to update the group private data
with new master.
Action: Restart your clusterware installation. If the problem persists, contact
Oracle Support Services.
CRS-01311: Oracle High Availability Service noticed abnormal termination by
Cluster Synchronization Service. Details at string in string.
Cause: Oracle High Availability Service terminating due to abnormal termination
of Cluster Synchronization Service layer.
CRS-00001 to CRS-29006 64-29
Action: Contact Oracle Support Services.
CRS-01312: Oracle High Availability Service received invalid update for group
private data. Details at string in string.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
CRS-01313: Oracle High Availability Service failed to retrieve user information.
Details at string in string.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
CRS-01314: Oracle High Availability Service failed to initialize OLR context.
Details at string in string.
Cause: Oracle High Availability Service unable to access local registry.
Action: Use the ocrcheck utility to detect errors in the OLR. If problems exist, the
registry may need to be recovered or restored.
CRS-01315: Oracle High Availability Service could not get the local node number.
Details at string in string.
Cause: Oracle High Availability Service could not retrieve the local node
incarnation number.
Action: Contact Oracle Support Services.
CRS-01316: Oracle High Availability Service could not determine node list. Details
at string in string.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
CRS-01317: Oracle High Availability Service unable to get node name. Details at
string in string.
Cause: Oracle High Availability Service could not determine node name.
Action: Contact Oracle Support Services.
CRS-01318: Oracle High Availability Service error during initialization. Details at
string in string.
Cause: Oracle High Availability Service could not initialize underlying layers
successfully.
Action: Contact Oracle Support Services.
CRS-01319: Cluster Synchronization Service not available. Details at string in
string.
Cause: Oracle High Availability Service was unable to initialize access to CSS,
which is required.
Action: Contact Oracle Support Services.
CRS-01320: Oracle High Availability Service could not retrieve local node number.
Details at string in string.
Cause: Oracle High Availability Service could not retrieve node number for local
node.
Action: Contact Oracle Support Services.
64-30 Oracle Database Error Messages
CRS-01321: Oracle High Availability Service failed to retrieve local node name.
Details at string in string.
Cause: Oracle High Availability Service could not retrieve node name.
Action: Contact Oracle Support Services.
CRS-01322: Oracle High Availability Service failed to retrieve maximum group size.
Details at string in string.
Cause: Oracle High Availability Service could not retrieve value for maximum
group size.
Action: Contact Oracle Support Services.
CRS-01323: Oracle High Availability Service error while reading cluster active
version. Details at string in string.
Cause: Could not retrieve cluster active version.
Action: Contact Oracle Support Services.
CRS-01324: Server authentication exception encountered, exception text is 'string'.
Details at string in string.
Cause: Oracle High Availability Service encountered error while authenticating
user.
Action: This is an internal error. Contact Oracle Support Services.
CRS-01325: Invalid identity exception encountered, exception text is 'string'. Details
at string in string.
Cause: Oracle High Availability Service could not verify user identity.
Action: This is an internal error. Contact Oracle Support Services.
CRS-01326: Failed to create message to send to policy engine. Details at string in
string.
Cause: Oracle High Availability Service encountered communication error.
Action: This is an internal error. Contact Oracle Support Services.
CRS-01327: Error during initialization of communication subsystem. Details at
string in string.
Cause: Oracle High Availability Service encountered communication error during
initialization.
Action: This is an internal error. Contact Oracle Support Services.
CRS-01328: Error while setting up user interface server. Details at string in string.
Cause: Oracle High Availability Service encountered communication error.
Action: This is an internal error. Contact Oracle Support Services..
CRS-01329: Error while listening for events. Details at string in string.
Cause: Oracle High Availability Service encountered communication error.
Action: This is an internal error. Contact Oracle Support Services..
CRS-01330: Oracle High Availability Services aborted due to internal error.
Cause: Fatal Internal Error. Check the Oracle High Availability Service log file to
determine the cause.
Action: Determine whether the Oracle High Availability Service gets auto-started.
CRS-01331: Failed to open key 'string' in OLR. Details at string in string.
CRS-00001 to CRS-29006 64-31
Cause: This is an internal error.
Action: This is an internal error. Contact Oracle Support Services.
CRS-01332: Could not get security attribute for system key 'string' in OLR. Details
at string in string.
Cause: Encountered error while reading system key attributes in OLR.
Action: This is an internal error. Contact Oracle Support Services.
CRS-01333: Failed to initialize batch handler for OLR. Details at string in string.
Cause: Could not initialize batch handler for multiwrite in OLR.
Action: This is an internal error. Contact Oracle Support Services.
CRS-01334: Encountered error while setting key value for key 'string' in OLR.
Details at string in string.
Cause: Encountered an error while executing a batch write in OLR.
Action: This is an internal error. Contact Oracle Support Services.
CRS-01335: Error while executing batch for multi writes in OLR. Details at string in
string.
Cause: Encountered an error while executing a batch write in OLR.
Action: This is an internal error. Contact Oracle Support Services.
CRS-01336: Error enumerating subkeys for key 'string' in OLR. Details at string in
string.
Cause: Encountered an error while reading subkey values in OLR.
Action: This is an internal error. Contact Oracle Support Services.
CRS-01337: Failed to retrieve the maximum value supported in OLR. Details at
string in string.
Cause: Could not read the maximum value size from registry.
Action: This is an internal error. Contact Oracle Support Services.
CRS-01338: Failed to add a delete key operation for key 'string' to a batch in OLR.
Details at string in string.
Cause: Encountered internal error while deleting key in OLR.
Action: This is an internal error. Contact Oracle Support Services.
CRS-01339: Oracle High Availability Service aborted due to an unexpected error
[string]. Details at string in string.
Cause: Look at the associated error message to fix the underlying issue.
Action: If the problem persists, contact Oracle Support Services.
CRS-01340: Node 'string' has a pending role change; Oracle High Availability
Services needs to be restarted.
Cause: A 'crsctl stop cluster' command was run after a node's role has changed.
Action: Run 'crsctl stop crs' and 'crsctl start crs' on the node for the node role
change to take effect.
CRS-01401: EVMD started on node string.
Cause: EVMD has started either because of a CRS start, a node reboot, or an
EVMD restart.
64-32 Oracle Database Error Messages
Action: None required. You can run the 'crsctl check evmd' command to validate
the health of EVMD.
CRS-01402: EVMD aborted on node string. Error [string]. Details in string.
Cause: EVMD has aborted due to an internal error. Check the EVMD log file to
determine the cause.
Action: Determine whether the EVMD is auto-started and contact Oracle Support
Services.
CRS-01403: The Event Management Service terminated on node string. Listening
port number is in use by another application. Details in string.
Cause: The Event Management Service has aborted because the configured
listening port is being used by another application on this node.
Action: Make the listening port listed above available. Restart the Event
Management Service using 'crsctl start crs' or 'crsctl start cluster' command.
CRS-01601: CSSD Reconfiguration complete. Active nodes are string.
Cause: A node joined or left the cluster.
Action: None
CRS-01602: CSSD aborted on node string. Error [string]; details in string.
Cause: The CSS daemon aborted on the listed node with the listed return code.
Action: Collect the CSS daemon logs from all nodes and any CSS daemon core
files and contact Oracle Support.
CRS-01603: CSSD on node string shutdown by user.
Cause: The CSS daemon on the listed node was terminated by a user.
Action: None
CRS-01604: CSSD voting file is offline: string; details at string in string.
Cause: The listed voting file became unusable on the local node.
Action: Verify that the filesystem containing the listed voting file is available on
the local node.
CRS-01605: CSSD voting file is online: string; details in string.
Cause: The CSS daemon has detected a valid configured voting file.
Action: None
CRS-01606: The number of voting files available, number, is less than the minimum
number of voting files required, number, resulting in CSSD termination to
ensure data integrity; details at string in string
Cause: The number of voting files has decreased to a number of files that is
insufficient.
Action: as indicated by those messages.
CRS-01607: Node string is being evicted in cluster incarnation number; details at
string in string.
Cause: The local node has detected that the indicated node is still active, but not
able to communicate with this node, so is forcibly removing the indicated node
from the cluster.
Action: Collect the CSS daemon logs from all nodes and any CSS daemon core
files and contact Oracle Support.
CRS-00001 to CRS-29006 64-33
CRS-01608: This node was evicted by node number, string; details at string in string.
Cause: The local node was evicted by the indicated node.
Action: Collect the CSS daemon logs from all nodes and any CSS daemon core
files and contact Oracle Support.
CRS-01609: This node is unable to communicate with other nodes in the cluster and
is going down to preserve cluster integrity; details at string in string.
Cause: Communication was lost with some nodes of the cluster and this node
detected that another sub-cluster was designated to be the surviving sub-cluster.
This node went down to preserve data integrity.
Action: Verify all network connections between cluster nodes and repair any
problematic connections. If there do not appear to be any network problems,
1. collect the CSS daemon logs, system messages and any CSS daemon core files
from all nodes and
2. contact Oracle Support.
CRS-01610: Network communication with node string (number) missing for 90% of
timeout interval. Removal of this node from cluster in number.number seconds
Cause: Did not receive heartbeat messages from the node. This could be due to
network problems or failure of the listed node.
Action: Check if the private interconnect network used by cluster is functioning
properly, including all the cables, network cards, switches/routers etc. between
this node and listed node. Correct any problems discovered.
CRS-01611: Network communication with node string (number) missing for 75% of
timeout interval. Removal of this node from cluster in number.number seconds
Cause: Did not receive heartbeat messages from the node. This could be due to
network problems or failure of the listed node.
Action: Check if the private interconnect network used by cluster is functioning
properly, including all the cables, network cards, switches/routers etc. between
this node and listed node. Correct any problems discovered.
CRS-01612: Network communication with node string (number) missing for 50% of
timeout interval. Removal of this node from cluster in number.number seconds
Cause: Did not receive heartbeat messages from the node. This could be due to
network problems or failure of listed node.
Action: Check if the private interconnect network used by cluster is functioning
properly, including all the cables, network cards, switches/routers etc. between
this node and listed node. Correct any problems discovered.
CRS-01613: No I/O has completed after 90% of the maximum interval. Voting file
string will be considered not functional in number milliseconds
Cause: Voting device I/O has not completed for a long time. This could be due
some error with the device the voting file is on or in some element in the path of
the I/O to the device.
Action: Verify that the device is working properly including all elements in the
I/O path. The voting file listed will be considered inactive in the number of
milliseconds specified. Failure of a majority of devices will result in node reboot.
CRS-01614: No I/O has completed after 75% of the maximum interval. Voting file
string will be considered not functional in number milliseconds
64-34 Oracle Database Error Messages
Cause: Voting device I/O has not completed for a long time. This could be due
some error with the device the voting file is on or in some element in the path of
the I/O to the device.
Action: Verify that the device is working properly including all elements in the
I/O path. The voting file listed will be considered inactive in the number of
milliseconds specified. Failure of a majority of devices will result in node reboot.
CRS-01615: No I/O has completed after 50% of the maximum interval. Voting file
string will be considered not functional in number milliseconds
Cause: Voting device I/O has not completed for a long time. This could be due
some error with the device the voting file is on or in some element in the path of
the I/O to the device.
Action: Verify that the device is working properly including all elements in the
I/O path. The voting file listed will be considered inactive in the number of
milliseconds specified. Failure of a majority of devices will result in node reboot.
CRS-01616: The BMC device used for IPMI at IP address string is not properly
configured for ADMIN access; details at string in string
Cause: The IPMI BMC is not configured to support the ADMIN access methods
required by Oracle Clusterware.
Action: Consult the clusterware admin manual for proper procedures in
configuring BMC. Use the BMC configuration tool (ipmitool or ipmiutil)
command to check and verify that the current configuration supports either MD5
or password validation for ADMIN access.
CRS-01617: The information required to do node kill for node string is incomplete;
details at string in string
Cause: Incomplete config information stored in Cluster Registry for node kill.
Action: Make sure all the information pertaining to the node kill method
CRS-01618: The requested node kill information change could not be validated by
node string; details at string in string
Cause: Unable to validate the node kill information for this node.
Action: Additional information can be found in the CRS alert log of the node that
performed the validation.
CRS-01619: The node kill information of node string could not be validated by this
node due to failure in connecting to the IPMI device; details at string in string
Cause: Unable to validate the node kill information for this node.
Action: Additional information can be found in the CSSD logs.
CRS-01620: The node kill information of node string could not be validated by this
node due to invalid authorization information; details at string in string
Cause: Unable to validate the kill information for this node.
Action: Additional information can be found in the CSSD logs.
CRS-01621: The IPMI configuration data for this node stored in the Oracle registry
is incomplete; details at string in string
Cause: All the necessary information such as IPMI username, password and IP
address are not present.
Action: Make sure all the information(BMC IPMI username, password and IP
address) are present. Use commands 'crsctl set css ipmiaddr' and 'crsctl set css
ipmiadmin' for this.
CRS-00001 to CRS-29006 64-35
CRS-01622: The IPMI node kill information could not be validated due to inability
to connect to the IPMI device at BMC IP address provided string; details at
string in string
Cause: Unable to validate the BMC IPMI IP address provided.
Action: Additional information can be found in the CSSD logs.
CRS-01623: The IPMI node kill information of BMC at IP address string could not
be validated due to invalid authorization information. The BMC username
provided is 'string'; details at string in string
Cause: Unable to validate the BMC IPMI UserName and password provided.
Action: Additional information can be found in the CSSD logs.
CRS-01624: The requested Node kill information change succeeds vacuously
because there is no other node in cluster to validate.
Cause: Unable to validate the credentials because this is the sole node in the
cluster.
Action: To complete the valdidation, shut down the clusterware stack on this
node, start another node and restart the stack on this node.
CRS-01625: Node string, number number, was shut down
Cause: A Clustware stack shutdown command was issued for a node in the
cluster and was observed by this node.
Action: None required.
CRS-01626: A Configuration change request completed successfully
Cause: A Configuration change request completed successfully.
Action: None required.
CRS-01627: A Configuration change request failed because another configuration
change is in progress; Details at string in string
Cause: Another configuration change is in still in progress.
Action: Wait until the other command completes and reissue the command if
necessary. Message 1626 would be printed if the command succeeds.
CRS-01628: A Configuration change request failed because read of existing voting
files failed; Details at string in string
Cause: CSSD was not able to read the lease blocks of a majority of Voting files
which is an indication of a problem with the voting files.
Action: Run the command 'crsctl query css votedisk' to get the list of currently
working voting files. User may delete problematic voting file or use a different set.
CRS-01629: A Configuration change request failed because write to new voting
files failed; Details at string in string
Cause: A voting file write failed, causing the associated configuration change to
fail. This often results from adding a voting file that is not accessible to one or
more nodes.
Action: Confirm that voting files added in a configuration change are accessible
and writeable from all cluster nodes. If they are, contact Oracle Customer Support.
CRS-01630: A configuration change request failed because not all the new voting
files were discovered; Details at string in string
64-36 Oracle Database Error Messages
Cause: One or more of the voting files being added were not discovered. Message
1638 identifies the unique ID(s) of the file(s) that could not be found.
Action: Verify if the discovery string is adequate to discover the new voting files.
If not, modify discovery string using command 'crsctl replace discoverystring
xxxxx'.
CRS-01631: A configuration change request failed because one or more nodes are
not a sufficient Clusterware version level; Details at string in string
Cause: One ore more nodes are not a sufficient version level.
Action: Configuration change would not be successful until all nodes are at at the
latest version. Try after all the nodes are upgraded.
CRS-01632: Node string is being removed from the cluster in cluster incarnation
number
Cause: The local node is removing the indicated node from the cluster because it
appears to be dead.
Action: Verify that the node that was removed, or the Oracle Clusterware on that
node, was down. The CRS alert log of the node that was removed has information
regarding why the node, or clusterware on the node, was no longer active. If the
node was still up and Oracle Clusterware still active on that node, collect the CSS
daemon logs from all nodes and any CSS daemon core files and contact Oracle
Support.
CRS-01633: CSSD failed to register group string in vendor clusterware; details at
string in string
Cause: The local node is not able to register the group of vendor clusterware.
Action: Verify that the vendor clusterware is installed and configured correctly.
CRS-01634: CSSD is unable to determine cluster name; details at string in string
Cause: Name of the cluster cannot be determined from configuration.
Action: Verify that Oracle Clusterware installation was successful.
CRS-01635: CSSSD failed to initialize vendor clusterware; details at string in string
Cause: The local node is not able to attach vendor clusterware.
Action: Verify that the vendor clusterware is installed and configured correctly.
CRS-01636: The CSS daemon was started in exclusive mode but found an active
CSS daemon on node string and is terminating; details at string in string
Cause: The CSS daemon was started in exclusive mode, which requires that the
clusterware stack is down on all other nodes to ensure data integrity. A CSS
daemon was detected on another node, so the CSS daemon on this node is
terminating.
Action: Stop the Oracle clusterware stack that is running on the indicated node.
CRS-01637: Unable to locate configured voting file with ID string; details at string
in string
Cause: The voting file with unique the ID indicated in the message was not found
during the voting file discovery phase of CSS initialization.
Action: Verify that all configured voting files are accessible on this node. Any
voting files that are not accessible should be removed and replaced with accessible
voting files using the appropriate 'crsctl' commands.
CRS-00001 to CRS-29006 64-37
CRS-01638: Unable to locate voting file with ID string that is being added to the list
of configured voting files; details at string in string
Cause: The voting file with the unique ID indicated in the message was not found
during the voting file discovery phase of CSS initialization. This voting file is in
the process of being added to the list of configured voting files.
Action: Verify that all voting files to be added are accessible on this node. Any
voting files that are not accessible should be removed and replaced with accessible
voting files using the appropriate 'crsctl' commands.
CRS-01639: Rejecting configuration change number:number because another
configuration change is already in progress; details at string in string
Cause: A configuration change was requested, but another configuration change
is already in progress and only one configuration change may be processed at a
time.
Action: Wait for the current configuration change to complete, then resubmit this
configuration change.
CRS-01640: Rejecting configuration change number:number because one or more
new voting files in the new configuration could not be found; details at string in
string
Cause: A configuration change that involved the addition of voting files is being
rejected because some of the new voting files were not located.
Action: Verify that the voting file name is correct and that it is accessible on this
node, if the voting files are not managed by ASM. Message number 1638 provides
greater detail.
CRS-01641: Rejecting configuration change number:number because only number of
the required number voting files of the new configuration were located; details
at string in string
Cause: A configuration change that involved a change to the list of voting files is
being rejected because a sufficient number of voting files in the new configuration
could not be located.
Action: Verify that all voting files in the new configuration are accessible on this
node.
CRS-01642: Node number is using a different CSS configuration from the one used
by this node; this node is terminating to preserve integrity; details at string in
string
Cause: Another node in the cluster is using a different set of CSS configuration
values, such as misscount or voting files. Inconsistency can result in data
corruption, so this node is terminating to avoid data corruption.
Action: Collect Clusterware alert log and the CSSD log indicated in the message
as well as the CSS daemon logs of all other nodes in the cluster and contact Oracle
Support Services.
CRS-01643: Failed to format the CSS voting disk string
Cause: Problems were encountered attempting to access the voting file.
Action: Verify that the voting file can be accessed, the file exists, has the proper
ownership and permissions, etc.
CRS-01644: The initialization of the EXADATA fencing facility failed in start with
error ORA-number; details at string in string
64-38 Oracle Database Error Messages
Cause: The start of the initialization of the EXADATA fencing facility failed with
the error code shown.
Action: See the Action section of the error message shown.
CRS-01645: The initialization of the EXADATA fencing facility failed in completion
with error ORA-number; details at string in string
Cause: The completion of the initialization of the EXADATA fencing facility failed
with the error code shown.
Action: See the Action section of the error message shown.
CRS-01646: Creation of a EXADATA fence identifier failed with error ORA-number;
details at string in string
Cause: An attempt to create an identifier for a fence to an EXADATA device failed
with the error code shown.
Action: See the Action section of the error message shown.
CRS-01647: Initialization of a EXADATA fence failed with error ORA-number;
details at string in string
Cause: An attempt to initiate a fence to an EXADATA device failed with the error
code shown.
Action: See the Action section of the error message shown.
CRS-01648: Completion of queued EXADATA fence requests failed with error
ORA-number; details at string in string
Cause: Previously queued fence requests to an EXADATA device failed with the
error code shown.
Action: See the Action section of the error message shown.
CRS-01649: An I/O error occurred for voting file: string; details at string in string.
Cause: The listed voting file became inaccessible.
Action: Verify that the filesystem containing the listed voting file is available on
the local node.
CRS-01650: Configuration change number:number rejected by node number string;
details at string in string
Cause: A new configuration change request from this node was not accepted due
to another node rejecting the change.
Action: Check the CRS alert log of the node rejecting this configuration change for
more details.
CRS-01651: Configuration change number:number rejected because it would make
the active version of node number lower than the current setting string of this
node; details at string in string
Cause: A new configuration change request from another node was not accepted
because the new Active Version in the request is lower than this node's Active
Version.
Action: Ensure that the new Active Version is not lower than the current Active
Version of the nodes in the cluster.
CRS-01652: Starting clean up of CRSD resources.
Cause: Clean up of the resources registered in CRSD started.
Action: None
CRS-00001 to CRS-29006 64-39
CRS-01653: The clean up of the CRSD resources failed.
Cause: Clean up of the resources registered in CRSD failed.
Action: Check the CRS alert log.
CRS-01654: Clean up of CRSD resources finished successfully.
Cause: Clean up of the resources registered in CRSD finished.
Action: None
CRS-01655: CSSD on node string detected a problem and started to shutdown.
Cause: The CSS daemon on the listed node detected a problem and started to
shutdown.
Action: Check the CRS alert log.
CRS-01656: The CSS daemon is terminating due to a fatal error; Details at string in
string
Cause: A fatal error occurred during CSS daemon processing.
Action: Check for prior errors logged in the alert log. Correct any errors that can
be corrected. If there are no errors shown, or the errors cannot be resolved, contact
Oracle support
CRS-01657: Unable to obtain the voting file discovery string; Details at string in
string
Cause: An attempt to obtain the voting file discovery string from the profile
failed, causing the CSS daemon to fail.
Action: Collect the Clusterware alert log and the CSSD log of this node as well as
all CSS daemon logs of all other nodes in the cluster and contact Oracle Support
Services.
CRS-01658: There is a mismatch of the initial cluster incarnation among the cluster
nodes; Details at string in string
Cause: An internal error occurred.
Action: Collect the Clusterware alert log and the CSSD log of this node as well as
all CSS daemon logs of all other nodes in the cluster and contact Oracle Support
Services.
CRS-01659: An attempt to kill node string failed; Details at string in string
Cause: To protect data integrity a node kill was attempted for the indicated node,
but it failed.
Action: Collect the Clusterware alert log and the CSSD log of this node as well as
the CSS daemon logs of all other nodes in the cluster and contact Oracle Support
Services.
CRS-01660: The CSS daemon shutdown has completed
Cause: A command to shut down the CSS daemon was issued by a user and the
shutdown processing is completed. The CSS daemon is terminated.
Action: No action is required.
CRS-01661: The CSS daemon is not responding. Reboot will occur in number
milliseconds; Details at string in string
Cause: The CSS daemon is failing to respond.
64-40 Oracle Database Error Messages
Action: Collect the Clusterware alert log and the CSSD log of this node as well as
the CSS daemon logs of all other nodes in the cluster and contact Oracle Support
Services.
CRS-01662: Member kill requested by node string for member number number,
group string
Cause: A request to kill a member of the indicated group was issued by a process
on the indicated node.
Action: No action is required.
CRS-01663: Member kill issued by PID string for number members, group string.
Details at string in string.
Cause: A member kill request was issued by the indicated process for the
members belonging to the indicated group.
Action: No action is required.
CRS-01664: No voting files found; switching node role to 'leaf'.
Cause: A node attempting to start as a Hub node was not able to find a voting file.
Action: No action is required.
CRS-01665: maximum number of cluster Hub nodes reached; the CSS daemon is
terminating
Cause: A node attempting to start as a Hub node found the maximum number of
Hub nodes already active.
Action: If the configured node role is 'auto', no action is required for the node to
restart as a Leaf node. If the configured node role is 'hub', then the configured role
must be changed to a Leaf node using 'crsctl set node role leaf' or the Hub size
must be increased using 'crsctl set cluster hubsize'.
CRS-01666: no Hub nodes found; switching node role to 'hub'
Cause: A node attempting to start as a Leaf node was unable to locate any Hub
nodes.
Action: No action is required.
CRS-01667: node string not allowed to join because the maximum number of Hub
nodes has been reached
Cause: A node attempting to start as a Hub node found the maximum number of
Hub nodes already active.
Action: No action is required.
CRS-01668: operation is not allowed on a Leaf node
Cause: An unsupported operation was requested on a Leaf node.
Action: Retry this operation on a Hub node.
CRS-01669: The number of voting files available number is less than the minimum
number of voting files required number.
Cause: The number of voting files has decreased to a number of files that is
insufficient.
Action: Look in the alert log for related messages such as 1714, 1604, 1613, 1614
and 1615 and act accordingly.
CRS-01670: Leaf node could not find any Hub nodes to connect to; details at string
in string
CRS-00001 to CRS-29006 64-41
Cause: A Leaf node attempted to join the cluster but could not find a Hub node to
which to connect.
Action: Verify that the clusterware stack is up and running on at least one Hub
node and, if not, start the stack on one or more Hub nodes. Verify that the Grid
Naming Service (GNS) resource is active on a Hub node. If not, start it on at least
one node. Check if the network connectivity is viable to all Hub nodes that have
the clusterware stack running. If the Leaf node startup has exhausted its retry
attempts, it may be necessary to start the clusterware stack manually on the Leaf
node. Contact Oracle Support Services if all of the above is verified and the Leaf
node is not able to find any Hub nodes to which to to connect.
CRS-01671: The value for parameter string is outside the allowed range of number
to number
Cause: An attempt was made to set a parameter with invalid value.
Action: Set the parameter with a value in the indicated range.
CRS-01672: The number of voting files currently available number has fallen to the
minimum number of voting files required number.
Cause: The Cluster Synchronization Service daemon (CSSD) has detected that the
number of voting files currently available is equal to the minimum number of
voting files required on the node. There is risk of node eviction in the case of
another voting disk failure.
Action: Restore access to voting files or configure additional voting disks so that
the number of voting files currently available is more than the minimum number
of voting files required.
CRS-01701: Initialization of the required component GIPC failed; details at string
in string
Cause: The initialization of the communications component GIPC failed, causing
the CSSD startup to fail.
Action: Collect alert log and the CSSD log indicated in the message and contact
Oracle Support Services.
CRS-01702: Initialization of the required component OLR failed; details at string in
string
Cause: The initialization of the local repository component OLR failed, causing
the CSSD startup to fail.
Action: Collect clusterware alert log and daemon logs and contact Oracle Support
Services.
CRS-01703: Initialization of the required component GPNP failed because the
GPNP server daemon is not up; details at string in string
Cause: The initialization of the configuration profile service failed because the
associated server is not up, causing the CSSD startup to fail.
Action: Collect clusterware alert log and daemon logs and contact Oracle Support
Services.
CRS-01704: Initialization of the required component string failed; details at string
in string
Cause: The initialization of a component required by the CSS daemon failed,
causing the CSSD startup to fail
Action: Collect clusterware alert log and daemon logs and contact Oracle Support
Services.
64-42 Oracle Database Error Messages
CRS-01705: Found number configured voting files but number voting files are
required, terminating to ensure data integrity; details at string in string
Cause: The voting file discovery was unable to locate a sufficient number of valid
voting files to guarantee data integrity and is terminating to avoid potential data
corruption.
Action: Delete the voting files that are no longer available, as indicated by
message number 1637, using appropriate 'crsctl' commands, run either on another
node where the clusterware stack is active, or by starting the clusterware stack in
exclusive mode.
CRS-01706: Found number of number voting files in a pending configuration change
but number voting files are required, terminating to ensure data integrity;
details at string in string
Cause: The voting file discovery was unable to locate a sufficient number of
voting files from the new configuration when a configuration change to add or
delete voting files is in progress. The CSS daemon is terminating to avoid potential
data corruption.
Action: Delete the voting files that are no longer available, as indicated by
message number 1638, using appropriate 'crsctl' commands, run either on another
node where the clusterware stack is active, or by starting the clusterware stack in
exclusive mode.
CRS-01707: Lease acquisition for node string number number completed
Cause: CSSD acquired a node number through a lease acquisition procedure.
Action: None
CRS-01708: Lease acquisition failed for node string because all lease slots are in
use; Details at string in string
Cause: The node failed to acquire a lease because all the lease slots were found to
be occupied by other nodes.
Action: Using olsnodes command get the list of leased nodes. Delete the unused
nodes using appropriate crsctl command.
CRS-01709: Lease acquisition failed for node string because no voting file has been
configured; Details at string in string
Cause: At least one voting file is required for CSSD to function properly. No
voting files have been configured.
Action: Add at lease one voting file using appropriate crsctl command.
CRS-01710: Lease acquisition failed for node string because CSSD failed to access
majority of voting files; Details at string in string
Cause: A majority of the voting files are not accessible by a node.
Action: Delete the voting files that are no longer available, as indicated by
message number 1637, using appropriate 'crsctl' commands, run either on another
node where the Clusterware stack is active, or by starting the Clusterware stack in
exclusive mode.
CRS-01711: Increasing the number of leases available for new nodes from number
to number
Cause: All the currently available leases are being used. Hence the number of
leases available are increased.
Action: None
CRS-00001 to CRS-29006 64-43
CRS-01712: Failed to save the node number acquired for node string; Details at
string in string
Cause: CSSD failed to save the node number acquired during startup. The node
number is saved to speed up the subsequent startup. Hence this is not a real
problem but just a performance degradation on the next startup.
Action: Collect Clusterware alert log, CSSD logs and OHASD logs indicated in
the message and contact Oracle Support Services.
CRS-01713: CSSD daemon is started in string mode
Cause: CSSD has been started on the node.
Action: None
CRS-01714: Unable to discover any voting files, retrying discovery in number
seconds; Details at string in string
Cause: No voting files were discovered. Possible reasons include:
- The filesystems the voting files are on are not available
- The voting files have been deleted
- The voting files are corrupted
Action: Verify that the filesystems that the voting files are on are active and that
the voting files have not been damaged. If necessary, start the clusterware stack in
exclusive mode using 'crsctl start crs -excl' and add voting files using 'crsctl add
css votedisk'
CRS-01715: A failure occurred in the CSS daemon during initialization; Details at
string in string
Cause: A fatal error occurred during the initialization of the CSS daemon.
Action: Check for prior errors logged in the alert log. Correct any errors that can
be corrected. If there are no errors shown, or the errors cannot be resolved, contact
Oracle Support Services
CRS-01716: The CSS daemon cannot join the cluster because the software version
string is lower than the active version string; Details at string in string
Cause: The cluster has been upgraded to the active version indicated. in the
message, but this node is at a lower software version, as indicated in the message.
Action: Upgrade this node to the active version indicated in the message
CRS-01717: The CSS daemon has detected a voting file add during startup and is
waiting for the add to complete; Details at string in string
Cause: A voting file add started on another node is in progress while this CSS
daemon is starting. To avoid the potential for data corruption, the CSS daemon on
this node must wait for the add to complete.
Action: This is normally a temporary condition that is automatically resolved. If
the clusterware stack cannot start on any node, this condition may be corrected by
starting the clusterware stack in exclusive mode using 'crsctl start crs -excl'
followed by 'crsctl stop crs' on one node. This will automatically correct the
condition and the clusterware can be started normally on all nodes.
CRS-01718: The CSS daemon is unable to continue due to a failure in required
component string.
Cause: A component required by the Cluster Synchronization Service (CSS)
daemon has failed. The CSS daemon is unable to continue and is failing.
64-44 Oracle Database Error Messages
Action: See the alert log for more detailed messages indicating the nature of the
problem and the location of additional information regarding this error.
CRS-01719: Cluster Synchronization Service daemon (CSSD) string not scheduled
for number msecs.
Cause: Excessive system load has prevented threads in the Cluster
Synchronization Service daemon (CSSD) from being scheduled for execution for
the time indicated in the message. This indicates the system is overloaded.
Action: Take steps to reduce the system load or increase system resources to
handle the load.
CRS-01805: Unable to connect to the CSS daemon, return code number
Cause: Could not initialize the CSS connection.
Action: Verify that the CSS daemon is running and restart it if it is not up. Retry
the operation.
CRS-01806: An error occurred when obtaining the node number of this host, return
code number
Cause: The request for node number of this node failed.
Action: Verify that the CSS daemon is running and restart it if not Retry the
operation that failed after restart. Look for error messages from the CSS daemon in
the alert log indicating any problems.
CRS-01807: An internal cluster configuration command failed in an OCR/OLR
operation. Details at string in string.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
CRS-01809: The cluster configuration command failed to open OCR or OLR key
string. Details at string in string.
Cause: An expected or required piece of configuration is missing from the cluster
or local registry.
Action: Use the ocrcheck utility to detect errors, and the ocrdump utility to review
the registry contents. If problems exist, the registry may need to be recovered or
restored. If the problem persists, contact Oracle Support Services.
CRS-02001: memory allocation error when initiating the connection
Cause: failed to allocate memory for the connection with the target process.
Action: None
CRS-02002: connection by user string to string refused
Cause: User command cannot connect to the target process.
Action: The user may not have sufficient privilege to connect.
CRS-02003: error number encountered when connecting to string
Cause: Connection to the target process failed.
Action: Examine whether the connection is made properly. Retry again at a later
time if necessary.
CRS-02004: error number encountered when sending messages to string
Cause: User command cannot communicate with the target process properly.
Action: Retry again at a later time.
CRS-00001 to CRS-29006 64-45
CRS-02005: timed out when waiting for response from string
Cause: the target process does not return acknowledgment in time.
Action: Retry again at a later time.
CRS-02006: error number encountered when receiving messages from string
Cause: no meta or response message was received from the target process.
Action: Retry again at a later time.
CRS-02007: invalid component key name used
Cause: the given component key name could not be recognized.
Action: re-run the command with a valid component key name.
CRS-02008: invalid message type used
Cause: an unrecognized message type was sent.
Action: Retry with a valid command again.
CRS-02009: unable to get authentication for user string
Cause: current user was not authenticated for connection.
Action: Log in as another user and try again.
CRS-02010: invalid response message from string
Cause: Response message has incorrect format.
Action: Retry again at a later time.
CRS-02011: no response at index number in response message from string
Cause: Response message did not contain a response at the specified index.
Action: If this is an unexpected result, retry again at a later time.
CRS-02012: syntax error in command
Cause: The command syntax is not valid.
Action: Issue 'crsctl debug -h' to see command syntax details. Watch out for ',' vs.
';'.
CRS-02013: user string does not have the required privileges
Cause: An attempt to make a diagnostic connection to a Clusterware daemon
failed because the user does not have required privileges.
Action: Use system tools to identify the user of the specified daemon process. Log
on as the same user as the specified daemon process and try again.
CRS-02101: The OLR was formatted using version number.
Cause: Successfully formatted the OLR location(s).
Action: None
CRS-02102: The OLR was restored from file string.
Cause: The OLR was successfully restored from a backup file as requested by the
user.
Action: None
CRS-02103: The OLR format was downgraded to version number.
Cause: The OLR was successfully downgraded to an earlier block format as
requested by the user.
64-46 Oracle Database Error Messages
Action: None
CRS-02104: The OLR was imported from string.
Cause: Successfully imported the OLR contents from a file.
Action: None
CRS-02105: The OLR upgrade was completed. Version has changed from number to
number. Details in string.
Cause: The OLR was successfully upgraded to a newer block format.
Action: None
CRS-02106: The OLR location string is inaccessible. Details in string.
Cause: An error occurred while accessing the OLR.
Action: Use the "ocrcheck -local" command to validate the accessibility of the
device and its block integrity. Check that the OLR location in question has the
correct permissions.
CRS-02112: The OLR service started on node string.
Cause: The OLR was successfully started.
Action: None
CRS-02114: Failed to import Oracle Local Registry from file string
Cause: Unable to read data from the import file and import to the local registry
Action: Check availability of the local registry and the details of the failure from
the log file
CRS-02120: The Oracle Local Registry has invalid contents. Details at string in
string.
Cause: Some of the Oracle Local Registry contents were invalid.
Action: Check the log file indicated in the message for more details. Use the
'ocrcheck -local' command to detect errors, and the 'ocrdump -local' command to
review the registry contents. If problems exist, the registry may need to be
recovered or restored. If the problem persists, contact Oracle Support Services.
CRS-02301: GPnP: string
Cause: This conveys a message from the GPnP layer to the alert log.
Action: Look up the imbedded message and respond accordingly.
CRS-02302: Cannot get GPnP profile. Error string (string).
Cause: Get GPnP profile operation failed.
Action: None
CRS-02303: GPNPD is not running on local node.
Cause: GPNPD is not running on local node. GPnP request cannot be completed.
Action: Make sure GPNPD is running and retry the operation.
CRS-02304: GPnP profile signature verification failed. string request aborted.
Cause: GPnP profile used in GPnP request or request result does not have a valid
signature.
Action: If error persists, contact Oracle Support Services.
CRS-02305: GPnP resource discovery (MDNSD) is not running on local node.
CRS-00001 to CRS-29006 64-47
Cause: GPnP resource discovery failed.
Action: Make sure resource discovery service (MDNSD) runs on local node.
CRS-02306: GPnP service on host "string" not found.
Cause: Remote GPnP service on requested host were not found in resource
discovery results.
Action: Make sure host is up, clusterware GPnP services (MDNSD and GPNPD)
are up and running and network connection is operational.
CRS-02310: Failed to initialize security facility.
Cause: Error occurred while initializing GPnP security component.
Action: If the problem persists, contact Oracle Support Services.
CRS-02311: Failed to initialize Resource Discovery. RD error: string. Make sure RD
providers installed properly.
Cause: Error occurred while initializing GPnP Resource Discovery (RD).
Action: If the problem persists, contact Oracle Support Services.
CRS-02312: Failed to initialize XML Developer's Kit (XDK). XDK error string.
Cause: Error occurred while initializing XML Developer's Kit component (XDK).
Action: If the problem persists, contact Oracle Support Services.
CRS-02313: Failed to initialize GIPC communication layer. GIPC error: string.
Cause: Error occurred while initializing GIPC communication layer.
Action: If the problem persists, contact Oracle Support Services.
CRS-02314: Cannot initialize locking subsystem.
Cause: Error occurred while initializing locking subsystem.
Action: If the problem persists, contact Oracle Support Services.
CRS-02315: Failed to initialize GPnP certkey providers.
Cause: GPnP certkey provider(s) data was not found or corrupt.
Action: If the problem persists, contact Oracle Support Services.
CRS-02316: Cannot initialize GPnP, string (string).
Cause: General GPnP initialization failure.
Action: If the problem persists, contact Oracle Support Services.
CRS-02317: Cannot get local GPnP security keys (wallet).
Cause: GPnP wallet(s) directory or files were not found or corrupt.
Action: If the problem persists, contact Oracle Support Services.
CRS-02318: GPNPD is not found.
Cause: Local GPnP service is not found.
Action: Make sure GPNPD is running.
CRS-02319: No cluster name found in GPnP profile.
Cause: Profile is invalid - it must specify a mandatory clustername parameter.
Action: Contact Oracle Support Services.
CRS-02320: No sequence number found in GPnP profile.
64-48 Oracle Database Error Messages
Cause: Profile is invalid - it must specify a mandatory profile sequence parameter.
Action: Contact Oracle Support Services.
CRS-02321: Flex Cluster mode configuration not found in Grid Plug and Play
(GPnP) profile.
Cause: The Profile did not have Flex Cluster mode configuration and could not be
used to bring up the stack in Flex Cluster mode.
Action: Contact Oracle Support Services.
CRS-02322: Cannot get local GPnP profile. Error initializing GPnP profile cache
providers.
Cause: Local GPnP setup was invalid.
Action: Contact Oracle Support Services.
CRS-02323: Error initializing one of the GPnP profile cache providers.
Cause: Local GPnP setup was invalid.
Action: Contact Oracle Support Services.
CRS-02324: Errors occurred while trying to push GPnP profile.
Cause: GPnP profile update partially failed.
Action: Try to repeat the update. If the problem persists, contact Oracle Support
Services.
CRS-02325: Unable to get GPnP profile from requested cluster nodes.
Cause: Get GPnP profile from remote nodes failed.
Action: Try to repeat the update. If the problem persists, contact Oracle Support
Services.
CRS-02326: GPnP profile is different across cluster nodes. string.
Cause: GPnP profile was different across cluster nodes.
Action: Try to repeat the update. If the problem persists, contact Oracle Support
Services.
CRS-02327: GPNPD already running on node string. Terminating.
Cause: GPnP service instance was already running on node.
Action: Bring down existing GPNPD instance first.
CRS-02328: GPNPD started on node string.
Cause: GPnP service started on node.
Action: None
CRS-02329: GPNPD on node string shut down.
Cause: GPnP service was shut down by request.
Action: None
CRS-02330: GPNPD failed to start listening for GPnP peers.
Cause: GPnP service failed to open server endpoint.
Action: Check GPNPD logs for the cause. If the problem persists, contact Oracle
Support Services.
CRS-02331: Error getting GPnP profile from "string".
Cause: Get remote GPnP profile from remote node operation failed.
CRS-00001 to CRS-29006 64-49
Action: Retry request. If the problem persists, contact Oracle Support Services.
CRS-02332: Error pushing GPnP profile to "string".
Cause: Push GPnP profile to remote node operation failed.
Action: Retry request. If the problem persists, contact Oracle Support Services.
CRS-02333: Could not write GPnP profile to local cache.
Cause: GPNPD service cannot save GPnP profile to local cache.
Action: Make sure there is at least 10MB of free disk space in Clusterware home. If
the problem persists, contact Oracle Support Services.
CRS-02334: Could not delete pending GPnP profile from local cache.
Cause: GPNPD service cannot delete GPnP profile from local cache.
Action: If the problem persists, contact Oracle Support Services.
CRS-02335: Could not write pending GPnP profile to local cache.
Cause: GPNPD service cannot save GPnP profile to local cache.
Action: Make sure there is at least 10MB of free disk space in Clusterware home. If
the problem persists, contact Oracle Support Services.
CRS-02336: GPNPD failed get local GPnP profile and cannot continue. Check
gpnpd/gpnp client logs.
Cause: GPnP service cannot find a profile in local cache, and cannot continue.
Action: Contact Oracle Support Services.
CRS-02339: GPNPD advertisement with string failed. This may block some cluster
configuration changes. Advertisement attempts will continue.
Cause: Grid Plug and Play Daemon (GPNPD) failed to advertise itself with a
specified service (for example, Multicast Domain Name Service Daemon
(MDNSD) or Oracle Grid Naming Service (GNS)). Advertisement attempts will
continue at regular intervals, and alerts will periodically be issued.
Action: Make sure the specified service is running and wait for the success
message CRS-2337 before changing the cluster configuration.
CRS-02340: Errors occurred while processing received gpnp message.
Cause: Invalid GPnP message received.
Action: Check gpnp client and GPNPD logs for details. If the problem persists,
contact Oracle Support Services.
CRS-02341: GPNPD on node string shutting down on signal number.
Cause: GPnP service shutting down due to received signal.
Action: Contact your cluster administrator.
CRS-02342: GPnP messaging received error : string (string).
Cause: GPnP message error received.
Action: If the problem persists, contact Oracle Support Services.
CRS-02401: The Cluster Time Synchronization Service started on host string.
Cause: The Cluster Time Synchronization Service successfully started on the listed
node.
Action: None
64-50 Oracle Database Error Messages
CRS-02402: The Cluster Time Synchronization Service aborted on host string.
Details at string in string.
Cause: The Cluster Time Synchronization Service aborted due to an internal error.
Check the Cluster Time Synchronization Service log file to determine the cause.
Action: Determine whether the Cluster Time Synchronization Service has
auto-started.
CRS-02403: The Cluster Time Synchronization Service on host string is in observer
mode.
Cause: The Cluster Time Synchronization Service detected an active vendor time
synchronization service on at least one node in the cluster.
Action: Oracle Clusterware requires a time synchronization service in active
mode. Oracle Clusterware will work with a vendor service or the Cluster Time
Synchronization Service. If you want to change the Cluster Time Synchronization
Service to active mode, stop and deconfigure the vendor time synchronization
service on all nodes.
CRS-02404: The Cluster Time Synchronization Service detects that the local time is
significantly different from the mean cluster time. Details in string.
Cause: The difference between the local time and the time on the reference node
was too much to be corrected.
Action: Shutdown the Oracle Clusterware on the local node. Adjust the clock via
native platform or OS methods. Restart the Oracle Clusterware on the local node.
CRS-02405: The Cluster Time Synchronization Service on host string is shutdown
by user
Cause: The Cluster Time Synchronization Service on listed node was terminated
by a user.
Action: None
CRS-02406: The Cluster Time Synchronization Service timed out on host string.
Details in string.
Cause: A Cluster Time Synchronization Service action failed. The information
from the reference node was discarded.
Action: Verify all network connections between cluster nodes and repair any
problematic connections. If no network problems are found,
1. Run diagcollection.pl.
2. Contact Oracle Support Services.
CRS-02407: The new Cluster Time Synchronization Service reference node is host
string.
Cause: A new Cluster Time Synchronization Service reference node has been
elected.
Action: None
CRS-02408: The clock on host string has been updated by the Cluster Time
Synchronization Service to be synchronous with the mean cluster time.
Cause: The clock was updated to be in sync with the mean cluster time.
Action: None
CRS-00001 to CRS-29006 64-51
CRS-02409: The clock on host string is not synchronous with the mean cluster time.
No action has been taken as the Cluster Time Synchronization Service is
running in observer mode.
Cause: The clock was not in sync with the mean cluster time. No action has been
taken as Cluster Time Synchronization Service is running in observer mode.
Action: Verify correct operation of the vendor time synchronization service on the
node.
CRS-02410: The Cluster Time Synchronization Service on host string is in active
mode.
Cause: The Cluster Time Synchronization Service did not detect an active vendor
time synchronization service on any node in the cluster.
Action: None. If a vendor time synchronization service is preferred to the Cluster
Time Synchronization Service, then configure and start the vendor time
synchronization service on all nodes to change the Cluster Time Synchronization
Service to observer mode.
CRS-02411: The Cluster Time Synchronization Service will take a long time to
perform time synchronization as local time is significantly different from mean
cluster time. Details in string.
Cause: The difference between the local time and the time on the reference node
was too much to be synchronized in a short period.
Action: (Optional) Shutdown and restart the Oracle Clusterware on this node to
instantaneously synchronize the time with the reference node.
CRS-02412: The Cluster Time Synchronization Service detects that the local time is
significantly different from the mean cluster time. Details in string.
Cause: The difference between the local time and the time on the reference node
was too large. No action has been taken as the Cluster Time Synchronization
Service was running in observer mode.
Action: Verify correct operation of the vendor time synchronization service on the
node. Alternatively, if you want to change the Cluster Time Synchronization
Service to active mode, stop and deconfigure the vendor time synchronization
service on all nodes.
CRS-02413: The Cluster Time Synchronization Service is unable to perform step
time synchronization due to high network latency with the reference node. The
local time is not significantly different from the mean cluster time. The Cluster
Time Synchronization Service is entering slew time synchronization mode.
Cause: The Cluster Time Synchronization Service experienced high network
latency. The local time was not significantly different from the mean cluster time;
therefore, the Cluster Time Synchronization Service will maintain the system time
with slew time synchronization.
Action: Determine the root cause of high network latency, and perform
appropriate repair if necessary.
CRS-02414: The Cluster Time Synchronization Service is unable to perform step
time synchronization due to high network latency with the reference node. The
local time is significantly different from the mean cluster time. The Cluster
Time Synchronization Service is aborting.
Cause: The Cluster Time Synchronization Service experienced high network
latency. The local time was significantly different from the mean cluster time;
therefore, the Cluster Time Synchronization Service is aborting.
64-52 Oracle Database Error Messages
Action: Shut down the Oracle Clusterware on the local node. Determine the root
cause of high network latency. Perform appropriate repair if necessary, then restart
the Oracle Clusterware on the local node.
CRS-02415: Resource 'string' cannot be registered because its owner 'string' is not
the same as the Oracle Restart user 'string'.
Cause: The resource indicated in the message could not be registered because it
was owned by a user other than the Oracle Restart user.
Action: Resubmit as the Oracle Restart user.
CRS-02500: Cannot stop resource 'string' as it is not running
Cause: A request to stop a resource that is not running was received.
Action: Check the current state of the resource, it should no longer be running.
CRS-02501: Resource 'string' is disabled
Cause: The resource is currently disabled and so may not be operated on.
Action: Enable the resource and re-submit your request.
CRS-02502: Resource 'string' has dependency error because of resource 'string'
Cause: The attempted operation has failed because of a dependency on the
specified resource.
Action: Ensure that the intended operation is still desired. If so, the specified
resource and its state need to be evaluated to decide on the corrective action.
CRS-02503: Resource 'string' is in UNKNOWN state and must be stopped first
Cause: The resource cannot be acted upon when it is in the UNKNOWN state.
Action: Stop the resource manually, make sure it is OFFLINE, and then re-submit
the request.
CRS-02504: Resource 'string' cannot be placed on any online servers that satisfy its
placement policy
Cause: The resource cannot be placed because of the constrains imposed by its
placement policy.
Action: Either change the placement policy of the resource or re-evaluate the
request.
CRS-02505: Another operation is being performed on 'string'. Retry later
Cause: Another operation is being performed on the specified object.
Action: Typically, waiting and retrying or using a way to queue the request are
the two choices to proceed.
CRS-02506: Operation on 'string' has been cancelled
Cause: A scheduled or running operation has been cancelled.
Action: None
CRS-02507: Unsupported modifier 'string' in dependency 'string'
Cause: The modifier is not a valid one.
Action: Check the specification of the dependency, fix the problem indicated, and
resubmit the request.
CRS-02508: Incomplete specification of dependency 'string'
Cause: The specification does not have the dependent object specified.
CRS-00001 to CRS-29006 64-53
Action: Check the specification of the dependency, fix the problem indicated, and
resubmit the request.
CRS-02509: Resource type 'string' used in dependency 'string' does not exist or is
not registered
Cause: The resource type referenced by the dependency specification is not found.
Action: Check the specification of the dependency, fix the problem indicated, and
resubmit the request.
CRS-02510: Resource 'string' used in dependency 'string' does not exist or is not
registered
Cause: The resource referenced by the dependency specification is not found.
Action: Check the specification of the dependency, fix the problem indicated, and
resubmit the request.
CRS-02511: Attribute 'string' cannot be specified on per-X basis for resource 'string'
Cause: The specified attribute is specified on per-X basis, which is not allowed for
this attribute.
Action: Remove the specification.
CRS-02512: Attribute format for 'string' is invalid in resource 'string'
Cause: The specification does not follow valid format.
Action: Correct the specification and re-submit the request.
CRS-02513: Attribute format for 'string' is invalid
Cause: The specification does not follow valid format.
Action: Correct the specification and re-submit the request.
CRS-02514: Dependency attribute specification 'string' is invalid in resource 'string'
Cause: The specification of relations does not follow valid format.
Action: Correct the specification and re-submit the request.
CRS-02515: Circular dependency found for resource 'string'
Cause: The resource dependency specification has a circular dependency.
Action: Circular dependencies are disallowed. Change the profile and re-submit.
CRS-02516: Server pool is not specified for resource 'string'
Cause: The resource profile does not have server pool specified.
Action: Either specify a an existing server pool or HOSTING_MEMBERS in the
profile and re-submit the request.
CRS-02517: Required attribute 'string' is not specified for resource 'string'
Cause: A required attribute is missing from the resource profile.
Action: Add the attribute to the profile and re-submit the request.
CRS-02519: Either 'string' or 'string' must be specified when 'string' is 'string'
Cause: Neither or both of the parameters was specified.
Action: Specify exactly one of the two and re-submit.
CRS-02520: Invalid value 'string' for attribute 'string'
Cause: The value specified for the attribute is inappropriate or invalid.
Action: Review the value, correct the problem and re-submit the request.
64-54 Oracle Database Error Messages
CRS-02521: Read-only attribute 'string' cannot be modified
Cause: An attempt was made to modify a read-only attribute.
Action: None
CRS-02522: No value is specified
Cause: There is nothing specified for the value.
Action: Provide a valid value.
CRS-02523: Invalid characters are used when specifying the value
Cause: 1 or more characters used to specify a value are inappropriate.
Action: Provide a valid value.
CRS-02524: Value specification may only contain
'string'/'string'/'string'/'string'/'string'/'string'
Cause: The value specified is not any of the allowed.
Action: The value must be one of the allowed ones, as specified. Provide a valid
one.
CRS-02525: All instances of the resource 'string' are already running; relocate is not
allowed because the force option was not specified
Cause: All instances of the resource are running and the start request does not
have the force option specified.
Action: Either specify the force option or re-evaluate the need for the request.
CRS-02526: There are no available instances of resource 'string' to start on 'string'
Cause: All instances of the resource are already running or otherwise unavailable
to be started on the specified server.
Action: Create more instances or re-evaluate the need for the request.
CRS-02527: Unable to start 'string' because it has a 'string' dependency on 'string'
Cause: Start/relocate of the resource is impossible because it has a dependency on
another entity which prevents it from being able to start.
Action: This message will usually be coupled with another one that details the
nature of the problem with the other resource. Follow up on the action
recommended for that message.
CRS-02528: Unable to place an instance of 'string' as all possible servers are
occupied by the resource
Cause: Out of possible servers to place the resource on, all already host an
instance of the resource.
Action: You need to add more servers or change the resource placement
parameters to allow placement on additional servers.
CRS-02529: Unable to act on 'string' because that would require stopping or
relocating 'string', but the force option was not specified
Cause: Acting on the resource requires stopping or relocating other resources,
which requires that force option be specified, and it is not.
Action: Re-evaluate the request and if it makes sense, set the force option and
re-submit.
CRS-02530: Unable to stop 'string' because 'string' has a stop-time 'string'
dependency on it
CRS-00001 to CRS-29006 64-55
Cause: Stopping the resource is impossible because it has a dependency on
another resource and there is a problem with that other resource.
Action: This message will usually be coupled with another one that details the
nature of the problem with the other resource. Follow up on the action
recommended for that message.
CRS-02531: Internal error while operating on 'string'
Cause: General-purpose message for highly unexpected internal errors.
Action: This message will usually be preceded by another one with a more
specific problem description. Contact Oracle Support Services.
CRS-02532: OCR write failed for 'string'
Cause: Unknown, but would usually imply corruption or unavailability of the
OCR or a lack of permissions to update keys or a software defect in the OCR code.
Action: Validate that OCR is accessible, validate that key permissions match.
Contact Oracle Support Services.
CRS-02533: Server 'string' is down. Unable to perform the operation on 'string'
Cause: The server is down and therefore the operation cannot be performed.
Action: Try using a different server.
CRS-02534: Resource type 'string' is not registered
Cause: The specified resource type is not registered.
Action: Re-evaluate the request.
CRS-02535: Resource type 'string' does not have attribute 'string' and thus it cannot
be updated
Cause: An non-existing attribute cannot be modified.
Action: Re-evaluate the request.
CRS-02536: Required attribute 'string' is not specified for 'string'
Cause: A required attribute is missing from the entity's profile.
Action: Add the attribute to the profile and re-submit the request.
CRS-02537: Resource type 'string' cannot be extended directly; use its extensions
instead
Cause: The type cannot be extended.
Action: Use a type that extends this one.
CRS-02538: Value for attribute 'string' is of incorrect type (string is expected)
Cause: The type of the value is not correct.
Action: Re-submit the request with the value specified in proper type.
CRS-02539: A resource with the name 'string' is already registered
Cause: A resource with specified name is already registered.
Action: Use a unique name for the new resource.
CRS-02540: Value for attribute 'string' is of incorrect type (integer is expected)
Cause: The type of the value is not correct.
Action: Re-submit the request with the value specified in proper type.
CRS-02541: Server pool 'string' is not registered
64-56 Oracle Database Error Messages
Cause: The specified server pool is not registered.
Action: Re-evaluate the request.
CRS-02542: The tag 'string' is mentioned in both 'string' and 'string' attributes,
which is conflicting
Cause: The same tag is used to specify exclusive as well as overlapping server
pools. These requirements cannot be satisfied simultaneously.
Action: Remove the tag from one of the attributes.
CRS-02543: The type is not specified for attribute 'string'
Cause: Value type specification is missing for the attribute.
Action: Specify a proper type and re-submit.
CRS-02544: The name 'string' is longer than the allowed maximum of 'number'
characters
Cause: The name is too long.
Action: Use a shorter name.
CRS-02545: Cannot operate on 'string'. string
Cause: The entity specified is currently locked as part of another operation.
Action: Re-submit the request later.
CRS-02546: Server 'string' is not online
Cause: Operation is invalid because the specified server is not online.
Action: Provide an online server name.
CRS-02547: Update of an internal or read-only attribute 'string' for resource 'string'
is not allowed
Cause: Internal and read-only attributes may not be updated.
Action: Exclude internal and read-only attributes from your request.
CRS-02548: A cyclical dependency on 'string' is detected from 'string'
Cause: There is a cycle in the dependency graph. Cycles are disallowed.
Action: Re-evaluate the dependency graph.
CRS-02549: Resource 'string' cannot be placed on 'string' as it is not a valid
candidate as per the placement policy
Cause: The resource cannot be placed because of the constrains imposed by its
placement policy.
Action: Either change the placement policy of the resource or re-evaluate the
request.
CRS-02550: Resource 'string' cannot be failed-over because it has other
non-OFFLINE instances on the server 'string'
Cause: The resource cannot be failed-over from the specified server because has
other non-OFFLINE instances still available on that server and fail-over can only
be done on all instances of the resource on the server as a whole.
Action: None
CRS-02551: Resource 'string' cannot be failed-over because it is of type 'string',
which cannot relocate
Cause: Local resources cannot be relocated from one server to another.
CRS-00001 to CRS-29006 64-57
Action: None
CRS-02552: There are no available instances of resource 'string' to start.
Cause: All instances of the resource are in the ONLINE or UNKNOWN state.
Action: Re-evaluate the need for the request.
CRS-02553: Server pool 'string' cannot be unregistered as it does not exist
Cause: The server pool you are trying to remove does not exist.
Action: Make sure the server pool you are trying to remove exists.
CRS-02554: Server pool 'string' cannot be unregistered as it is referenced by
resource 'string'
Cause: The server pool you are trying to remove has references to it.
Action: Make sure the server pool you are trying to remove is not referenced by
other entities.
CRS-02555: Resource 'string' cannot be relocated as it is a local resource
Cause: The request is impossible to complete as local resources never relocate.
Action: Re-evaluate the request.
CRS-02556: Resource 'string' cannot be restored to its original state after a failed
relocate attempt
Cause: After an unsuccessful attempt to relocate a resource, crsd was unable to
restore the resource.
Action: Manual intervention may be required. Re-try starting the resource.
CRS-02557: Server pool 'string' cannot be unregistered as it is referenced by server
pool 'string'
Cause: The server pool you are trying to remove has references to it.
Action: Make sure the server pool you are trying to remove is not referenced by
other entities.
CRS-02558: Resource type 'string' may not be unregistered as there are types that
are based on it.
Cause: Types may not be unregistered if they have derived types.
Action: Remove derived types first, then remove this one.
CRS-02559: Resource type 'string' may not be unregistered as it has the following
resources:string
Cause: Types may not be unregistered if they have resources registered.
Action: Remove the specified resources first, then remove the type.
CRS-02560: Resource type 'string' does not exist
Cause: The resource type referenced does not exist.
Action: Specify a correct type.
CRS-02561: Resource type 'string' may not be unregistered as it is referenced by
resource 'string'
Cause: Types may not be unregistered if they are referenced in resource
dependencies.
Action: Make sure there are no existing resources that reference this type in their
dependencies.
64-58 Oracle Database Error Messages
CRS-02562: Resource 'string' cannot be relocated as it is not running
Cause: Only currently running resources can be relocated.
Action: Make sure the resource is running before issuing the request.
CRS-02563: Attempt to start resource 'string' on 'string' has failed. Will re-retry on
'string' now.
Cause: Undirected (no target member) start of a resource has failed for the server;
a retry is in progress.
Action: None, this is an informational message.
CRS-02564: Failed to relocate resource 'string'. Will attempt to restore it on 'string'
now.
Cause: Resource relocate operation was unable to relocate the resource to any of
the possible servers.
Action: None, this is an informational message.
CRS-02565: Attempt to relocate resource 'string' to 'string' has failed. Will re-retry
on 'string' now.
Cause: Undirected (no target member) relocate of a resource has failed for the
server; a retry is in progress.
Action: None, this is an informational message.
CRS-02566: User 'string' does not have sufficient permissions to operate on resource
'string', which is part of the dependency specification.
Cause: User does not have permissions to operate on the resource as it will
prevent the current resource from starting or staying online in future.
Action: The user performing the operation must have access privileges to operate
on the entire resource dependency tree. The user must either be given those
privileges by modifying the dependent resources' access rights or another user
having permissions should perform this operation.
CRS-02567: Error while parsing the default value for attribute 'string'
Cause: The default value specified is not proper.
Action: Make sure the value is proper for its type.
CRS-02568: Base resource type name 'string' does not exist
Cause: The name of a base type used is not valid.
Action: Use an existing type as a base.
CRS-02569: Unsupported value type is used in attribute 'string'
Cause: An unsupported value type was specified in the attribute's definition.
Action: Use one of the supported types.
CRS-02570: Internal Error: Number of objects 'number' is different from number of
lists 'number'
Cause: This is an internal error.
Action: Contact Oracle Support Services.
CRS-02571: Dependency kind 'string' is specified more than once for resource
'string'
Cause: A dependency kind is used more than once in the profile of the resource.
CRS-00001 to CRS-29006 64-59
Action: Combine multiple specifications of the same dependency kind into a
single clause.
CRS-02572: 'string' is not a supported Special Value
Cause: The specified identifier is not a valid Special Value.
Action: Check the value for correctness.
CRS-02573: ACL entry for owner field is missing.
Cause: The complete value for the ACL attribute has been provided but it is
missing a mandatory entry specifying permissions for the owner.
Action: Include permissions for the owner in the value of ACL attribute.
CRS-02574: ACL entry for primary group field is missing.
Cause: The complete value for the ACL attribute has been provided but it is
missing a mandatory entry specifying permissions for the primary group.
Action: Include permissions for the primary in the value of ACL attribute.
CRS-02575: ACL entry for users other than the owner and those belonging to
primary group is missing.
Cause: The ACL attribute is missing a mandatory entry specifying permissions
for users other than the owner and those belonging to the primary group.
Action: Include permissions for other users in the value of ACL attribute.
CRS-02576: User 'string' is not a member of group 'string'
Cause: The group that the caller claims to be a member of has no such user by
configuration.
Action: Make sure the group is configured to have the calling user as a member.
CRS-02577: Use of 'string' in attributes and values is not allowed
Cause: A disallowed character was detected.
Action: Retry without the disallowed character.
CRS-02578: Value of 'string' (number) may not be greater than that of 'string'
(number)
Cause: The specified values do not make sense - one may not be less than the
other.
Action: Use valid values.
CRS-02579: Value 'number' may not be less than 'number'
Cause: The value is less than the allowed minimum.
Action: Use a proper value.
CRS-02580: Value 'number' is neither 'number' nor 'number'
Cause: The value must be one of the two and it is neither.
Action: Use a proper value.
CRS-02581: Value 'string' is not any of the following 'string', 'string', 'string'
Cause: The value must be one of the ones specified and it is not.
Action: Use a proper value.
CRS-02582: Value 'string' does not follow expected format: [s|d|m|w|h]
Cause: The value specification does not follow required format.
64-60 Oracle Database Error Messages
Action: Use a proper value.
CRS-02583: Value 'number' must be in the 'number' - 'number' range
Cause: The value is not within the allowed range.
Action: Use a proper value.
CRS-02584: Value 'string' is not allowed here
Cause: The value is not proper in this context.
Action: Use a proper value.
CRS-02585: Deletion of built-in resource types is not allowed
Cause: An attempt was made to delete a built-in resource type.
Action: Removal of built-in types is not allowed.
CRS-02586: Deletion of a running resource 'string' requires the force option
Cause: An attempt was made to delete a resource that is still running.
Action: Stop the resource first using the 'crsctl stop resource' command. If the
resource cannot be stopped, specify the force option to the 'crsctl delete' command.
CRS-02587: Attribute 'string' is internal and thus may not be overridden in type
'string'
Cause: Attributes defined in built-in resource types that are internal to the
subsystem may never be overridden in user-defined resource types.
Action: Do not specify this attribute in the new user-defined type.
CRS-02588: A cyclical dependency on 'string' is detected from 'string' via type
'string'
Cause: There is a cycle in the dependency graph, via a resource type. Cycles are
disallowed.
Action: Re-evaluate the dependency graph.
CRS-02589: Relation modifier 'string' is invalid for relation kind 'string'
Cause: An unexpected relation modifier is specified.
Action: Use defined modifiers only.
CRS-02590: A resource name may not be empty or contain spaces
Cause: A name must not be empty or contain space character(s).
Action: Specify a valid name.
CRS-02591: A server pool name may not be empty or contain spaces
Cause: A name must not be empty or contain space character(s).
Action: Specify a valid name.
CRS-02592: A type name may not be empty or contain spaces
Cause: A name must not be empty or contain space character(s).
Action: Specify a valid name.
CRS-02593: Comparator value 'string' in the filter specification is not supported
Cause: An unsupported comparator was supplied.
Action: Use a supported value.
CRS-02594: Filter specification 'string' is invalid
CRS-00001 to CRS-29006 64-61
Cause: The filter specification invalid or empty.
Action: Provide a valid filter or do not specify you have one.
CRS-02595: Server pool 'string' has already been registered
Cause: A server pool with this name has already been registered.
Action: Provide a name that is not currently in use.
CRS-02596: Modifications to the 'string' attribute of server pools are not supported
Cause: Changes to the value of the attribute are not allowed.
Action: Create a different pool with the desired value and use it.
CRS-02597: Server 'string' may not be moved to pool 'string'
Cause: Because of one or more of configuration-related constrains, the move of
the server is not a valid operation at the time.
Action: Re-evaluate the request's validity in the context of the entire error stack.
CRS-02598: Server pool 'string' is already at its maximum size of 'number'
Cause: The pool is already at the maximum.
Action: The request is impossible to execute.
CRS-02599: Server 'string' is not in a parent pool of 'string'
Cause: The server is not in a parent pool of the pool in question.
Action: The request is impossible to execute.
CRS-02600: Server 'string' is already in another top-level server pool
Cause: The server is already consumed by a different top-level pool and all such
pools are exclusive as far as server ownership.
Action: The request is impossible to execute.
CRS-02601: Server 'string' is not explicitly mentioned as a candidate by server pool
'string'
Cause: The server is not in the list of names the pool allows as candidates.
Action: Use a server that is in the specified group.
CRS-02602: Server 'string' is in server pool 'string' which is exclusive with server
pool 'string'
Cause: The server is already in a pool that's configured to be exclusive with the
one at hand.
Action: The request is impossible to execute.
CRS-02603: Server 'string' cannot be assigned to server pool 'string' because it is not
a top-level pool
Cause: Server movement is only supported between top-level server pools.
Action: The request is impossible to execute as such an action is not supported.
CRS-02604: Server 'string' is already assigned to server pool 'string'
Cause: Server movement makes no sense: the server is already in the target pool.
Action: Check the request validity.
CRS-02605: Server 'string' cannot be relocated from server pool 'string' because the
pool disallows transfers
Cause: The server pool is configured not to allow server transfers.
64-62 Oracle Database Error Messages
Action: Check the request validity.
CRS-02606: Server 'string' may not be relocated from server pool 'string' because it
is not above its minimum size
Cause: Server pools of identical or higher importance may not be used to steal
servers from if they are not above their minimum size.
Action: Update the configuration of server pools by either changing the
importance or the minimum size or both and then re-submit the request.
CRS-02607: Attribute 'string' has not been specified on per-X basis for resource
'string'
Cause: The specified attribute has not been specified on per-X basis for this
resource.
Action: Check the per-X attribute for the resource, fix and resubmit.
CRS-02608: Attribute 'string' is not a per-X value and cannot be removed
Cause: The specified attribute is not a per-X value.
Action: Check the per-X attribute for the resource, fix and resubmit.
CRS-02609: Server 'string' may not be relocated to server pool 'string' as the pool
disallows transfers
Cause: The server pool is configured not to allow server transfers.
Action: Check the request validity.
CRS-02610: Server 'string' is unavailable
Cause: The server is not available at the moment.
Action: Check available servers and rerun the request with an active server.
CRS-02611: Server pool 'string' is built-in and may not be deleted
Cause: Built-in server pools may never be deleted.
Action: None
CRS-02612: Server pools do not have attribute named 'string'
Cause: An unsupported attribute was provided as part of the register or update
request.
Action: Double check the attributes that are supplied.
CRS-02613: Could not find resource 'string'.
Cause: An attempt was made to operate on a resource that is not registered.
Action: Check if the resource is registered.
CRS-02614: Could not find resource type 'string'.
Cause: An attempt was made to operate on a resource type that is not registered.
Action: Check if the resource type is registered.
CRS-02615: Could not find server pool 'string'.
Cause: An attempt was made to operate on a server pool that is not registered.
Action: Check if the server pool is registered.
CRS-02616: The owner of resource type 'string' does not have sufficient permissions
to operate on resource type 'string', from which it is directly or indirectly
derived.
CRS-00001 to CRS-29006 64-63
Cause: Update of a resource type in the current manner is not allowed as it will
severely limit operations on the current resource type and will potentially prevent
resources of derived types from starting or staying online in future.
Action: If access privileges must be changed, then they need to changed
bottom-up in a dependency.
CRS-02617: Incorrect value of attribute flags has been specified for attribute string.
Only READONLY flag can be changed for a type attribute.
Cause: Attempt was made to update the flag on a resource type attribute. The
only change allowed is to the readonly property of the attribute.
Action: Provide correct value of the attribute flag.
CRS-02618: Cannot change data type string of existing attribute string to type string.
Cause: Attempt was made to update the data type of attribute value.
Action: Data type of the attribute cannot be changed.
CRS-02619: Server pool 'string' may not be edited
Cause: The pool's attributes may not be edited.
Action: None
CRS-02620: Attribute 'string' of server pool 'string' may not be edited
Cause: Editing of the attribute of the server pool is not allowed.
Action: None
CRS-02621: Server 'string' is assigned to 'string' to which you have no permission.
The operation is not authorized.
Cause: The operation requires making the specified server a placement candidate
for the resources owned by the requesting user. However, this is not allowed
because the user is not authorized to utilize the server.
Action: Either specify another server that that's in the pool you are authorized to
use or request that a cluster administrator gives you access to the pool to which
the server is currently assigned.
CRS-02622: Server 'string' is not assigned to any server pool and thus may only be
specified by a cluster administrator
Cause: The operation makes use of the server that's not currently assigned to a
server pool and the requesting user is not a cluster administrator. Because of that
use of the server cannot be authorized at the moment.
Action: Either request a cluster administrator to perform the operation for you or
wait until the server has joined the cluster and is assigned to a pool to which you
have an x-permission.
CRS-02623: Server pool 'string' cannot accept server 'string' because its name is not
specified in 'string'
Cause: Only servers whose names are mentioned in the attribute may be assigned
to the pool.
Action: None
CRS-02624: One of 'string', 'string' must be specified when 'string' is 'string'
Cause: Neither of the parameters was specified.
Action: Specify either of the two and re-submit.
64-64 Oracle Database Error Messages
CRS-02625: Owner of resource 'string' does not have execute permission to pool
'string' and may not use it
Cause: Resource profile references a server pool to which the owner of the
resource does not have the X-permission.
Action: Either have the pool's permission changed appropriately or use a different
pool.
CRS-02626: Owner of server pool 'string' does not have execute permission to
parent server pool 'string'
Cause: Parent pool does not have the X-permission for the pool's parent.
Action: Either have the desired parent pool's permission changed appropriately
or use a different pool.
CRS-02627: You must have execute permission on pool 'string' to relocate server
'string'
Cause: The client requesting the operation does not have proper permissions to
the specified pool.
Action: Acquire required permissions or use another server/pool. Permissions
can be added by an authorized user using 'crsctl setperm' command.
CRS-02628: Server pool 'string' may not be a parent of itself
Cause: An attempt was made to make a server pool a parent of itself.
Action: Re-evaluate the server pool dependencies.
CRS-02629: Only cluster administrators are allowed to create top-level server pools
Cause: An attempt was made to create a server pool that has no parent pools.
Creation of such pools is only allowed for cluster administrators.
Action: Either acquire the role of cluster administrator or have one create the pool
for you.
CRS-02630: Only cluster administrators are allowed to create local resources
Cause: An attempt was made to create a local resource which is only allowed for
cluster administrators.
Action: Either acquire the role of cluster administrator or have one create the
resource for you.
CRS-02631: Only cluster administrators are allowed to create cluster resources that
may run anywhere in the cluster
Cause: An attempt was made to create a cluster resource that may run anywhere
in the cluster which is only for cluster administrators.
Action: Either acquire the role of cluster administrator or have one create the
resource for you.
CRS-02632: There are no more servers to try to place resource 'string' on that would
satisfy its placement policy
Cause: After one or more attempts, the system ran out of servers that can be used
to place the resource and satisfy its placement policy.
Action: None
CRS-02640: Required resource 'string' is missing.
Cause: A resource that's configured as required is not registered.
CRS-00001 to CRS-29006 64-65
Action: Register the missing resource or update the dependency specification so
as to the missing resource is not required for start.
CRS-02641: The value of 'string' cannot override that defined in the resource's type:
'string'
Cause: Agent filename cannot be overridden on per-resource basis.
Action: Define a sub-type that uses the agent. Then create a resource of this new
type.
CRS-02642: Relocate resource is not a valid command for this configuration
Cause: A relocate command was issued in the configuration where it is not
possible in principle.
Action: None
CRS-02643: The server pool(s) where resource 'string' could run have no servers
Cause: All of the server pools the resource uses (and has permissions to use) have
no servers assigned.
Action: Either make sure there are active servers in the pools or use different
pools for the resource.
CRS-02644: No hosting members of 'string' are either online or are allowed to be
used by the resource
Cause: No server out of the enumerated as hosting members is online or, if it is,
may be used by the resource.
Action: You need to either add more servers into the cluster or request permission
to pools to which currently available servers are assigned.
CRS-02645: Cannot create resources of type 'string'
Cause: The type is abstract.
Action: Only concrete extensions of the type can be created.
CRS-02646: 'string' must have a default value if specified
Cause: This attribute must have a default value if specified.
Action: Modify the type definition so that the attribute is removed or has a valid
default value.
CRS-02647: Attribute 'string' may not be a negative value
Cause: A negative value was provided for an attribute which only accepts
non-negative values.
Action: Specify a non-negative number.
CRS-02648: Configuration of resource 'string' prevents it from starting on any
online servers.
Cause: An attempt was made to start a resource, but the resource configuration
prevented it from starting.
Action: Check resource configuration.
CRS-02649: Attribute 'string' of 'string' is internally managed and may not be
specified
Cause: An internal attribute was specified as part of an add/modify request.
Action: Re-execute the request without any internal attribute.
64-66 Oracle Database Error Messages
CRS-02650: Resource 'string' is configured to run only on 'string' and cannot be
started on 'string'
Cause: An attempt was made to start a resource on a server where it cannot run
given its placement configuration.
Action: Make sure you start resources where they are configured to run.
CRS-02651: Resource alias 'string' must use special values to be unique for each
server
Cause: Resource alias name must resolve to a unique identifier for every server in
the cluster. To achieve that, special values that yield different values on for each
server must be used.
Action: You need to special an alias with special variables that will make it unique
for every server.
CRS-02652: string is a resource and only resource instances can be relocated.
Cause: An attempt was made to relocate a resource.
Action: Make sure you supply a resource instance rather than a resource.
CRS-02653: Special value evaluation must be associated with a resource instance
Cause: Because some special values are per-server, each special value evaluation
request must be associated with a resource instance.
Action: Specify a server for the resource using -k or -n.
CRS-02660: Resource 'string' or all of its instances are disabled
Cause: This is an API return code for requests that cannot be performed because
the resource is disabled.
Action: Look at the detailed error messages that should always accompany this
error.
CRS-02661: All instances of resource 'string' are disabled
Cause: All instances of the resource instances are disabled.
Action: In order to change a resource state through CRS, its instances need to be
enabled.
CRS-02662: Resource 'string' is disabled on server 'string'
Cause: The resource was disabled on the specified server.
Action: Either re-enable, or use a different server.
CRS-02663: Resource instance of 'string' with string=number, string=number is
disabled
Cause: The resource instance whose cardinality/degree is specified is disabled.
Action: Either re-enable or use a different resource instance.
CRS-02664: Resource 'string' is already running on 'string'
Cause: The resource is already running everywhere it may run.
Action: None
CRS-02665: Resource 'string' is disabled on 'string'
Cause: The resource is disabled on every server it is configured to start on.
Action: None
CRS-02666: Resource 'string' is disabled on 'string' and is already running on 'string'
CRS-00001 to CRS-29006 64-67
Cause: The resource is disabled on every server it is configured to start on.
Action: None
CRS-02667: Resource 'string' with string=string may only run on servers assigned to
string and string, both of which are empty
Cause: The resource's placement policy only allows it to run on servers assigned
to the specified pools, and they are all empty.
Action: Either change the placement policy of the resource, or change the cluster
configuration so that there are servers in those pools.
CRS-02668: The value of attribute 'string' (number) may not not be above 'number'
Cause: Attribute value specified is above the allowed maximum.
Action: Use a value below the specified maximum.
CRS-02669: The value is out of range. Maximum allowed value is 'number'
Cause: Attribute value is out of the valid range.
Action: The value needs to be in a valid range.
CRS-02670: Unable to start/relocate 'string' because 'string' has a stop-time 'string'
dependency on it
Cause: Start/relocate of the resource is impossible because another resource has a
stop-time dependency on it and the action requires stopping that resources.
Action: This message will usually be coupled with another one that details the
nature of the problem with the other resource. Follow up on the action
recommended for that message.
CRS-02671: Error processing attribute 'string': string
Cause: The value specified for the attribute is inappropriate or invalid.
Action: Review the value, correct the problem and re-submit the request.
CRS-02672: Attempting to start 'string' on 'string'
Cause: This is a status message.
Action: None
CRS-02673: Attempting to stop 'string' on 'string'
Cause: This is a status message.
Action: None
CRS-02674: Start of 'string' on 'string' failed
Cause: This is a status message.
Action: None
CRS-02675: Stop of 'string' on 'string' failed
Cause: This is a status message.
Action: None
CRS-02676: Start of 'string' on 'string' succeeded
Cause: This is a status message.
Action: None
CRS-02677: Stop of 'string' on 'string' succeeded
Cause: This is a status message.
64-68 Oracle Database Error Messages
Action: None
CRS-02678: 'string' on 'string' has experienced an unrecoverable failure
Cause: This is a status message.
Action: Perform whatever steps necessary to reset the state.
CRS-02679: Attempting to clean 'string' on 'string'
Cause: This is a status message.
Action: None
CRS-02680: Clean of 'string' on 'string' failed
Cause: This is a status message.
Action: None
CRS-02681: Clean of 'string' on 'string' succeeded
Cause: This is a status message.
Action: None
CRS-02682: It is locked by 'string' for command 'string' issued from 'string'
Cause: This message is generated for operations that have a locking conflict.
Action: None
CRS-02683: It is locked by 'string' for command 'string'
Cause: This message is generated for operations that have a locking conflict.
Action: None
CRS-02714: 'string' is specified multiple times in 'string' of 'string'
Cause: The specified value is specified multiple times.
Action: Remove duplicates and retry.
CRS-02715: Update to attribute AGENT_FILENAME is not currently supported.
Recreate the resource type with new value.
Cause: Attempt was made to update AGENT_FILENAME attribute.
Action: Delete existing resource type and add it back with the new value.
CRS-02716: Failure threshold exhausted for resource 'string'
Cause: The resource instance has failed more times than allowed in the specified
time interval. It will not be restarted automatically.
Action: Identify and fix the problem. Restart the resource manually thereafter.
CRS-02717: Server 'string' is not in any of the server pool(s) hosting resource 'string'
Cause: An attempt was made to start a resource on a server that is not currently
an active server in any of the resource's server pool(s).
Action: Use a server name that is currently an active server of the resource's
server pools(s).
CRS-02718: Server 'string' is not a hosting member of resource 'string'
Cause: An attempt was made to start the resource on a server not listed as a
hosting member of the resource.
Action: Use a server name that is listed as a hosting member.
CRS-00001 to CRS-29006 64-69
CRS-02719: Resource 'string' may not be started on server 'string' because the server
is not in either 'string' or 'string' server pools
Cause: The resource's placement policy only allows it to run in the specified
server pools. An attempt was made to start it on a server assigned to a different
pool.
Action: Either use a different server or set the value of SERVER_POOLS to *,
which will allow the resource to run on any server.
CRS-02720: 'string' is a resource alias for 'string' and cannot be updated
Cause: An attempt was made to update a resource as if it were a resource.
Action: Update the resource which this alias refers to instead.
CRS-02721: 'string' is a resource alias for 'string' and cannot be unregistered
Cause: An attempt was made to unregister a resource alias as if it were a resource.
Action: Either unregister the resource which this alias refers to or modify its
ALIAS_NAME attribute to not have a resource alias.
CRS-02722: The instance of resource 'string' may only run on 'string'; check on
'string' is unnecessary
Cause: A check was issued on a server for a resource instance that may only run
on a particular server.
Action: Issue a check on the server where the resource instance is supposed to be
run.
CRS-02723: No instance of resource 'string' found on 'string'
Cause: A check was issued on a server for a resource which does not have any
offline instances and no running instances on that server.
Action: Issue a check on a server where a resource instance might be running.
CRS-02724: Modifications to the built-in resource type 'string' are not allowed
Cause: An attempt was made to modify a built-in resource type.
Action: Modification of built-in resource types is not allowed.
CRS-02725: User string does not have permission to operate on resource string.
Cause: Access control list on the resource do not permit the user to operate on the
resource.
Action: Access privileges on the resource must be honored or this user must be
given appropriate permissions.
CRS-02726: Invalid permissions specified for access control.
Cause: Access permissions are specifies using 'r', 'w', 'x' and '-' characters to
indicate read, write and execute permissions. '-' indicates no access of any kind.
Action: Check format for the permissions string and re-run the command with the
correct string.
CRS-02727: Acl entry 'string' has been specified more than once.
Cause: Access permissions for the entry have been specified more than once.
Action: Specify permissions for each entry only once and rerun the command.
CRS-02728: A resource type with the name 'string' is already registered
Cause: A resource type with such name is already registered.
Action: Use a unique name for the new resource type.
64-70 Oracle Database Error Messages
CRS-02729: Attribute 'string' cannot be overridden for a resource type
Cause: An attribute was specified that is not allowed in a resource type.
Action: Do not use the attribute specified in the error message for a resource type.
CRS-02730: Resource 'string' depends on resource 'string'
Cause: An attempt was made to unregister a resource that is referenced by
another resource in the dependency specification(s).
Action: Either remove the reference to this resource or the other resource first.
Alternatively, the operation can be retried with a force option.
CRS-02731: Resource 'string' is already running on server 'string'
Cause: The resource is already running on the server; relocate is impossible.
Action: Select another server.
CRS-02732: Resource 'string' is already starting on server 'string'
Cause: The resource is currently starting on the server.
Action: Wait for the request to complete.
CRS-02733: Failed to stop all required resources on 'string'; the server will be
restored into the original server pool(s)
Cause: In order to successfully relocate a server, all resources that cannot run in
the new server pool(s) must be stopped. That did not happen and thus the server
was placed back into the its original server pool(s).
Action: Manual intervention in stopping resources is required. The operation can
be retried thereafter. Alternatively, another server can be used.
CRS-02734: Failed to stop all required resources on 'string'; the server will stay in
RECONFIGURING state
Cause: In order to successfully relocate a server, all resources that cannot run in
the new server pool(s) must be stopped. Since that did not happen, the server will
be kept in the RECONFIGURING state until the resources that did not stop have
been stopped or unregistered.
Action: Manually stop the resources that did not stop or unregister them.
CRS-02735: The operation requires relocating resource 'string' from server 'string'
Cause: The operation would end up relocating the resource and the force option is
not specified.
Action: Add more servers to the cluster, stop or relocate the resource, or use the
force option for the same command.
CRS-02736: The operation requires stopping resource 'string' on server 'string'
Cause: The operation would end up stopping the resource and the force option is
not specified.
Action: Add more servers to the cluster, stop or relocate the resource, or use the
force option for the same command.
CRS-02737: Unable to register server pool 'string' as this will affect running
resources, but the force option was not specified
Cause: One or more running resources would be affected by the operation.
Action: Add more servers to the cluster, stop or relocate the resources mentioned
right before this error, or use the force option for the same command.
CRS-00001 to CRS-29006 64-71
CRS-02738: Unable to modify server pool 'string' as this will affect running
resources, but the force option was not specified
Cause: One or more running resources would be affected by the operation.
Action: Add more servers to the cluster, stop or relocate the resources mentioned
right before this error, or use the force option for the same command.
CRS-02739: Unable to relocate server 'string' as this will affect running resources,
but the force option was not specified
Cause: One or more running resources would be affected by the operation.
Action: Add more servers to the cluster, stop or relocate the resources mentioned
right before this error, use a different server, or use the force option for the same
command.
CRS-02740: Failed to relocate server 'string' to server pool 'string'. The server has
been restored to original server pool(s).
Cause: In order to successfully relocate a server, all resources that cannot run in
the new server pool(s) must be stopped. That did not happen and thus the server
was placed back into the its original server pool(s).
Action: Manual intervention in stopping or unregistering resources is required.
The operation can be retried thereafter. Alternatively, another server can be used.
CRS-02741: A value must be specified for attribute 'string'
Cause: The attribute was not given a value.
Action: Provide a value and retry.
CRS-02742: The update of resource 'string' would lose track of one or more running
instances
Cause: An attempt was made to modify the configuration of the resource such
that one or more currently running instance will be lost track of (the new
configuration would change the resource to have fewer instances).
Action: Stop the resource and resubmit.
CRS-02743: Unable to register resource 'string' as this will affect running resources,
but the force option was not specified
Cause: One or more running resources would be affected by the operation.
Action: Add more servers to the cluster, stop or relocate the resources mentioned
right before this error, or use the force option for the same command.
CRS-02744: Unable to modify resource 'string' as this will affect running resources,
but the force option was not specified
Cause: One or more running resources would be affected by the operation.
Action: Add more servers to the cluster, stop or relocate the resources mentioned
right before this error, or use the force option for the same command.
CRS-02745: Unable to relocate server string because it results in violation of a pool
string constraint
Cause: The requested move was rejected because it would cause either the source
or target pool (or both) to violate a pool size constraint, as indicated.
Action: Either change the pool size constraint(s) to accommodate your intent with
this move, or choose a different server to move.
CRS-02746: Cannot act on the instance of resource 'string' which is last known to
have run on 'string' where Cluster Ready Services are not properly functioning
64-72 Oracle Database Error Messages
Cause: The resource had been running on the server in the past but currently
there's no way to know if it's still running there because the Cluster Ready Services
daemon does not appear to be running on the server. To prevent possible
configuration violation, any attempt to start the resource instance on another
server is rejected.
Action: The underlying problem preventing Cluster Resource Services on the
server from functioning properly must be addressed. Only then the resources that
used to run there can be operated on again. Alternatively, the server may be shut
down or the clusterware stack on it stopped completely.
CRS-02747: Server reconfiguration has failed to stop resources 'string' on server
'string'. Resources that did not stop must be stopped or unregistered manually.
Details at string in string.
Cause: The specified resources could not be stopped.
Action: Stop the specified resources manually using and retry the last action.
CRS-02748: Failed to stop resource 'string' during server reconfiguration on server
'string'.
Cause: The specified resources could not be stopped.
Action: Stop the specified resources manually and retry the last action.
CRS-02749: A write of OCR server data 'string' failed. Details at string in string.
Cause: Could not persist data to OCR.
Action: Use the ocrconfig and ocrcheck utilities to detect errors in OCR. If
problems exist, the registry may need to be recovered or restored.
CRS-02750: Cardinality violation detected on server 'string', resource 'string' is in
unexpected state. Details at string in string.
Cause: The specified resource was in an unexpected state.
Action: Manually restart the resource.
CRS-02751: Cannot create new resource, the resource type 'string' is not supported.
Details at string in string.
Cause: The specified resource had an incorrect base type.
Action: Check the attributes for the resource and add it using crsctl again.
CRS-02752: Unable to write event sequence number to OCR. Details at string in
string.
Cause: Could not update OCR with event sequence number.
Action: Use the ocrconfig and ocrcheck utilities to detect errors in OCR. If
problems exist, the registry may need to be recovered or restored.
CRS-02753: Timed out waiting for the server pools to be unfrozen.
Cause: Timed out while waiting for a client to unfreeze the pools it froze.
Action: If the problem persists, contact Oracle Support Services.
CRS-02754: Unable to change locks for a running operation 'string'. Details at string
in string.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
CRS-02755: Error reading type definition for type 'string'. Details at string in string.
CRS-00001 to CRS-29006 64-73
Cause: This is an internal error.
Action: Contact Oracle Support Services.
CRS-02756: Invalid tag for command 'string'. Details at string in string.
Cause: An invalid command was received by the CRS daemon.
Action: Contact Oracle Support Services.
CRS-02757: Command 'string' timed out waiting for response from the resource
'string'. Details at string in string.
Cause: Timeout occurred while waiting for response to specified command.
Action: Check that the server targeted by the command is online and responsive.
CRS-02758: Resource 'string' is in an unknown state.
Cause: Unable to determine the current state of specified resource.
Action: Manually restart the resource.
CRS-02759: Failed to read repository key for NLS language 'string'. Details at string
in string.
Cause: The key for the specified language could not be read from OCR.
Action: Use the ocrconfig and ocrcheck utilities to detect errors in OCR. If
problems exist, the registry may need to be recovered or restored.
CRS-02760: Policy engine failed to initialize internal types. Details at string in
string.
Cause: Error during initialization of internal data.
Action: If the problem persists, contact Oracle Support Services.
CRS-02761: Consistency problem in registry while processing resource 'string'.
Details at string in string.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
CRS-02762: Unable to find type 'string' in registry while processing resource
'string'. Details at string in string.
Cause: This is an internal error.
Action: Contact Oracle Support Services
CRS-02763: Error while reading resources. Details at string in string.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
CRS-02764: CRSADMIN and CRSUSER keys are not in repository. Details at string
in string.
Cause: Error with repository. Required keys are not present.
Action: Use the ocrconfig and ocrcheck utilities to detect errors in OCR. If
problems exist, the registry may need to be recovered or restored.
CRS-02765: Resource 'string' has failed on server 'string'.
Cause: The specified resource was no longer running.
Action: The resource will be automatically brought back online. Use crsctl to
confirm that it is online.
64-74 Oracle Database Error Messages
CRS-02766: Received state change for disabled resource 'string' from server 'string'.
Cause: Received command to change state for a resource that was disabled.
Action: None
CRS-02767: Resource state recovery not attempted for 'string' as its target state is
OFFLINE
Cause: Target state for resource was OFFLINE. Clusterware will not attempt to
recover it.
Action: None
CRS-02768: Failure threshold exhausted by resource 'string'.
Cause: The specified resource failed too many times. No further restart attempts
will be made.
Action: Fix the underlying cause of resource failure and manually restart the
resource.
CRS-02769: Unable to failover resource 'string'.
Cause: Could not failover the specified resource.
Action: Restart the resource manually.
CRS-02770: Resource target 'string' is offline; will not restart.
Cause: The target state of the specified resource was offline.
Action: None
CRS-02771: Maximum restart attempts reached for resource 'string'; will not restart.
Cause: Specified resource had been restarted too many times.
Action: Change the maximum restart parameter of the resource, and restart it
manually.
CRS-02772: Server 'string' has been assigned to pool 'string'.
Cause: The specified server had been assigned to a server pool.
Action: None
CRS-02773: Server 'string' has been removed from pool 'string'.
Cause: The specified server had been removed from a server pool.
Action: None
CRS-02774: Failed to save resource 'string' to the repository. Details at string in
string.
Cause: Could not update repository with resource details.
Action: Use the ocrcheck utility to detect errors in OCR. If problems exist, the
registry may need to be recovered or restored.
CRS-02775: Failed to update resource 'string'. Details at string in string.
Cause: Could not update repository with resource details.
Action: Use the ocrcheck utility to detect errors in OCR. If problems exist, the
registry may need to be recovered or restored.
CRS-02776: Failed to update server pool 'string'. Details at string in string.
Cause: Could not update repository with server pool details.
CRS-00001 to CRS-29006 64-75
Action: Use the ocrcheck utility to detect errors in OCR. If problems exist, the
registry may need to be recovered or restored.
CRS-02777: Failed to delete resource 'string' from repository. Details at string in
string.
Cause: Unable to update resource details in repository.
Action: Use the ocrcheck utility to detect errors in OCR. If problems exist, the
registry may need to be recovered or restored.
CRS-02778: Failed to delete server pool 'string' from repository. Details at string in
string.
Cause: Could not update repository with server pool details.
Action: Use the ocrcheck utility to detect errors in OCR. If problems exist, the
registry may need to be recovered or restored.
CRS-02779: Failed to delete type 'string' from repository. Details at string in string.
Cause: Failed to update repository.
Action: Use the ocrcheck utility to detect errors in OCR. If problems exist, the
registry may need to be recovered or restored.
CRS-02780: Could not find Access Control List for resource 'string'. Details at string
in string.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
CRS-02781: Error during registration for resource 'string'. Details at string in string.
Cause: Error occurred during registration callback of new resource.
Action: Contact Oracle Support Services.
CRS-02782: Unable to find attributes for resource 'string'. Details at string in string.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
CRS-02783: Internal error in local placement policy for resource 'string'. Details at
string in string.
Cause: Internal error in CRS Policy Engine.
Action: Contact Oracle Support Services.
CRS-02784: Internal error, invalid server 'string' in local placement policy. Details at
string in string.
Cause: Internal error in CRS Policy Engine.
Action: Contact Oracle Support Services.
CRS-02785: Failed to register resource 'string'. Details at string in string.
Cause: Could not update repository with resource details.
Action: Use the ocrcheck utility to detect errors in OCR. If problems exist, the
registry may need to be recovered or restored.
CRS-02786: Failed to register server pool 'string'. Details at string in string.
Cause: Could not update repository with server pool details.
Action: Use the ocrcheck utility to detect errors in OCR. If problems exist, the
registry may need to be recovered or restored.
64-76 Oracle Database Error Messages
CRS-02787: Server pool 'string' has fallen below its minimum size. Details at string
in string.
Cause: The specified server pool has fallen below its minimum size and will be
reconfigured.
Action: None
CRS-02788: Server reconfiguration failed to stop resources 'string'. The server
'string' has been restored into the original pool(s).
Cause: The specified resources could not be stopped.
Action: Stop the specified resources manually and retry the last action.
CRS-02789: Cannot stop resource 'string' as it is not running on server 'string'
Cause: An request to stop a resource on a server where it is not running was
received
Action: Check the current state of the resource; it should no longer be running on
that server.
CRS-02790: Starting shutdown of Cluster Ready Services-managed resources on
'string'
Cause: Shutdown of Cluster Ready Services and the resources it manages has
started on the specified server.
Action: None
CRS-02791: Starting shutdown of Oracle High Availability Services-managed
resources on 'string'
Cause: Shutdown of Oracle High Availability Services and the resources it
manages has started on the indicated server.
Action: None
CRS-02792: Shutdown of Cluster Ready Services-managed resources on 'string' has
completed
Cause: Shutdown of Cluster Ready Services and the resources it manages on the
indicated server has completed.
Action: None
CRS-02793: Shutdown of Oracle High Availability Services-managed resources on
'string' has completed
Cause: Shutdown of Oracle High Availability Services and the resources it
manages has completed on the indicated server.
Action: None
CRS-02794: Shutdown of Cluster Ready Services-managed resources on 'string' has
failed
Cause: The failure is associated with one or more of the resources affected by this
command on the indicated server."
Action: Error message(s) preceding this one should have the details about the
resources that refused to shut down. Either manually stop those resources or retry
with the force option.
CRS-02795: Shutdown of Oracle High Availability Services-managed resources on
'string' has failed
CRS-00001 to CRS-29006 64-77
Cause: The failure is associated with one or more of the resources affected by this
command on the indicated server."
Action: Error message(s) preceding this one should have the details about the
resources that refused to shut down. Either manually stop those resources or retry
with the force option.
CRS-02796: The command may not proceed when Cluster Ready Services is not
running
Cause: This command must stop Cluster Ready Services-managed resources.
However, Cluster Ready Services is not running, which does not mean its
resources are not running.
Action: The underlying reason for Cluster Ready Services not running needs to be
resolved and the command retried. Alternatively, the command can be retried
with the force option.
CRS-02797: Shutdown is already in progress for 'string', waiting for it to complete
Cause: Another shutdown command was issued for the indicated server in the
past and it is currently in progress. This command will wait until the original
command completes and then complete as well.
Action: None
CRS-02798: State change received for resource 'string' from unexpected server
'string'. Details at 'string' in 'string'.
Cause: A state change was reported for an instance of the resource from a server
where the resource was never started.
Action: Shutdown the resource on the unexpected server
CRS-02799: Failed to shut down resource 'string' on 'string'
Cause: Shut down failed because the listed resource failed to stop.
Action: Error message(s) preceding this one should have the details about the
resources that refused to shut down. Either manually stop those resources or retry
with the force option.
CRS-02800: Cannot start resource 'string' as it is already in the INTERMEDIATE
state on server 'string'
Cause: An attempt was made to start a resource that is already in the
INTERMEDIATE state.
Action: Determine why the resource is in the INTERMEDIATE state based on the
value of the STATE_DETAILS attribute. If it is due to a check timeout, no action is
needed. Otherwise, manual intervention is required to bring the resource out of
the INTERMEDIATE state.
CRS-02801: No instance of the resource 'string' should be running
Cause: An attempt was made to relocate resource and the resource's instances to
be relocated have TARGET=OFFLINE.
Action: Restart the resource to change the value of the TARGET attribute to
ONLINE. Examining the value of the INTERNAL_STATE attribute can be used to
determine if the instances are being operated on currently.
CRS-02802: Purging events not published within 15 minutes
Cause: The events could not be published to the Event Manager Daemon either
because it is down or there are errors doing the publish.
Action: Check the status of the Event Manager Daemon.
64-78 Oracle Database Error Messages
CRS-02803: Attribute 'string' has already been declared in a derived type 'string'
Cause: An attempt was made to add a new attribute definition to a resource type
that has an identically named attribute already defined in one or more derived
types. Attributes declared in base types can be overridden in derived ones, but the
opposite is not allowed.
Action: Pick a different attribute name or delete the derived type(s), resubmit, and
then add derived types back.
CRS-02805: Unable to start 'string' because it has a 'string' dependency on resource
type 'string' and no resource of that type can satisfy the dependency
Cause: Start/relocate of the resource is impossible because it has a dependency on
a resource type no resource of which can currently be used to satisfy the
dependency.
Action: This message will normally be coupled with one or more other messages
that detail the nature of the problem for each existing resource of the type.
CRS-02806: Failed to create stop operation for resource 'string'
Cause: Creating the stop operation did not complete successfully.
Action: Error message(s) preceding this one should have more details about the
problem. Try shutting down the resource manually, or retrying with the force
option.
CRS-02807: Resource 'string' failed to start automatically.
Cause: This message comes up when the automatic start for the resource has
failed during a reboot of the cluster node or restart of the clusterware stack. See
previous resource specific messages for more details.
Action: Use 'crsctl start resource' to start the resource manually.
CRS-02809: Failed to update cluster configuration policy set. Details at string in
string.
Cause: Could not update repository with new configuration data.
Action: Use the ocrcheck utility to detect errors in OCR. If problems exist, the
registry may need to be recovered or restored.
CRS-02810: Cluster configuration policy set is corrupted. Details at string in string.
Cause: Could not read the configuration data from the repository.
Action: Use the ocrcheck utility to detect errors in OCR. If problems exist, the
registry may need to be recovered or restored.
CRS-02814: Server category 'string' does not exist.
Cause: A request was received that referenced a non-existing server category.
Action: Make sure a registered server category is used.
CRS-02815: Server category 'string' is already registered.
Cause: A request to register a server category with a duplicate name was
received.
Action: Use a unique name.
CRS-02816: Server category 'string' cannot be unregistered as it is referenced by
resource 'string'.
Cause: The server category you are trying to remove has references to it.
CRS-00001 to CRS-29006 64-79
Action: Make sure the server category you are trying to remove is not referenced
by other entities.
CRS-02817: Server category 'string' cannot be unregistered as it is referenced by
server pool 'string'.
Cause: The server category you are trying to remove has references to it.
Action: Make sure the server category you are trying to remove is not referenced
by other entities.
CRS-02818: Failed to delete server category 'string' from repository. Details at string
in string.
Cause: Could not update repository with server category details.
Action: Use the ocrcheck utility to detect errors in OCR. If problems exist, the
registry may need to be recovered or restored.
CRS-02819: Failed to save server category 'string'. Details at string in string.
Cause: Could not update repository with server pool details.
Action: Use the ocrcheck utility to detect errors in OCR. If problems exist, the
registry may need to be recovered or restored.
CRS-02820: Required attribute 'string' is missing for configuration policy 'string'.
Cause: A required attribute was not specified.
Action: Make sure the attribute is specified.
CRS-02821: Fatal error while validating configuration policy 'string'.
Cause: There's a problem with the configuration data in the specified policy.
Action: This message always follows the actual error description.
CRS-02822: Server pool 'string' is not declared in the policy set.
Cause: Each configuration policy may only define server pool. configuration for
the pools declared to be a part of the policy set.
Action: Either remove the server pool from the policy, change its name, or extend
the policy set to include the pool's name.
CRS-02823: The new active policy name 'string' was not found.
Cause: An attempt to activate non-existent policy was made.
Action: Use a registered policy's name instead.
CRS-02824: 'string' is reserved for a built-in configuration policy and cannot be
used.
Cause: This name is reserved for a built-in object.
Action: Use a different name.
CRS-02825: Configuration policy 'string' already exists.
Cause: A configuration policy name specified was defined multiple times.
Action: Make sure each policy is only defined once.
CRS-02826: Server pools cannot be removed from the configuration policy set
without activating a new policy at the same time.
Cause: Server pools can be removed from the configuration policy set only if the
command also activates a policy.
64-80 Oracle Database Error Messages
Action: To remove the server pools from the system, activate a new policy with
the update. To remove the server pools from the policy control only, resubmit with
the -ksp option.
CRS-02828: Failed to stop resource while attempting CARDINALITY modification
Cause: An attempt to stop a resource during CARDINALITY modification failed.
Action: Use 'crsctl stop resource' to stop the resource manually and then retry the
update operation.
CRS-02829: Update operation cannot proceed because it would need to stop
resources.
Cause: An update to CARDINALITY would require the operation to stop
resources.
Action: Either manually stop enough resources using 'crsctl stop resource' or
specify the force option to have them selected for you.
CRS-02830: A server category name may not be empty or contain spaces.
Cause: A name must not be empty or contain space character(s).
Action: Specify a valid name.
CRS-02831: Either 'string' or 'string' may be specified, but never both.
Cause: Two mutually exclusive attributes were used at the same time, which is
not allowed.
Action: Use either one or the other.
CRS-02833: Either 'string' or 'string' must be specified, or both.
Cause: At least one of the two attributes must have a value.
Action: Specify a value for either or both.
CRS-02834: One of 'string', 'string' or 'string' must be specified when 'string' is
'string'.
Cause: One attribute of the three is required for this configuration.
Action: Specify a value for one attribute of the three.
CRS-02835: Resource 'string' cannot start on server 'string' as the server does not
belong to the resource's server category.
Cause: This resource may only run on the servers that belong to the server
category of the resource.
Action: Pick a server that belongs to the category.
CRS-02836: When using a server category, the resource must have 'string' attribute
set to 'string'.
Cause: An attempt was made to register a resorce that uses a server category and
yet is not configured to utlize any available server.
Action: Set the attribute to the required value.
CRS-02837: There are no servers that belong to the server category 'string' of
resource 'string'.
Cause: The resource cannot be started as there are no available servers that belong
to its category.
Action: Add servers to the cluster or change the category to be more inclusive.
CRS-00001 to CRS-29006 64-81
CRS-02838: 'string' is not a valid attribute of server categories.
Cause: An attempt was made to set a value for an attribute which does not belong
to server categories.
Action: Use a valid attribute.
CRS-02839: Cluster Ready Services' active version is below required level of
'string'.
Cause: An attempt was made to use functionality that is only available starting
from the specified active version.
Action: Upgrade to the minimum required version.
CRS-02840: Resource instance 'string' does not exist.
Cause: A request was received that referenced a nonexistent resource instance.
Action: Make sure a registered resource instance is used.
CRS-02841: 'string' must be a resource instance.
Cause: This command may only be issued on a resource instance but the supplied
reference was to an object of a different type.
Action: Use a registered resource instance.
CRS-02842: Action 'string' on resource 'string' timed out.
Cause: The action did complete within the allotted time.
Action: None
CRS-02843: Unable to complete processing of the 'string' action for resource 'string'
on server 'string' as Cluster Ready Services is not reachable.
Cause: The processing of the specified action was aborted because Cluster Ready
Services was no longer reachable.
Action: can be retried thereafter.
CRS-02844: Waiting for resource 'string' to start on server 'string'.
Cause: The resource is now expected to start on the server.
Action: None
CRS-02845: Waiting for resource 'string' to stop on server 'string'.
Cause: The resource is now expected to stop on the server.
Action: None
CRS-02846: There is no active action on resource instance 'string'
Cause: An attempt was made to finish an action on the resource instance while no
corresponding attempt to start the action was found or an attempt to start the
action was timed out before a request to finish the action arrived.
Action: Check the state of the resource and re-do the complete cycle if needed.
CRS-02847: Authorization failure: OS User 'string' does not exist on server 'string'
Cause: The specified operating system user does not exist on the specified server.
Cluster Ready Services requires that all users used by the resource it manages exist
on each server of the cluster.
Action: Add the specified operating user on the specified server.
CRS-02848: Error while reading resources: Resource: string . Error: string Details at
string in string.
64-82 Oracle Database Error Messages
Cause: This is an internal error.
Action: Contact Oracle Support Services.
CRS-02849: Authorization failure: Resource [ string ]
Cause: A resource operation could not be performed because authorization
checking failed.
Action: Check the ownership, group, and permissions associated with the
resource and ensure that the associated operating system user and group
definitions are consistent on all cluster nodes.
CRS-02850: Start of 'string' on 'string' has been delayed to maintain concurrency
limit of number.
Cause: The configured concurrent start action limit was reached.
Action: The start action will automatically resume as soon as possible.
CRS-02851: Stop of 'string' on 'string' has been delayed to maintain concurrency
limit of number.
Cause: The configured concurrent stop action limit was reached.
Action: The stop action will automatically resume as soon as possible.
CRS-02852: Conflicting specification of server pool and server.
Cause: Server pool name and server name were specified in a start command.
Action: Specify either server pool name or servername, not both.
CRS-02853: Unknown server pool name: 'string' .
Cause: The server pool name given to start/stop command did not exist.
Action: Specify a valid server pool name.
CRS-02854: Resource 'string' cannot be started in a server pool because it is a local
resource.
Cause: A local resource name was given to start/stop command.
Action: Specify a cluster resource name.
CRS-02855: Resource 'string' is not configured to run in server pool 'string'.
Cause: An attempt was made to start or stop the resource in a server pool where
resource was not configured to run.
Action: Modify resource's attribute to have this server pool or specify a different
resource.
CRS-02856: Unknown names for server pools or for filters.
Cause: An invalid value was supplied for the '-s' or '-w' argument in a start/stop
command or to the API calls.
Action: Provide valid server pool names or filter attributes.
CRS-02857: Cannot stop resource 'string' because it is not running in server pool
'string'.
Cause: A resource stop request specified a server pool on which the resource is
not running.
Action: Check the current state of the resource; it should no longer be running in
that server pool.
CRS-00001 to CRS-29006 64-83
CRS-02858: User 'string' does not have permission to run action 'string' on resource
'string'.
Cause: A username and/or group was specified for the action permissions, but
the current user is not included in the specification.
Action: Use 'crsctl modify' to update the ACTIONS attribute for this resource to
add the current user to the permission list for this action, or remove all user and
group specifications to enable universal access.
CRS-02859: Cannot run action 'string' on resource 'string' because the resource is not
online.
Cause: A resource action operation could not be performed because the resource
was not online.
Action: Ensure the resource is online before attempting to run an action.
CRS-02862: Cannot update the ACTIONS attribute, because the input is not valid
Cause: A resource update operation could not be performed, because the input
value is not vvalid.
Action: Ensure the ACTIONS name attribute is specified in 32 or less US7ASCII
characters. Ensure users and groups are prefixed with the appropriate identifier,
either "user:" or "group:"
CRS-02863: Cannot restart resource 'string' because it is not running.
Cause: A resource restart action was not performed because the resource is not
running.
Action: Ensure that the resource which needs to be restarted is up and running.
CRS-02865: Resource 'string' cannot be started on server 'string' because it has an
exclusion dependency with resources of type 'string'.
Cause: An exclusion dependency was configured without the right to preempt a
running resource.
Action: Pick a different server or stop the other resource(s) on this server.
CRS-02866: Resource 'string' cannot be started on server 'string' because it has an
exclusion dependency with resources of type 'string' and the force option was
not specified.
Cause: An exclusion dependency was configured but the force option was not
used to stop the running resource(s).
Action: Either pick a different server or use the force option.
CRS-02867: Server pool 'string' cannot be added to the policy set.
Cause: The Generic server pool as well as its sub-pools cannot be added to the
policy set.
Action: Remove the pool from SERVER_POOL_NAMES attribute.
CRS-02868: 'string' is not a valid attribute of configuration policies.
Cause: An attempt was made to set a value for an attribute which does not belong
to configuration policies.
Action: Use a valid attribute.
CRS-02869: 'string' is not a valid attribute of the policy set.
Cause: An attempt was made to set a value for an attribute which does not belong
to the policy set.
64-84 Oracle Database Error Messages
Action: Use a valid attribute.
CRS-02870: An OCR write operation has failed during upgrade of the object
schema.
Cause: While performing CRS upgrade as part of the clusterware upgrade, an
OCR write operation has failed.
Action: Examine the clusterware alert log for more information about OCR
failures.
CRS-02871: Resource 'string' cannot be started on server 'string' because it has an
exclusion dependency with resource 'string'.
Cause: An exclusion dependency was configured between the two resources
without the right to preempt a running resource.
Action: Pick a different server or stop the other resource on this server.
CRS-02872: Resource 'string' cannot be started on server 'string' because it has an
exclusion dependency with resource 'string' and the force option is not used.
Cause: An exclusion dependency was configured between the two resources but
the force option was not used to stop the running resource.
Action: Either pick a different server or use the force option.
CRS-02874: Could not restart resource 'string' on server 'string'.
Cause: A required part of restart operation has failed.
Action: Check the preceding errors to see the cause and take appropriate action.
CRS-02875: Failed to record shutdown information in OLR.
Cause: An attempt to record information during a normal shutdown failed. This
will cause the shutdown to be regarded as unplanned on the next startup, and
may lead to some driver resources being disabled.
Action: Use the ocrconfig and ocrcheck utilities to detect errors in OCR. If
problems exist, the registry may need to be recovered or restored.
CRS-02876: Disabled resource 'string' due to OHASD crashes
Cause: OHASD crashes have exceeded the autostart thresholds set for this
resource, and the resource has been disabled as a result.
Action: Use crsctl config to look up whether a resource has been disabled, and
crsctl enable/disable to manually change the status.
CRS-02877: Owner 'string' of the entity 'string' does not belong to the 'string' group.
Cause: The owner of an entity being configured was not a member of the required
group.
Action: The user, issuing the command, needs to be configured to be in the group.
CRS-02878: Failed to restart resource 'string'
Cause: An attempt to start the resource has failed.
Action: If failover is not enabled, try manually starting the resource on a different
server. If failover is enabled, the resource has been failed over, and any problems
are reported in subsequent messages.
CRS-02879: Cannot update the ALERT_TEMPLATE attribute, because the input is
not valid
Cause: A resource update operation could not be performed, because the input
value is not valid.
CRS-00001 to CRS-29006 64-85
Action: Ensure that valid attributes are specified in a space separated list.
CRS-02880: Incorrect specification of dependency 'string', only one modifier may be
specified.
Cause: During resource update, an exclusion dependency specified more than the
maximum of one modifier.
Action: Check the specification of the dependency, fix the problem indicated, and
resubmit the request.
CRS-02881: Additional exclusion dependency discovered on resource 'string' within
the same dependency tree.
Cause: During resource update, a dependency specified more than the maximum
of one exclusion per hard dependency tree.
Action: Check the specification of the dependency, fix the problem indicated, and
resubmit the request.
CRS-02882: Unable to place an instance of resource 'string' due to an exclusion
dependency on 'string'.
Cause: The resource cannot be placed because of the constraints imposed by its
start dependencies.
Action: Either change the resource start dependencies or re-evaluate the request.
CRS-02883: Resource 'string' failed during Clusterware stack start.
Cause: During Clusterware startup, automatic startup of the indicated resource
succeeded but the resource failed before Clusterware startup completed.
Action: Retry starting Clusterware.
CRS-02884: Server 'string' cannot be used for resource placement currently.
Cause: The server is currently configured such that it cannot be used for resource
placement.
Action: Use a different server.
CRS-02890: An administrator-managed database cannot be configured on a
non-Hub server 'string'.
Cause: An attempt was made to register a database on a server whose role is not
'hub' or the node is currently down.
Action: Use only online servers configured as Hub servers.
CRS-02891: Policy-managed databases can only be configured in server pools that
use 'string' category.
Cause: An attempt was made to configure a database using a server pool that
does not currently use a category that includes only nodes with the specified role.
Action: Either use an existing server pool that uses such a category or create and
use a server pool with such category.
CRS-02892: In order to use 'string' in resources of 'string' type, 'string' must be set to
'string' and 'string' must be set to 'string'.
Cause: An attempt was made to use an attribute such that other attributes must
be set to specific values.
Action: Resubmit with the mentioned attributes set to the mentioned values.
CRS-02893: Cannot stop ASM instance on server 'string' because it is the only
instance running.
64-86 Oracle Database Error Messages
Cause: An attempt was made to stop the last ASM instance in the cluster, which
would lead to a complete cluster outage.
Action: Reissue the request when there are at least two ASM instances running in
the cluster.
CRS-02894: Cannot stop the ASM resource because it will lead to a complete cluster
outage.
Cause: An attempt was made to stop all ASM instances in the cluster, which
would lead to a complete cluster outage.
Action: Reissue the request by specifying a concrete node name.
CRS-02900: User 'string' does not exist on node 'string'.
Cause: An attempt was made to add an unknown username to the CRS
Administrator list.
Action: Reissue the command with a known username. Or create the user on the
node(s) specified, and reissue the command.
CRS-02901: Not authorized to modify the CRS Administrator list.
Cause: An attempt was made to modify the CRS Administrator list by a user not
belonging to the CRS Administrator list.
Action: Either acquire the role of cluster administrator or have one modify the
CRS Administrator list for you.
CRS-02904: Parameter 'string' for 'relocate' is not a singleton resource.
Cause: A relocate request specified a resource that is not singleton.
Action: Specify a singleton resource or a filter that resolves to an instance of the
resource.
CRS-02905: Server pools in a policy do not have ACL attribute
Cause: A 'crsctl modify serverpool' command specified an ACL attribute with
-policy or -all_policies.
Action: Omit ACL from the attributes.
CRS-02906: Server category 'string' cannot be unregistered as it is referenced by
server pool 'string' in policy 'string'.
Cause: The server category you are trying to remove has references to it in a
policy.
Action: Make sure the server category you are trying to remove is not referenced
by other entities in the policy.
CRS-02907: Resource 'string' is not completely configured, and hence cannot be
operated upon.
Cause: A request was made without specifying the PID_FILES or EXECUTABLE_
NAMES.
Action: Specify a value for PID_FILES and/or EXECUTABLE_NAMES attribute,
or specify values for STOP_PROGRAM, CHECK_PROGRAM and CLEAN_
PROGRAMS attributes. 2908 no longer used
CRS-02909: Server 'string' cannot be assigned to server pool 'string' because its
current role is not 'string'.
Cause: An attempt was made to assign a server to the server pool that did not
have the specified role. Only servers with the specified role can be assigned to this
server pool.
CRS-00001 to CRS-29006 64-87
Action: Retry using a different server.
CRS-02910: Unable to register server category 'string' as this will affect running
resources, but the force option was not specified.
Cause: One or more running resources were affected by the operation.
Action: Add more servers to the cluster, stop or relocate the resources mentioned
right before this error, or use the force option for the same command.
CRS-02911: Unable to modify server category 'string' as this will affect running
resources, but the force option was not specified.
Cause: One or more running resources were affected by the operation.
Action: Add more servers to the cluster, stop or relocate the resources mentioned
right before this error, or use the force option for the same command.
CRS-02912: Unable to start resource 'string' on server 'string' because resource
dependencies require stopping it on a different server.
Cause: A start request failed because resource dependencies would require
stopping the resource in order to start it somewhere else.
Action: Manually stop the resource before starting it elsewhere.
CRS-02913: 'autostart delay' value 'string' is invalid.
Cause: The command specified an 'autostart delay' time that was non-numeric or
negative.
Action: Specify a non-negative numeric value for the 'autostart delay' argument.
CRS-02914: 'autostart servercount' value 'string' is invalid.
Cause: The command specified an 'autostart servercount' value that was
non-numeric or negative.
Action: Specify a positive numeric value for the 'autostart servercount' argument.
CRS-02915: Failed to update 'autostart delay' (string) or 'autostart servercount'
(string). Details at string in string.
Cause: A request to update the automatic start details failed because of incorrect
input values.
Action: Use the ocrcheck utility to detect errors in OCR. If problems exist, the
registry may need to be recovered or restored.
CRS-02917: The 'string' server pool cannot be removed from the system.
Cause: The command to remove the server pool from the policy set would have
caused it to be removed from the system completely.
Action: Reissue the 'crsctl modify policyset' command with the -ksp option.
CRS-02918: Authorization failure: operating system group 'string' does not exist on
server 'string'
Cause: The specified operating system group does not exist on the specified
server. Cluster Ready Services requires that all groups used by the resources it
manages exist on each server of the cluster.
Action: Add the specified operating system group on the specified server.
CRS-02919: Resource 'string' has no instances to act upon.
Cause: An attempt was made to act on a resource that has no resource instances
because it is configured to run on servers that have never existed in the cluster.
64-88 Oracle Database Error Messages
Action: Retry the command when the resource has instances.
CRS-02920: Unable to activate policy 'string' because this will affect running
resources, but the force option was not specified.
Cause: An attempt to activate a new policy would have affected one or more
running resources but the force option was not specified.
Action: Reevaluate the request and if it makes sense, set the force option and
resubmit.
CRS-02921: Unable to register policy because attribute 'string' for resource 'string'
does not have the POLICY_CONFIG flag.
Cause: An attempt was made to specify resource attributes in the policy that do
not have the POLICY_CONFIG flag.
Action: Only attributes that can be policy managed and have the POLICY_
CONFIG flag can be specified in a policy definition.
CRS-02922: The attribute 'string' is not supported for resource type 'string'.
Cause: An attempt to update a CRS resource specified an attribute that is not
associated with the resource type.
Action: Specify only attributes that are associated with the type of resource being
updated.
CRS-02923: The EXPRESSION attribute cannot accept 'string' as a server
configuration attribute.
Cause: An attempt was made to set a server configuration attribute that cannot be
used with the EXPRESSION attribute.
Action: Use a valid attribute.
CRS-02924: The EXPRESSION attribute contains invalid value 'string' for server
configuration attribute 'string'.
Cause: An attempt was made to set a value which cannot be assigned to a server
configuration attribute.
Action: Use a valid value.
CRS-02925: The dependency modification 'string' for the targets 'string' has an
unknown dependency or incorrect syntax.
Cause: An attempt was made to modify an existing dependency without
providing a known dependency or the correct modification syntax.
Action: Refer to the Oracle Clusterware documentation for an explanation of
supported dependencies and the resource dependency modification syntax.
CRS-02926: Cannot find a match for target 'string' in the modification list for
dependency 'string'.
Cause: There was no existing dependency that had the same target to be
modified.
Action: Supply the correct target for the dependency modification.
CRS-02927: The requested action for the resource 'string' was aborted due to a
timeout.
Cause: The timeout specified for a custom action was reached before the action
could complete.
Action: Revise the timeout setting and retry the action.
CRS-00001 to CRS-29006 64-89
CRS-02928: The dependency on type 'string' cannot be accepted because it is
specified multiple times.
Cause: A duplicate type was assigned as a dependency to a resource.
Action: Revise the dependency list to ensure that no duplicate types exist.
CRS-02929: The dependency on resource 'string' cannot be accepted because it is
specified multiple times.
Cause: A duplicate resource was assigned as a dependency to a resource.
Action: Revise the dependency list to ensure that no duplicate resources exist.
CRS-03501: The Cluster Health Analysis service started on host string.
Cause: The Cluster Health Analysis service was successfully started on the listed
node.
Action: None
CRS-03502: The Cluster Health Analysis service aborted on host string. Details at
string in string.
Cause: The Cluster Health Analysis service aborted due to an internal error.
Action: Determine whether the Cluster Health Analysis service has automatically
restarted by checking the Oracle Clusterware alert log. If the problem persists,
contact Oracle Support Services.
CRS-03503: The Cluster Health Analysis service on host string is shutting down.
Cause: The Cluster Health Analysis service on the listed node was terminated.
Action: None
CRS-04000: Command string failed, or completed with errors.
Cause: The specified command did not complete successfully. If the command
performs multiple operations internally, one or more of those operations
experienced an error that is reported in a previous message.
Action: Examine the error message(s) preceding this message and correct the
problem(s) they describe.
CRS-04016: Key 'string' is missing in the OCR.
Cause: Internal error.
Action: Contact Oracle Support Services.
CRS-04017: Failed to get the value for key 'string' from OCR.
Cause: Internal error.
Action: Contact Oracle Support Services.
CRS-04038: Cannot delete invalid user 'string' from CRS Admin list.
Cause: An attempt was made to delete an invalid username from the CRS Admin
list.
Action: Reissue the command with a valid username.
CRS-04040: The value of attribute 'string' contains the following invalid characters:
'string'
Cause: An attribute value with invalid characters was specified.
Action: Reissue the command and provide valid characters for the attribute value.
CRS-04044: CRS Administrator List: string
64-90 Oracle Database Error Messages
Cause: Output message, not an error.
Action: None
CRS-04046: Invalid Oracle Clusterware configuration.
Cause: The Oracle Clusterware configuration is invalid.
Action: Configure Oracle Clusterware or Oracle Restart.
CRS-04047: No Oracle Clusterware components configured.
Cause: No Oracle Clusterware components have been configured.
Action: Configure Oracle Clusterware or Oracle Restart.
CRS-04050: Rejecting the command because the cluster active version [string] is less
than the required cluster active version [string]
Cause: The command was rejected because the cluster active version was less
than the required cluster active version.
Action: Reissue the command with a valid cluster active version.
CRS-04200: Failed to initialize a security context during wallet IPMI credentials
creation.
Cause: Internal error.
Action: Contact Oracle Support Services.
CRS-04201: Hash context initialization failure during wallet IPMI credentials
creation
Cause: Internal error.
Action: Contact Oracle Support Services.
CRS-04202: String hashing failed during wallet credentials creation
Cause: Internal error.
Action: Contact Oracle Support Services.
CRS-04203: Hashing creation error during wallet credentials creation
Cause: Internal error.
Action: Contact Oracle Support Services.
CRS-04204: Failed to initialize the IPMI credentials wallet: string
Cause: While trying to initialize the IPMI credentials wallet, the cluster wallet
subsystem returned an unexpected error. The error is included with this message.
Action: See the documentation and follow the directions for the displayed error.
CRS-04205: Failed to open the IPMI credentials wallet. The wallet does not exist.
Cause: The wallet does not exist.
Action: Configure the wallet for the IPMI device using 'crsctl set'\n"
CRS-04206: Error reading IPMI credentials wallet: 'string'
Cause: While trying to read the IPMI credentials wallet, the cluster wallet
subsystem returned an unexpected error. The error is included with this message.
Action: See the documentation and follow the directions for the displayed error.
CRS-04207: Error writing IPMI credentials wallet: 'string'
Cause: While trying to write the IPMI credentials wallet, the cluster wallet
subsystem returned an unexpected error. The error is included with this message.
CRS-00001 to CRS-29006 64-91
Action: See the documentation and follow the directions for the displayed error.
CRS-04208: Unexpected error encountered during lookup of IPMI credentials in the
wallet
Cause: Possible corruption in wallet or internal error.
Action: Reconfigure the IPMI wallet using 'crsctl set' and then retry the operation.
If the retry fails call Oracle Support Services.
CRS-04209: IPMI credentials not contained in the wallet
Cause: The wallet has not been configured.
Action: Configure the wallet for the IPMI device using 'crsctl set'\n
CRS-04210: Failed to obtain the length of IPMI credentials while accessing the
wallet.
Cause: Possible corruption in wallet or internal error.
Action: Reconfigure the IPMI wallet using "crsctl set" and then retry the
operation. If the retry fails call Oracle Support Services.
CRS-04211: Failed to allocate memory
Cause: Insufficient system memory resources.
Action: Correct the system memory resources problem and retry.
CRS-04212: Failed to obtain the secret from the wallet.
Cause: Possible corruption in wallet or internal error.
Action: Reconfigure the IPMI wallet using "crsctl set" and then retry the
operation. If the retry fails call Oracle Support Services.
CRS-04213: Secret from wallet has incorrect size
Cause: Possible corruption in wallet or internal error.
Action: Reconfigure the IPMI wallet using "crsctl set" and then retry the
operation. If the retry fails call Oracle Support Services.
CRS-04214: crsctl string and string wallet versions of IPMI do not match.
Cause: A mismatch occurred between the IPMI versions of crsctl and the Cluster
Synchronization Services Daemon.
Action: Check proper installation and configuration of crsctl and the Cluster
Synchronization Services Daemon.
CRS-04215: Wallet secret encoding error
Cause: Internal error.
Action: Contact Oracle Support Services.
CRS-04216: Unexpected error configuring the wallet contents
Cause: Possible corruption in wallet or internal error.
Action: Reconfigure the IPMI wallet using "crsctl set" and then retry the
operation. If the retry fails call Oracle Support Services.
CRS-04217: Unexpected error saving IPMI credentials wallet: string
Cause: While trying to save the IPMI credentials wallet, the cluster wallet
subsystem returned an unexpected error. The error is included with this message.
Action: See the documentation and follow the directions for the displayed error.
64-92 Oracle Database Error Messages
CRS-04218: Unable to access an IPMI device on this system
Cause: A test for the availability of an IPMI device failed. This can occur if:
- the IPMI device driver is not installed,
- the installed device driver is not supported by Oracle,
- IPMI is not supported on this platform or operating system,
- no IPMI device is present, or
- an IPMI device is present but not configured.
Action: Verify that IPMI hardware supporting IPMI version 1.5 or greater is
present and supported on this server, that the IPMI device is configured and the
device driver is properly installed.
CRS-04219: Failed to open the wallet. User must be the creator of the wallet: string
Cause: Not the owner/creator of the wallet. The cluster wallet subsystem
returned an error included with this message.
Action: Retry as the owner/creator of the wallet. If necessary, also see the
documentation and follow the directions for the displayed error.
CRS-04221: Must specify a password
Cause: No password entered in response to password prompt.
Action: Specify a password which matches the local servers IPMI BMC password.
CRS-04222: Supplied password was greater than number bytes
Cause: The password specified was too long for the IPMI device.
Action: Supply a password with a length no greater than the indicated size while
still matching the password used to configure the IPMI device. Retry.
CRS-04223: Username is greater than number bytes
Cause: The username specified was too long for the IPMI device.
Action: Supply a username with a length no greater than the indicated size while
still matching the username used to configure the IPMI device. Retry.
CRS-04224: Unable to communicate with the Cluster Synchronization Services
daemon to update IPMI values.
Cause: crsctl modified the IPMI credential wallet but could not notify the Cluster
Synchronization Services Daemon.
Action: Retry after assuring the Cluster Synchronization Services Daemon is
functioning by executing csscheck.
CRS-04225: Unexpected authorization error while creating the IPMI credentials
wallet: string
Cause: Error creating the IPMI credentials wallet. The cluster wallet subsystem
returned an unexpected error. The error is included with this message.
Action: See the documentation and follow the directions for the displayed error
and retry.
CRS-04226: Unexpected authorization error while saving the IPMI credentials
wallet: string
Cause: While attempting to save the IPMI credentials wallet, the cluster wallet
sub-system returned an authorization error. The text of the authorization error text
is included with this message. This error was unexpected, and might have been
CRS-00001 to CRS-29006 64-93
due to an internal error, because wallet creation should be authorized for anyone,
and, if the wallet was pre-existing, it had already been read after proper
authorization checks.
Action: Consult the documentation for the included message to investigate the
root cause of the authorization error, and retry the "set" operation if indicated. If
this fails, contact Oracle Support Services.
CRS-04227: Configuration data stored but IPMI IP address is required to complete
the change. The change cannot be validated until the information is complete.
Cause: Not proceeding with Client's IPMI login change request because all
information such as IPMI username, password and IP address need to be present.
Action: Execute 'crsctl set css ipmiaddr' from crsctl.
CRS-04228: Value of attribute 'string' is missing
Cause: The user did not provide a value for the attribute.
Action: Provide a value using the format =, where
may be empty single quotes.
CRS-04229: The IPMI information change was successful
Cause: The IPMI address and authorization information have been validated and
the change completed.
Action: None required.
CRS-04230: A device was found where the IPMI device should be, but the device is
not an IPMI device
Cause: The IPMI driver may not be configured or supported by this host.
Action: Check the configuration of the IPMI driver and verify the server's support
of an IPMI version 1.5 or greater device.
CRS-04231: IPMI device and/or driver found
Cause: An IPMI device and/or device driver was identified on the machine.
Detection mechanisms for IPMI hardware vary by platform.
Action: None required.
CRS-04232: Configuration data stored but IPMI authorization information is
required to complete the change. The change cannot be validated until the
information is complete.
Cause: Not proceeding with Client's IPMI login change request because all
information (IPMI username, password and IP address) need to be present.
Action: Execute 'crsctl set css ipmiadmin' from crsctl.
CRS-04233: New IPMI configuration data stored, but failed validation by remote
node.
Cause: The supplied configuration data was stored in the Oracle registry, but the
resulting configuration could not be used for IPMI access by a remote node. The
stored IP address and/or IPMI admin credentials is/are incorrect.
Action: The validating node is identified in the CRS alert log, and further details
can be found in the alert log on that node. Verify the credentials for the local IPMI
device and reset the configuration using commands 'crsctl set css ipmiadmin' and
'crsctl set css ipmiaddr'
CRS-04234: IPMI configuration unset and registry entries deleted.
64-94 Oracle Database Error Messages
Cause: Requested operation successful. However, if the CRS stack was able to
access and use the deleted configuration data, it will continue to do so until it is
restarted.
Action: None required. Enter new configuration data or restart the CRS stack if
desired.
CRS-04235: Failed to delete the IPMI configuration from the Oracle Registry:
'string'
Cause: An error was encountered in the Oracle registry sub-system while trying
to clear IPMI configuration and delete the IPMI configuration entries. The detailed
error message is included with this message.
Action: See the documentation and follow the directions for the displayed error.
CRS-04236: Oracle Clusterware configured to use IPMI
Cause: The Oracle Registry contains complete configuration data for IPMI.
Action: None required.
CRS-04237: Oracle Clusterware is not fully configured to use IPMI
Cause: The Oracle Registry does not contain complete configuration data for
IPMI.
Action: None required.
CRS-04251: Failed to change the discovery string
Cause: An internal error happened during this operation.
Action: Contact Oracle Support Services.
CRS-04252: Failed to update the profile with the new discovery string
Cause: An internal error happened when updating the discovery string in the
profile.
Action: Contact Oracle Support Services.
CRS-04253: The discovery string can not be changed because the voting files are on
ASM
Cause: Changing the discovery string is allowed only if the voting files are not on
ASM.
Action: None
CRS-04254: The discovery string has already been set to this value
Cause: The value being passed is the same as the current discovery string.
Action: Pass a different discovery string if necessary.
CRS-04255: Not able to find the current configured voting files with the provided
discovery string
Cause: The supplied discovery string does not discover the voting files that are
currently configured.
Action: Pass a different discovery string that includes the location of the current
configured voting files.
CRS-04256: Updating the profile
Cause: An update to the profile is being performed.
Action: None
CRS-00001 to CRS-29006 64-95
CRS-04257: Voting file discovery string successfully replaced
Cause: A request to replace a discovery string completed.
Action: None
CRS-04258: Addition and deletion of voting files are not allowed because the
voting files are on ASM
Cause: A voting file add or delete request was issued, but voting files have been
configured on ASM storage. Once voting files are configured for ASM, changes in
the configuration can be made only with 'crsctl replace votedisk'.
Action: Use 'crsctl replace votedisk' to modify the voting file configuration.
CRS-04259: Only one ASM diskgroup may be specified
Cause: If the voting files will be on ASM, no more than one diskgroup should be
specified.
Action: Specify the correct ASM diskgroup.
CRS-04260: Voting file string is already configured
Cause: The location provided is already configured as a voting file.
Action: Specify another location that is not a current voting file.
CRS-04261: Diskgroup string is already configured with voting files
Cause: The diskgroup name provided is already configured with voting files.
Action: Specify another location for the voting files.
CRS-04262: Failure when retrieving information from the GPnP profile
Cause: An internal error happened when accessing GPnP profile.
Action: Contact Oracle Support Services.
CRS-04263: This operation is not allowed
Cause: Replacing a list of non-ASM voting files with a different list of voting files
is not supported.
Action: To change the list of non-ASM voting files and add new voting files, use
'crsctl add css votedisk ... '.
CRS-04264: The operation could not be validated
Cause: An internal error happened during the validation of the discovery string.
Action: Contact Oracle Support Services.
CRS-04265: The operation cannot be performed because the profile is busy with
another operation
Cause: Another operation on the profile is taking place.
Action: Let the other operation finish and retry.
CRS-04266: Voting file(s) successfully replaced
Cause: A request to replace a voting files(s) completed.
Action: None
CRS-04267: Error while updating the profile with ASM discovery string
Cause: An internal error happened while updating the ASM discovery string.
Action: Contact Oracle Support Services.
64-96 Oracle Database Error Messages
CRS-04268: '-name' option is allowed only with APPQOSDB or CVUDB type
wallets
Cause: The '-name' option was specified in a wallet command for other than
APPQOSDB or CVUDB type wallet.
Action: Use the '-name' option only for actions on APPQOSDB or CVUDB type
wallets.
CRS-04269: Successful get priority number string for Cluster Synchronization
Services.
Cause: The 'get' operation was performed successfully.
Action: None
CRS-04271: Voting file creation in other than an ASM disk group prohibited in this
cluster.
Cause: An attempt was made to create voting files outside of the ASM disk group
in a client cluster.
Action: Specify an ASM disk group for voting file creation or replacement.
CRS-04272: error while identifying voting files in use
Cause: More than one voting file was identified for the cluster.
Action: Contact Oracle Support Services.
CRS-04273: Creation of voting files in an ASM disk group not allowed using the
command 'crsctl add votedisk'.
Cause: An attempt was made to create voting file in the ASM disk group with the
command 'crsctl add votedisk'.
Action: Use 'crsctl replace votedisk' to add or replace the voting files in ASM disk
group.
CRS-04274: Command not supported in this cluster.
Cause: An attempt was made to add voting file(s) in a client cluster with the
command 'crsctl add votedisk'.
Action: Use 'crsctl replace votedisk' to add or replace the voting file in client
clusters.
CRS-04402: The CSS daemon was started in exclusive mode but found an active
CSS daemon on node string, number string, and is terminating
Cause: The CSS daemon was started in exclusive mode, which requires that the
clusterware stack is down on all other nodes to ensure data integrity. A CSS
daemon was detected on another node, so the CSS daemon on this node is
terminating.
Action: is required, otherwise stop the Oracle clusterware stack that is running on
the indicated node. The name and number of the active node may be unknown.
CRS-04404: The following nodes did not reply within the allotted time: string
Cause: The clusterized command timed out before the specified nodes responded
to the command.
Action: Check if the nodes are online; also check for communications problems.
Consider issuing the command locally on the specified node(s).
CRS-04405: The following nodes are unknown to Oracle High Availability Services:
string
CRS-00001 to CRS-29006 64-97
Cause: The local Oracle High Availability Services is not in contact with Oracle
High Availability Services on the specified nodes.
Action: Check if the nodes are online and Oracle High Availability Services is
running. Check for communications problems and consider issuing the command
locally on the specified node(s).
CRS-04406: Oracle High Availability Services synchronous start failed.
Cause: A start of Oracle High Availability Services with the '-wait' or '-waithas'
option did not complete successfully. This message is preceded by others
describing errors that occurred.
Action: Examine the error messages preceding this message and correct the
problems they describe.
CRS-04407: Values bigger than 10 are not allowed for parameter string.
Cause: This parameter does not allow values higher than 10.
Action: Use a value between 0 and 10.
CRS-04408: Node 'string' configured role successfully changed; restart Oracle High
Availability Services for new role to take effect.
Cause: The 'crsctl set node role' command was run to change the role of a node in
a Flex Cluster.
Action: Restart Oracle High Availability Services on the node by running 'crsctl
stop crs' and 'crsctl start crs'.
CRS-04409: Node 'string' is already configured in 'string' role.
Cause: A 'crsctl set node role' command specified the role already configured for
the node."
Action: Specify a different role or a different node, if appropriate.
CRS-04411: The role of node string cannot be converted to 'leaf'.
Cause: An attempt was made to modify the role of the last remaining configured
'hub' node to 'leaf' node, which is not allowed or the node is already a 'leaf' node."
Action: If role of this node must to be modified to 'leaf', first bring up another
node as a 'hub' node to ensure that there is always at least one 'hub' node.
CRS-04481: Unable to spawn a process.
Cause: There was an internal error while spawning a process.
Action: Report the error to Oracle Support.
CRS-04482: A child process terminated abnormally.
Cause: A child process exited due to an internal error.
Action: Report the error to Oracle Support.
CRS-04602: Failed number to add voting file string.
Cause: An attempt to add a voting file failed. The number following "Failed" is a
return code, which can be: 1 - internal OCSSD server error; 8 - rejected by OCSSD;
15- insufficient privileges for this operation; 19- version incompatibility between
client and server;
Action: Respond based on the return code as follows: 15 - adjust privileges or use
a different userid 19 - ensure that compatible versions are installed others - report
to Oracle Support Services
64-98 Oracle Database Error Messages
CRS-04608: Failure number with Cluster Synchronization Services while deleting
voting disk.
Cause: An attempt to delete a voting disk failed. The number following "Failed" is
a return code, which can be: 1 - internal OCSSD server error; 8 - rejected by
OCSSD; 15- insufficient privileges for this operation; 16- either the specified voting
disk does not exist or you tried to delete a majority of voting disks; 19- version
incompatibility between client and server;
Action: Respond based on the return code as follows: 15 - adjust privileges or use
a different userid 16 - review the voting disk configuration displayed by 'crsctl
query css votedisk' and correct your request accordingly 19 - ensure that
compatible versions are installed others - report to Oracle Support Services
CRS-04615: Software version query failed for node string
Cause: Internal error.
Action: Contact Oracle Support Services.
CRS-04625: Failure to allocate number bytes for username.
Cause: System is out of memory.
Action: Free up memory on system and retry.
CRS-04626: The requested setting must be between number and number.
Cause: An attempt to change a setting to an out of bounds value.
Action: Retry with the setting within the proper limits.
CRS-04627: Unable to lock the configuration before making changes. number
Cause: Failure in a CSS API acquiring a lock.
Action: Retry or contact support for information on the error code.
CRS-04628: Change to configuration failed, but was successfully rolled back.
Cause: See accompanying messages for explanation of cause.
Action: No action is required. This indicates that no damage was done.
CRS-04629: Unable number to mark unformat information on voting file string
Cause: Probably an unreadable / unwritable voting file was being removed.
Action: If cause is correct, this is ignorable, but not ideal.
CRS-04630: Unable to apply correct permissions to new voting file string.
Cause: An attempt to set permissions on a new voting file failed. This message is
accompanied by others that provide OS-specific details of the error.
Action: Examine the OS-specific error and correct it if possible; otherwise, specify
a different voting file.
CRS-04631: Unable number to undo initialization of voting file.
Cause: Could not roll back format of voting file.
Action: Disk should be cleaned out before an attempt to add again.
CRS-04632: Unable number to roll back OCR settings for voting file.
Cause: Could not remove temporary changes to OCR adding voting file.
Action: Shut down the cluster and restart. New voting file must be removed with
"crsctl delete css votedisk".
CRS-04633: This could take several minutes.
CRS-00001 to CRS-29006 64-99
Cause: CRS daemons is engaged in an activity take could potentially take a long
time.
Action: None
CRS-04634: Retrying stop resources.
Cause: crsctl command is trying again to stop resources.
Action: None
CRS-04635: Internal error 'number' while attempting to send shutdown request
Cause: This is an internal error.
Action: If retrying does not work, contact Oracle support
CRS-04636: Failure number in clsvrelversion
Cause: Internal error.
Action: Contact Oracle Support Services.
CRS-04637: Oracle High Availability Services release version on the local node is
[string]
Cause: Output message, not an error.
Action: None
CRS-04651: No resources found on server 'string'.
Cause: The server has no resources associated with it.
Action: Provide a server with resources running.
CRS-04652: Failure number in clsvswversion for the local node
Cause: Internal error.
Action: Contact Oracle Support Services.
CRS-04653: Server name 'string' contains invalid characters.
Cause: The name provided contains invalid characters.
Action: Use a server name with only alphanumeric characters.
CRS-04654: Server 'string' could not be found.
Cause: The name provided is not a known server's name.
Action: Use a known server's name.
CRS-04655: Resource 'string' could not be found.
Cause: The name provided is not a known resource's name.
Action: Use a known resource's name.
CRS-04656: Resource 'string' is not running on server 'string'.
Cause: The resource is not on the server the user specified.
Action: User must type a known server.
CRS-04657: Source and destination servers are the same.
Cause: The source and destination servers may not be the same.
Action: Specify a different destination server.
CRS-04658: The clusterware stack on node string is not completely down.
Cause: There is indication that the clusterware stack is still up.
64-100 Oracle Database Error Messages
Action: Shut down the entire clusterware stack before deleting the node.
CRS-04659: Error while trying to unpin node string.
Cause: An internal error happened during this operation.
Action: Contact Oracle Support Services.
CRS-04660: Could not find node string to delete.
Cause: The node to be deleted could not be found because it has not been a
member of this cluster recently.
Action: Check the name provided. If the name is correct, the node has been
automatically deleted because it was inactive for a long time and no further action
is required to delete the node from the cluster.
CRS-04661: Node string successfully deleted.
Cause: A request to delete a node completed.
Action: None
CRS-04662: Error while trying to delete node string.
Cause: Some internal error happened during this operation.
Action: Contact Oracle Support Services.
CRS-04663: could not find node string to pin
Cause: The indicated node was not an active Hub node in the cluster.
Action: Ensure that the node name is correct, is a Hub node, and that Oracle
Clusterware is running on the node.
CRS-04664: Node string successfully pinned.
Cause: A request to pin a node completed.
Action: None
CRS-04665: Error while trying to pin node string.
Cause: An internal error happened during this operation.
Action: Contact Oracle Support Services.
CRS-04666: Could not find node string to unpin.
Cause: An unpin request specified a node that is not an active hub node in the
cluster.
Action: Ensure that the node name is correct, that it is a hub node, and that Oracle
Clusterware is running on the node.
CRS-04667: Node string successfully unpinned.
Cause: A request to unpin a node completed.
Action: None
CRS-04668: This ASM diskgroup does not contain voting disks to be deleted
Cause: The ASM diskgroup name provided does not contain voting files.
Action: Provide the right ASM diskgroup name.
CRS-04669: Failed to set parameter string to number due to conflicting parameter
string; the new value for string must be less than number.
Cause: An attempt was made to set a new value to a configuration parameter
which conflicts with another parameter's current value.
CRS-00001 to CRS-29006 64-101
Action: Set the value of this parameter to a lower value than what is indicated in
the message.
CRS-04670: Failed to unset parameter string due to conflicting parameter string
currently set to number.
Cause: An attempt was made to unset a configuration parameter which conflicts
with another parameter's current value.
Action: Set the conflicting parameter to a value which can coexist with proposed
parameter change before submitting this parameter change.
CRS-04671: This command is not supported for ASM diskgroups.
Cause: The command 'crsctl add css votedisk' contains one or more ASM
diskgroups in the list of voting files. Voting files may be migrated to and from
ASM, but diskgroups cannot be added or deleted.
Action: Use an appropriate 'crsctl set' command to add ASM diskgroups. Use
'crsctl replace votedisk' command to migrate voting files to ASM.
CRS-04672: Successfully backed up the Voting File for Cluster Synchronization
Service.
Cause: The backup of the voting file completed successfully.
Action: None
CRS-04673: Oracle High Availability Services version on the local node is [string]
Cause: Output message, not an error.
Action: None
CRS-04674: Cannot add invalid user 'string' to CRS Admin list.
Cause: An attempt was made to add an invalid username to the CRS Admin list.
Action: Reissue the command with a valid username.
CRS-04675: Failed to get logfilesize for Cluster Synchronization Services.
Cause: An internal error happened during this operation for Cluster
Synchronization Services.
Action: Contact Oracle Support Services.
CRS-04676: Successful get logfilesize number for Cluster Synchronization Services.
Cause: The operation is done successfully for Cluster Synchronization Services.
Action: None
CRS-04677: Failed to get string for Cluster Synchronization Services.
Cause: An internal error happened during this operation for Cluster
Synchronization Services.
Action: Contact Oracle Support Services.
CRS-04678: Successful get string number for Cluster Synchronization Services.
Cause: The 'get' operation was performed successfully.
Action: None
CRS-04679: Failed to unset logfilesize for Cluster Synchronization Services.
Cause: An internal error happened during this operation for Cluster
Synchronization Services.
Action: Contact Oracle Support Services.
64-102 Oracle Database Error Messages
CRS-04680: Successful unset logfilesize for Cluster Synchronization Services.
Cause: The 'unset' operation was performed successfully.
Action: None
CRS-04681: Failed to unset priority for Cluster Synchronization Services.
Cause: An internal error happened during this operation for Cluster
Synchronization Services.
Action: Contact Oracle Support Services.
CRS-04682: Successful unset priority for Cluster Synchronization Services.
Cause: The 'unset' operation was performed successfully.
Action: None
CRS-04683: Failed to set parameter string to number for Cluster Synchronization
Services.
Cause: An internal error happened during this operation for Cluster
Synchronization Services.
Action: Contact Oracle Support Services.
CRS-04684: Successful set of parameter string to number for Cluster
Synchronization Services.
Cause: The 'set' operation was performed successfully for Cluster
Synchronization Services.
Action: None
CRS-04685: Failed to set logfilesize number for Cluster Synchronization Services.
Cause: An internal error happened during this operation for Cluster
Synchronization Services.
Action: Contact Oracle Support Services.
CRS-04686: Successful set logfilesize number for Cluster Synchronization Services.
Cause: The 'set' operation was performed successfully for Cluster
Synchronization Services.
Action: None
CRS-04687: Shutdown command has completed with errors.
Cause: Processing of a shutdown command has completed with errors.
Action: Refer to preceding error message(s) for information about the errors that
occurred.
CRS-04688: Oracle Clusterware is already stopped on server 'string'
Cause: Oracle Clusterware is not running on the indicated server.
Action: None
CRS-04689: Oracle Clusterware is already stopped
Cause: Oracle Clusterware is not running.
Action: None
CRS-04690: Oracle Clusterware is already running on 'string'
Cause: Oracle Clusterware is already running on the indicated server.
Action: None
CRS-00001 to CRS-29006 64-103
CRS-04691: Oracle Clusterware is already running
Cause: Oracle Clusterware is already running.
Action: None
CRS-04692: Cluster Ready Services is online in exclusive mode
Cause: Cluster Ready Services is limited to providing internal services to other
Oracle Clusterware components. External Cluster Ready Services are not available.
Action: When in exclusive mode, Oracle Clusterware components are dedicated
to the repair or reconfiguration of the Oracle Cluster Registry, voting files or both.
Oracle Clusterware should be down and remain down on every other cluster
node. Only commands that check or stop the stack, interact with Cluster
Synchronization Services or aid in Clusterware repair or reconfiguration should be
issued.
CRS-04693: Failed to back up the voting file for Cluster Synchronization Service.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
CRS-04694: Number of voting files cannot exceed number. Failed to add voting
files.
Cause: The request to add voting files would cause the maximum number
allowed to be exceeded.
Action: Specify fewer voting files to add so that the maximum is not exceeded, or
include the -purge option on 'crsctl add css votedisk' to replace the existing set of
files with an allowable number of new files.
CRS-04695: Voting disk addition failed because this disk string is a duplicate of an
existing voting disk with matching File Universal ID string.
Cause: This disk is already a part of the current cluster.
Action: None needed.
CRS-04696: Failed to set parameter string to number due to conflicting parameter
string; the new value for string must be greater than number.
Cause: An attempt was made to set a new value to a configuration parameter
which conflicts with another parameter's current value.
Action: Set the value of this parameter to a higher value than what is indicated in
the message.
CRS-04697: This command must be executed by Operating System user 'string'.
Cause: A crsctl command was executed by the wrong Operating System user.
Action: The specified Operating System user should execute the command.
CRS-04698: Error code number in retrieving the patch level
Cause: Internal error.
Action: Contact Oracle Support Services.
CRS-04699: Error code number in retrieving the cluster configuration type
Cause: Internal error.
Action: Contact Oracle Support Services.
CRS-04700: The Cluster Time Synchronization Service is in Observer mode.
64-104 Oracle Database Error Messages
Cause: Vendor time synchronization software exists on at least one of the nodes in
the cluster.
Action: None
CRS-04701: The Cluster Time Synchronization Service is in Active mode.
Cause: Vendor time synchronization software is not detected on any of the nodes
in the cluster.
Action: None
CRS-04703: The Cluster Time Synchronization Service is Offline.
Cause: The Cluster Time Synchronization Service is not running on the current
node.
Action: None
CRS-04704: Shutdown of Clusterware failed on node string.
Cause: The shutdown did not complete successfully. One or more of the internal
operations experienced an error that is reported in previous messages.
Action: Examine the error message(s) preceding this message and correct the
problem(s) they describe.
CRS-04705: Start of Clusterware failed on node string.
Cause: The start did not complete successfully. One or more of the internal
operations experienced an error that is reported in previous messages.
Action: Examine the error message(s) preceding this message and correct the
problem(s) they describe.
CRS-04708: Server name is missing
Cause: The server name provided was empty or no name was provided.
Action: Provide a valid server name.
CRS-04730: Command aborted due to an internal error
Cause: An inconsistent internal state was detected.
Action: Call Oracle Support Services.
CRS-04731: Specified file string could not be created.
Cause: JAZN configuration file required by the OC4J container could not be
created.
Action: Ensure that the directory path exists and that its permissions will allow
the file to be created by oracle owner of clusterware home.
CRS-04732: Could not be open file string.
Cause: JAZN configuration file required by the OC4J container could not be
opened.
Action: Ensure that the directory path exists and that its permissions will allow
the file to be created by oracle owner of clusterware home.
CRS-04733: File string does not exist.
Cause: The JAZN configuration file required by the OC4J container does not exist.
Action: Ensure that the directory path exists and that its permissions will allow
the file to be created oracle owner of the clusterware home.
CRS-04734: Filename was not specified.
CRS-00001 to CRS-29006 64-105
Cause: filename was not supplied or was an empty string.
Action: Re-try the command by specifying a valid JAZN configuration filename.
CRS-04735: Expected OCR key does not exist
Cause: An infrastructure error occurred because a required OCR key was missing.
Action: Call Oracle Support Services.
CRS-04736: Operation on OCR key failed
Cause: Operation on OCR key failed due to an OCR error.
Action: Re-issue the command as oracle owner of clusterware home.
CRS-04737: Failed to allocate number bytes of memory
Cause: Could not allocate memory for internal buffers due to insufficient system
memory resources
Action: Correct the system memory resources problem and retry the command
CRS-04738: Size of file string is too large
Cause: Specified file size exceeds 65536 bytes.
Action: Re-issue the command after reducing the size of the file.
CRS-04739: Could not close file string
Cause: Due to an internal error the specified file could not be closed
Action: Re-issue the command after verifying disk space, permissions and path.
CRS-04740: I/O operation on file string failed.
Cause: Due to an internal error an I/O operation on the specified file failed.
Action: Call Oracle Support if the problem persists.
CRS-04741: Insufficient permissions on OCR key
Cause: Operation on OCR key failed due to insufficient permissions.
Action: Re-issue the command as oracle owner of clusterware home.
CRS-04742: OCR updated with contents of string (New = number, Old = number
bytes)
Cause: set jazn command was issued and OCR key was updated.
Action: None Required.
CRS-04743: File string was updated from OCR(Size: number(New), number(Old)
bytes)
Cause: get jazn command was issued and specified file was updated with the
contents from OCR key.
Action: None Required.
CRS-04839: Required attribute 'string' is missing for 'string'.
Cause: A required attribute was not specified.
Action: Make sure the attribute is specified.
CRS-04840: Attribute 'string' cannot be specified using this command.
Cause: An attribute was specified that cannot be used with this command.
Action: Server pool configuration can be changed or created using 'crsctl modify
policyset' and 'crsctl modify serverpool -policy' commands.
64-106 Oracle Database Error Messages
CRS-04843: Policy 'string' does not exist.
Cause: An invalid policy name was specified.
Action: Verify the name.
CRS-04846: Configuration policy set has an invalid profile.
Cause: An invalid policy set definition was specified. Missing elements or
duplicate elements may be present in the profile.
Action: Verify the contents of the policy set profile and resubmit the command.
CRS-04847: File 'string' does not exist.
Cause: The specified for the comamnd did not exist or could not be opened.
Action: Verify the filename and resubmit the command.
CRS-04848: Policy 'string' appears more than once in a policy set file.
Cause: A policy was defined more than once in the profile.
Action: Verify the contents of the policy and remove the duplicate policy.
CRS-04849: Server pool 'string' appears more than once for policy 'string' in the
policy set file.
Cause: A server pool was defined more than once in the profile for the same
policy.
Action: Verify the contents of the policy and remove the duplicate server pool.
CRS-04873: At least one attribute must be specified for this command.
Cause: The 'crsctl eval modify' command was run without specifying any
attributes.
Action: Rerun the command with at least one attribute specified.
CRS-04891: Invalid value of level specified.
Cause: An invalid value for output level was specified. Output level can only be
1, 2 or 3.
Action: Rerun the command with a level of 1, 2 or 3.
CRS-04922: Module string: string ignored; module level out of bounds (valid range
number - number)
Cause: An attempt to set a log or trace level supplied a level that is out of range
for the module.
Action: Specify a log or trace level within the valid range.
CRS-04923: string module: string ignored; module level is invalid (range 0 - 65535)
Cause: Module log/trace level was invalid (range 0 - 65535).
Action: Specify a log/trace level within the valid range (0 - 65535).
CRS-04925: 'all' module keyword was specified with other module names
Cause: The module keyword 'all' already refers to all module names.
Action: When referring to all modules, use 'all' without duplicate references to
other module names.
CRS-04932: Failed to get the current cluster mode
Cause: There was an internal error while getting cluster mode.
Action: Contact Oracle Support Services.
CRS-00001 to CRS-29006 64-107
CRS-04933: Cluster mode set to "flex"; restart Oracle High Availability Services on
all nodes for cluster to run in "flex" mode.
Cause: Cluster mode was changed to "flex", which requires a cluster restart.
Action: Restart Oracle High Availability Services on all nodes for cluster to run in
"flex" mode.
CRS-04934: Failed to set the cluster mode
Cause: There was an internal error while setting cluster mode.
Action: Contact Oracle Support Services.
CRS-04937: Unable to set the cluster mode.
Cause: An attempt was made to set the cluster mode to 'flex' but Grid Naming
Service(GNS) was not configured.
Action: Configure GNS and try again to set the cluster mode to 'flex'.
CRS-04940: Cluster must run in standard or flex mode to use this command
Cause: An attempt was made to set the cluster mode but machine is not running
as a cluster.
Action: Cluster must be in standard or flex mode to change the cluster mode.
CRS-04942: Cluster mode set to "standard"
Cause: Cluster mode is changed. Cluster will shut down now.
Action: None
CRS-04953: CSS already running in nonexclusive mode
Cause: An exclusive mode CRS stack start was attempted when CSS was already
running in nonexclusive mode.
Action: Stop the CRS stack first and then start in exclusive mode.
CRS-04954: CRSD already running in nonexclusive mode
Cause: An exclusive mode CRS stack start was attempted when CRSD was
already running in nonexclusive mode.
Action: Stop the CRS stack first and then start in exclusive mode.
CRS-04955: CSS failed to start in exclusive mode
Cause: An exclusive mode CRS stack start was attempted but CSS failed to start
in exclusive mode.
Action: Check the Clusterware alert log for errors. Correct the reported error(s)
and retry.
CRS-04956: CRSD failed to start in exclusive mode
Cause: An exclusive mode CRS stack start was attempted but CRSD failed to start
in exclusive mode.
Action: Check the Clusterware alert log for errors. Correct the reported error(s)
and retry.
CRS-04967: Input values are out of range for parameter string
Cause: A value was provided which was out of range for this parameter.
Action: Specify a value which is appropriate for this parameter.
CRS-04968: Invalid values for parameter string. Specify either 0 or 1.
Cause: A value was provided which was out of range for this parameter.
64-108 Oracle Database Error Messages
Action: Specify a value which is appropriate for this parameter.
CRS-04969: Specified server attribute string does not exist
Cause: A nonexistent attribute was specified for get/set command.
Action: Specify an attribute that exists.Run 'crsctl stat res -p' to
list all the attributes of that resource.
CRS-04973: Flex ASM must be enabled before switching the cluster mode to 'flex'
Cause: An attempt to change the cluster mode to 'flex' failed because Flex ASM is
not enabled.
Action: Enable Flex ASM before changing the cluster mode. Refer to Oracle
Automatic Storage Management Administrator's Guide for configuring Flex ASM.
CRS-04977: Cluster cannot be converted from 'flex' mode to 'standard' mode
Cause: An attempt was made to set the cluster mode to standard from flex mode.
Action: If a cluster needs to be converted to standard mode, reinstall Clusterware.
CRS-04980: Duplicate value string specified for resource attribute string
Cause: A duplicate value was specified for a resource attribute.
Action: Specify only one value for a resource attribute.
CRS-04981: Duplicate value string specified for type attribute keyword string
Cause: A duplicate value was specified for a type attribute keyword.
Action: Specify only one value for DEFAULT_VALUE, FLAGS and TYPE per type
attribute.
CRS-04982: Valid type attribute keyword string specified outside a type attribute
Cause: A valid type attribute keyword was specified outside a type attribute.
Action: Specify the ATTRIBUTE type attribute keyword before specifying the
DEFAULT_VALUE, FLAGS or TYPE type attribute keywords.
CRS-04983: Invalid type attribute keyword string specified
Cause: An invalid type attribute keyword was specified.
Action: Specify only the valid type attribute keywords ATTRIBUTE, DEFAULT_
VALUE, FLAGS and TYPE.
CRS-04984: Duplicate definition for type attribute string
Cause: The same type attribute was named on more than one ATTRIBUTE
keyword.
Action: Define a type attribute only once.
CRS-04985: The value 'string' of FLAGS attribute is invalid.
Cause: An invalid flag value was specified.
Action: Flag values may be combined using the '|' character as a separator.
CRS-04986: This command is for Oracle's internal use only
Cause: A command meant for internal use was specified.
Action: Refer to 'crsctl -h' for list of commands available for use.
CRS-04989: Module string: string ignored; module level out of bounds (valid range
number - number)
CRS-00001 to CRS-29006 64-109
Cause: An attempt to set a log or trace level supplied a level that is out of range
for the module.
Action: Specify a log or trace level within the valid range.
CRS-04990: Issued command does not support filter in this version of CRS.
Cause: The command was rejected because a filter (-w) was specified. Filters are
not currently supported for this command.
Action: Reissue the command without the filter.
CRS-04991: Could not delete the resource because it does not exist.
Cause: An attempt to delete a resource failed because the resource specification
did not identify an existing resource. Either there was no resource with the
specified name, or no resource satisfied the specified filter.
Action: Reissue the command specifying the name of an existing resource or a
filter that will select an existing resource.
CRS-04992: Could not delete the server pool because it does not exist.
Cause: An attempt to delete a server pool failed because the server pool
specification did not identify an existing server pool. Either there was no server
pool with the specified name, or no server pool satisfied the specified filter.
Action: Reissue the command specifying the name of an existing server pool or a
filter that will select an existing server pool.
CRS-04993: Could not delete the server category because it does not exist.
Cause: An attempt to delete a server category failed because the server category
specification did not identify an existing server category. Either there was no
server category with the specified name, or no server category satisfied the
specified filter.
Action: Reissue the command specifying the name of an existing server category
or a filter that will select an existing server category.
CRS-04994: Could not delete the resource type because it does not exist.
Cause: An attempt to delete a resource type failed because the resource type
specification did not identify an existing resource type. Either there was no
resource type with the specified name, or no resource type satisfied the specified
filter.
Action: Reissue the command specifying the name of an existing resource type or
a filter that will select an existing resource type.
CRS-04995: The command 'string' is invalid in crsctl. Use srvctl for this command.
Cause: An attempt was made to use an unsupported command in crsctl.
Action: Use srvctl for the mentioned command.
CRS-04996: Command ('crsctl string policyset') is not supported in this version of
CRS.
Cause: The command was rejected because policy-based management is not a
supported feature in this release.
Action: If this error occurs during rolling upgrade, wait for the upgrade to finish.
Otherwise, upgrade to the required release or higher.
CRS-04997: Command ('crsctl string category') is not supported in this version of
CRS.
64-110 Oracle Database Error Messages
Cause: The command was rejected because the server category is not a supported
feature in this release.
Action: If this error occurs during rolling upgrade, wait for the upgrade to finish.
Otherwise, upgrade to the required release or higher.
CRS-04998: Command ('crsctl eval string' ) is not supported in this version of CRS.
Cause: The command was rejected because What-If is not a supported feature in
this release.
Action: If this error occurs during rolling upgrade, wait for the upgrade to finish.
Otherwise, upgrade to the required release or higher.
CRS-04999: Command ('crsctl string policy') is not supported in this version of CRS.
Cause: The command was rejected because policy-based management is not a
supported feature in this release.
Action: If this error occurs during rolling upgrade, wait for the upgrade to finish.
Otherwise, upgrade to the required release or higher.
CRS-05000: Expected resource string does not exist in agent process
Cause: The expected resource must have been created by Oracle Configuration
tools.
Action: Check that the resource was not manually deleted. If not the case call
Oracle Support.
CRS-05001: Expected dependency in resource string on a resource of type string
does not exist
Cause: The expected resource dependency must have been created by Oracle
Configuration tools.
Action: Check that the resource dependency was not manually removed.
CRS-05002: Agent action was aborted
Cause: Agent action was aborted either due to action timeout expiry or the user
canceled the action.
Action: Retry the operation.
CRS-05003: Invalid attribute value: 'string' for attribute string
Cause: An attribute value passed to the Agent was NULL or invalid.
Action: Give the correct value to the attribute and retry.
CRS-05004: Cannot find listener endpoint for listener string
Cause: listener endpoint not found.
Action: Check listener.ora for that listener.
CRS-05005: IP Address: string is already in use in the network
Cause: The VIP resource attempted to use an IP address already in use in the
network.
Action: Use srvctl to re-create vip or scanvip specifying an IP address which is not
being used in the network and retry the operation.
CRS-05006: Unable to automatically select a network interface which has subnet
mask string and subnet number string
Cause: The subnet mask and subnet number configured for the resource did not
match the subnet mask and subnet number of any network interface on this node.
CRS-00001 to CRS-29006 64-111
Action: Provide a subnet mask and subnet number which matches at least one
network interface's subnet mask and subnet number using srvctl remove and add
vip and retry the operation.
CRS-05007: Cannot remove the primary IP string from the network interface
Cause: The primary IP of the network interface was incorrectly configured as the
VIP.
Action: Use 'srvctl remove' and 'srvctl add vip' or 'srvctl remove' and 'srvctl add
scan' to provide the correct IP address for the VIP and retry the operation.
CRS-05008: Invalid attribute value: string for the network interface
Cause: The network interface value did not match the subnet mask and subnet
number of any network interface on the node.
Action: Modify the network interface's value such that the subnet mask and
subnet number matches the subnet mask and subnet number of at least one
network interface on the node using 'srvctl remove' and 'srvctl add vip' and retry
the operation.
CRS-05009: The VIP address string does not belong to the subnet string
Cause: The VIP's subnet number and the network interface's subnet number did
not match.
Action: Make the VIP's subnet number match the network interface's subnet
number using 'srvctl remove' and 'srvctl add vip' or 'srvctl remove' and 'srvctl add
scan' and retry the operation.
CRS-05010: Update of configuration file "string" failed: details at "string" in "string"
Cause: An attempt to open the specified file failed. Common causes are that the
file does not exist, or the file permissions prohibit access.
Action: Check that the file exists and has the proper permissions.
CRS-05011: Check of resource "string" failed: details at "string" in "string"
Cause: The check of the database or Automatic Storage Management instance
failed.
Action: Check the database or ASM instance alert log and the referenced Oracle
Clusterware trace file for additional information. Recover the instance if necessary.
CRS-05012: Check of service resource "string" failed: details at "string" in "string"
Cause: The check of the preconnect service failed because it could not run on the
same node as the main service.
Action: Check the referenced Oracle Clusterware trace file for additional
information. Start the preconnect service on a different node.
CRS-05013: Agent "string" failed to start process "string" for action "string": details
at "string" in "string"
Cause: The named agent failed to start the named process for the named action.
Action: Check the referenced Oracle Clusterware trace file for additional
operating system specific information. Refer to operating system documentation
to correct the error.
CRS-05014: Agent "string" timed out starting process "string" for action "string":
details at "string" in "string"
Cause: The named agent aborted the named process because the process failed to
respond within the timeout period.
64-112 Oracle Database Error Messages
Action: Check the agent log files for further information
CRS-05015: Agent timed out waiting for a response from the DHCP server
Cause: Agent and the DHCP server were not able to communicate with each
other. Common causes of this failure are due to the DHCP server not running, or
improper DHCP server configuration, or the DHCP server running out of DHCP
leases.
Action: Identify the cause of the problem from the DHCP server log files. If the
problem is due to the DHCP server running out of leases, increase the number of
addresses which can be served by the DHCP server.
CRS-05016: Process "string" spawned by agent "string" for action "string" failed:
details at "string" in "string"
Cause: The named process failed to complete succesfully.
Action: Check details in the agent log for error information from the spawned
process.
CRS-05017: The resource action "string string" encountered the following error:
string. For details refer to "string" in "string".
Cause: An error occurred during the resource action.
Action: Examine the accompanying error messages and respond accordingly.
CRS-05018: Clusterware has disabled an IP route associated with destination
"string" and interface "string". For details, refer to "string" in "string".
Cause: A potentially conflicting route in the same subnet used by the address for
the redundant interconnect was found and removed to prevent routing conflicts.
Action: Validate that the route described was not actually in use.
CRS-05019: All OCR locations are on ASM disk groups [string], and none of these
disk groups are mounted. Details are at "string" in "string".
Cause: OCR was configured on ASM disk groups, and all of the listed disk groups
failed to mount. The possible causes are:
1. A disk was not accessible.
2. A disk in a normal or high redundancy disk group failed after the most recent
dismount.
3. The ASM_DISKSTRING in the SPFILE or the GPnP profile was incorrect.
Action: Check the ASM alert logs for more information. To correct disk access or
failure issues either: a) restore access to the disks in the disk group and mount the
disk group (via ASMCMD or SQL). or b) Issue a force mount to the disk group to
offline missing disks and mount a normal or high redundancy disk group. To
correct the ASM_DISKSTRING in the SPFILE and propagate the change to the
GPnP profile, in sqlplus, issue the SQL command "ALTER SYSTEM SET ASM_
DISKSTRING ...", see Setting Oracle ASM Initialization
Parameters in the Automatic Storage Management Administrator's Guide
CRS-05020: Not all endpoints are registered for listener string
Cause: Listener agent failed to register all endpoints to listener.
Action: Check listener log file for that listener.
CRS-05021: Check of storage failed: details at "string" in "string"
Cause: The check of ASM storage failed because the storage was not accessible.
CRS-00001 to CRS-29006 64-113
Action: Check Clusterware alert log and the referenced Oracle Clusterware trace
file for additional information.
CRS-05022: Stop of resource "string" failed: current state is "string"
Cause: The named resource failed to stop.
Action: Ensure there are no users of the resource and reissue the stop.
CRS-05023: Failed to unmount file system "string"; details at "string" in "string"
Cause: The named file system resource failed to unmount.
Action: Determine which OS processes are accessing the mount point using an OS
command such as 'fuser' or 'lsof' for Unix based platforms or 'handle' for
Windows. Close, shut down, or terminate applications and processes accessing the
mount point, then retry.
CRS-05024: Unmounting file system "string"
Cause: A 'stop' of the file system resource mounted on the indicated path started.
Action: This is an informational message only.
CRS-05025: File system "string" unmounted
Cause: A 'stop' of the file system resource mounted on the indicated path
completed normally.
Action: This is an informational message only.
CRS-05026: Failed to clean mount point "string"; details at "string" in "string"
Cause: The clean of the volume failed because one or more processes on the
system were accessing the mount point.
Action: Determine which OS processes are accessing the mount point using an OS
command such as 'fuser' or 'lsof' for Unix based platforms or 'handle' for
Windows. Close, shut down, or terminate applications and processes accessing the
mount point, then retry.
CRS-05027: The ASM instance on node "string" cannot be stopped because it is
currently being used by Cluster Ready Services.
Cause: An attempt to stop the ASM instance on the indicated server failed
because Cluster Ready Services was using that ASM instance.
Action: Use 'crsctl stop crs' or 'crsctl stop cluster' to stop the Cluster Ready
Services on the node.
CRS-05028: Cannot start resource "string" because the resource it depends on,
"string", failed to start on the same node
Cause: The resource could not be started because the resource on which it
depends failed to start on the same node.
Action: Manually start the dependency resource and then the resource on the
same node.
CRS-05029: Agent failed to initialize ARP devices required for starting the HAIP
resource
Cause: The resource could not be started because the ARP devices failed to start
on the same node.
Action: Manually check the ARP devices on the same node and then start the
resource.
64-114 Oracle Database Error Messages
CRS-05030: The resource action "string string" completed with the following error:
string
Cause: An error occurred during the resource action.
Action: Examine the accompanying error messages and respond accordingly.
CRS-05031: invalid instance open mode: 'string'
Cause: The instance open mode passed to the Agent was invalid.
Action: Provide a correct instance open mode and retry.
CRS-05032: incompatible instance open mode: 'string' with the role of the database
in an Oracle Data Guard configuration: 'string'
Cause: The instance open mode passed to the Agent was invalid for the role of the
database in an Oracle Data Guard configuration.
Action: Provide a correct instance open mode or change the role of the database in
an Oracle Data Guard configuration and retry.
CRS-05033: Open mode 'string' is incompatible with the current instance state
'string'.
Cause: An attempt to change the instance to the specified open mode failed
because the specified mode was incompatible with the current instance state.
Action: Reissue the command with a correct instance open mode.
CRS-05034: failed to get instance connection
Cause: Agent process failed to get an instance connection. Internal error.
Action: If error persists, contact Oracle Support Services.
CRS-05100: One or more attributes were not found for the entity.
Cause: The operation failed because the entity lacked one or more attributes.
Action: Provide the required attributes and retry the operation.
CRS-05101: The specified entity was not found in the entity list.
Cause: The Cluster Ready Services daemon was unable to locate the input entity
in its entity list.
Action: Retry the operation after deleting the entity and registering it again.
CRS-05102: The entity is already registered.
Cause: An attempt was made to register an entity that was already registered.
Action: If the specification of the entity was incorrect, retry the operation with the
correct entity specification.
CRS-05103: The entity is not registered.
Cause: An attempt was made to operate on an entity that was not registered.
Action: If the specification of the entity was incorrect, retry specifying the correct
entity otherwise register the entity and retry the operation.
CRS-05104: The registration of the entity failed.
Cause: An attempt to register an entity failed. The preceding error messages
provide additional details.
Action: Correct the issues described in the accompanying error messages and
retry the registration.
CRS-05105: Unregistering the entity failed.
CRS-00001 to CRS-29006 64-115
Cause: An attempt to unregister an entity failed. The preceding error messages
provide additional details.
Action: Correct the issues described in the accompanying error messages and try
to unregister the entity again.
CRS-05106: The entity failed to start.
Cause: An attempt to start an entity failed. The preceding error messages provide
additional details.
Action: Correct the issues described in the accompanying error messages and try
to start the entity again.
CRS-05107: The entity failed to stop.
Cause: An attempt to stop an entity failed. The preceding error messages provide
additional details.
Action: Correct the issues described in the accompanying error messages and try
to stop the entity again.
CRS-05108: The entity failed to relocate.
Cause: An attempt to relocate an entity failed. The preceding error messages
provide additional details.
Action: Correct the issues described in the accompanying error messages and try
to relocate the entity again.
CRS-05109: The status code is invalid.
Cause: The status code was not of the type enum CLSCRS_STAT.
Action: Verify that the status code argument is a valid code returned from the
CLSCRS API and retry.
CRS-05110: The entity failed to update.
Cause: An attempt to update an entity failed. The preceding error messages
provide additional details.
Action: Correct the issues described in the accompanying error messages and try
to update the entity again.
CRS-05111: The entity has an invalid profile.
Cause: There were invalid attributes in the entity profile.
Action: Check the entity profile, remove any invalid attributes and retry the
operation.
CRS-05112: The action script of the entity cannot be found.
Cause: The action script of the entity specified by the attribute ACTION_SCRIPT
could not be located.
Action: Ensure that the attribute ACTION_SCRIPT exists and specifies a valid
script for the entity.
CRS-05113: The entity has a dependency error.
Cause: An attempt to operate on an entity failed because of the resulting effect on
one or more dependent entities. Preceding messages provide details on the nature
of the problem.
Action: Take the corrective action as suggested by the preceding messages and
resubmit the operation.
64-116 Oracle Database Error Messages
CRS-05114: A placement error was encountered while attempting to operate on the
entity.
Cause: Based on the placement policy for the entity, there was no available server
to which the entity could failover or start.
Action: Check the target server for the entity and restart the entity using the 'crsctl
start' command.
CRS-05115: The specified server is not in the cluster.
Cause: The specified server name did not designate a server in the cluster.
Action: Check the server names in the cluster and retry the operation specifying a
server that is a member of the cluster.
CRS-05116: The operation on the entity has been cancelled.
Cause: A scheduled or running operation was cancelled.
Action: None
CRS-05117: An internal error occurred while operating on the entity.
Cause: There was an internal error. This message will be preceded by another
message with a more specific problem description.
Action: Review the accompanying error messages and contact Oracle Support
Services.
CRS-05118: The entity or all of its instances are disabled.
Cause: The attempted request could not be serviced because the entity was
disabled.
Action: Enable the entity and retry the operation.
CRS-05119: The active version of Cluster Ready Services is below the required
level.
Cause: An attempt was made to use the functionality that has only been available
beginning with the active version specified in the preceding message.
Action: Upgrade to the minimum required version stated in the preceding
message.
CRS-05120: The requested action for the entity was aborted due to a timeout.
Cause: The timeout specified for a custom action was reached before the action
could complete.
Action: Revise the timeout setting and retry the action.
CRS-05121: The operation cannot be completed due to invalid arguments.
Cause: Invalid arguments were specified to execute the CRS command.
Action: Check the arguments and specify only valid arguments to the command.
CRS-05122: The entity could not be registered due to a type mismatch.
Cause: The registration of an entity failed because the input entity type to the API
did not match the type of the entity to be registered.
Action: Specify the correct entity type to register the entity.
CRS-05123: The resource validity check failed due to an invalid resource type.
Cause: The value of the attribute TYPE for the resource was not 'application'.
Action: Specify the value 'application' for the resource attribute TYPE.
CRS-00001 to CRS-29006 64-117
CRS-05124: The entity has one or more attributes missing.
Cause: The validity check failed to find one or more of the attributes NAME,
TYPE or ACTION_SCRIPT for the entity.
Action: Update the entity to have the missing attributes.
CRS-05125: The action script does not exist for the entity.
Cause: The validity check on the entity failed to find the file specified in the
attribute ACTION_SCRIPT of the entity.
Action: Provide the full path to an existing file for the attribute ACTION_SCRIPT.
CRS-05126: The entity has invalid hosting servers for the placement policy.
Cause: Either the attribute HOSTMEM_REQ was not set or was empty for the
entity.
Action: Either set the attribute HOSTMEM_REQ or set the attribute
PLACEMENT to 'balanced'.
CRS-05127: The attribute HOSTING_MEMBERS must not be specified for the
entity.
Cause: The attribute HOSTING_MEMBERS was specified for the entity with the
balanced placement policy.
Action: Either unset the attribute HOSTING_MEMBERS or set the entity's
placement policy to be 'favored' or 'restricted'.
CRS-05128: The value of the attribute HOSTING_MEMBERS for the entity is
invalid.
Cause: The value of the attribute HOSTING_MEMBERS for the entity contained
one or more of the characters: ',', ';' or ':'.
Action: Remove the invalid characters from the value of the attribute HOSTING_
MEMBERS.
CRS-05129: An invalid placement policy was specified for the entity.
Cause: The attribute PLACEMENT for the entity was set to an invalid value.
Action: Set the attribute PLACEMENT to either 'favored','restricted', or 'balanced'.
CRS-05130: An invalid value was specified for the attribute AUTO_START.
Cause: The attribute AUTO_START of the entity was set to an invalid value.
Action: Set the attribute AUTO_START to either 'always', 'never', or 'restore'.
CRS-05131: One or more attribute of the entity are set to invalid values.
Cause: An attempt was made to set the attribute to a value of different type.
Action: Check the attributes and set the value to the appropriate type.
CRS-05132: The entity list is not empty.
Cause: The entity list passed to receive the information for the queried CRS
entities was not empty.
Action: Create an empty list to pass as the output argument and retry.
CRS-05133: The generated connection key is too long.
Cause: The size of the environment variables HOST and HOSTNAME were
greater than 255 characters.
Action: Set the environment variables HOST and HOSTNAME to values whose
length is no more than 255 characters.
64-118 Oracle Database Error Messages
CRS-05151: Memory could not be allocated.
Cause: An attempt to allocate memory for an entity failed.
Action: Check the system logs, correct the condition and retry the operation.
CRS-05152: The pointer to the context is invalid.
Cause: A null pointer was passed as a pointer to the context.
Action: Create a valid context and pass its address to the requested operation.
CRS-05153: The entity pointer is invalid.
Cause: A null pointer was passed to the API for the entity name or the entity
value."
Action: Allocate memory for the entity name and the entity value and pass in the
valid pointers to the API.
CRS-05154: The input attribute name not found in the entity's attribute list.
Cause: An attempt was made to modify a nonexistent attribute of an entity.
Action: Provide an existing attribute of the entity and retry the operation.
CRS-05155: The end of the entity list was reached.
Cause: An attempt was made to search beyond the end of the entity list.
Action: None
CRS-05156: The entity has no attributes.
Cause: An attempt was made to get the attribute list for an entity that has no
attributes.
Action: Check the entity name that is being passed. If it's correct then delete the
entity, register it with correct attributes and retry the operation.
CRS-05157: The pointer to the operation status message in the entity structure is
null.
Cause: The message pointer in the entity structure was null. The entity maybe
corrupted.
Action: Delete the entity, register the entity and retry the operation.
CRS-05158: The entity list could not be found.
Cause: An attempt was made to perform an operation on an entity list, but no
valid entity list was passed.
Action: None
CRS-05159: The specified entity already exists.
Cause: An attempt was made to add an entity that already exists.
Action: Check the entity name to be added. If it is correct and the existing entity
must be recreated, then delete the entity and retry the operation.
CRS-05160: The entity list is empty.
Cause: The query failed because the entity list was empty.
Action: Retry the query supplying the intended list of entities.
CRS-05161: The entity name contains invalid characters.
Cause: An attempted operation was rejected because the specified entity name
contained invalid characters.
CRS-00001 to CRS-29006 64-119
Action: Retry the operation specifying a valid entity name.
CRS-05162: The name of a resource or a filter contains invalid characters.
Cause: An attempted operation was rejected because the specified resource name
or the filter name contained invalid characters.
Action: Retry the operation specifying a valid resource name or the filter name.
CRS-05164: The attribute name is longer than 255 characters.
Cause: An attempt was made to use an attribute name with a length of more than
255 characters.
Action: Use an attribute name shorter than 255 characters and retry the operation.
CRS-05165: The supplied buffer is too small for the filter to string conversion.
Cause: The buffer supplied to the API was too small to hold the output string.
Action: Increase the buffer size and pass it to the API.
CRS-05166: The specified return code is invalid.
Cause: The return code was not of the type 'enum clscrsret'.
Action: Verify that the return code argument is a valid code returned from the
CLSCRS API and retry.
CRS-05501: Unable to connect to eONS server on port number
Cause: The eONS server may not be active or listening on a different port.
Action: Ensure that the eONS resource is ONLINE and listening on the above
port.
CRS-05502: Invalid event template string
Cause: The event template specified is invalid.
Action: The event template format must be ( name>=) ...
CRS-05503: Error creating the eONS subscriber
Cause: The eONS server may not be active.
Action: Ensure that the CRS eONS resource is in ONLINE state.
CRS-05504: Node down event reported for node 'string'.
Cause: The specified node was not responsive.
Action: Restart the specified node.
CRS-05601: MDNS: string
Cause: None, generic bypass mdns message.
Action: None
CRS-05602: mDNS service stopping by request.
Cause: MDNSD stopping by OHASD request.
Action: None
CRS-05705: Failed to get required resources
Cause: There was an internal error while evaluating the required resources for the
subject resource.
Action: Contact Oracle Support Services.
64-120 Oracle Database Error Messages
CRS-05706: No more members to consider
Cause: There was no host found on which to start the resource based on the
placement policy.
Action: Check the placement policy and the required resources for the subject
resource.
CRS-05707: Failed after successful dependency consideration
Cause: There was no host found on which to start the resource based on the
placement policy.
Action: Check the placement policy and the required resources for the subject
resource.
CRS-05709: Resource 'string' is already running on member 'string'
Cause: An attempt was made to start a resource on a host while it is already
running on that host.
Action: This is an insignificant error. Check the operation being performed.
CRS-05801: Agent path is null or does not resemble a filesystem path
Cause: Unable to spawn the agent program because of incorrect agent path.
Action: Fix the agent path using 'crsctl modify type'.
CRS-05802: Unable to start the agent process
Cause: An attempt to start the agent process failed.
Action: Ensure that the agent path is correct and has the proper permissions, and
retry the command.
CRS-05805: Missing the required action callback in agent
Cause: Unable to execute resource's command.
Action: Ensure that agent executable or action script contains the missing
function.
CRS-05809: Failed to execute 'string' value of 'string' for 'string'. Error information
'string', Category : number, OS error : number
Cause: Unable to spawn the resource action script due to incorrect path value or
incorrect permissions or other OS error.
Action: Correct the action script path and permissions or check and fix the
reported OS error.
CRS-05810: Attempt to add a duplicate resource 'string'. Details at string in string.
Cause: An identical resource was already being monitored.
Action: Rename the resource and retry the operation.
CRS-05811: Failed to read ORA_CRS_HOME from environment. Details at string in
string.
Cause: The ORA_CRS_HOME environment variable was not set correctly.
Action: This variable is set during CRS installation. If necessary, reinstall CRS.
CRS-05812: Could not get local hostname. Details at string in string.
Cause: The hostname could not be read.
Action: Check that the hostname for the local machine is valid. If the problem
persists, contact Oracle Support Services.
CRS-00001 to CRS-29006 64-121
CRS-05813: Could not change directory to 'string'. Details at string in string.
Cause: The specified path is inaccessible to the agent process.
Action: Check that the specified path exists.
CRS-05814: Agent 'string' started with invalid arguments. Details at string in string.
Cause: An invalid parameter was supplied to the agent.
Action: Contact Oracle Support Services.
CRS-05815: Agent 'string' could not find any base type entry points for type 'string'.
Details at string in string.
Cause: Action entry points were not defined for this agent.
Action: No action necessary if this is a script agent. If this is not a script agent,
define action points in your agent code.
CRS-05816: Agent 'string' could not start implicit monitoring for resource 'string'.
Details at string in string.
Cause: The resource was currently disabled and hence could not be monitored.
Action: Enable the resource.
CRS-05817: Caught exception from user code for command 'string'. Details at string
in string.
Cause: An exception was thrown from the user code when an action entry point
was called.
Action: This is due to an error in the agent user code. Modify the agent's code to
resolve this.
CRS-05818: Aborted command 'string' for resource 'string'. Details at string in
string.
Cause: Execution of the specified command was aborted due to a timeout.
Action: Restart the resource manually. If the problem persists, contact Oracle
Support Services.
CRS-05819: Could not abort command 'string' for resource 'string'. Details at string
in string.
Cause: Attempt to abort the specified command failed.
Action: Define an abort action entry point for the agent.
CRS-05820: Agent 'string' failed to initialize server process address. Details at string
in string.
Cause: Agent could not connect to the server process.
Action: Contact Oracle Support Services.
CRS-05821: Agent 'string' is started with wrong user 'string'. Details at string in
string.
Cause: An incorrect owner was specified for the agent.
Action: Make sure CRSD has enough privileges to spawn programs as the value
specified as the 'owner' in the ACL attribute.
CRS-05822: Agent 'string' disconnected from server. Details at string in string.
Cause: Agent could not connect to server process.
Action: Contact Oracle Support Services.
64-122 Oracle Database Error Messages
CRS-05823: Could not initialize agent framework. Details at string in string.
Cause: Initialization of the agent failed.
Action: Contact Oracle Support Services.
CRS-05824: Could not initialize server connect string 'string'. Details at string in
string.
Cause: Incorrect server connect string was specified in the environment.
Action: Contact Oracle Support Services.
CRS-05825: Agent 'string' is unresponsive and will be restarted. Details at string in
string.
Cause: The specified agent did not respond and will be restarted automatically.
Action: None
CRS-05826: Agent 'string' could not read environment variable 'string'. Details at
string in string.
Cause: The agent could not read a required environment variable.
Action: Contact Oracle Support Services.
CRS-05827: Could not find information for resource 'string'. Details at string in
string.
Cause: The specified resource was not found in the internal list of resources.
Action: Check the agent parameters and restart the resource manually.
CRS-05828: Could not start agent 'string'. Details at string in string.
Cause: Creation of the agent process failed.
Action: Contact Oracle Support Services.
CRS-05829: Failed to get definition for resource 'string'. Details at string in string.
Cause: The definition of the resource could not be determined.
Action: Delete the resource and add it again using the crsctl command.
CRS-05830: Invalid path 'string' found for agent filename. Details at string in string.
Cause: The path that was specified for the agent was incorrect.
Action: Check that the path exists and is readable.
CRS-05831: Agent 'string' has exceeded maximum failures and has been disabled.
Details at string in string.
Cause: The specified agent has failed too many times.
Action: Contact Oracle Support Services.
CRS-05832: Agent 'string' was unable to process commands. Details at string in
string.
Cause: Agent was unable to process commands.
Action: Contact Oracle Support Services.
CRS-05833: Cleaning resource 'string' failed as part of reboot-less node fencing
Cause: A resource 'clean' action associated with reboot-less node eviction
encountered an error. This is an expected occurence in most cases.
Action: None
CRS-00001 to CRS-29006 64-123
CRS-05834: Resource 'string' monitoring disabled due to repeated agent failures.
Details at string in string.
Cause: A cluster resource was disabled because it was causing repeated agent
failures.
Action: Restart the resource after resolving the problems with the agent.
CRS-05835: Agent version incapable of processing this command
Cause: A request encountered an older agent version that is not capable of
processing that request.
Action: Upgrade the agent to the Clusterware version.
CRS-05836: Agent 'string' version 'string' cannot process command. Details at string
in string.
Cause: A request encountered an older agent version that is not capable of
processing that request.
Action: Upgrade the agent to the Clusterware version.
CRS-05837: Unable to open environment file 'string'.
Cause: The environment file specified could not be opened.
Action: Verify that the filename, its location and its permsissions are correct.
CRS-05838: Syntax error in environment file 'string'.
Cause: The environment file specified did not have key value pairs in the correct
format.
Action: Correct the key value format and retry. Consult the administration
document for the correct format.
CRS-05839: The requested action 'string' for the resource 'string' on server 'string'
was aborted due to a timeout.
Cause: The timeout specified for a custom action was reached before the action
could complete.
Action: Revise the timeout setting and retry the action.
CRS-06001: User does not have permission to start CRSD.
Cause: Unable to start CRSD due to insufficient permissions.
Action: Start CRSD as a privileged user.
CRS-06007: Could not communicate with Event Manager.
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-06015: Oracle Clusterware has experienced an internal error. Details at string
in string.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
CRS-06016: Resource auto-start has completed for server string
Cause: CRS has completed startup of resources on the specified server.
Action: None
CRS-06017: Processing resource auto-start for servers: string
64-124 Oracle Database Error Messages
Cause: The blocking start of Oracle High Availability Services has updated its list
of servers to process.
Action: None
CRS-06021: Could not set system resource limits for Clusterware: "ulimit -string
string".
Cause: A ulimit command issued internally to set system resource limits failed.
Action: Ensure that the correct resource limit values are set in the user profile and
limits.conf.
CRS-06022: Starting Oracle High Availability Services-managed resources
Cause: Oracle High Availability Services is attempting to start resources for the
local server.
Action: None
CRS-06023: Starting Oracle Cluster Ready Services-managed resources
Cause: Oracle Cluster Ready Services is attempting to start resources for the
cluster.
Action: None
CRS-06024: Completed start of Oracle Cluster Ready Services-managed resources
Cause: Oracle Cluster Ready Services has started resources for the cluster.
Action: None
CRS-06504: 'string' cannot be specified as an attribute.
Cause: An effort was made to explicitly specify an attribute that cannot be
specified by the user
Action: Remove the mentioned attribute, and re-issue the command.
CRS-06505: Format of the EXPRESSION attribute 'string' is invalid
Cause: The EXPRESSION attribute is invalid.
Action: Provide a valid value for the EXPRESSION attribute.
CRS-06530: cannot set node role because cluster is not configured in "flex" mode
Cause: An attempt to set a node's role using 'crsctl set node role' was rejected
because the cluster is not running in "flex" mode. Node roles can only be set for
nodes in "flex" clusters.
Action: Reissue the command after the cluster is configured in "flex" mode."
CRS-06531: Issued command is not supported in this version of CRS.
Cause: The command was rejected because related feature is not supported in this
release.
Action: If this error occurs during rolling upgrade, wait for the upgrade to finish.
Otherwise, upgrade to the required release or higher.
CRS-06602: No password specified.
Cause: A password was not entered in response to the password prompt.
Action: Enter a password.
CRS-06603: Cannot modify 'string' policy.
Cause: An attempt was made to modify a read-only policy.
Action: Specify a policy that is not read-only.
CRS-00001 to CRS-29006 64-125
CRS-06705: Oracle Clusterware Release Version ('string') does not match Software
Version ('string'). Oracle Clusterware cannot be started.
Cause: Oracle Clusterware was started from an older home that has since been
upgraded.
Action: Start Oracle Clusterware from the upgraded home. Also, check the CRS
home configured in olr.loc and the /etc/init.d/ohasd script to make sure they
have not been accidentally changed.
CRS-06706: Oracle Clusterware Release patch level ('number') does not match
Software patch level ('number'). Oracle Clusterware cannot be started.
Cause: Oracle Clusterware was started from an older home that has since been
patched.
Action: Start Oracle Clusterware from the patched home. Also, check the CRS
home configured in olr.loc and the /etc/init.d/ohasd script to make sure they
have not been accidentally changed.
CRS-06749: unable to get the software version
Cause: The crsctl query failed because the software version could not be retrieved.
Either the clusterware stack was down, or the user was not root (UNIX) or
Administrator (WINDOWS).
Action: Bring up the clusterware stack or run the query as a privileged user.
CRS-06750: unable to get the active version
Cause: The crsctl query failed because the active version could not be retrieved.
Either the clusterware stack was down, or the user was not root (UNIX) or
Administrator (WINDOWS).
Action: Bring up the clusterware stack or run the query as a privileged user.
CRS-06751: unable to get the software patch version
Cause: The crsctl query failed because the software patch version could not be
retrieved. Either the clusterware stack was down, or the user was not root (UNIX)
or Administrator (WINDOWS).
Action: Bring up the clusterware stack or run the query as a privileged user.
CRS-06752: Active version query failed.
Cause: The crsctl query failed because the active version could not be retrieved.
Action: See the accompanying error message and respond.
CRS-06753: Software patch query failed.
Cause: The crsctl query failed because the software patch version could not be
retrieved.
Action: See the accompanying error message and respond.
CRS-06754: Software version query failed for node string.
Cause: The crsctl query failed to retrieve the software version.
Action: See the accompanying error message and respond.
CRS-06761: Invalid value for QoS Management policy management key 'string' in
OCR.
Cause: An invalid value for Quality of Service Management policy management
key was found in the OCR.
Action: Contact Oracle Support Services.
64-126 Oracle Database Error Messages
CRS-06762: Unable to use CRSCTL for Policy Management because Quality of
Service Management (QoS) is managing the Clusterware policies.
Cause: CRSCTL cannot be used for Policy Management because Quality of
Service Management is configured to manage Clusterware policies.
Action: Use Quality of Service Management for Policy Management.
CRS-07000: Generic GPnP success
Cause: This is an internal error.
Action: Contact Oracle Support Services.
CRS-07001: Generic GPnP error
Cause: This is an internal error.
Action: Contact Oracle Support Services.
CRS-07002: Not enough memory
Cause: This is an internal error.
Action: Contact Oracle Support Services.
CRS-07003: GPnP facility initialization failed
Cause: This is an internal error.
Action: Contact Oracle Support Services.
CRS-07004: This feature is unsupported or not implemented
Cause: This is an internal error.
Action: Contact Oracle Support Services.
CRS-07005: Requested item not found
Cause: This is an internal error.
Action: Contact Oracle Support Services.
CRS-07006: Insufficient buffer size
Cause: This is an internal error.
Action: Contact Oracle Support Services.
CRS-07007: Error in file I/O operation
Cause: This is an internal error.
Action: Contact Oracle Support Services.
CRS-07008: Invalid permissions for the operation
Cause: This is an internal error.
Action: Contact Oracle Support Services.
CRS-07009: Bad authority id
Cause: This is an internal error.
Action: Contact Oracle Support Services.
CRS-07010: Key does not exist
Cause: This is an internal error.
Action: Contact Oracle Support Services.
CRS-07011: Bad key
CRS-00001 to CRS-29006 64-127
Cause: This is an internal error.
Action: Contact Oracle Support Services.
CRS-07012: Hostname not found
Cause: This is an internal error.
Action: Contact Oracle Support Services.
CRS-07013: GPNPD daemon is not running
Cause: This is an internal error.
Action: Contact Oracle Support Services.
CRS-07014: Attempting to set a bad value
Cause: This is an internal error.
Action: Contact Oracle Support Services.
CRS-07015: Bad hostname value
Cause: This is an internal error.
Action: Contact Oracle Support Services.
CRS-07016: Bad authority id value
Cause: This is an internal error.
Action: Contact Oracle Support Services.
CRS-07025: Duplicate profile
Cause: This is an internal error.
Action: Contact Oracle Support Services.
CRS-07026: Profile is not given or not available
Cause: This is an internal error.
Action: Contact Oracle Support Services.
CRS-07027: Badly formed profile
Cause: This is an internal error.
Action: Contact Oracle Support Services.
CRS-07028: Profile is too big to be valid
Cause: This is an internal error.
Action: Contact Oracle Support Services.
CRS-07029: Profile is older than the current
Cause: This is an internal error.
Action: Contact Oracle Support Services.
CRS-07030: Profile exists in memory only, not saved
Cause: This is an internal error.
Action: Contact Oracle Support Services.
CRS-07031: Request retry message from GPNPD
Cause: This is an internal error.
Action: Contact Oracle Support Services.
64-128 Oracle Database Error Messages
CRS-07032: Value already set in profile
Cause: This is an internal error.
Action: Contact Oracle Support Services.
CRS-07040: Generic XML error
Cause: This is an internal error.
Action: Contact Oracle Support Services.
CRS-07041: GPnP XML profile is not well formed
Cause: This is an internal error.
Action: Contact Oracle Support Services.
CRS-07047: Communication timeout
Cause: This is an internal error.
Action: Contact Oracle Support Services.
CRS-07053: Resource discovery error
Cause: This is an internal error.
Action: Contact Oracle Support Services.
CRS-07056: OCR Init error
Cause: This is an internal error.
Action: Contact Oracle Support Services.
CRS-07057: Reinit OCR to a different bootlevel
Cause: This is an internal error.
Action: Contact Oracle Support Services.
CRS-07058: OCR error
Cause: This is an internal error.
Action: Contact Oracle Support Services.
CRS-07065: GPnP wallet error
Cause: This is an internal error.
Action: Contact Oracle Support Services.
CRS-07066: Requested GPnP wallet is not found
Cause: This is an internal error.
Action: Contact Oracle Support Services.
CRS-07067: Invalid GPnP wallet password given
Cause: This is an internal error.
Action: Contact Oracle Support Services.
CRS-07068: GPnP wallet is too big to be valid
Cause: This is an internal error.
Action: Contact Oracle Support Services.
CRS-07069: GPnP wallet is corrupted or invalid
Cause: This is an internal error.
Action: Contact Oracle Support Services.
CRS-00001 to CRS-29006 64-129
CRS-07070: Bad or missing private key in GPnP wallet
Cause: This is an internal error.
Action: Contact Oracle Support Services.
CRS-07071: Bad or missing public key in GPnP wallet
Cause: This is an internal error.
Action: Contact Oracle Support Services.
CRS-07076: Failed to init crypto libraries
Cause: This is an internal error.
Action: Contact Oracle Support Services.
CRS-07085: GPnP profile unsigned
Cause: This is an internal error.
Action: Contact Oracle Support Services.
CRS-07086: GPnP profile signature invalid
Cause: This is an internal error.
Action: Contact Oracle Support Services.
CRS-07087: GPnP profile valid peer signature
Cause: This is an internal error.
Action: Contact Oracle Support Services.
CRS-07088: GPnP profile valid PA signature
Cause: This is an internal error.
Action: Contact Oracle Support Services.
CRS-07089: GPnP profile was signed with a different wallet
Cause: This is an internal error.
Action: Contact Oracle Support Services.
CRS-07090: Grid Naming Service (GNS) error
Cause: This is an internal error.
Action: Contact Oracle Support Services.
CRS-07095: GPnP tool usage
Cause: This is an internal error.
Action: Contact Oracle Support Services.
CRS-07096: GPnP tool version
Cause: This is an internal error.
Action: Contact Oracle Support Services.
CRS-08000: unable to obtain local host name for reboot advisory log file scan
Cause: An attempt to retrieve the local host name failed. The scan for reboot
advisory files will not use host name criteria and so may report occurrences for
other nodes as well as this one.
Action: Report this error to Oracle Support Services.
CRS-08001: an error occurred accessing reboot advisory log file location: string
64-130 Oracle Database Error Messages
Cause: The scan for reboot advisory log files was unable to access the indicated
file system location. The location was skipped, so any reboot advisory files that it
contains will not be reported. This message is accompanied by CLSU- messages
containing details of the access error.
Action: Respond based on the error described by the accompanying CLSUmessages. This may involve re-creating the directory or changing its permissions.
CRS-08002: an error occurred searching reboot advisory log file location: string
Cause: The scan for reboot advisory log files was unable to read the next file name
from the indicated file system location. No further processing of reboot advisory
files from that location occurs. This message is accompanied by CLSU- messages
containing details of the access error.
Action: Respond based on the error described by the accompanying CLSUmessages.
CRS-08003: reboot advisory log file: string is unexpectedly empty
Cause: The scan for reboot advisory log files encountered a file that was empty.
This might happen (rarely) if a component is initializing its use of reboot advisory
at the same time the scan is running. Processing of other files in the location
continues.
Action: Frequent occurrence of this message should be reported to Oracle Support
Services.
CRS-08004: an error occurred reading reboot advisory log file: string
Cause: The scan for reboot advisory log files experienced a read error on a reboot
advisory file. No further processing is done for that file, but the scan continues
with other files. This message is accompanied by CLSU- messages containing
details of the read error.
Action: Respond based on the accompanying CLSU- messages.
CRS-08005: an error occurred closing reboot advisory log file: string
Cause: The scan for reboot advisory log files experienced a close error on a reboot
advisory file. The scan continues with other files. This message is accompanied by
CLSU- messages containing details of the close error.
Action: Report this error to Oracle Support Services.
CRS-08006: an error occurred opening reboot advisory log file: string
Cause: The scan for reboot advisory log files experienced an error when it opened
a reboot advisory file. The scan continues with other files. This message is
accompanied by CLSU- messages containing details of the open error.
Action: If the error indicated in the accompanying CLSU- messages is one that
can be corrected, do so. Otherwise, report this error to Oracle Support Services.
CRS-08007: an error occurred closing reboot advisory log file location: string
Cause: The scan for reboot advisory log files experienced an error when it closed
the indicated file system location. Processing of other reboot advisory locations (if
any) continues normally. This message is accompanied by CLSU- messages
containing details of the close error.
Action: Report this error to Oracle Support Services.
CRS-08008: string
Cause: Operating system error data related to reboot advisory file processing was
returned. The error data is packaged in a CLSU- message that follows
CRS-00001 to CRS-29006 64-131
"CRS-08008:". One or more of these messages appears after a message announcing
the error condition.
Action: Look up the embedded CLSU- message for an explanation of the
operating system error data. If there is no CLSU- message ID present, contact
Oracle Support Services.
CRS-08009: reboot advisory log file: string contains invalid data (length number,
error code number)
Cause: A reboot advisory log record read from the indicated file contained
incorrect data.
Action: Report this error to Oracle Support Services.
CRS-08010: invalid network reboot advisory message detected (length number, error
code number)
Cause: A reboot advisory record received over the network was improperly
formed or contained incorrect data.
Action: Report this error to Oracle Support Services.
CRS-08011: reboot advisory message from host: string, component: string, with time
stamp: string
Cause: d a reset or reboot of the affected host, and respond accordingly. Refer to
the discussion of reboot advisories in the Oracle Clusterware administration
documentation for additional guidance.
Action: Use the reboot advisory message(s) to determine why Oracle Clusterware
CRS-08012: reboot advisory message from a higher Oracle Clusterware version
detected
Cause: A reboot advisory message from a higher version installation of Oracle
Clusterware was detected. This is an expected occurrence with network reboot
advisories when there are nodes with a higher Oracle Clusterware version than
this node (such as during an upgrade). It is an unexpected condition with file
reboot advisories.
Action: The reboot advisory message is displayed in a following CRS-08013
message in a "raw" text form. In the case of network reboot advisories, the
explanatory message text should be readable and useful to determine the cause of
the node reboot. If the reboot advisory message is from a file, report this message
to Oracle Support Services.
CRS-08013: reboot advisory message text: string
Cause: An explanatory text message associated with a reboot advisory announced
in a preceding CRS-08011 or CRS-08012 message was displayed. These text
messages are always written in US English locale.
Action: Refer to the descriptions of messages CRS-08011 and -08012, and to the
Oracle Clusterware documentation on reboot advisories.
CRS-08014: reboot advisory binary data (number bytesstring) follows:
Cause: Binary data associated with a reboot advisory message was displayed. It is
followed by one or more lines of CRS-08015 message containing the binary data
formatted in hexadecimal. If an asterisk appears inside the parentheses, an invalid
data length was detected.
Action: Refer to the description of message CRS-08011 and -08012, and to the
Oracle Clusterware documentation on reboot advisories.
64-132 Oracle Database Error Messages
CRS-08015: number string
Cause: Hexadecimal display of binary data included in a reboot advisory log
message was displayed. The first number is an offset and is followed by up to 16
bytes of data.
Action: Refer to the description of message CRS-08011 and -08012, and to the
Oracle Clusterware documentation on reboot advisories.
CRS-08016: an error occurred determining the location for reboot advisory log files
Cause: The search for reboot advisory log files was unable to determine the file
system location used for those files. Processing of reboot advisory files is skipped.
This message is accompanied by CLSU- messages containing failure details. This is
an internal error.
Action: Report this error to Oracle Support Services.
CRS-08017: location: string has number reboot advisory log files, number were
announced and number errors occurred
Cause: This summary message is written during Oracle Clusterware startup if
one or more reboot advisory log files was found and examined.
Action: This message is informational, but if the error count is nonzero the
associated messages (earlier in the alert log) should be examined.
CRS-08018: warning: missing cluster identity data for reboot advisory message
validation
Cause: During Oracle Clusterware start up, an attempt to obtain the identity of
the cluster failed. Processing continues normally, but network reboot advisories
from nodes in other clusters may be reported in this cluster's alert log.
Action: Report this error to Oracle Support Services.
CRS-08019: warning generated by the initialization of the reboot advisory in the
CSS agent, string
Cause: During initialization of the reboot advisory, a warning was generated
Action: Report this warning to Oracle Support Services.
CRS-08020: error generated by the initialization of the reboot advisory in the CSS
agent, string
Cause: During initialization of the reboot advisory, an error was generated.
Action: Report this error to Oracle Support Services.
CRS-08500: Oracle Clusterware string process is starting with operating system
process ID string
Cause: The indicated service or component of Oracle Clusterware began
execution.
Action: None
CRS-08501: Oracle Clusterware string process with operating system process ID
string is ending with return value number
Cause: The indicated service or component of Oracle Clusterware ended
execution.
Action: None
CRS-08502: Oracle Clusterware string process with operating system process ID
string failed in initialization
CRS-00001 to CRS-29006 64-133
Cause: The indicated service or component of Oracle Clusterware was unable to
complete initialization.
Action: Report this error to Oracle Support Services.
CRS-08503: Oracle Clusterware string process with operating system process ID
string experienced fatal signal or exception code number
Cause: The indicated service or component of Oracle Clusterware encountered a
fatal exception.
Action: Report this error to Oracle Support Services.
CRS-08504: Oracle Clusterware string process with operating system process ID
string is exiting
Cause: The indicated service or component of Oracle Clusterware ended
execution using the operating system 'exit' function.
Action: None
CRS-08505: Oracle Clusterware string process with operating system process ID
string experienced fatal error string-number
Cause: The indicated service or component of Oracle Clusterware encountered an
internal error, causing an ADR incident to be raised.
Action: Report this error to Oracle Support Services.
CRS-09000: Failed to allocate memory.
Cause: During intialization, memory could not be allocated.
Action: Report this error to Oracle Support Services.
CRS-09001: Internal Error
Cause: An internal error occurred.
Action: Report this error to Oracle Support Services.
CRS-09003: Cluster Health Monitor is not supported in this configuration.
Cause: Grid Infrastructure Management Repository was not configured.
Action: Re-Install Grid Infrastructure and ensure that Grid Infrastructure
Management Repository is configured.
CRS-09004: Error reading from standard input
Cause: Could not read commands from the command line.
Action: Report this error to Oracle Support Services.
CRS-09005: Quoted string not ended
Cause: An unmatched " was found in the command entered.
Action: Put in the corresponding quote or remove the unmatched quote.
CRS-09008: Unknown verb string
Cause: Unknown or invalid verb passed to oclumon.
Action: Use 'oclumon -h' in command line or help command in interactive mode
to see the supported verbs.
CRS-09009: Error string: Parsing error. Invalid arguments specified.
Cause: Invalid or unknown arguments passed.
Action: Refer to product documentation or to command online help for an
explanation of verbs and arguments.
64-134 Oracle Database Error Messages
CRS-09010: Error string: mandatory data not supplied
Cause: Mandatory data not supplied to the command.
Action: Refer to product documentation or to command online help for an
explanation of verbs and arguments.
CRS-09011: Error string: Failed to initialize connection to the Cluster Logger Service
Cause: Error occurred while connecting to the Cluster Logger Service.
Action: Ensure that Cluster Logger Service is running and reachable from the
client node by using the 'ping' command for the given node.
CRS-09012: Error string: Error sending query to the Cluster Logger Service
Cause: Error occurred while sending query to the Cluster Logger Service.
Action: Ensure that the Cluster Logger Service is running and reachable from the
client node by using the 'ping' command for the specified node.
CRS-09013: Error string: Invalid data received from the Cluster Logger Service
Cause: Invalid or unknown data received from the Cluster Logger Service.
Action: Ensure that the Cluster Logger Service is running and reachable from the
client node by using the 'ping' command for the specified node.
CRS-09014: Error: Corrupt reply from the Cluster Logger Service
Cause: Invalid or unknown data received from the Cluster Logger Service.
Action: Make sure that the version of both master and client installation is same.
Also, check the connectivity between master and client using the 'ping'.
CRS-09017: Error: Invalid or unknown reply received from the Cluster Logger
Service
Cause: Error occurred in the data received.
Action: Make sure that the version of both master and client installation is same.
Also, check the connectivity between master and client.
CRS-09018: Error string: No arguments supplied
Cause: No argument was supplied with the command.
Action: Some commands need arguments with them. Refer to the product
documentation or to the online help display.
CRS-09019: Error string: No parameter string supported
Cause: A wrong parameter was passed with the command.
Action: Refer to the command help and pass the correct parameters.
CRS-09020: Error string: No master node name specified
Cause: The master node name was not specified in the command.
Action: Pass the appropriate master node name with the command.
CRS-09021: Error string: Invalid or no start time specified
Cause: A start time was not specified or the time was passed in the wrong format.
Action: Pass the correct start time. For correct format, refer to command help.
CRS-09022: Error string: Invalid or no end time specified
Cause: A end time was not specified or the time was passed in the wrong format.
Action: Pass the correct end time. For correct format, refer to command help.
CRS-00001 to CRS-29006 64-135
CRS-09023: Error string: Time not specified or in wrong format or invalid
Cause: Time was not specified or was invalid.
Action: Pass the correct and valid time. For correct format, refer to command
help.
CRS-09024: Error string: No node name specified
Cause: Node name not specified.
Action: Provide a node name in the command. Refer to the product
documentation or to the command online help for information.
CRS-09025: Error string: No disk ID name specified
Cause: Disk ID was not specified in the command with -diskid.
Action: Pass a valid disk ID with -diskid option.
CRS-09026: Error string: No parameter specified
Cause: The parameter was not specified in the query.
Action: Pass appropriate parameter for query. Refer to the product
documentation or to the command online help for information.
CRS-09027: Error string: Parameter string is not supported with this verb
Cause: Invalid or unknown parameter passed.
Action: Pass the correct parameter. Refer to the product documentation or to the
command online help for information.
CRS-09028: Error string: No NIC ID specified
Cause: NIC ID was not specified in the command with -nicid.
Action: Pass a valid NIC ID with -nic option.
CRS-09029: Error string: No PID specified
Cause: PID was not specified in the command with -pid.
Action: Pass a valid PID with -pid option.
CRS-09030: Error string: No region specified
Cause: Incorrect or no region specified with -c option.
Action: Pass a valid region with -c option. Refer to the product documentation or
to the command online help for information.
CRS-09031: Error string: Argument string not supported with this verb
Cause: Unknown or invalid argument passed with the command.
Action: Refer to the product documentation or to the command online help for
information on supported arguments.
CRS-09032: Invalid hour specified in the time argument
Cause: Invalid hour in the time string was passed.
Action: Pass a valid time string in accordance with the format. Refer to the
product documentation or to the command online help for information on
supported arguments.
CRS-09033: Invalid minutes specified in the time argument
Cause: Invalid minutes in the time string was passed.
64-136 Oracle Database Error Messages
Action: Pass a valid time string in accordance with the format. Refer to the
product documentation or to the command online help for information on
supported arguments.
CRS-09034: Invalid seconds specified in the time argument
Cause: Invalid seconds in the time string was passed.
Action: Pass a valid time string in accordance with the format. Refer to the
product documentation or to the command online help for information on
supported arguments.
CRS-09035: Arguments not in proper format, or invalid arguments
Cause: Invalid arguments specified.
Action: Pass a valid verb and correct arguments for it. Refer to the product
documentation or to the command online help for information on supported
arguments.
CRS-09036: Invalid Cluster Health Monitor repository size specified
Cause: Non-numeric value or value out of range specified for Cluster Health
Monitor repository size.
Action: Specify Cluster Health Monitor repository size in the valid range. Refer to
the product documentation or to the command online help for information on
supported arguments.
CRS-09037: string Error: Node name not specified. -disk, -nic or -proc need node
name
Cause: The required node name was not specified for -disk, -nic or -proc.
Action: Provide a node name with -n option. Refer to the product documentation
or to the command online help for information on supported arguments.
CRS-09038: Error: -s and -e need to be specified together
Cause: Either -s or -e is missing.
Action: Start and end time need to be specified together for range queries, which
cannot be unbounded. Refer to the product documentation or to the command
online help for information on supported arguments.
CRS-09039: Error string: -i is not allowed with the range query
Cause: The -i option was specified on a oclumon range query.
Action: Use -i only in continuous mode. Refer to the command inline help or
product documentation for more information.
CRS-09040: Error string: Band value not specified or incorrect
Cause: The band value was not specified with -t option or was invalid.
Action: Provide a valid band value. Refer to the product documentation or to the
command online help for information on supported arguments..
CRS-09041: Error string: The -repos argument was specified without an option.
Cause: -repos was not specified with the option, generating a parsing error.
Action: Provide a valid option to -repos. Refer to the product documentation or to
the command online help for information on supported arguments.
CRS-09042: Error string: No size specified with 'checkretentiontime'
Cause: A valid value was not specified with 'checkretentiontime'.
CRS-00001 to CRS-29006 64-137
Action: Provide a valid numerical value with 'checkretentiontime'. Refer to the
product documentation or to the command online help for information on
supported arguments.
CRS-09043: Error string: Non-numeric or invalid value for size: string
Cause: An invalid or non-numeric value was specified for size.
Action: Provide a valid numeric size. Refer to the product documentation or to
the command online help for information on supported arguments.
CRS-09044: No key specified with -getkey
Cause: An option was not specified with -getkey.
Action: Provide a valid key as an option with -getkey.
CRS-09045: No key specified for -get
Cause: An option was not specified with -get.
Action: Provide a valid option with -get. Refer to the product documentation or to
the command online help for information on supported arguments.
CRS-09046: Invalid key specified
Cause: An unknown key was specified with -get.
Action: Provide a supported key with -get. Refer to the product documentation or
to the command online help for information on supported arguments.
CRS-09047: Error string: Error Dumping Log (return code:number ) for node string
Cause: An error occurred while dumping local log.
Action: Report this error to Oracle Support Services. Cluster Health Monitor
repository directory may be unreachable, unreadable or incorrect.
CRS-09048: Error string: No data received from the Cluster Logger Service after
number attempts
Cause: Data was not received from the Cluster Logger Service after the specified
number of attempts or data was not available.
Action: None
CRS-09049: Error string: Cannot get environment variable CRFHOME
Cause: An internal error occurred.
Action: Report this error to Oracle Support Services.
CRS-09050: Error string: Too many host names
Cause: Too many host names were specified.
Action: Provide valid number of host names. Refer to the product documentation
or to the command online help for information.
CRS-09051: Error string: Invalid interval size specified
Cause: Non-numeric or invalid interval specified.
Action: Provide a valid numerical value for interval size. Refer to the product
documentation or to the command online help for information
CRS-09052: Error string: string control not supported
Cause: The specified debug control was not supported.
Action: Provide a supported control. Refer to the product documentation or to the
command online help for information.
64-138 Oracle Database Error Messages
CRS-09053: Key:value pair missing
Cause: A required key:value pair was missing.
Action: Provide a valid key:value pair. Refer to the product documentation or to
the command online help for information
CRS-09054: Incomplete or invalid parameters string
Cause: Incomplete or invalid parameters supplied.
Action: Provide the complete and correct parameters. Refer to the product
documentation or to the command online help for information
CRS-09055: module:level specified in invalid format or invalid value
Cause: Invalid format or value specified for module:level.
Action: Provide correct module:level. Refer to the product documentation or to
the command online help for information
CRS-09056: Error string: Invalid Cluster Health Monitor repository location
specified
Cause: Invalid Cluster Health Monitor repository location specified.
Action: Provide a directory with read and write permissions for Cluster Health
Monitor repository location. Refer to the product documentation or to the
command online help for information.
CRS-09057: Error string: No response received from the Cluster Logger Service
Cause: No data received from the Cluster Logger Service for the query.
Action: Ensure that the Cluster Logger Service is running and reachable from the
client node by using the 'ping' command for the specified node.
CRS-09058: Error string: Changing log level failed due to authentication failure
Cause: Log level could not be changed due to authentication failure.
Action: Ensure that this command is run as root.
CRS-09059: Error string: Changing log level failed due to connection failure
Cause: A connection failure occurred while changing the log.
Action: Ensure that the daemons are running and are reachable.
CRS-09060: Error string: Unable to send message due to memory allocation failure
Cause: Memory could not be allocated for debug message.
Action: Report this error to Oracle Support Services.
CRS-09061: Error string: Changing log level failed due to response time-out
Cause: A time out happened while waiting for response.
Action: Report this error to Oracle Support Services.
CRS-09062: Error string: Error in changing log level
Cause: An error occurred while changing log level.
Action: Report this error to Oracle Support Services.
CRS-09063: Given time range is more than 1 hour
Cause: The time range specified with showtrail command was more than one
hour.
Action: Provide a range of less than 1 hour for showtrail.
CRS-00001 to CRS-29006 64-139
CRS-09064: Error string: Changing log level failed due to connection failure. Cannot
connect to daemon string.
Cause: A connection failure occurred while changing the log level.
Action: Ensure that the specified daemon is running and reachable.
CRS-09065: Disk ID not found
Cause: Given disk ID was not found or not present in the interesting list.
Action: Provide a disk ID which is available at the start of the query range.
CRS-09066: Process ID not found
Cause: Given process ID was not found.
Action: Provide a process ID which is available at the start of the query range.
CRS-09067: NIC ID not found
Cause: Given NIC ID was not found.
Action: Provide a correct NIC ID.
CRS-09068: Error string: -allnodes and -n must not be used together
Cause: Both -allnodes and -n were supplied on a dumpnodeview command.
Action: Specify either -allnodes or -n with specific nodes.
CRS-09069: The new Cluster Health Monitor repository location is string.
Cause: The Cluster Health Monitor repository location was successfully replaced.
Action: None
CRS-09070: The new Cluster Health Monitor repository retention time is number
seconds.
Cause: The Cluster Health Monitor repository retention time was successfully
modified.
Action: None
CRS-09071: Internal error in Cluster Health Analysis during problem analysis
Cause: An internal error occurred during problem analysis.
Action: Contact Oracle Support Services.
CRS-09072: Internal error in Cluster Health Analysis report output
Cause: An internal error occurred while reporting a problem.
Action: Contact Oracle Support Services.
CRS-09073: No problems to display
Cause: No problems were found that matched the selection criteria specified to
the 'oclumon analyze' command.
Action: None
CRS-09074: No component specified to the component argument
Cause: An 'oclumon analyze' command was issued without a component.
Action: Provide a component to the 'oclumon analyze' command. Refer to the
product documentation or to the command online help for information.
CRS-09075: Invalid component name 'string' specified as the component argument
Cause: An 'oclumon analyze' command was issued with an invalid component.
64-140 Oracle Database Error Messages
Action: Pass a valid component to the 'oclumon analyze' command. Refer to the
product documentation or to the command online help for information on
supported arguments.
CRS-09076: Error loading the required Cluster Health models
Cause: The required Cluster Health models did not exist, did not have the
required permission, or had an invalid format.
Action: Ensure that the Cluster Health models are present in the 'cdata/model'
subdirectory of the Oracle Grid Infrastructure home, and that their permissions
are correct. If the problem persists, check for entries in the oclumon log file for
more details.
CRS-09077: Invalid path 'string' was specified as the data directory argument
Cause: An 'oclumon analyze' command was issued specifying a data directory
that does not exist or is not accessible to the user.
Action: Pass a valid path to the 'oclumon analyze' command. Look at
accompanying messages for more information.
CRS-09078: Invalid severity value 'string' provided as the severity argument
Cause: An 'oclumon analyze' command was issued with an invalid severity value.
Action: Pass a valid severity value to the 'oclumon analyze' command. Refer to
the product documentation or to the command online help for information.
CRS-09079: No instance name specified for the instance argument
Cause: An 'oclumon' command was issued without an instance name.
Action: Provide an instance name with the 'oclumon' command. Refer to the
product documentation or to the command online help for information.
CRS-09080: data for other nodes of cluster cannot be viewed from this node
Cause: An 'oclumon dumpnodeview -n' command was issued for other nodes
from a leaf node.
Action: Refer to the Cluster Health Monitor documentation for more information.
CRS-09081: Internal error in Cluster Health calibration
Cause: An internal error occurred during cluster health model calibration.
Action: Contact Oracle Support Services.
CRS-09082: Insufficient permission to execute command. Require privileged user
Cause: A non-privileged user attempted to execute a command requiring
privilege.
Action: Issue the command again as a privileged user.
CRS-09083: No database name specified for the database argument
Cause: An 'oclumon' command was issued without a database name.
Action: Provide a database name with the 'oclumon' command. Refer to the
product documentation or to the command online help for information.
CRS-09084: Error string: Node name is greater than string bytes
Cause: An 'oclumon' command was issued with a node name that was too long.
Action: Supply a node name no greater than the indicated size with the 'oclumon'
command and retry. Refer to the product documentation or to the command
online help for information.
CRS-00001 to CRS-29006 64-141
CRS-09085: Model name missing or invalid for the model argument
Cause: The previous oclumon command was rejected because it did not include a
valid model name.
Action: Reissue the oclumon command providing a valid model name. Refer to
the product documentation or to the command online help for information.
CRS-09086: Server pool name missing or invalid for the server pool argument
Cause: The previous oclumon command was rejected because it did not include a
valid server pool name.
Action: Reissue the oclumon command providing a valid server pool name. Refer
to the product documentation or to the command online help for information.
CRS-09087: Server pool name specified in a cluster without user-defined server
pools
Cause: The previous oclumon command was rejected because it was issued with a
server pool name on a cluster without user-defined server pools.
Action: Reissue the oclumon command without a server pool name. Refer to the
product documentation or to the command online help for information.
CRS-09088: Node name specified in a cluster with user-defined server pools
Cause: The previous oclumon command was rejected because it was issued with a
node name on a cluster with user-defined server pools.
Action: Reissue the oclumon command without a node name. Refer to the
product documentation or to the command online help for information.
CRS-09089: Parameter 'string' is not supported in combination with parameter
'string'.
Cause: The command was rejected because the combination of parameters passed
was invalid.
Action: Refer to the product documentation or to the online help for the
command and reissue the command with the correct parameters.
CRS-09090: Error string: Parameter 'string' is specified multiple times.
Cause: The previous 'oclumon' command was rejected because the parameter
listed in the message was specified multiple times.
Action: Refer to the product documentation or to the online help for the
command and reissue the command with the correct parameters.
CRS-09091: database name 'string' is invalid
Cause: An 'oclumon' command was issued with an invalid database name.
Action: Provide a valid database name with the 'oclumon' command. Refer to the
product documentation or to the online help for the command for information.
CRS-09092: No instance of database 'string' is active on this node.
Cause: The 'oclumon calibrate' command was rejected because no instance of the
above listed database was active on the local node.
Action: Issue the 'srvctl start database' command to start the above listed
database. Issue the 'srvctl status database' command to retrieve a list of nodes on
which the database instances are online. Issue the 'oclumon calibrate' command
again from a node on which the database instance is online. Refer to the product
documentation or to the online help for the command for information.
64-142 Oracle Database Error Messages
CRS-09093: Database 'string' of type 'string' is not supported in a cluster with
user-defined server pools.
Cause: An 'oclumon' command was issued with an administrator-managed
database in a cluster with user-defined server pools.
Action: Reconfigure the database to be policy-managed using the 'srvctl modify
database' command to enable monitoring by the Oracle Cluster Health Analysis
service. Verify the monitoring status using the 'srvctl status cha' command.
Re-issue the 'oclumon calibrate' command. Refer to the product documentation or
to the online help for the command for information.
CRS-09100: Error setting Cluster Health Monitor repository size
Cause: An error occurred while setting Cluster Health Monitor repository size on
the Cluster Logger Service.
Action: Report this error to Oracle Support Services.
CRS-09101: Error updating Cluster Health Monitor repository size in configuration
file.
Cause: An error occurred while writing the Cluster Health Monitor repository
size to configuration files.
Action: Report this error to Oracle Support Services.
CRS-09102: No data for the node at the specified time
Cause: Data was not found for the specified node.
Action: This is an informational message only.
CRS-09103: No data available
Cause: Data was not available for the query.
Action: Make sure the System Monitor Service is running on the specified node.
CRS-09104: No data available for the specified nodes
Cause: Data was not available for specified nodes.
Action: Make sure the System Monitor Service is running on the specified nodes.
CRS-09105: Internal Error on master
Cause: An internal error on master caused this error.
Action: Report this error to Oracle Support Services.
CRS-09106: Data requested was outside Cluster Health Monitor retention time
limits.
Cause: A request for data outside Cluster Health Monitor repository limit caused
this error.
Action: Data needs to be requested in the proper Cluster Health Monitor
repository limits. Refer to the product documentation for more information.
CRS-09107: Start time greater than end time
Cause: A start time greater [or later] than end time caused an error.
Action: Make sure the start time is less than the end time for the specified range
query.
CRS-09108: Threshold out of acceptable range
Cause: A threshold was specified that is outside the allowed range.
CRS-00001 to CRS-29006 64-143
Action: Make sure threshold is within the acceptable range. Refer documentation
or online help for more information
CRS-09109: New Cluster Health Monitor repository location same as the old
location on node string
Cause: The new location specified for Cluster Health Monitor repository is same
as the old location.
Action: Provide a different location for Cluster Health Monitor repository. Refer
documentation or online help for more information.
CRS-09110: Cluster Health Monitor repository location not changed as the location
specified does not exist on node string.
Cause: The new location specified for Cluster Health Monitor repository does not
exist.
Action: Provide a different location for Cluster Health Monitor repository. Refer
documentation or online help for more information.
CRS-09111: Error updating Cluster Health Monitor repository location string in
configuration file.
Cause: An error occurred while writing the Cluster Health Monitor repository
location to configuration files.
Action: Report this error to Oracle Support Services.
CRS-09114: Cluster Health Monitor repository location change failed on one or
more nodes. Aborting location change.
Cause: An error occurred while setting Cluster Health Monitor repository
location on the Cluster Logger Service.
Action: Retry specifying a valid location.
CRS-09116: Cluster Health Monitor repository retention change failed on one or
more nodes. Aborting retention change.
Cause: An error occurred while setting Cluster Health Monitor repository size on
the Cluster Logger Service.
Action: Retry specifying a valid location.
CRS-09117: Grid Infrastructure Management Repository configuration error string
Cause: Grid Infrastructure Management Repository configuration error occurred.
Action: Take the following steps. 1) Examine the accompanying ORA-nnnnn or
CRS-nnnn error messages. If possible, correct the issue reported. 2) Issue a 'srvctl
status mgmtdb' command to determine the status of the Grid Infrastructure
Management Repository database. If it is not online, examine the database
instance alert log to determine what happened. 3) If you are unable to determine
or correct the problem, run 'diagcollection.pl' and contact Oracle Support Services.
CRS-09118: Grid Infrastructure Management Repository connection error string
Cause: Grid Infrastructure Management Repository connection error occurred.
Action: Take the following steps. 1) Examine the accompanying ORA-nnnnn or
CRS-nnnn error messages. If possible, correct the issue reported. 2) Issue a 'srvctl
status mgmtdb' command to determine the status of the Grid Infrastructure
Management Repository database. If it is not online, examine the database
instance alert log to determine what happened. 3) If you are unable to determine
or correct the problem, run 'diagcollection.pl' and contact Oracle Support Services.
64-144 Oracle Database Error Messages
CRS-09119: Warning: string option has been deprecated and will be ignored.
Cause: A deprecated option was specified on the command line. The option was
ignored.
Action: Check the documentation for the new syntax of the command.
CRS-09120: oclumon was not able to connect to the Grid Infrastructure
Management Repository because an authorization failure occurred. string
Cause: An authorization failure occurred when connecting to the Grid
Infrastructure Management Repository.
Action: Run the 'srvctl config mgmtdb' command to verify that Grid
Infrastructure Management Repository has been created successfully. If not, run
the 'mgmtca' command to reset the passwords in the wallet. If the problem
persists, run 'diagcollection.pl' and contact Oracle Support Services.
CRS-09121: oclumon was not able to connect to the Grid Infrastructure
Management Repository because no listener was available.
Cause: An attempt to connect to the Grid Infrastructure Management Repository
failed because no Grid Infrastructure Management Repository listener was
running.
Action: Use the 'srvctl status mgmtlsnr' command to confirm that Grid
Infrastructure Management Repository listener is running. If it is not, start it using
the 'srvctl start mgmtlsnr' command. If the problem persists, run 'diagcollection.pl'
and contact Oracle Support Services.
CRS-09122: oclumon was not able to retrieve the security keys from the wallet.
Cause: An attempt to retrieve the security keys from the wallet failed.
Action: Run the 'crsctl query wallet -type MGMTDB' command to verify that the
wallet exists. If the problem persists, contact Oracle Support Services.
CRS-09123: oclumon was not able to connect to the Grid Infrastructure
Management Repository because a Cluster Synchronization Services request
failed.
Cause: An attempt to connect to the Grid Infrastructure Management Repository
failed due to a Cluster Synchronization Services failure.
Action: If the problem persists, run 'diagcollection.pl' and contact Oracle Support
Services.
CRS-09124: Cluster Health Monitor repository retention change failed. Aborting
retention change. Error: string
Cause: An error occurred while setting the Cluster Health Monitor repository size
on the cluster logger service.
Action: Take the following steps. 1) Examine the accompanying ORA-nnnnn or
CRS-nnnn error messages. If possible, correct the issue reported. 2) Issue a 'srvctl
status mgmtdb' command to determine the status of the Grid Infrastructure
Management Repository database. If it is not online, examine the database
instance alert log to determine what happened. 3) If you are unable to determine
or correct the problem, run 'diagcollection.pl' and contact Oracle Support Services.
CRS-09125: Error string: string is an invalid node name.
Cause: The 'oclumon' command could not be carried out as entered because the
node name cited in the message was invalid. The cited node name was ignored
and the query executed with any remaining names.
CRS-00001 to CRS-29006 64-145
Action: Reissue the 'oclumon' command, if desired, supplying a valid name for
the node name cited in the message. Refer to the product documentation or to
command online help for information.
CRS-09500: The System Monitor Service aborted on host string. Details at string in
string.
Cause: The System Monitor Service aborted due to an internal error.
Action: If the problem persists, run 'diagcollection.pl' and contact Oracle Support
Services.
CRS-09501: The Cluster Logger Service aborted on host string. Details at string in
string.
Cause: The Cluster Logger Service aborted due to an internal error.
Action: If the problem persists, run 'diagcollection.pl' and contact Oracle Support
Services.
CRS-09502: The Cluster Health Monitor repository location string is inaccessible.
Details at string in string.
Cause: An error occurred while accessing the Cluster Health repository.
Action: Check that the Cluster Health Monitor repository 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 'oclumon manage
-repos reploc ' command to replace the Cluster Health Monitor
repository location.
CRS-09503: The System Monitor Service on this host is unable to communicate
with the Cluster Logger Service on host string, and will log the Cluster Health
Monitor data to the local repository.
Cause: Communication was lost with the Cluster Logger Service node.
Action: Verify all network connections between cluster nodes and repair any
problematic connections. If network problems are not found, execute the following
steps:
1. Run diagcollection.pl.
2. Contact Oracle Support Services.
CRS-09504: The Cluster Logger Service on host string is dropping the Cluster
Health Monitor node view. Details at string in string.
Cause: The Cluster Logger Service was unable to insert Cluster Health Monitor
node view into Cluster Health Monitor repository .
Action: Contact Oracle Support Services.
CRS-09505: The Cluster Health Monitor repository is deleted due to corruption and
the Cluster Logger Service is disabled on string. Details at string in string.
Cause: A critical error occurred while operating on Cluster Health Monitor
repository.
Action: Contact Oracle Support Services.
CRS-09506: The System Monitor Service local repository is disabled on the host
string. Details at string in string.
Cause: An internal error occurred while writing to the System Monitor Service
local repository.
Action: Contact Oracle Support Services.
64-146 Oracle Database Error Messages
CRS-09507: The maximum Cluster Health Monitor repository retention time is
reached. Deleting the oldest Cluster Health Monitor node views in age order.
Cause: The maximum time for which the oldest Cluster Health Monitor node
view will be available on Cluster Health Monitor repository was reached.
Action: If necessary, use 'oclumon manage -repos changerepossize '
command to change the retention time.
CRS-09508: The Cluster Health Monitor repository retention time cannot be
changed due to lack of disk space on node string.
Cause: The Cluster Health Monitor retention time condition could not be fulfilled
because the Cluster Health Monitor repository ran out of disk space at run time at
the repository location.
Action: Use the 'oclumon manage -repos reploc ' command to replace
the Cluster Health Monitor repository with a disk location that has at least 1GB of
available space per cluster node.
CRS-09509: The new Cluster Logger Service master is string.
Cause: A new Cluster Logger Service master node was elected.
Action: None
CRS-09510: The new Cluster Logger Service replica is string.
Cause: A new Cluster Logger Service replica node was elected.
Action: None
CRS-09511: The System Monitor Service was not able to collect disk information on
node string.
Cause: There was a problem in reading the disk-related information.
Action: Confirm that disks are properly configured and usable on the indicated
node. If no issues are found and the problem persists, run 'diagcollection.pl' and
contact Oracle Support Services.
CRS-09512: The System Monitor Service was not able to collect network interface
card information on node string.
Cause: There was a problem in reading the network interface card related
information.
Action: Confirm that network interface cards are properly configured and usable
on the indicated node. If no issues are found and the problem persists, run
'diagcollection.pl' and contact Oracle Support Services.
CRS-09513: The version of the Grid Infrastructure Management Repository [string]
is incompatible with the version of the Oracle Clusterware [string].
Cause: During startup, the Cluster Logger Service found that the version of Grid
Infrastructure Management Repository was older than that of the Oracle
Clusterware.
Action: Upgrade the Grid Infrastructure Management Repository to a version
which is at least that of the Oracle Clusterware.
CRS-09514: The Cluster Logger Service encountered an unexpected error during
inserting the data into the Grid Infrastructure Management Repository. string.
Cause: An unexpected Oracle error was returned by the Grid Infrastructure
Management Repository.
CRS-00001 to CRS-29006 64-147
Action: 1) Examine the accompanying ORA-nnnnn error messages. If possible,
correct the issue reported. 2) Issue a 'srvctl status mgmtdb' command to determine
the status of the Grid Infrastructure Management Repository database. If it is not
online, examine the database instance alert log to determine what happened. 3) If
you are unable to determine or correct the problem, contact Oracle Support
Services.
CRS-09515: The Cluster Logger Service encountered an unexpected error during
deleting the data from Grid Infrastructure Management Repository. string.
Cause: An unexpected Oracle error was returned by the Grid Infrastructure
Management Repository.
Action: 1) Examine the accompanying ORA-nnnnn error messages. If possible,
correct the issue reported. 2) Issue a 'srvctl status mgmtdb' command to determine
the status of the Grid Infrastructure Management Repository database. If it is not
online, examine the database instance alert log to determine what happened. 3) If
you are unable to determine or correct the problem, contact Oracle Support
Services.
CRS-09516: Encountered an unexpected error during querying the data from Grid
Infrastructure Management Repository. string.
Cause: An unexpected Oracle error was returned by the Grid Infrastructure
Management Repository.
Action: 1) Examine the accompanying ORA-nnnnn error messages. If possible,
correct the issue reported. 2) Issue a 'srvctl status mgmtdb' command to determine
the status of the Grid Infrastructure Management Repository database. If it is not
online, examine the database instance alert log to determine what happened. 3) If
you are unable to determine or correct the problem, contact Oracle Support
Services.
CRS-09517: An unrecoverable configuration error occurred in the Grid
Infrastructure Management Repository. Details at string in string. string
Cause: An unexpected condition happened in the Grid Infrastructure
Management Repository.
Action: 1) Examine the accompanying ORA-nnnnn error messages. If possible,
correct the issue reported. 2) Issue a 'srvctl status mgmtdb' command to determine
the status of the Grid Infrastructure Management Repository database. If it is not
online, examine the database instance alert log to determine what happened. 3) If
you are unable to determine or correct the problem, contact Oracle Support
Services.
CRS-09518: The Cluster Logger Service was not able to connect to the Grid
Infrastructure Management Repository because an authorization failure
occurred. string
Cause: An authorization failure occurred when connecting to the Grid
Infrastructure Management Repository.
Action: Run the 'srvctl config mgmtdb' command to verify that Grid
Infrastructure Management Repository has been created successfully. If not, run
the 'mgmtca' command to reset the passwords in the wallet. If the problem
persists, run 'diagcollection.pl' and contact Oracle Support Services.
CRS-09519: The Cluster Logger Service was not able to connect to the Grid
Infrastructure Management Repository because no listener was available.
64-148 Oracle Database Error Messages
Cause: An attempt to connect to the Grid Infrastructure Management Repository
failed because no Grid Infrastructure Management Repository listener was
running.
Action: Use the 'srvctl status mgmtlsnr' command to confirm that Grid
Infrastructure Management Repository listener is running. If it is not, start it using
the 'srvctl start mgmtlsnr' command. If the problem persists, run 'diagcollection.pl'
and contact Oracle Support Services.
CRS-09520: The storage of Grid Infrastructure Management Repository is number%
full. The storage location is 'string'.
Cause: The storage of Grid Infrastructure Management Repository was close to
full. This storage can be a shared file system or an Oracle ASM disk group.
Action: Make sure there is sufficient free space in repository location.
CRS-09521: Grid Infrastructure Management Repository was not available on the
node string. The System Monitor Service will store the data in its local
repository on all nodes. string
Cause: Grid Infrastructure Management Repository was initializing or was
shutting down when the Cluster Logger Service tried to connect, insert or delete
the data.
Action: Check if the Grid Infrastructure Management Repository is online using
the 'srvctl status mgmtdb' command. If it is offline, start it using the 'srvctl start
mgmtdb' command.
CRS-09522: The Cluster Logger Service was not able to retrieve the security keys
from the wallet.
Cause: The Cluster Logger Service could not get the security keys due a wallet
read failure.
Action: Run the 'crsctl query wallet -type MGMTDB' command to verify that the
wallet exists. If the problem persists, contact Oracle Support Services.
CRS-09523: The Cluster Logger Service was not able to connect to the Grid
Infrastructure Management Repository because a Cluster Synchronization
Services request failed.
Cause: An attempt to connect to the Grid Infrastructure Management Repository
failed due to a Cluster Synchronization Services failure.
Action: If the problem persists, run 'diagcollection.pl' and contact Oracle Support
Services.
CRS-09524: The System Monitor Service on this host is unable to communicate
with the Cluster Logger Service on host string, and will log the Cluster Health
Analysis data to the local repository.
Cause: Communication was lost with the Cluster Logger Service node.
Action: Verify all network connections between cluster nodes and repair any
problematic connections. If network problems are not found, execute the following
steps:
1. Run diagcollection.pl.
2. Contact Oracle Support Services.
CRS-09525: The Cluster Health Analysis local repository is disabled on host string.
Details at string in string.
CRS-00001 to CRS-29006 64-149
Cause: An internal error occurred while writing to the Cluster Health Analysis
local repository.
Action: Contact Oracle Support Services.
CRS-09526: The Cluster Logger Service was unable to reset the password for
Cluster Health Monitor.
Cause: A password reset failure occurred when the Cluster Logger Service tried to
reset the Cluster Health Monitor password after finding that the password had
expired.
Action: Run the 'srvctl config mgmtdb' command to verify that Grid
Infrastructure Management Repository has been created successfully. If not, run
the 'mgmtca setpasswd -user CHM' command to reset the password for Cluster
Health Monitor. If the problem persists, run 'diagcollection.pl' and contact Oracle
Support Services.
CRS-09527: The Cluster Logger Service was unable to reset the password for
Cluster Health Analysis.
Cause: A password reset failure occurred when the Cluster Logger Service tried to
reset the Cluster Health Analysis password after finding that the password had
expired.
Action: Run the 'srvctl config mgmtdb' command to verify that Grid
Infrastructure Management Repository has been created successfully. If not, run
the 'mgmtca setpasswd -user CHA' command to reset the password for Cluster
Health Analysis. If the problem persists, run 'diagcollection.pl' and contact Oracle
Support Services.
CRS-09600: Failed to initialize string daemon
Cause: An error occurred during initialization.
Action: Report this error to Oracle Support Services.
CRS-09603: Failed to read configuration files
Cause: An error encountered while retrieving information from configuration
files.
Action: Report this error to Oracle Support Services.
CRS-09607: Cannot spawn thread for string
Cause: An error encountered while spawning thread.
Action: Report this error to Oracle Support Services.
CRS-09608: ASM disk method failed
Cause: An error encountered with ASM disks configuration.
Action: Report this error to Oracle Support Services.
CRS-09609: Encountered cssd failure. Reinitializing CSSD layer.
Cause: An error was encountered with CSSD layer while retrieving information.
Action: Report this error to Oracle Support Services.
CRS-09610: Encountered a fatal internal error. Daemon string exiting.
Cause: A fatal error occurred with CSSD layer.
Action: Report this error to Oracle Support Services.
CRS-09611: Mark string disks encountered errors
64-150 Oracle Database Error Messages
Cause: An error occurred while accessing disk.
Action: Report this error to Oracle Support Services.
CRS-09612: Mark string disks failed
Cause: A fatal error occurred while accessing disk.
Action: Report this error to Oracle Support Services.
CRS-09615: Disk method Failure : string
Cause: Internal error occurred.
Action: Report this error to Oracle Support Services.
CRS-09616: Daemon started : string
Cause: A daemon process started successfully.
Action: None
CRS-09617: Invalid message type encountered
Cause: An invalid or corrupted message was received.
Action: Report this error to Oracle Support Services.
CRS-09618: Daemon stopped : string
Cause: A daemon process stopped successfully.
Action: None
CRS-10002: failed to allocate memory
Cause: Memory allocation failed.
Action: Correct the system memory problem and retry.
CRS-10004: unable to reach string address from local node
Cause: An attempt to reach the IP address specified failed.
Action: Make sure that the specified IP address is a valid IP address and is
assigned to an interface. Make sure that there are no firewalls between local node
and node on which specified IP address is hosted.
CRS-10005: unable to determine local hostname
Cause: The hostname could not be determined.
Action: Check that the hostname for the local machine is valid. Look at the
accompanying messages. If the problem persists, contact Oracle Support Services.
CRS-10006: APPVIP type needs a VIP name. Specify a VIP name using -vip
commandline option.
Cause: VIP resource name was missing in the command line for APPVIP type.
Action: Specify a VIP name using -vip option.
CRS-10008: unable to generate client ID for VIP type string, cluster name string,
VIP resource name string
Cause: An attempt to generate client ID for specified cluster name, VIP type and
resource name failed.
Action: Make sure that cluster name and VIP resource name do not exceed 252
characters. Make sure that VIP type is a valid VIP type. Refer to 'crsctl get clientid
-help' for more information.
CRS-00001 to CRS-29006 64-151
CRS-10010: unable to discover DHCP server in the network listening on port
number for client ID string
Cause: An attempt to discover DHCP server listening on port specified failed.
Action: Make sure that DHCP servers exist on the network and are listening on
port specified. If they are listening on a different port then specify that port using
the -port option. For more information refer to help for 'crsctl discover dhcp'
command.
CRS-10011: unable to request DHCP lease for client ID string on port number
Cause: An attempt to request DHCP lease for the specified client ID on specified
port failed.
Action: Make sure that there are DHCP servers with IP addresses available on the
network. If other DHCP servers are available which are listening on a different
port specify an alternative port using the -port option. For more information refer
to help for 'crsctl request dhcp' command.
CRS-10013: unable to release DHCP lease for client ID string, on port number
Cause: An attempt to release DHCP lease for the specified client ID on specified
port failed.
Action: Make sure that there are DHCP servers listening on port specified. If the
DHCP server is listening on a different port specify an alternative port using -port
option. For more information refer to help for 'crsctl release dhcp' command.
CRS-10014: HOSTVIP type needs a node name. Specify a node name using -n
option.
Cause: Node name was missing in the command line for HOSTVIP type.
Action: For HOSTVIP type node name needs to be specified via -n option.
CRS-10015: VIP type string is invalid
Cause: An invalid VIP type was specified for DHCP client ID generation.
Action: Make sure that VIP type is a valid VIP type. Refer to 'crsctl get clientid
-help' for more information.
CRS-10016: error obtaining local host DNS resolver configuration
Cause: An attempt to obtain local host DNS configuration failed.
Action: Make sure that the user executing the command has sufficient permission
to read local system configuration.
CRS-10017: the number name servers configured on this system exceeds the number
maximum allowed
Cause: An attempt to obtain local host DNS configuration failed because more
name servers were found then allowed on this operating system.
Action: Reduce the number of name servers configured to the maximum allowed.
CRS-10023: Domain name look up for name string failed. Operating system error:
string
Cause: An attempt to query DNS servers for name specified failed.
Action: Look at accompanying messages for more information on the failure.
CRS-10029: could not verify if port number at address string is in use
Cause: An attempt to verify if port at address specified is in use failed.
64-152 Oracle Database Error Messages
Action: Make sure that the user has permission to create socket at port specified.
For ports < 1024 user should be root. Also look at the accompanying messages for
more information.
CRS-10030: could not verify if port number on local node is in use
Cause: An attempt to verify if port specified on local node is in use failed.
Action: Make sure that the user has permission to create socket at port specified.
For ports < 1024 the user should be root. Also look at the accompanying messages
for more information.
CRS-10033: could not stop the DNS listening daemon running on port number at
address string
Cause: An attempt to stop the DNS listening daemon running on port and
address specified failed.
Action: Make sure that the user has permission to send packets at the port
specified. For ports < 1024 the user should be root. Also look at the accompanying
messages for more information.
CRS-10034: could not stop the DNS listening daemon running on port number on
local node
Cause: An attempt to stop the DNS listening daemon on local node running on
port specified failed.
Action: Make sure that the user has permission to send packets at the port
specified. For ports < 1024 the user should be root. Also look at the accompanying
messages for more information.
CRS-10035: invalid name server 'string' specified in command line
Cause: An invalid IPv4 address was specified on the command line for -dnsserver
option.
Action: Specify a valid IPv4 address on the command line.
CRS-10036: value for command line parameter 'string' is not an integer
Cause: An invalid value was specified for the specified command line parameter.
Action: Re-submit the request with an integer value.
CRS-10038: invalid IP address 'string' specified
Cause: An invalid IPv4 or IPv6 address was supplied on command line.
Action: Supply an IP address that conforms to IETF RFC-791 or IETF RFC-2373.
CRS-10039: invalid subnet 'string' specified
Cause: An invalid IPv4 or IPv6 subnet was supplied to crsctl.
Action: Supply a subnet address that conforms to IETF RFC-950 or IETF
RFC-5942.
CRS-10040: unable to get list of network interfaces
Cause: An attempt to get the list of network interfaces failed.
Action: Look at the accompanying messages for more information.
CRS-10041: subnet 'string' is not configured on the node
Cause: The subnet specified did not match subnet of any network interface on this
node.
CRS-00001 to CRS-29006 64-153
Action: Specify a subnet that matches at least one network interface's subnet on
this node.
CRS-10043: DNS daemon is not listening on port number at address string
Cause: An attempt to check if the DNS daemon is listening on port and address
specified failed.
Action: Make sure that the address specified is reachable. Make sure that there is
no firewall between the node on which this command was run and the address
specified. Also look at the accompanying messages for more information.
CRS-10044: invalid cluster name 'string' specified
Cause: An invalid cluster name was supplied to the CRSCTL utility.
Action: Specify a cluster name which is at least one character but no more than 15
characters in length. The cluster name must be alphanumeric, it cannot begin with
a numeric character, and it may contain hyphen (-) characters. However, it cannot
end with a hyphen (-) character.
CRS-10045: invalid node name 'string' specified
Cause: An invalid node name was supplied to the CRSCTL utility.
Action: Specify a node name which is at least one character but no more than 63
characters in length. The node name must be alphanumeric, it cannot begin with a
numeric character, and it may contain hyphen (-) characters. However, it cannot
end with a hyphen (-) character.
CRS-10046: invalid client ID 'string' specified
Cause: An invalid client ID was supplied to the CRSCTL utility.
Action: The client ID can be obtained by running the command 'crsctl get clientid
dhcp'.
CRS-10051: CVU found following errors with Clusterware setup : string
Cause: A resource-specific error was detected by the Clusterware Verification
Utility (CVU). This message is accompanied by others providing details of the
error condition.
Action: Respond based on the accompanying messages.
CRS-10100: Execution of crswrapexece.pl script with arguments 'string' fails.
Cause: crswrapexece.pl script failed when executed with the specific arguments.
Action: Check system log and crswrapexece.log for more details. Contact Oracle
Support Services.
CRS-10101: Internal Error
Cause: Execution of crswrapexece.pl script failed due to missing argument.
Action: Contact Oracle Support Services.
CRS-10102: Failure to open environment file string.
Cause: The crswrapexece.pl script failed to open the environment file, which
might be caused by hostname change or user edits.
Action: Check for the existence and permission of the environment file.
CRS-10103: Found string syntax errors in environment file string.
Cause: crswrapexece.pl found syntax errors in the provided environment file.
64-154 Oracle Database Error Messages
Action: Check and fix syntax error in the indicated environment file. If the
problem persists, contact Oracle Support Services.
CRS-10131: Failure to create named pipe string. Details [string].
Cause: The specified named pipe could not be created. Oracle High Availability
Service would not be able to restart if crashes.
Action: Check for the existence and permission of the parent directory, where the
named pipe was created.
CRS-10132: Oracle High Availability Service was restarted at least string times
within the last string seconds. Stop auto-restarting Oracle High Availability
Service.
Cause: Oracle High Availability Service was restarted too rapidly within a short
period of time.
Action: Check the Oracle High Availability Service log file to determine the cause.
If the problem persists, contact Oracle Support Services.
CRS-10201: Internal error
Cause: An unexpected condition was detected in the cluster event module.
Action: Contact Oracle Support Services.
CRS-10202: Failed to allocate process memory
Cause: Insufficient system memory resources.
Action: Correct the system memory resources problem and retry. If this does not
appear to be caused by an operating system issue, contact Oracle Support Services.
CRS-10203: Could not connect to the Event Manager daemon
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-10250: Database name is required to access database wallets. Use -name option
to supply a database name.
Cause: The option -name was missing on the command line.
Action: For APPQOSDB wallet types -name is a mandatory parameter. Retry the
command with -name option.
CRS-10251: User name is required to create OSUSER wallets. Use -user option to
supply a username.
Cause: The option -user was missing on the command line.
Action: For OSUSER wallet types -user is a mandatory parameter. Retry the
command with -user option.
CRS-10301: Unable to contact Oracle high availability service on peer nodes for
cluster wide commands. Details at string in string.
Cause: Multicast Domain Name Server (mDNS) or Grid Plug and Play (GPnP) or
both daemons on the local node were not running.
Action: If you are shutting down the Clusterware stack, this is expected. If you
had issued a cluster wide command, reissue the command after the stack has been
restarted. If you are not shutting down the stack, the missing component(s) may
have failed and may restart automatically. Any cluster wide commands can be
retried after a few seconds. However, the failure should be investigated and
reported to Oracle Support Services.
CRS-00001 to CRS-29006 64-155
CRS-10302: Oracle high availability service on peer nodes is reachable. Details at
string in string.
Cause: Oracle high availability service on peer nodes was reachable.
Action: None
CRS-10401: Internal error in credentials processing.
Cause: An unexpected condition was detected in the credentials module.
Action: Contact Oracle Support Services.
CRS-10402: Failed to allocate process memory.
Cause: There were insufficient system memory resources.
Action: Correct the system memory resources problem and retry. If this does not
appear to be caused by an operating system issue, contact Oracle Support Services.
CRS-10403: Could not connect to credential storage: string.
Cause: An attempt to communicate with Oracle Cluster Registry (OCR) or Oracle
Local Registry (OLR) credential storage failed.
Action: Run the 'crsctl check crs' command to determine whether Cluster Ready
Services or Oracle High Availability Services are online.
CRS-10405: Credential domain already exists.
Cause: The provided credential domain already existed.
Action: Specify another credential domain path.
CRS-10406: Authorization error.
Cause: The user did not have permissions to view or modify the provided
credential information.
Action: Use a different user to view or modify the credential information.
CRS-10407: Credential domain does not exist.
Cause: The provided credential domain did not exist.
Action: Specify another credential domain path or create the credential domain.
CRS-10408: Credential set already exists.
Cause: The provided credential set already existed.
Action: Specify another credential domain path to which the credential set will be
added.
CRS-10409: Credential target already exists.
Cause: The provided credential target already existed.
Action: Specify another credential target name, or modify the value of the existing
one.
CRS-10410: Credential set member does not exist.
Cause: The provided credential set member did not exist.
Action: Specify another credential set member or create a new member.
CRS-10411: Credential set does not exist.
Cause: The provided credential set did not exist.
Action: Specify another credential set or create a new member.
CRS-10412: Security layer returned failure: string.
64-156 Oracle Database Error Messages
Cause: Credential operation failed due to error from security layer.
Action: Depending on the reason, this operation may be retried after correcting
the situation.
CRS-10413: Invalid argument specified for attribute.
Cause: An invalid argument was found for a given attribute.
Action: Rerun the command using correct value.
CRS-10414: User name or group name does not match the owner or group of the
credential object.
Cause: Credential permissions for the owner could not be modified because the
user name did not match the owner of the credential.
Action: Specify the owner's user ID in the argument to change owner's
permission.
CRS-10415: ACL string is missing the user or group modifier.
Cause: The access control list (ACL) string did not specify whether user's or
group's permission needs to be changed.
Action: Specify the correct format in the argument and rerun the command.
CRS-10416: Credentials target does not exist.
Cause: The provided credentials target did not exist.
Action: Specify another credentials target.
CRS-10417: The directory 'string' does not exist.
Cause: The specified directory did not exist.
Action: Provide a directory for which the user has read and write permissions.
CRS-10418: The directory 'string' is not accessible.
Cause: An attempt to access the specified directory failed.
Action: Ensure that the user has read and write permissions on the directory.
CRS-10419: Unable to open file 'string' for read access.
Cause: An attempt to open the specified file for read access failed.
Action: Ensure that the user has read access permission on the file.
CRS-10420: Unable to open file 'string' for write access.
Cause: An attempt to open the specified file for write access failed.
Action: Ensure that the user has write access permission on the file.
CRS-10421: Section name does not exist.
Cause: The credentials could not be imported because the provided section name
did not exist in the XML file.
Action: Verify the sections included in the credentials file and retry the import
supplying the correct section name.
CRS-29000: Oracle VM Manager job failed with the following error: string
Cause: The Oracle Virtual Machine (Oracle VM) Manager was unable to complete
the action due to the indicated error.
Action: Consult Oracle Virtual Machine (Oracle VM) documentation if the
problem persists.
CRS-00001 to CRS-29006 64-157
CRS-29001: could not find Grid Infrastructure virtual machine 'string'
Cause: The name specified for the Grid Infrastructure virtual machine was not
found.
Action: Specify a known virtual machine, or create a new virtual machine with
the specified name and add it to the Oracle Clusterware cluster.
CRS-29002: could not find a virtual machine with the ID 'string'
Cause: The ID specified for the virtual machine was not found.
Action: Specify a known virtual machine, or create a new virtual machine with
the specified ID.
CRS-29003: could not find a virtual machine with the name or ID 'string'
Cause: Either the name or the ID provided for the virtual machine was not found.
Action: Specify a known virtual machine, or create a new virtual machine with
the specified name or ID.
CRS-29004: not authorized to perform the Oracle VM Manager operation
Cause: The Oracle Virtual Machine (Oracle VM) user name and password
combination did not work, or the user did not have permission to perform the
action requested.
Action: Update the user's password using the 'srvctl modify ovmm' command, or
specify a different user who has the correct permissions.
CRS-29005: could not connect to the Oracle VM Manager on host string at port
string
Cause: A connection to the Oracle Virtual Machine (Oracle VM) Manager could
not be established or timed out.
Action: Start the Oracle VM Manager on the appropriate host and port, or specify
a different host or port using the 'srvctl modify ovmm' command.
CRS-29006: could not find Oracle VM Manager credentials
Cause: Authentication credentials were not found for the Oracle Virtual Machine
(Oracle VM) Manager.
Action: Create or modify the credentials by using the 'srvctl {add | modify}
ovmm' command.
64-158 Oracle Database Error Messages
65
EVM-00001 to EVM-00901 65-1
EVM-00001 to EVM-00901 5 6
EVM-00001: Cannot write raw events to a terminal
Cause: Attempted to redirect binary events to a terminal.
Action: Use evmshow to format events for display.
EVM-00002: Use evmshow to format events for display
Cause: Attempted to redirect binary events to a terminal.
Action: Use evmshow instead.
EVM-00003: Failed to open file "string": string
Cause: Filename, path or the permisions were not valid.
Action: Use a valid path and filename, check permissions. Otherwise contact
Oracle Customer Support.
EVM-00004: Failed to open channel config file "string"
Cause: Configuration file name,the path or the permissions were not valid.
Action: Use a vaild path and filename, check permissions. Otherwise contact
Oracle Customer Support.
EVM-00006: Failed to create temporary file
Cause: The file being used as a temporary file for evmsort had one of the
following issues; filename, path or the permisions were not valid.
Action: Use a valid path and filename, check permissions. Otherwise contact
Oracle Customer Support.
EVM-00007: Failed to write to temporary file
Cause: The file being used as a temporary file for evmsort had one of the
following issues; filename, path or the permisions were not valid.
Action: Use a valid path and filename, check permissions. Otherwise contact
Oracle Customer Support.
EVM-00008: Failed to read from temporary file
Cause: The file being used as a temporary file for evmsort had one of the
following issues; filename, path or the permisions were not valid.
Action: Use a valid path and filename, check permissions. Otherwise contact
Oracle Customer Support.
EVM-00009: Failed to create EVM posting connection
Cause: Error occured while communicating with the EVM daemon.
Action: Check log and status of the EVM daemon.
65-2 Oracle Database Error Messages
EVM-00010: Failed to read from EVM posting connection
Cause: Error occured while communicating with the EVM daemon.
Action: Check log and status of the EVM daemon.
EVM-00011: Failed to write to EVM posting connection
Cause: Error occured while communicating with the EVM daemon.
Action: Check log and status of the EVM daemon.
EVM-00012: Failed to create EVM listening connection
Cause: Error occured while communicating with the EVM daemon.
Action: Check log and status of the EVM daemon.
EVM-00013: Failed to read from EVM listening connection
Cause: Error occured while communicating with the EVM daemon.
Action: Check log and status of the EVM daemon.
EVM-00014: Failed to write to EVM listening connection
Cause: Error occured while communicating with the EVM daemon.
Action: Check log and status of the EVM daemon.
EVM-00015: Failed to create EVM service connection
Cause: Error occured while communicating with the EVM daemon.
Action: Check log and status of the EVM daemon.
EVM-00016: Failed to read from EVM service connection
Cause: Error occured while communicating with the EVM daemon.
Action: Check log and status of the EVM daemon.
EVM-00017: Failed to start EVM service "string"
Cause: EVM daemon failed to start.
Action: Check log for the EVM daemon.
EVM-00018: Failed to write to output stream
Cause: Failed to write to standard output.
Action: Contact Oracle Customer Support.
EVM-00019: Failed to read event from input stream
Cause: Bad input file for evmshow/evmsort EOF missing.
Action: Check the input file.
EVM-00020: Failed to create event subscription
Cause: Bad network connection between subscriber and EVM daemon.
Action: Check the network connection and filter string.
EVM-00021: Failed to create filter
Cause: Used a null filter string or memory allocation failed.
Action: Use a non null filter string.
EVM-00022: Invalid filter string
Cause: Used a null or invalid filter string.
Action: Contact Oracle Customer Support.
EVM-00001 to EVM-00901 65-3
EVM-00023: Filter test operation failed
Cause: Used a null or invalid filter string.
Action: Use a non null filter string. Otherwise contact Oracle Customer Support.
EVM-00024: Lost connection to EVM daemon
Cause: Evmlogger lost connection to evmdaemon.
Action: Check status of evmlogger,evmd daemons and logs.
EVM-00025: Authorization database error
Cause: Not authorized to post/listen for certain events.
Action: Check evm.auth file to ensure the current user is authorized to post/listen
for specific events.
EVM-00026: Failed to post event "string"
Cause: Evmpost failed to post an event.
Action: Check the status and log for EVM daemon.
EVM-00027: Memory allocation failure
Cause: The system is running low on memory.
Action: Check the availability of memory in the system.
EVM-00029: Event contains invalid values
Cause: Invalid syntax for an event was used.
Action: Use a valid syntax for an event.
EVM-00030: Event name is missing
Cause: Name of the event was missing.
Action: Use a valid syntax for an event.
EVM-00031: Event name has too few components
Cause: Invalid syntax for an event was used.
Action: Use a valid syntax for an event.
EVM-00032: Failed to write event
Cause: Failed to write event to output file.
Action: Check the permissions of the file. Otherwise contact Oracle Customer
Support.
EVM-00033: Error in input file "string", line number
Cause: Failed to parse input file.
Action: Check input file and the line for possible errors. Otherwise contact Oracle
Customer Support.
EVM-00034: Error: string
Cause: Error Occured.
Action: Look at the error message for details.
EVM-00035: EVM service "string" terminated with exit code number
Cause: EVM daemon died.
Action: Check the EVM daemon log.
65-4 Oracle Database Error Messages
EVM-00036: Host "string" is unknown
Cause: Invalid hostname discovered while trying to create a connection to the
EVM daemon.
Action: Check the hostname, on which EVM daemon is running. Otherwise
contact Oracle Customer Support.
EVM-00037: Failed to connect to EVM daemon on "string"
Cause: EVM daemon is dead or is not responding.
Action: Check the status of EVM daemon and logs.
EVM-00038: Failed to create an EVM event
Cause: Failed to create an EVM event.
Action: Check the EVM daemon log.
EVM-00039: Invalid port number in host name "string"
Cause: Used an invalid port number.
Action: Use a valid or a different port number.
EVM-00040: Error occurred while reading from "string"
Cause: Error occured when evmshow was reading from an input file.
Action: Check the input file.
EVM-00042: Use "string -A" to format events, or pipe output to evmshow
Cause: Invalid use of evmshow command.
Action: Use evmshow command as instructed.
EVM-00043: Attempting to reconnect to the EVM daemon...
Cause: Evmwatch trying to reconnect to the evm daemon.
Action: Not an error message.
EVM-00044: Attempting to reconnect to the EVM daemon on "string"...
Cause: Evmwatch trying to reconnect to the evm daemon on this host.
Action: Not an error message.
EVM-00045: EVM connection re-established
Cause: Evmwatch was able to reconnect to the evm daemon.
Action: Not an error message.
EVM-00104: End of file reached unexpectedly
Cause: End of event template file reached unexpectedly.
Action: Check the event template file in evm/admin.
EVM-00105: Missing end-of-group character
Cause: end-of-group character missing in event template file.
Action: Check the event template file in evm/admin.
EVM-00106: Missing end-of-string character
Cause: end-of-string character missing in event template file.
Action: Check the event template file in evm/admin.
EVM-00107: Value "string" is not valid
EVM-00001 to EVM-00901 65-5
Cause: Invalid value found in the event template file.
Action: Check the event template file in evm/admin.
EVM-00108: Keyword "string" is not valid
Cause: Invalid keyword found in the event template file.
Action: Check the event template file in evm/admin.
EVM-00201: Failed to allocate space for application object
Cause: The system is running low on memory.
Action: Check the availability of memory in the system.
EVM-00202: Failed to allocate space for local lock pathname
Cause: The system is running low on memory.
Action: Check the availability of memory in the system.
EVM-00301: Failed to open logger config file "string"
Cause: Configuration file had one of the following problems; filename, path or
permissions were not valid.
Action: Check whether path and permissions are valid. Otherwise contact Oracle
Customer Support.
EVM-00302: Configuration error - using default configuration
Cause: Configuration file had invalid configuration details
Action: Check the configuration file.
EVM-00303: Keyword "string" is invalid in this position
Cause: Valid Keyword was used in an invalid position in configuration file.
Action: Use the correct syntax.
EVM-00304: Configuration error in file string, line number
Cause: Configuration error in configuration file.
Action: Check the configuration file.
EVM-00305: Memory allocation failure for "string"
Cause: The system is running low on memory.
Action: Check the availability of memory in the system.
EVM-00306: Failed to create filter for "string"
Cause: Failed to create a filter for events for evmlogger.
Action: Check the availability of memory.
EVM-00307: Filter string invalid for "string"
Cause: Used a null filter string or memory allocation failed.
Action: Use a non null filter string.
EVM-00308: Failed to open eventlog "string": string
Cause: Eventlog file had one of the following problems; filename, path or
permissions were not valid.
Action: Check whether path and permissions are valid. Otherwise contact Oracle
Customer Support.
65-6 Oracle Database Error Messages
EVM-00309: Failed to write to eventlog "string"
Cause: Eventlog had one of the following problems; size or permissions were not
valid.
Action: Check the permissions and the size of the eventlog file. Otherwise contact
Oracle Customer Support.
EVM-00310: Invalid suppression filter for eventlog "string"
Cause: Invalid filter was used.
Action: Use a non null filter. Otherwise contact Oracle Customer Support.
EVM-00311: Invalid entry in eventlog "string" (number events OK)
Cause: Evmlogger found an invalid entry in eventlog.
Action: Check the eventlog file.
EVM-00312: Eventlog "string" disabled
Cause: Events could not be written to the eventlog file.
Action: Check the permissions,max size of the logfile.
EVM-00313: Eventlog "string" re-enabled
Cause: Events logging is reenabled.
Action: Not an error message.
EVM-00314: Forwarder "string" disabled
Cause: Forwarding is disabled by the evmlogger.
Action: Not an error message.
EVM-00315: Forwarder "string" re-enabled
Cause: Forwarding is disabled by the evmlogger.
Action: Not an error message.
EVM-00316: Suppression disabled for "string"
Cause: Error message filtering supression disabled for this string.
Action: Not an error message.
EVM-00317: Suppression re-enabled for "string"
Cause: Error message filtering supression reenabled for this string.
Action: Not an error message.
EVM-00318: Failed to open config info file "string"
Cause: Configuration file had one of the following problems; filename, path or
permissions were not valid.
Action: Check whether path and permissions are valid. Otherwise contact Oracle
Customer Support.
EVM-00319: Keyword "string" is not allowed in a secondary config file
Cause: Invalid Keyword was used.
Action: Use a valid Keyword.
EVM-00323: Config file "string" has insecure write permission
Cause: The configuration file had write permissions for the group 'other'.
Action: Change the write permissions for the configuration file
EVM-00001 to EVM-00901 65-7
EVM-00324: Config file "string" has incorrect ownership
Cause: Configuration file should be owned by root or bin.
Action: Change the owner of configuration file to root or bin.
EVM-00325: Config file "string" is not a regular file
Cause: Configuration file is not a regular file.
Action: Check the configuration file.
EVM-00401: Failed to open binary event library file
Cause: Binary event file had one of the following problems; filename, path or
permissions were not valid.
Action: Check whether path and permissions are valid. Otherwise contact Oracle
Customer Support.
EVM-00601: Data read from the input stream is not a valid EVM event
Cause: evmshow tried to read an invalid EVM event.
Action: Check the logs for the evm daemon.
EVM-00701: Check that the event is registered and you are authorized to post it
Cause: Not authorized to post for certain events.
Action: Check evm.auth file to ensure the current user is authorized to post the
specific event.
EVM-00702: Priority must be an integer in the range 0-number
Cause: Used an integer out of the range for priority.
Action: Use a valid integer.
EVM-00801: Missed number subscribed-to event(s)
Cause: Missed some events during the connection setup phase.
Action: Not an error message.
EVM-00802: Failed to reconnect within number seconds - terminating
Cause: Failed to establish a connection with EVM daemon.
Action: Check the logs for EVM daemon.
EVM-00901: Invalid sort specification "string"
Cause: Invalid sort specification used for evmsort.
Action: Use a valid sort specification. Look at documentation for evmsort using
evmsort -h.
65-8 Oracle Database Error Messages
66
GIPC-00000 to GIPC-00020 66-1
GIPC-00000 to GIPC-00020 6 6
GIPC-00000: general success.
Cause: The operation succeeded.
Action: No action is required.
GIPC-00001: general failure.
Cause: A GIPC operation failed.
Action: Examine the trace and log files for the specific cause.
GIPC-00002: GIPC needs to be initialized.
Cause: The application failed to initialize GIPC prior to performing an operation.
Action: Initialize GIPC.
GIPC-00014: buffer not large enough to hold data.
Cause: The buffer provided by the application was not big enough to hold the
data received.
Action: Use a larger buffer.
GIPC-00016: timeout waiting on request.
Cause: A wait call returned because the time expired.
Action: This error happens normally in most cases. If this error was not expected,
examine the trace and log files for the reason.
GIPC-00017: waiting call has been posted.
Cause: A wait was interrupted by another thread posting it.
Action: This error happens normally in most cases. If this error was not expected,
examine the trace and log files for the reason.
GIPC-00020: bind address already in use.
Cause: The application attempt to bind an endpoint to an address which has
already been bound.
Action: Specify another address.
66-2 Oracle Database Error Messages
67
RDE-00000 to RDE-08001 67-1
RDE-00000 to RDE-08001 7 6
RDE-00000: no error
Cause: Operation was successful.
Action: No action needed.
RDE-00001: unspecified error
Cause: An unknown error occurred. This is an internal error.
Action: Contact Oracle Support Services and provide details about how and when
the error occurred.
RDE-00002: provider busy
Cause: The provider is processing a request.
Action: This is not an error.
RDE-00003: no value found for service tag string.
Cause: A value was not found for the given service tag.
Action: This is normally not an error.
RDE-00004: operation timeout
Cause: A FIND or REGISTER operation timed out.
Action: For a FIND operation, this is only an error if the find was expected to
successfully locate a service.
RDE-00005: invalid universe: "string"
Cause: An unknown universe was specified for the address.
Action: Specify a valid universe.
RDE-00006: invalid protocol: "string"
Cause: An invalid protocol was specified in an address.
Action: Specify a valid protocol.
RDE-00009: data too large for buffer. Buffer length: number. Required: number.
Cause: This error is internal and normally is not seen by users.
Action: Contact Oracle Support Services.
RDE-00010: not found
Cause: A value was not found in a list.
Action: This error should not be visible to the user. If it occurs, contact Oracle
Support Services.
67-2 Oracle Database Error Messages
RDE-00011: invalid type: number
Cause: The type given for a piece of data was invalid.
Action: This error should not be visible to the user. If it occurs, contact Oracle
Support Services.
RDE-00012: no list name specified.
Cause: A name was not given for a list.
Action: This error should not be visible to the user. If it occurs, contact Oracle
Support Services.
RDE-00013: name busy.
Cause: This is an internal error.
Action: This error should not be visible to the user. If it occurs, contact Oracle
Support Services.
RDE-00014: operation was interrupted.
Cause: An operation was interrupted.
Action: None. This normally is not an error.
RDE-00015: load of provider library failed.
Cause: The load of a library which implements the interface for a provider failed.
Action: Enable tracing to determine the exact error that occurred.
RDE-00016: no provider libraries found.
Cause: It was not possible to locate any provider libraries.
Action: Make sure that the provider libraries have been installed.
RDE-00017: provider error.
Cause: A provider generated an error.
Action: If errors follow, examine them to determine the exact error. Otherwise,
enable tracing to determine the exact error.
RDE-00018: regular expression compilation failed. Pattern "string" Error: number.
Cause: The creation of a pattern for use in a comparison failed.
Action: This error should not be visible to the user. If it occurs, contact Oracle
Support Services.
RDE-00019: pattern match failed. String: "string" Pattern: "string" Error: number.
Cause: A comparison against a regular expression failed.
Action: This error should not be visible to the user. If it occurs, contact Oracle
Support Services.
RDE-00020: no host name or IP address
Cause: An address must contain either the name of the server or its IP address.
Action: Specify a host name or an IP address in the address.
RDE-00021: no providers found for universe "string".
Cause: A provider was not found for the specified universe.
Action: Either specify a different universe or obtain a provider library for that
universe. Examine the errors that follow (if any) for more information.
RDE-00022: property not found.
RDE-00000 to RDE-08001 67-3
Cause: A provider property was not found.
Action: This error should not be visible to the user. If it occurs, contact Oracle
Support Services.
RDE-00023: provider not found. Universe "string".
Cause: A provider was not found for the specified universe.
Action: Either specify a different universe or obtain a provider library for that
universe.
RDE-00024: address invalid
Cause: The address is not in the correct format.
Action: Specify an address in the correct format. The syntax is described in rd.h.
RDE-00025: service type not specified.
Cause: The service type is not specified in the address.
Action: Specify an address with the service type.
RDE-00026: expected delimiter not found. Expected: "string" Found: "string"
Cause: The delimiter expected in the address was not found.
Action: Correct the address so that the delimiter is present.
RDE-00027: port number not found.
Cause: When a colon (":") follows the host name, it must be followed by a port
number.
Action: Specify a port number.
RDE-00028: initialization failed.
Cause: Initialization of RD failed.
Action: Examine the errors that follow this one to determine the problem that is
causing the error.
RDE-00029: no server found.
Cause: No server for the specified provider could be found to perform the desired
operation.
Action: Start a server for the desired provider or use a different provider.
RDE-00030: memory allocation failure.
Cause: An operation failed because it was not possible to allocate enough process
memory.
Action: If memory is low on the system, terminate other processes, or threads, or
both, and try the operation again. Otherwise, this is an internal error and Oracle
Support Services should be contacted.
RDE-00031: invalid domain: number.
Cause: The application specified an invalid number for the domain.
Action: Specify a correct domain. See rd.h for the allowed values.
RDE-00032: length of service type "string" (number) is greater than than the
maximum allowed: number
Cause: The user specified a service type which is longer than that permitted by
the provider.
Action: Use a shorter service type.
67-4 Oracle Database Error Messages
RDE-00033: no universe specified.
Cause: The user did not specify a universe in the address.
Action: Specify a universe.
RDE-00034: address not registered: "string"
Cause: The application attempted to use an address which does not exist.
Action: Specify a registered address.
RDE-00037: invalid service instance tag: number
Cause: The value for a service instance tag was incorrect.
Action: Specify a valid tag. They are listed in rd.h.
RDE-00038: invalid protocol type: "string" Valid protocols: string
Cause: The user specified a protocol which is not supported by the provider.
Action: Specify a valid protocol. The protocol must be at least one character which
is not a period (".").
RDE-00039: invalid host name: "string"
Cause: The name of the host specified was not in the correct format.
Action: Use the correct host name format. The host name must be one of the
following:
1. The name of the machine;
2. A valid IPv4 address (N.N.N.N);
3. A valid IPv6 address (N[:N]*).
RDE-00040: invalid search domain: "string"
Cause: The name of the domain searched by the service was not in the correct
format.
Action: Use the correct domain name format. A domain is a series of one or more
alphanumeric characters.
RDE-00041: no protocol or domain specified.
Cause: The service name was followed by a period separator, but no protocol or
domain was found after it.
Action: Specify a valid protocol, or domain, or both.
RDE-00042: invalid port number: "string"
Cause: The port specified in the service address was not valid. A port number
may only be a positive decimal number.
Action: Specifiy a valid port number.
RDE-00043: no search domain specified.
Cause: No search domain followed the period separator.
Action: Specify a valid search domain.
RDE-00044: no protocol specified.
Cause: No protocol was specified for the service.
Action: Specify a valid protocol.
RDE-00045: port number required to register with a generic address.
RDE-00000 to RDE-08001 67-5
Cause: Because of the requirements of some providers, the port number must be
specified when registering using a generic address.
Action: Specify a port number.
RDE-00046: invalid attribute
Cause: An attribute was specified using an incorrect format.
Action: An attribute should be specified using the following format:
"name=value[, name1=value1 ...]"
RDE-00047: no name specified for attribute.
Cause: A value was given for an attribute but no name was specified.
Action: Specify a name for the attribute.
RDE-00048: no attribute specified.
Cause: An attribute was not found in the address where it was expected.
Action: Specify a valid attribute. An attribute is composed of a name followed by
an equals sign ("=") and then by an optional value. The name and value may both
contain spaces.
RDE-00049: expected separator not found. Expected: "string" Found: "string"
Cause: The separator expected to be present between the mandatory and optional
sections of the address was not found.
Action: Specify the separator.
RDE-00050: provider initialization for universe "string" failed.
Cause: The operation failed because providers could not be initialized for the
specified universe.
Action: The message(s) that follow describe the errors encountered by the
providers.
RDE-00051: provider "string" error.
Cause: The specified provider failed to perform an operation.
Action: The message(s) that follow describe the errors encountered by the
provider.
RDE-00052: invalid numeric value specified: "string".
Cause: The value specified as a number was not valid.
Action: Specify a valid number.
RDE-00053: invalid or null service instance.
Cause: The service instance used for an operation is either invalid or null.
Action: Specify a valid service instance.
RDE-00054: invalid operation: number.
Cause: The operation specified was not valid.
Action: Specify a valid operation.
RDE-00055: no providers available.
Cause: No providers were available for an operation. This may be caused by the
failure of a process or service needed by the provider (e.g. the mDNS service).
Action: Examine the trace and log files for details. Ensure that the process or
service required by the process is running.
67-6 Oracle Database Error Messages
RDE-00056: registration of service instance "string" failed.
Cause: The registration of the specified service instance failed.
Action: Examine the errors that follow for more information about the error.
RDE-00057: unregistration of service instance "string" failed.
Cause: The deletion of the registration of the specified service instance failed.
Action: Examine the errors that follow for more information about the error.
RDE-00058: confirmation of service instance "string" failed.
Cause: The confirmation of the specified service instance failed.
Action: Examine the errors that follow for more information about the error.
RDE-00059: location of service types "string" failed.
Cause: It was not possible to retrieve types of services supported by Resource
Discovery.
Action: Examine the errors that follow for more information about the error.
RDE-00060: service instance "string" was not found.
Cause: The location of the specified service.
Action: Examine the errors that follow for more information about the error.
RDE-00061: retrieval of details about service instance "string" failed.
Cause: It was not possible to get details about the specified service instance.
Action: Examine the errors that follow for more information about the error.
RDE-00062: termination failed.
Cause: The call to terminate the use of Resource Discovery failed.
Action: Examine the errors that follow for more information about the error.
RDE-00063: operation failed.
Cause: A FIND or REGISTER operation failed.
Action: Examine the errors that follow for more information about the error.
RDE-00064: retrieval of a provider for universe "string" failed.
Cause: It was not possible to retrieve a provider descriptor for the specified
universe.
Action: Examine the errors that follow for more information about the error.
RDE-00065: creation of service instance failed.
Cause: An error occurred while trying to assemble a service instance using
components.
Action: Examine the errors that follow for more information about the error.
RDE-00066: parsing of service instance "string" failed.
Cause: An error occurred while trying to parse the specified address.
Action: Examine the errors that follow for more information about the error.
RDE-00067: location of domain failed.
Cause: An error occurred while trying to locate domains of the specified type.
Action: Examine the errors that follow for more information about the error.
RDE-00000 to RDE-08001 67-7
RDE-00068: length of universe component "string" (number) is longer than the
maximum: number.
Cause: The string specified for the universe-specific portion of the service instance
is longer than the maximum allowed by the provider.
Action: Specify a universe component which is shorter than the maximum. If this
error occurs when no universe-specific portion was specified, the provider may
have used the service type for the universe-specific component. In that case, make
sure that the length of the service type does not exceed the maximum.
RDE-00069: property "string" is read-only.
Cause: An error occurred while trying to set a property value. Property had
read-only access and could not be altered.
Action: Specify a property name with read/write access.
RDE-01999: internal error
Cause: RD failed due to some unforeseen reason.
Action: This error should not be visible to the user. If it occurs, contact Oracle
Support Services.
RDE-02000: invalid service type: "string"
Cause: The user specified a service type which does not conform to the standard
specifed by RFC's 1034 and RFC 1123. The service type must be one or more
characters and must start and end with a letter or digit. The interior characters
may be letters, digits, or hyphens.
Action: Specify a service type which conforms to the RFC.
RDE-02001: failed to connect to the mDNS responder.
Cause: The provider was unable to make a connection with the multicast /
Domain Name Server (mDNS) responder.
Action: Check to ensure that the responder is running. If it is, this is an internal
error and Oracle Support Services should be contacted.
RDE-04000: client waiting
Cause: The client uses this error to signal to the server that it is waiting for query
results.
Action: This error is used for signaling between the client and the DNS server. It
should not be visible to the user. If it occurs, contact Oracle Support Services
RDE-04001: no error
Cause: Operation was successful.
Action: No action needed.
RDE-04002: unknown error has occurred
Cause: An unknown error has occurred.
Action: This error should not be visible to the user. If it occurs, contact Oracle
Support Services.
RDE-04003: no such name
Cause: A record could not be found with the given name.
Action: This error should not be visible to the user. If it occurs, contact Oracle
Support Services.
67-8 Oracle Database Error Messages
RDE-04004: memory allocation failed
Cause: An operation failed because it was not possible to allocate enough process
memory.
Action: If memory is low on the system, terminate other processes, or threads, or
both, and try the operation again. Otherwise, this is an internal error and Oracle
Support Services should be contacted.
RDE-04005: invalid parameter
Cause: A record contained an illegal or nonexisting value.
Action: This error should not be visible to the user. If it occurs, contact Oracle
Support Services.
RDE-04006: invalid reference
Cause: An unknown DNS record was found.
Action: This error should not be visible to the user. If it occurs, contact Oracle
Support Services.
RDE-04007: invalid state
Cause: This is an internal error.
Action: This error should not be visible to the user. If it occurs, contact Oracle
Support Services.
RDE-04008: invalid flags
Cause: This is an internal error.
Action: This error should not be visible to the user. If it occurs, contact Oracle
Support Services.
RDE-04009: unsupported operation
Cause: The provider interface attempted to perform an operation which is not
supported by the provider.
Action: This error should not be visible to the user. If it occurs, contact Oracle
Support Services.
RDE-04010: not initialized
Cause: This is an internal error.
Action: This error should not be visible to the user. If it occurs, contact Oracle
Support Services.
RDE-04011: no cache allocated
Cause: A Domain Name Server (DNS) query failed because no cache was
allocated.
Action: This error should not be visible to the user. If it occurs, contact Oracle
Support Services.
RDE-04012: service already registered
Cause: The user attempted to register a service that was already registered.
Action: A service should only be registered once.
RDE-04013: service name conflict
Cause: The user attempted to register a service whose name already exists.
Action: A service should only be registered once.
RDE-00000 to RDE-08001 67-9
RDE-04014: invalid record entry
Cause: The provider interface attempted to perform an operation whose record
contained invalid or nonexistent data.
Action: This error should not be visible to the user. If it occurs, contact Oracle
Support Services.
RDE-04015: client software incompatible with server
Cause: The version of the client software used by the provider interface is not
compatible with the version of the server software.
Action: This error should not be visible to the user. If it occurs, contact Oracle
Support Services.
RDE-04016: invalid interface
Cause: The provider interface attempted to use an unknown interface.
Action: This error should not be visible to the user. If it occurs, contact Oracle
Support Services.
RDE-04017: cache size must be increased
Cause: The size of the cache maintained by the provider interface was insufficient
and should be increased.
Action: This error is used as a status indicator. It should not be visible to the user.
If it occurs, contact Oracle Support Services.
RDE-04018: configuration changed
Cause: The server configuration changed during an operation.
Action: This error should not be visible to the user. If it occurs, contact Oracle
Support Services.
RDE-04019: client should free resources
Cause: This error is used as an internal status indicator and should not be visible
outside of the provider.
Action: This error should not be visible to the user. If it occurs, contact Oracle
Support Services.
RDE-06000: no more data
Cause: This error is used internally to signal that there is no more data to be
passed by the SLP provider.
Action: This error is normal - no action is required.
RDE-06001: no error
Cause: Operation was successful.
Action: This error is normal - no action is required.
RDE-06002: language not supported
Cause: No service could be found that supports the language required.
Action: A service will have to be added or modified which supports the requested
language.
RDE-06003: parse error
Cause: The SLP message rejected by a remote SLP agent.
Action: This error should not be visible to the user. If it occurs, contact Oracle
Support Services.
67-10 Oracle Database Error Messages
RDE-06004: invalid registration
Cause: The SLP provider attempted to register a URL which is malformed.
Action: This error should not be visible to the user. If it occurs, contact Oracle
Support Services.
RDE-06005: scope not supported
Cause: This is an internal error.
Action: This error should not be visible to the user. If it occurs, contact Oracle
Support Services.
RDE-06006: authenticator not provided
Cause: The SLP provider failed to authenticate itself.
Action: This error should not be visible to the user. If it occurs, contact Oracle
Support Services.
RDE-06007: authentication failed
Cause: The SLP provider failed to authenticate itself.
Action: This error should not be visible to the user. If it occurs, contact Oracle
Support Services.
RDE-06008: invalid update
Cause: An update for a nonexisting registration was issued, or the update
includes a service type or scope different than that in the initial registration.
Action: This error should not be visible to the user. If it occurs, contact Oracle
Support Services.
RDE-06009: refresh rejected
Cause: Attempts were made to refresh a registration more frequently than the
minimum refresh interval.
Action: This error should not be visible to the user. If it occurs, contact Oracle
Support Services.
RDE-06010: feature unimplemented
Cause: An unimplemented feature was used.
Action: This error should not be visible to the user. If it occurs, contact Oracle
Support Services.
RDE-06011: buffer overflow
Cause: An outgoing request overflowed the maximum network MTU size.
Action: This error should not be visible to the user. If it occurs, contact Oracle
Support Services.
RDE-06012: network timed out
Cause: An reply to an SLP request did not arrive in the configured timeout
interval.
Action: Check the network connection and retry the request.
RDE-06013: network initialization failure
Cause: The network failed to initialize properly.
Action: Check the network connection and retry the request.
RDE-06014: memory allocation failed
RDE-00000 to RDE-08001 67-11
Cause: The SLP provider was unable to allocate enough process memory.
Action: If memory is low on the system, terminate other processes, or threads, or
both, and try the operation again. Otherwise, this is an internal error and Oracle
Support Services should be contacted.
RDE-06015: invalid parameter
Cause: The provider attempted to pass an invalid parameter.
Action: This error should not be visible to the user. If it occurs, contact Oracle
Support Services.
RDE-06016: network error
Cause: The network failed to initialize properly.
Action: Check the network connection and retry the request.
RDE-06017: internal system error
Cause: The SLP subsystem failed for unknown reasons.
Action: This error should not be visible to the user. If it occurs, contact Oracle
Support Services.
RDE-06018: handle in use
Cause: The SLP provider attempted to recursively use a handle.
Action: This error should not be visible to the user. If it occurs, contact Oracle
Support Services.
RDE-06019: generic error
Cause: The provider failed for unknown reasons.
Action: This error should not be visible to the user. If it occurs, contact Oracle
Support Services.
RDE-06020: unicast query must be sent.
Cause: The provider must send a unicast query.
Action: This error should not be visible to the user. If it occurs, contact Oracle
Support Services.
RDE-08000: invalid service type: "string".
Cause: This is an internal error.
Action: Contact Oracle Support Services.
RDE-08001: failed to connect to the GNS server.
Cause: A connection with the Grid Naming Service (GNS) server failed.
Action: Check to ensure that the Oracle Grid Naming Service Daemon (GNSD)
resource is online. If it is, this is an internal error and Oracle Support Services
should be contacted.
67-12 Oracle Database Error Messages
68
PRKU-01001 to PRKU-01060 68-1
PRKU-01001 to PRKU-01060 8 6
PRKU-01001: Unexpected argument {0}.
Cause: The command line argument reported in above error message is not
expected the by tool
Action: Refer to the tool's inline help display or to the product documentation of
the command line tool for valid options and arguments, and then rerun the tool.
PRKU-01002: The option {0} is required.
Cause: The command line option reported by the above error message is a
mandatory option required by the tool
Action: Review the tool's inline help display or to the product documentation of
the command line tool for type of value required for this option. And then rerun
the command specifying the above option in command line options.
PRKU-01003: The parameter {0} requires an argument.
Cause: The command line parameter reported in error message needs a value.
Action: Review the tool's inline help display or to the product documentation of
the command line tool for type of value required for this option. And then rerun
the command specifying the above option in command line options.
PRKU-01015: Oracle Clusterware is not properly stopped and de-configured on
node "{0}". The files "{1}" exist as configured.
Cause: The files init.ohasd, or ocr.loc and/or directory scls_scr still exists on this
node which makes the tool believe that the clusterware stack is not shutdown
properly
Action: Run the Oracle clusterware deconfiguration utility to completely cleanup
the configuration. The Clusterware deconfiguration tool is available in Oracle
clusterware home and also on Oracle OTN (Technology Network) page.
PRKU-01016: Failed to stop Oracle Clusterware on nodes "{0}". Run the command
"{1}" after fixing the problem.
Cause: The clusterware deconfiguration tool has failed to stop Oracle clusterware
stack. The reason for failure can be found browsing through clusterware alert logs
found in log//alert.log directory under Oracle
clusterware.
Action: You should browse through deamon logs in log/ under
Oracle clustereware home and manually correct the problem to stop clusterware
stack. And then rerun the command specified in above error message.
PRKU-01018: Run the following command as the root user on node "{0}".
68-2 Oracle Database Error Messages
Cause: The clusterware deconfiguration that is run as non-root user cannot
automatically run the command specified in above message.
Action: You should login to another session as a privileged user and run the
command specified in above message
PRKU-01019: Run the following command as administrator.
Cause: The clusterware deconfiguration which is run as non-root user cannot
automatically run the command specified in above message.
Action: You should login to another session as a privileged user and run the
command specified in above message
PRKU-01021: As the privileged user, Execute "{0}" on every node in this cluster
except for this node, and then execute "{1}" on this node to remove the
configuration of the Oracle Clusterware and to completely remove the Oracle
software
Cause: This is the message reported by Oracle clusterware deconfiguration tool
when it is run in non-interactive (or silent) mode.
Action: Execute the identified scripts as described. Deconfiguring Oracle
Clusterware in silent mode requires one set of operations on all nodes but the last
followed by a special set of operations on the last node.
PRKU-01023: Oracle Clusterware is not stopped and de-configured on node "{0}"
due to error "{1}"
Cause: The tool failed to deconfigure Oracle clusterware stack on the node
because of errors reported in the above message
Action: You should review the error messages reported in above message to
perform corrective actions and then rerun the tool
PRKU-01024: The stopping and de-configuring of Oracle Clusterware failed on
some nodes. Fix the problem and rerun this tool to completely remove the
Oracle Clusterware configuration and the software
Cause: This is a message reported by the tool to inform you that the Oracle
clusterware deconfiguration did not happen on some of the nodes in the cluster.
Action: You should review the error messages reported by the tool for failing to
deconfigure clusterware stack on each node, perform corrective actions after
reviewing the error messages, and rerun the tool to completely deconfigure Oracle
clusterware stack
PRKU-01025: You must delete or downgrade Clusterware-managed Oracle
databases and de-install Clusterware-managed Oracle homes before attempting
to remove the Oracle Clusterware home.
Cause: An attempt was made to deconfigure the Oracle Clusterware when one or
more Clusterware-managed Oracle databases still exist.
Action: Run the Oracle Clusterware deconfiguration tool from
Clusterware-managed Oracle homes to delete, deconfigure or downgrade Oracle
database and then run the same tool from Oracle Clusterware home to
deconfigure Clusterware.
PRKU-01029: The node "{0}" is currently not responding.
Cause: The host reported in the above message may have rebooted or hung
Action: Login to the host if possible and review system logs, correct the problem
PRKU-01001 to PRKU-01060 68-3
PRKU-01035: The stopping and de-configuring of Oracle Restart failed. Fix the
problem and rerun this tool to completely remove the Oracle Restart
configuration and the software
Cause: The Oracle Restart stack couldn't be stopped cleanly before
de-configuring.
Action: Review the error messages reported by the tool for failing to deconfigure
Oracle Restart stack, perform corrective actions after reviewing the error messages,
and rerun the tool to completely deconfigure Oracle Restart stack.
PRKU-01036: The deinstall tool failed to create the script file "{0}" that needs to be
run in silent mode due to error "{1}"
Cause: The tool failed to create silent mode script file because of errors reported in
the above message.
Action: You should review the error messages reported in above message to
perform corrective actions and then rerun the tool.
PRKU-01037: As the privileged user, execute "{0}" on this node to remove the
configuration of the Oracle Restart and to completely remove the Oracle
software
Cause: This is the message reported by Oracle Restart deconfiguration tool when
it is run in non-interactive (or silent) mode.
Action: Execute the identified scripts as described.
PRKU-01039: Can't deconfigure Oracle Restart before removing or downgrading
managed Oracle databases.
Cause: A request to deconfigure Oracle Restart found one or more managed
Oracle database homes, so the request was rejected.
Action: Run the Oracle deconfiguration tool from Oracle database homes to
delete, deconfigure or downgrade Oracle database and then run the same tool
from Oracle Restart home to deconfigure the Oracle Restart stack.
PRKU-01057: The home being deconfigured is NOT a configured Grid
Infrastructure home ({0})
Cause: The home that was deconfigured has a different path from the configured
Infrastructure home.
Action: If it is required to deconfigure the active CRS home, specify the
configured CRS home in the deinstall command argument, or run deinstall from
the configured CRS home.
PRKU-01059: Root script execution failed on nodes {0}
Cause: Root script execution failed on one or more nodes.
Action: Examine the accompanying output messages from the root script and
correct the issue reported, if possible. Otherwise, contact Oracle Support Services.
PRKU-01060: Deleting the last node of a cluster using 'deinstall -local' is not
allowed. Rerun deinstall without the '-local' flag.
Cause: The '-local' flag was specified with the 'deinstall' command on the last
node.
Action: Rerun deinstall without the '-local' flag.
68-4 Oracle Database Error Messages
69
PRKH-01014 to PRKH-03450 69-1
PRKH-01014 to PRKH-03450 9 6
PRKH-01014: Current user "{0}" is not the oracle owner user "{1}" of oracle home
"{2}"
Cause: The command was run as a different user than the owner user of the
oracle home path.
Action: Retry the command as the user who owns the specified oracle home.
PRKH-01016: Failed to get CSS mode
Cause: An error occurred on a Cluster Synchronization Services request. This
message may be accompanied by others identifying the specific problem.
Action: Correct the problem indicated by the accompanying messages, if possible.
Otherwise. contact Oracle Support Services.
PRKH-01050: Buffer is too small
Cause: An internal error occurred.
Action: Contact Oracle Support Services.
PRKH-01051: Cluster software (skgxn) error
Cause: An error occurred when Cluster Synchronization Services attempted to
use non-Oracle vendor clusterware. This message may be accompanied by others
identifying the specific problem.
Action: Correct the problem indicated by the accompanying messages, if possible.
Otherwise, contact Oracle Support Services.
PRKH-01052: Invalid arguments
Cause: An internal error occurred.
Action: Contact Oracle Support Services.
PRKH-01053: Cluster synchronization services are not active
Cause: CSS daemon is not running or unable to authenticate with CSS daemon
Action: Use 'crsctl check css' to ensure that CSS daemon is running. If CSS
daemon is not running, execute 'crsctl start crs' command.
PRKH-01054: Communications error
Cause: CSS daemon is not running on the local node or unable to authenticate
with CSS daemon
Action: Use 'crsctl check css' to ensure that CSS daemon is running. If CSS
daemon is not running, execute 'crsctl start crs' command.
PRKH-01055: Oracle Cluster Registry error
69-2 Oracle Database Error Messages
Cause: OCR returned an error while processing a CSS request
Action: Ensure that CRSD daemon is running e.g. with crsctl check clusterware
PRKH-01056: Unexpected CSS error
Cause: An internal error occurred.
Action: Contact Oracle Support Services.
PRKH-01057: Check for node with node number 0 failed.
Cause: CSS daemon is not running on local node or unable to authenticate with
CSS daemon.
Action: Use 'crsctl check css' to ensure that CSS daemon is running. If CSS
daemon is not running, execute 'crsctl start crs' command.
PRKH-01058: Node number specified for the node name lookup is beyond the
allowed node number range
Cause: An internal error occurred.
Action: Contact Oracle Support Services.
PRKH-01059: Failed to get ASM mode
Cause: An error occurred on an Oracle Clusterware request. This message may be
accompanied by others identifying the specific problem.
Action: Correct the problem indicated by the accompanying messages, if possible.
Otherwise, contact Oracle Support Services.
PRKH-03002: Vendor cluster software error occurred in Cluster Synchronization
Services
Cause: An error occurred when Cluster Synchronization Services attempted to
use non-Oracle vendor clusterware. This message may be accompanied by others
identifying the specific problem.
Action: Correct the problem indicated by the accompanying messages, if possible.
Otherwise, contact Oracle Support Services.
PRKH-03003: An attempt to communicate with the CSS daemon failed
Cause: CSS daemon is not running.
Action: Ensure that CSS daemon is running.
PRKH-03004: Failed due to insufficient memory for Cluster Synchronization
Services
Cause: An internal error occurred.
Action: Contact Oracle Support Services.
PRKH-03005: Entity {0} was not registered with CSS
Cause: The given entity (e.g. instance) was not registered with CSS.
Action: Start the entity before retrying the operation.
PRKH-03009: An attempt was made by Cluster Synchronization Services to release
a lock that was not held
Cause: An internal error occurred.
Action: Contact Oracle Support Services.
PRKH-03011: Cluster Synchronization Services was started but has not completed
startup
PRKH-01014 to PRKH-03450 69-3
Cause: An attempt to connect to CSS failed because initialization is still in
progress.
Action: None
PRKH-03013: An improper buffer argument was supplied to Cluster
Synchronization Services
Cause: This is an internal error.
Action: Contact Oracle Support Services.
PRKH-03016: Invalid arguments
Cause: An internal error occurred.
Action: Contact Oracle Support Services.
PRKH-03050: Unexpected error ({0}) returned from Cluster Synchronization
Services
Cause: An internal error occurred.
Action: Contact Oracle Support Services.
PRKH-03101: GIPC Error returned from DHCP module
Cause: A communication error occurred on a DHCP operation. This message may
be accompanied by others identifying the specific problem.
Action: Correct the problem indicated by the accompanying messages, if possible.
Otherwise, contact Oracle Support Services.
PRKH-03150: Unexpected error ({0}) returned from DHCP module
Cause: An internal error occurred.
Action: Contact Oracle Support Services.
PRKH-03202: An error occurred in Oracle Clusterware during an Operating System
function call or request
Cause: An error occurred in Oracle Clusterware. This message may be
accompanied by others identifying the specific problem.
Action: Correct the problem indicated by the accompanying messages, if possible.
Otherwise, contact Oracle Support Services.
PRKH-03203: Required password not supplied
Cause: A requested operation requires a password but none was supplied. This
message may be accompanied by others identifying the specific problem.
Action: Correct the problem indicated by the accompanying messages, if possible.
Otherwise, contact Oracle Support Services.
PRKH-03204: An improper buffer argument was supplied to Oracle Clusterware
Cause: An internal error occurred.
Action: Contact Oracle Support Services.
PRKH-03205: Internal error in Oracle Clusterware
Cause: An internal error occurred.
Action: Contact Oracle Support Services.
PRKH-03250: Unexpected error ({0}) returned from Oracle Clusterware
Cause: An internal error occurred.
Action: Contact Oracle Support Services.
69-4 Oracle Database Error Messages
PRKH-03301: Invalid arguments
Cause: An internal error occurred.
Action: Contact Oracle Support Services.
PRKH-03302: Oracle Clusterware database support layer returned OCR error
Cause: This message may be accompanied by others identifying the specific
problem.
Action: Correct the problem indicated by the accompanying messages, if possible.
Otherwise, contact Oracle Support Services.
PRKH-03303: Oracle Clusterware database support layer returned OSD error
Cause: This message may be accompanied by others identifying the specific
problem.
Action: Correct the problem indicated by the accompanying messages, if possible.
Otherwise, contact Oracle Support Services.
PRKH-03304: Internal error returned from Oracle Clusterware database support
layer
Cause: An internal error occurred.
Action: Contact Oracle Support Services.
PRKH-03306: Internal error returned from Oracle Clusterware database support
layer
Cause: An internal error occurred.
Action: Contact Oracle Support Services.
PRKH-03307: Internal error returned from Oracle Clusterware database support
layer
Cause: An internal error occurred.
Action: Contact Oracle Support Services.
PRKH-03340: Following VIP error occurred from Oracle Clusterware database
support layer
Cause: An error occurred while processing a VIP request. This message may be
accompanied by others identifying the specific problem.
Action: Correct the problem indicated by the accompanying messages, if possible.
Otherwise, contact Oracle Support Services.
PRKH-03350: Unexpected error returned from Oracle Clusterware database support
layer
Cause: An internal error occurred.
Action: Contact Oracle Support Services.
PRKH-03401: An improper buffer argument was supplied to an internal interface
Cause: An internal error occurred.
Action: Contact Oracle Support Services.
PRKH-03402: OCR error returned from an internal interface
Cause: An internal interface encountered an error in OCR processing. This
message may be accompanied by others identifying the specific problem.
Action: Correct the problem indicated by the accompanying messages, if possible.
Otherwise, contact Oracle Support Services.
PRKH-01014 to PRKH-03450 69-5
PRKH-03450: Unexpected error ({0}) returned from an internal interface
Cause: An internal error occurred.
Action: Contact Oracle Support Services.
69-6 Oracle Database Error Messages
70
PRKA-02001 to PRKA-02005 70-1
PRKA-02001 to PRKA-02005 0 7
PRKA-02001: GSD already exists
Cause: An attempt was made to create the Global Services Daemon (GSD)
application while there was a running GSD application.
Action: Stop and remove the GSD and create the GSD application again using
'srvctl add nodeapps'.
PRKA-02002: Listener already exists
Cause: An attempt was made to create a Listener application while there was a
running Listener application.
Action: Stop and remove the running Listener and create the Listener application
again using 'srvctl add nodeapps'.
PRKA-02003: EM Agent already exists
Cause: An attempt was made to create an Agent application while there was a
running Agent application.
Action: Stop the running Agent and create the Agent application again using
'srvctl add nodeapps'.
PRKA-02005: Netmasks are different for starting and ending IP addresses
Cause: An invalid range of VIP addresses was specified for the cluster
Action: Check if the starting and ending addresses in the VIP range belong to the
same netmask.
70-2 Oracle Database Error Messages
71
PRKC-01000 to PRKC-01177 71-1
PRKC-01000 to PRKC-01177 1 7
PRKC-01000: No active nodes detected in the cluster
Cause: The active node list of the cluster could not be retrieved. This could occur
if the operating system dependent clusterware was not functioning properly in
one or more nodes in the cluster, or because there was no clusterware installed on
the system.
Action: Check the state of the cluster by running 'lsnodes' binary from your
ORACLE_HOME/bin and see if it prints the node list correctly.
PRKC-01001: Error submitting commands in the buffer
Cause: This is an internal error.
Action: Contact Oracle Support Services.
PRKC-01002: Not all the submitted commands completed successfully.
Cause: Some of the submitted commands failed to complete on the nodes
specified either because the node in question failed or because communication
between the nodes was disrupted.
Action: Check that all the specified nodes are up and running or check the details
of the failures on the given nodes.
PRKC-01004: Problem in copying file to nodes
Cause: Attempted file copy operation(s) from the local node to one or more nodes
in the cluster and one or multiple of those copy file operations failed. Possible
causes: 1) One or more file copy operations to nodes in the cluster failed. 2) The
destination directory did not have write permission for the user on one or more of
the nodes .the source file did not exist. 3) The 'rcp' command to one or more nodes
failed on UNIX platforms.
Action: 1) Check that the source file exists. 2) Check that all nodes in the cluster
are up. 3) Check that destination directory has write permission for the user. 4) On
UNIX based platforms check that user can do 'rcp' to all the nodes.
PRKC-01005: Problem in removing file from nodes
Cause: Attempted file remove operation(s) from the local node to one or more
nodes in the cluster and one or multiple of those file remove operations failed.
Possible causes: 1) One or more nodes failed during the operation. 2) The
destination directory did not have write permission for the user on one or more of
the nodes. 3) The source file did not exist. 4) The 'rcp' command to one or more
nodes failed on UNIX platforms.
Action: Check the accompanying error messages for details.
PRKC-01006: Problem in moving file to nodes
71-2 Oracle Database Error Messages
Cause: Attempted file move operation(s) from the local node to one or more
nodes in the cluster and one or multiple of those move file operations failed.
Possible causes: 1) One or more nodes failed during the operation. 2) The
destination directory did not have write permission for the user on one or more of
the nodes. 3) The source file did not exist. 4) The 'rcp' command to one or more
nodes failed on UNIX platforms.
Action: Check the accompanying error messages for details.
PRKC-01007: Problem in creating directories on the nodes
Cause: Attempted directory create operation(s) from the local node to one or more
nodes in the cluster and one or multiple of those directory create operations failed.
Possible causes: 1) One or more nodes failed during the operation. 2) The
destination directory did not have write permission for the user on one or more of
the nodes. 3) The 'rcp' command to one or more nodes failed on UNIX platforms.
Action: Check the accompanying error messages for details.
PRKC-01009: Failed to start the service on all nodes
Cause: The service failed to start on one or more nodes of the cluster.
Action: Check if all the nodes in cluster are up and look in the clusterware alert
log.
PRKC-01010: Failed to stop the service on all nodes
Cause: The service failed to stop on one or more nodes of the cluster.
Action: Check if all the nodes in cluster are up and service is still up on failed
nodes. Look in the clusterware alert log.
PRKC-01011: Failed to delete the service from all nodes
Cause: The service failed to be deleted on one or more nodes of the cluster.
Action: Check if all the nodes in cluster are up and service is still registered. Look
in the clusterware alert log.
PRKC-01012: Failed to create the service on all nodes
Cause: The service failed to be created on one or more nodes of the cluster.
Action: Check if all the nodes in cluster are up. Look in the clusterware alert log.
PRKC-01016: Failed to retrieve value of the environment variable "{0}", {1}
Cause: A required environment variable was not defined.
Action: Define the environment variable.
PRKC-01017: Problem restarting GSD
Cause: GSD (Global Services Daemon) could not be started on the local node. This
could occur if the operating system dependent clusterware was not functioning
properly or there is already a running GSD.
Action: Check the state of your clusterware by running 'lsnodes' from ORACLE_
HOME/bin. It should list the nodes in the cluster. Try 'gsdctl stop' and then 'gsdctl
start' again.
PRKC-01018: Error getting coordinator node
Cause: This could occur if the operating system dependent clusterware was not
functioning properly.
Action: Use 'gsdctl stop' on each node to stop the GSDs. Use 'gsdctl start' on each
node in the cluster.
PRKC-01000 to PRKC-01177 71-3
PRKC-01019: Error creating handle to GSD daemon on the node {0}
Cause: Global Services Daemon was not running on the node.
Action: Use 'gsdctl stat' to check the status of the daemon. Use 'gsdctl start' to
start it.
PRKC-01020: Exception while executing the operation on the remote node {0}
Cause: Attempted to execute an operation on the remote node when the Global
Services Daemon was not up on the remote node {0}.
Action: Start the Global Services Daemon on the remote node using 'gsdctl start'.
PRKC-01021: Problem in the clusterware
Cause: The operating system dependent clusterware could not be contacted. This
could occur because the operating system dependent clusterware was not
functioning properly.
Action: Check the state of the operating system dependent clusterware.
PRKC-01022: Could not get node name for node {0} in {1}
Cause: The operating system dependent clusterware could not be contacted. This
could occur because the operating system dependent clusterware was not
functioning properly.
Action: Check the state of the operating system dependent clusterware using
'lsnodes -n'.
PRKC-01023: Invalid IP address format: {0}
Cause: The provided IP address was neither an IPv4 nor an IPv6 valid address.
Action: Make sure that the IP address is a valid IPv4 or IPv6 address.
PRKC-01025: Failed to create a file under the filepath {0} because the filepath is not
executable or writable
Cause: The directory of the specified filepath did not have execute or write
permission. So the temporary file could not be created to test whether the filepath
was shared among nodes.
Action: Make the directory of the specified filepath executable and writable.
PRKC-01141: Oracle Restart is not supported in version {0}. It is supported from
version {1} onwards
Cause: This is an internal error.
Action: Contact Oracle Support Services.
PRKC-01144: File "{0}" not found.
Cause: The file was not found in the file system.
Action: Make sure that the file exists in the file system.
PRKC-01148: Failed to get host name for the local computer
Cause: An error occurred while attempting to retrieve the TCP/IP host name
Action: Correct the problem indicated by the accompanying error messages.
PRKC-01149: Failed to get OCR locations
Cause: An error occurred while attempting to retrieve the OCR locations, possibly
due to missing or incorrrect OCR locations file, or incomplete OCR configuration,
or due to missing or incorrect SRVM shared libraries.
71-4 Oracle Database Error Messages
Action: Verify that the Clusterware has been correctly installed and configured.
Verify that the ocr.loc file is present and readable in the appropriate location for
your platform.
PRKC-01150: Failed to get drive letters used on following nodes: "{0}"
Cause: An error occurred while attempting to retrieve used drive letters on one or
more nodes.
Action: Look at the accompanying messages and fix the error(s). The messages
typically relate to a node not being reachable, or the remote execution service not
running on the node, or some permissions issue when attempting to use the
remote execution service on the remote node.
PRKC-01151: The given path "{0}" does not exist
Cause: The specified path may not have been created or an incorrect path has
been specified.
Action: Make sure that the given path exists by specifying a correct existing path.
PRKC-01152: The specified path "{0}" is not a directory
Cause: The specified path may be a file, not a directory, or an incorrect path may
have been specified.
Action: Make sure to specify a path that is a valid directory path.
PRKC-01153: No directory is available on the remote node "{0}" to copy the binary
RemoteExecService.exe
Cause: Either the path defined by value of registry key HKEY_LOCAL_
MACHINE/System/CurrentControlSet/Services/OracleRemExecService is not
available on the remote node, or the c:/temp/ directory is not available or not
accessible on the specified remote node.
Action: Make sure that the required path is available on the remote node.
PRKC-01155: The node list provided had only one entry or had multiple entries that
were duplicates of a single nodename entry
Cause: The list of nodes provided for the shared path check was either only one
node, or the list included entries that were duplicates of the same single node.
Action: Please provide the correct nodelist for the cluster on which the check is
being called, making sure that there are at least two distinct entries.
PRKC-01156: Failed to validate raw device "{0}" -- Details: {1}
Cause: The raw device was not an existing device that could be opened and
recognized by the OS as a "raw/character" device type.
Action: Make sure the supplied value identifies a valid raw device that can be
opened as a "raw/character" device type.
PRKC-01157: Failed to validate raw device "{0}"
Cause: The raw device was not an existing device that could be opened and
recognized by the OS as a "raw/character" device type.
Action: Make sure the supplied value identifies a valid raw device that can be
opened as a "raw/character" device type.
PRKC-01158: Failed to validate raw device "{0}" -- Details: {1}
Cause: The device was not an existing device that could be opened and
recognized by the OS as either "raw/character" or a "block" device type.
PRKC-01000 to PRKC-01177 71-5
Action: Make sure the supplied value identifies a valid device that can be opened
as a "raw/character" or "block" device type.
PRKC-01159: Failed to validate device "{0}"
Cause: The device was not an existing device that could be opened and
recognized by the OS as either "raw/character" or a "block" device type.
Action: Make sure the supplied value identifies a valid device that can be opened
as a "raw/character" or "block" device type.
PRKC-01160: Failed to retrieve the value of environment variable "{0}" on following
nodes: "{1}", [{2}]
Cause: An error occurred while attempting to retrieve value of environment
variable on one or more nodes due to the node not being reachable, or the remote
execution service not running on the node, or some permissions issue when
attempting to use the remote execution service on the remote node.
Action: Look at the accompanying messages and respond accordingly.
PRKC-01161: Failed to retrieve the Windows domain on following nodes: "{0}"
Cause: An error occurred while attempting to retrieve the Windows domain on
one or more nodes. The possible causes include:"
- A node is not reachable.
- Remote execution service is not running on the node.
- Permissions problems prevented use of remote execution service on a node.
Action: Look at the accompanying messages and respond accordingly.
PRKC-01162: "{0}" is not a file
Cause: The indicated object was expected to be a file, but it was not.
Action: Make sure that the indicated object is a file and not a directory.
PRKC-01163: {0} Exception occurred while determining validity of storage type.
Cause: An error occurred while getting storage type of the given path. Null
arguments might have been passed.
Action: Make sure that the native api is passing non null arguments.
PRKC-01164: invalid command or arguments
Cause: This is an internal error.
Action: Contact Oracle Support Services.
PRKC-01165: Failed to set up Windows service OracleRemoteExecService on node
'{0}'
Cause: An error occurred while setting up OracleRemoteExecService on the
specified nodes."
Action: Look at the accompanying messages and respond accordingly.
PRKC-01166: Storage is partially shared. Details: {0}
Cause: A subset of the nodes provided shared the given filesystem path with the
local node.
Action: Mount the NFS filesystem on the node(s) that do not share the filesystem
path.
71-6 Oracle Database Error Messages
PRKC-01167: Failed to resolve the specified path "{0}" to its physical path on
following nodes: "{1}", [{2}]
Cause: An error occurred while attempting to resolve the path on one or more
nodes due to the node not being reachable, the remote execution service not
running on the node, or some permissions issue when attempting to use the
remote execution service on the remote node.
Action: Look at the accompanying messages and respond accordingly.
PRKC-01168: The supplied IP address "{0}" is invalid or specifies an unknown host
name
Cause: The provided string had an invalid IP address format or could not be
resolved to a known host name.
Action: Make sure that the IP address has a valid IPv4 or IPv6 address format or
that it resolves to a known host name.
PRKC-01169: The supplied IPv6 address "{0}" is invalid
Cause: The provided string had not the correct IPv6 address format.
Action: Make sure that the IP address has a valid IPv6 address format.
PRKC-01170: The IPv6 prefix length "{0}" is out of the allowed range of 0 to 128
Cause: The specified IPv6 prefix length was out of the allowed range.
Action: Make sure that the IPv6 prefix length is an integer from 0 to 128.
PRKC-01171: Internal error: {0}
Cause: An internal error occurred. The included value is an internal identifier.
Action: Oracle internal error. Contact Oracle Support Services.
PRKC-01172: The supplied IPv6 prefix length "{0}" is not an integer
Cause: The provided string for the IPv6 prefix length was not an integer.
Action: Make sure that the IPv6 prefix length is an integer from 0 to 128.
PRKC-01173: VIP name "{0}" does not resolve to an {1} address matching the
netmask or prefix length {2}
Cause: The VIP name did not resolve to the IP address type specified by the
netmask or prefix lengths.
Action: Make sure that the VIP name resolves to the IP address type which is
indirectly specified by the netmask or prefix length.
PRKC-01174: Failed to verify whether the following IP addresses are reachable or
not: {0}
Cause: A network error occurred while attempting to reach the specified IP
addresses.
Action: Use an Operating System command such as 'ping' or 'traceroute' to
determine accessibility of the IP address.
PRKC-01175: Failed to copy directories "{0}" to one or more nodes
Cause: An attempt to copy file system directories from the local node to one or
more nodes in the cluster failed. Possible causes: 1) One or more nodes failed
during the copy operation. 2) The user does not have write permission for a given
destination directory on one or more of the nodes. 3) The user does not have read
access to files or directories being copied. 4) On UNIX or Linux platforms, the 'scp'
command failed.
PRKC-01000 to PRKC-01177 71-7
Action: Check the accompanying error messages for details.
PRKC-01176: Failed to list contents of directory "{0}" on nodes "{1}"
Cause: An attempt to list the contents of the indicated directory failed. Possbile
causes: 1) The specified directory does not exist. 2) One or more nodes failed
during the operation.
Action: Check the accompanying error messages for details.
PRKC-01177: The format of the specified version "{0}" is invalid.
Cause: An attempt to compare the target version against the software version
failed because the specified version was not valid.
Action: Specify a version number that is one to five sequences of decimal digits
separated by periods.
71-8 Oracle Database Error Messages
72
PRKE-01008 to PRKE-01011 72-1
PRKE-01008 to PRKE-01011 2 7
PRKE-01008: Failed to get list of active nodes from Clusterware
Cause: Possible causes: 1) Not operating in cluster mode. 2) Failed to load SRVM
libraries. 3) Failed to initialize clusterware context.
Action: Check for the health of clusterware using "lsnodes" utility to get the list of
active nodes in the cluster. Also, check for the presence of srvm libraries in the
load library path. If these two checks get cleared, please contact Oracle Support
Services.
PRKE-01009: Failed to start GSD on local node
Cause: GSD is already running on the local node, or GSD could not be started
because of some other reason.
Action: Run "gsdctl stat" to check if a daemon is already running on the local
node. If a daemon is not running on local node, please contact Oracle Support
Services to check for the other reasons for failure.
PRKE-01010: Failed to stop GSD on local node
Cause: GSD is not running on the local node, or GSD could not shut down
gracefully.
Action: Run "gsdctl stat" to check if a GSD is running on the local node. If a GSD
is running, please contact Oracle Support Services to check for other reasons for
failure.
PRKE-01011: Failed to get status of GSD on local node
Cause: Failure to get the list of active nodes from the cluster, or failure to query
the list of live daemons from the clusterware.
Action: Run "lsnodes" to check the health of the clusterware. If the clusterware is
working fine, check for the presence of SRVM libraries in the load library path. If
the libraries are present, please contact Oracle Support Services for further
assistance.
72-2 Oracle Database Error Messages
73
PRKN-01031 to PRKN-01041 73-1
PRKN-01031 to PRKN-01041 3 7
PRKN-01031: Failed to retrieve local host name
Cause: An attempt to retrieve the local host name using Java network functions
failed.
Action: Ensure that the 'localhost' entry exists in the hosts configuration file.
PRKN-01032: error occurred while reading input from user's terminal session.
Cause: An attempt to read input from the standard input failed.
Action: Use an operating system command line to run the proper command.
PRKN-01033: The following nodes do not share the filesystem path "{0}" with node
{1}: {2}
Cause: A subset of the nodes provided shared the given filesystem path with the
local node.
Action: Mount the NFS filesystem on the node(s) that do not share the filesystem
path.
PRKN-01034: Failed to retrieve IP address of host "{0}"
Cause: An attempt to retrieve IP address for the host specified failed.
Action: Run 'nslookup' on the host name and make sure the name is resolved or
add the host name to OS hosts file.
PRKN-01035: Host "{0}" is unreachable
Cause: An attempt to reach the specified host via IP failed.
Action: Make sure that the host is up and there are no firewalls blocking
connectivity between local node and remote host.
PRKN-01036: Windows registry key "{0}" not found on node "{1}"
Cause: Could not find the specified Windows registry key on the identified node.
Action: Contact Oracle Support Services.
PRKN-01037: Unexpected command output on node {0}: "{1}"
Cause: A remotely-executed command produced output when none was
expected.
Action: Ensure that ssh or rsh is configured properly on the target node. If it is,
contact Oracle Support Services for assistance.
PRKN-01038: The command "{0}" run on node "{1}" gave an unexpected output: "{2}"
Cause: A remote-shell command produced an output when none was expected.
73-2 Oracle Database Error Messages
Action: Ensure that ssh or rsh is configured properly on the specified nodes. If it
is, contact Oracle Support Services for assistance.
PRKN-01039: Failed to create directory "{0}" on node "{1}"
Cause: The specified directory could not be created on the specified node.
Action: Ensure that the user is an administrator on the specified node, that the
specified drive has default share configured on it, and that there is enough space
in the specified location. Look at accompanying error messages and respond
accordingly.
PRKN-01040: Failed to remove directory "{0}" on node "{1}"
Cause: The specified directory could not be removed on the specified node.
Action: Ensure that the user is an administrator on the specified node, that the
specified drive has default share configured on it. Look at accompanying error
messages and respond accordingly.
PRKN-01041: Failed to retrieve the current Windows user name: {0}
Cause: An attempt to retrieve the current Windows user name failed with the
error cited in the message.
Action: Ensure that the Windows Domain Server is reachable; log in to the OS as a
domain user.
74
PRKP-01000 to PRKP-01088 74-1
PRKP-01000 to PRKP-01088 4 7
PRKP-01000: Cannot retrive configuration for cluster database {0}
Cause: The cluster database configuration could not be retrieved from the
repository. This could occur either because the database was never registered, or
because the repository itself had not been created.
Action: Check if the database has been configured by printing a list of all cluster
databases using 'srvctl config'. If the repostitory has not been created, use
'srvconfig -init' to create it.
PRKP-01001: Error starting database instance {0} on node {1}
Cause: The instance could not be started using the SQL*Plus startup command.
Action: Try starting the named instance manually using SQL*Plus to see why it
failed and examine the database instance alert log.
PRKP-01002: Error stopping database instance {0} on node {1}
Cause: The SQL*Plus shutdown command returned an error while stopping the
instance.
Action: Try stopping the named instance manually using SQL*Plus to see why it
failed and examine the database instance alert log.
PRKP-01003: Startup operation partially failed
Cause: Some components of the cluster database could not be started.
Action: Check the accompanying error messages for details.
PRKP-01004: Shutdown operation partially failed
Cause: Some components of the cluster database reported errors while being
stopped.
Action: Check the accompanying error messages for details.
PRKP-01005: Failed to start up cluster database {0}
Cause: The cluster database could not be started.
Action: Check the accompanying error messages for details.
PRKP-01006: Failed to shut down cluster database {0}
Cause: The cluster database reported errors while being shut down.
Action: Check the accompanying error messages for details.
PRKP-01007: Failed to start all the listeners associated with all the instances of
cluster database {0}
Cause: Internal error.
74-2 Oracle Database Error Messages
Action: Contact your customer support representative.
PRKP-01008: Failed to start listeners associated with instance {0} on node {1}
Cause: Internal error.
Action: Contact your customer support representative.
PRKP-01009: Failed to stop all the listeners associated with all the instances of
cluster database {0}
Cause: Either the listener name associated with an instance could not be
determined, or 'lsnrctl stop' failed for a listener.
Action: Verify that listener.ora contains a SID_LIST entry for each instance of the
named database, and that the 'lsnrctl stop' command succeeds for those listeners.
PRKP-01010: Failed to stop all the listeners associated with instance {0} on node {1}
Cause: Either the listener name associated with an instance could not be
determined, or 'lsnrctl stop' failed for a listener.
Action: Verify that listener.ora contains a SID_LIST entry for each instance of the
named database, and that the 'lsnrctl stop' command succeeds for those listeners.
PRKP-01011: Failed to get all the listeners associated with instance {0} on node {1}
Cause: The listener name associated with an instance could not be determined.
Action: Ensure that listener.ora contains a SID_LIST entry for the named instance.
PRKP-01012: Invalid environment variable {0} setting for cluster database {1}
Cause: The argument to the -t option was not of the form = or it
contained special characters.
Action: Ensure that the -t option has an argument of the form =.
Enclose the argument to the -t flag in quotes.
PRKP-01013: {0}: undefined environment variable for cluster database {1}
Cause: The named environment variable is not defined for the named cluster
database
Action: Set a value for the variable with 'srvctl setenv'.
PRKP-01014: {0}: undefined environment variable for instance {1} of cluster
database {2}
Cause: The named environment variable is not defined for the given instance
Action: Set a value for the variable with 'srvctl setenv'.
PRKP-01015: {0}: undefined environment variable
Cause: The named environment variable is not defined
Action: Set a value for the named environment variable with 'srvctl setenv'.
PRKP-01084: Database "{0}" cannot have more than "{1}" services
Cause: Attempt to add a new service to database was rejected because database
has already reached the maximum services limit.
Action: Retry after removing a service of this database via 'srvctl remove service'
command, or contact Oracle Support Services.
PRKP-01088: Failed to retrieve configuration of cluster database {0}
PRKP-01000 to PRKP-01088 74-3
Cause: Attempt to retrieve configuration of cluster database failed. This failure is
most likely due to user incorrectly using a tool, such as SRVCTL, that is of
different version than that of database's configuration.
Action: If error is due to user using SRVCTL that is of different version than than
of the database's, then run SRVCTL tool from the ORACLE_HOME reported in the
error message. Otherwise, contact Oracle support services.
74-4 Oracle Database Error Messages
75
PRKR-01001 to PRKR-01082 75-1
PRKR-01001 to PRKR-01082 5 7
PRKR-01001: cluster database {0} does not exist
Cause: The cluster database was never registered in the repository.
Action: Check if the database has been configured by printing a list of all cluster
databases using 'srvctl config'.
PRKR-01002: cluster database {0} already exists
Cause: An attempt was made to register a cluster database which already existed
in the repository.
Action: Check if the database has already been configured by printing a list of all
cluster databases using 'srvctl config'.
PRKR-01003: instance {0} does not exist
Cause: The named instance was never registered in the repository.
Action: Use 'srvctl config instance' to check if the instance is registered in the
repository.
PRKR-01005: adding of cluster database {0} configuration failed, {1}
Cause: Internal error.
Action: Contact your customer support representative.
PRKR-01006: deleting of cluster database {0} configuration failed, {1}
Cause: Internal error.
Action: Contact Oracle Support Services.
PRKR-01007: getting of cluster database {0} configuration failed, {1}
Cause: Internal error.
Action: Contact Oracle Support Services.
PRKR-01008: adding of instance {0} on node {1} to cluster database {2} failed.
Cause: Internal error.
Action: Contact Oracle Support Services.
PRKR-01009: deleting of instance {0} from cluster database {1} failed, {2}
Cause: Internal error.
Action: Contact Oracle Support Services.
PRKR-01010: moving of instance {0} to node {1} of cluster database {2} failed.
Cause: Internal error.
75-2 Oracle Database Error Messages
Action: Contact Oracle Support Services.
PRKR-01011: renaming of instance {0} to instance {1} of cluster database {2} failed,
{3}
Cause: Internal error.
Action: Contact Oracle Support Services.
PRKR-01012: error {0} while serializing configuration of cluster database {1}
Cause: Internal error.
Action: Contact Oracle Support Services.
PRKR-01013: error {0} while deserializing configuration of cluster database {1}
Cause: Internal error.
Action: Contact Oracle Support Services.
PRKR-01014: error {0} while serializing directory
Cause: Internal error.
Action: Contact Oracle Support Services.
PRKR-01015: error {0} while deserializing directory
Cause: Internal error.
Action: Contact Oracle Support Services.
PRKR-01016: reading of cluster database {0} configuration failed, {1}, {2}
Cause: Internal error.
Action: Contact Oracle Support Services.
PRKR-01017: writing of cluster database {0} configuration failed, {1}, {2}
Cause: Internal error.
Action: Contact Oracle Support Services.
PRKR-01018: reading of directory failed, {0}, {1}
Cause: Internal error.
Action: Contact Oracle Support Services.
PRKR-01019: writing of directory failed, {0}, {1}
Cause: Internal error.
Action: Contact Oracle Support Services.
PRKR-01020: reading of version information failed, {0}, {1}
Cause: Internal error.
Action: Contact Oracle Support Services.
PRKR-01021: writing of version information failed, {0}, {1}
Cause: Internal error.
Action: Contact Oracle Support Services.
PRKR-01022: Cluster registry {0} contains incompatible version, {1} != {2}
Cause: Internal error.
Action: Contact Oracle Support Services.
PRKR-01001 to PRKR-01082 75-3
PRKR-01023: file {0} does not exist
Cause: The named file did not exist.
Action: Specify a file that exists.
PRKR-01024: file {0} does not have {1} permissions
Cause: The named file did not have the specified permission.
Action: Try changing the permission on the file to the specified permission.
PRKR-01025: file {0} does not contain property {1}
Cause: The file did not contain the specified property.
Action: Contact Oracle Support Services.
PRKR-01026: property {0} not set in file {1}
Cause: The file did not contain the specified property.
Action: Contact Oracle Support Services.
PRKR-01027: failed to retrieve list of cluster databases
Cause: Internal error.
Action: Contact Oracle Support Services.
PRKR-01028: Cluster registry {0} is invalid [HINT: initialize cluster registry by
using "srvconfig" tool]
Cause: The management repository was never initialized.
Action: Use 'srvconfig -init' to initialize the repository.
PRKR-01039: invalid option {0} specified
Cause: The specified option was invalid.
Action: Check the command documentation or the inline help display for usage
details.
PRKR-01040: missing argument for {0} option
Cause: The specified option was invalid for srvconfig.
Action: Check the command documentation or the inline help display for usage
details.
PRKR-01050: file {0} creation in {1} directory failed
Cause: Either the directory did not exist or it did not have the required
permissions.
Action: Create the directory if it did not exist or change the permission of the
directory.
PRKR-01051: file {0} does not contain an entry for dbname {1}
Cause: Internal error.
Action: Contact Oracle Support Services.
PRKR-01052: file name {0} is not of .conf form
Cause: Internal error.
Action: Contact Oracle Support Services.
PRKR-01053: invalid range {0} specified in node_list = {1}
Cause: Internal error.
75-4 Oracle Database Error Messages
Action: Contact Oracle Support Services.
PRKR-01054: invalid parameter {0} specified in inst_oracle_sid = {1}
Cause: Internal error.
Action: Contact Oracle Support Services.
PRKR-01055: invalid extra arguments {0} specified to {1} option
Cause: Provided invalid arguments to srvconfig.
Action: Check the command documentation or the inline help display for usage
details.
PRKR-01056: invalid registry entry {0} found; should be of form {1}
Cause: Internal error.
Action: Contact Oracle Support Services.
PRKR-01057: environment variable does not exist
Cause: Attempted to retrieve non existing environment variable.
Action: Set the environment variable.
PRKR-01078: Database {0} of version {1} cannot be administered using current
version of srvctl. Instead run srvctl from {2}
Cause: An attempt was made to access configuration of database using srvctl that
was of different version than that of the database.
Action: Perform the operation using srvctl from the ORACLE_HOME mentioned
in the error message.
PRKR-01082: Failed to get OCR locations
Cause: An error occurred while attempting to retrieve the OCR locations, possibly
due to missing or incorrrect OCR locations file, or incomplete OCR configuration,
or due to missing or incorrect SRVM shared libraries.
Action: Verify that the Clusterware has been correctly installed and configured.
Verify that the ocr.loc file is present and readable in the appropriate location for
your platform.
76
PRKO-00371 to PRKO-09089 76-1
PRKO-00371 to PRKO-09089 6 7
PRKO-00371: No option specified for "modify gns"
Cause: No option was specified for the "modify gns" command.
Action: Specify at least one option.
PRKO-00372: The "-{0}" option requires the specification of the "-{1}" option.
Cause: An option was specified which requires that another option to be specified
at the same time.
Action: Specify the required option.
PRKO-00373: Invalid host name or address: "{0}".
Cause: The host name or address specified for the address on which GNS is to
listen was not valid.
Action: Specify a valid host name or IP address. If an IP address is used, it must
be one of the following:
1. A valid IPv4 address (N.N.N.N);
2. A valid IPv6 address (N[:N]*).
PRKO-00374: The "-{0}" option may not be used with the "-{1}" option.
Cause: The two options may not be used together.
Action: Run srvctl with each option specified separately.
PRKO-00375: No option was specified for the GNS "modify" command.
Cause: An option was not specified for the modify command.
Action: Specify an option.
PRKO-00377: The "-{0}" option requires the specification of either the "-{1}" or the
"-{2}" option.
Cause: An option was specified which requires that one of the other possible
options to be specified at the same time.
Action: Specify the one of the other options.
PRKO-00378: Both "-{0}" and "-{1}" options may not be specified with the "-{2}"
option.
Cause: An invalid combination of options was specified.
Action: Specify only one of the other possible options.
PRKO-00380: No other option is allowed when the '-loglevel' option is specified.
Cause: If the '-loglevel' option is specified, no other option may be given.
76-2 Oracle Database Error Messages
Action: Only specify the '-loglevel' option.
PRKO-00381: Both '-serverpool' and '-node' options are required to set server pool
{0} for single instance database {1} on the cluster.
Cause: Option '-node' is not specified in 'srvctl modify database' command for a
single instance database on the cluster.
Action: Specify both -serverpool and -node options in 'srvctl modify database'
and retry.
PRKO-00382: The number of candidate servers {0} in server pool {1} should be one
for single instance database {2}
Cause: The server pool specified in 'srvctl modify database' command for a single
instance database contained more than 1 candidate servers.
Action: Either modify the given server pool via 'srvctl modify srvpool' command
to have only one candidate server specified via -node argument or specify another
server pool that contains only one candidate server specified via -node argument.
PRKO-00383: Invalid IP address for name "{0}": "{1}"
Cause: The address used for a name was not valid.
Action: Specify a valid IP address. It must be one of the following:
1. A valid IPv4 address (N.N.N.N);
2. A valid IPv6 address (N[:N]*).
PRKO-00384: No option was specified for the GNS "update" command.
Cause: An option was not specified for the update command.
Action: Specify an option.
PRKO-02000: Invalid command line syntax for a single instance database
Cause: user specified invalid command line syntax.
Action: Look at the usage provided for this command and specify all mandatory
options.
PRKO-02001: Invalid command line syntax
Cause: The syntax of the command is incorrect.
Action: Look at the usage provided for this command and use the correct syntax.
PRKO-02002: Invalid command line option: {0}
Cause: Invalid command line option was specified.
Action: Check the value printed along with the exception and specify the correct
value.
PRKO-02003: Invalid command line option value:
Cause: Invalid command line option was specified.
Action: Check the value printed along with the exception and specify the correct
value.
PRKO-02004: Repetition of command line option: -{0}
Cause: The command line option printed along with the exception was repeated.
Action: Delete the repeated command line option and try the command again.
PRKO-02005: Failure in getting Cluster Database Configuration for:
PRKO-00371 to PRKO-09089 76-3
Cause: The specified database does not exist.
Action: Check the specified database name and try again.
PRKO-02006: Invalid node name: {0}
Cause: Unable to get the hostname for the given node/machine name.
Action: Check the node name and try again.
PRKO-02007: Invalid instance name: {0}
Cause: Unable to obtain the node name on which the instance name specified was
running.
Action: Check the instance name specified and try again.
PRKO-02008: Invalid connect string:
Cause: The connect string specified was not in the format username/password [as
{SYSDBA|SYSOPER}]
Action: Check the connect string and try again.
PRKO-02009: Invalid name/value string: {0}
Cause: The name value string should be of the form name = value
Action: check the input name/value pair and try again.
PRKO-02010: Invalid command specified on command line: {0}
Cause: The specified on the command line was not recognized.
Action: Valid commands are
enable|disable|start|stop|relocate|status|add|remove|modify|getenv|setenv
|unsetenv|config. Usage of srvctl is printed with this error. Check the usage and
specify a valid command.
PRKO-02011: Invalid object specified on command line: {0}
Cause: The