CRS-00001 to CRS-48104

24 CRS-00001 to CRS-48104

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.
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: 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.; 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: 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". Additional diagnostics: Path: string. Filename: string. rc: number: Cause: An error was encountered while attempting to open the specified file.; Action: Review the 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". Additional diagnostics: Path: string. Filename: string. rc: number: Cause: An error was encountered while attempting to open the specified file. Tracing was disabled for the process.; Action: Review the 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-00066: The thread passing trace information to ADR has been non-responsive for number minutes and number seconds. Additional diagnostics: process name: string, process ID: string, thread ID: string: Cause: The diagnostic infrastructure attempted to pass trace information to the Automatic Diagnostic Repository (ADR) and encountered a problem. This is an internal error.; Action: Contact Oracle Support Services.
CRS-00067: The thread passing alert information to ADR has resumed after number minutes and number seconds. Additional diagnostics: process name: string, process ID: string, thread ID: string: Cause: A thread in the diagnostic infrastructure that became non-responsive for the indicated period while attempting to pass trace information to the Automatic Diagnostic Repository (ADR) became responsive again for unknown reasons. This situation could be indicative of an internal problem.; Action: If this situation recurs, contact Oracle Support Services.
CRS-00068: The thread passing alert information to ADR has been non-responsive for number minutes and number seconds. Additional diagnostics: process name: string, process ID: string, thread ID: string: Cause: The diagnostic infrastructure attempted to pass trace information to the Automatic Diagnostic Repository (ADR) and encountered a problem. This is an internal error.; Action: Contact Oracle Support Services.
CRS-00069: The thread passing trace information to ADR has resumed after number minutes and number seconds. Additional diagnostics: process name: string, process ID: string, thread ID: string: Cause: A thread in the diagnostic infrastructure that became non-responsive for the indicated period while attempting to pass trace information to the Automatic Diagnostic Repository (ADR) became responsive again for unknown reasons. This situation could be indicative of an internal problem.; Action: If this situation recurs, contact Oracle Support Services.
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.; 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.: 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.\n: 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.\n: 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.; 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-00325: Unable to process the command; CRS upgrade is in progress.: Cause: A command that cannot be executed when CRS upgrade is in progress was issued.; Action: Retry the command after the CRS upgrade is complete.
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.: Cause: The Oracle Cluster Registry key which contains the user default CRSD connection is not initialized.; Action: Check the OCR configuration using the ocrcheck utility and resolve any issues it reports. If the problem persists, contact Oracle Support Services.
CRS-00453: CRS configuration error, unable to find Instance Information in Oracle Cluster Registry.: Cause: The Oracle Cluster Registry key which contains the Instance's information is not initialized.; Action: Check the OCR configuration using the ocrcheck utility and resolve any issues it reports. If the problem persists, contact Oracle Support Services.
CRS-00471: Node number is not found: Cause: Cluster Synchronization Services is unable to retrieve the node name.; Action: Verify your cluster installation, including any vendor cluster ware. If necessary reinstall the cluster.
CRS-00472: Node name is not found: Cause: Cluster Services is unable to retrieve the node name.; Action: Verify your cluster installation, including any vendor cluster ware. If necessary reinstall the cluster.
CRS-00602: Encountered operating system error 'string' while authenticating user 'string'. Details at string in string.: Cause: The operating system experienced an error when Clusterware authenticated the specified user.; Action: Verify that the authentication service in your environment is functioning correctly. If the problem persists, contact Oracle Support Services.
CRS-00700: Oracle High Availability Service aborted due to failure to allocate memory. Details at string in string.: Cause: Memory allocation failed.; Action: Restart Cluster Ready Service using 'crsctl stop crs -f' followed by 'crsctl start crs'. If the problem persists, contact Oracle Support Services.
CRS-00701: Oracle High Availability Service aborted due to failure to obtain identity of the running process. Details at string in string.: Cause: Failed to retrieve user id.; Action: Check <crs_home> owner and restart Cluster Ready Service using 'crsctl stop crs -f' followed by 'crsctl start crs'. If the problem persists, contact Oracle Support Services.
CRS-00702: Oracle High Availability Service aborted due to failure to run as privileged user. Details at string in string.: Cause: Oracle High Availability Service was not running as privileged user.; Action: On Unix, restart Cluster Ready Service as privileged user using 'crsctl stop crs -f' followed by 'crsctl start crs'. On Windows, check the privileges of the Oracle High Availability Service and restart Cluster Ready Service using 'crsctl stop crs -f' followed by 'crsctl start crs' If the problem persists, contact Oracle Support Services.
CRS-00703: Oracle High Availability Service aborted due to failure to initialize the communication context. Details at string in string.: Cause: The network layer initialization failed.; Action: Restart Cluster Ready Service using 'crsctl stop crs -f' followed by 'crsctl start crs'. If the problem persists, contact Oracle Support Services.
CRS-00704: Oracle High Availability Service aborted due to Oracle Local Registry error [string]. Details at string in string.: Cause: Oracle Local Registry aborted with an error. Look at the associated error message to determine the underlying issue.; Action: Solve the underlying issue and restart Cluster Ready Service using 'crsctl stop crs -f' followed by 'crsctl start crs'. If the problem persists, contact Oracle Support Services.
CRS-00708: Oracle High Availability Service aborted due to failure to retrieve ORA_CRS_HOME environment variable. Details at string in string.: Cause: An environment variable required by Oracle High Availability Service failed to be set at initialization.; Action: Run 'rootcrs.pl -unlock' followed by 'rootcrs.pl -patch' and restart Cluster Ready Service using 'crsctl stop crs -f' followed by 'crsctl start crs'. If the problem persists, contact Oracle Support Services.
CRS-00709: Oracle High Availability Service aborted due to failure to initialize ORA_CRS_HOME path. Details at string in string.: Cause: Oracle High Availability Service ORA_CRS_HOME path could not be initialized.; Action: Check for execute permissions on the Grid Infrastructure home or <crs_home> and restart Cluster Ready Service using 'crsctl stop crs -f' followed by 'crsctl start crs'. If the problem persists, contact Oracle Support Services.
CRS-00712: Oracle High Availability Service aborted due to failure to initialize the network layer with error [number]. Details at string in string.: Cause: The network layer initialization failed.; Action: Restart Cluster Ready Service using 'crsctl stop crs -f' followed by 'crsctl start crs'. If the problem persists, contact Oracle Support Services.
CRS-00713: An error occurred initializing the Reboot Advisory Monitor: error code [number]. Details at string in string.: Cause: An error occurred initializing the Reboot Advisory Monitor component of Oracle High Availability Service. This error is not fatal; Oracle High Availability Service processing continues.; Action: Examine the Clusterware alert log for messages providing details of the error. If the error is correctable, do so and then restart Cluster Ready Service using 'crsctl stop crs -f' followed by 'crsctl start crs'. If no messages are found or you do not understand how to correct the problem, contact Oracle Support Services.
CRS-00714: Oracle Clusterware Release number.number.number.number.number.: Cause: The Oracle High Availability Services Daemon (OHASD) was started as part of a general start of the Oracle Clusterware stack on this node.; Action: None
CRS-00715: Oracle High Availability Service has timed out waiting for init.ohasd to be started.: Cause: The Oracle High Availability Service requires that initd start init.ohasd to successfully initialize.; Action: 1. Check the run level to ensure that you are in the correct runlevel using cluvfy ("cluvfy stage -pre crsinst -n nodelist"); 2. If the run level is correct, diagnose the reason for init.d not starting init.ohasd.
CRS-00716: Oracle High Availability Service failed to initialize ADR automatic purge. Details at string in string.: Cause: An attempt to initialize automatic purge processing for the Automatic Diagnostic Repository (ADR) failed. This error is not fatal, but automated periodic removal of ADR trace and related data will not occur.; Action: ADR data can be purged manually using the ADRCI command line tool. However, repeated occurrences of this message should be reported to Oracle Support Services.
CRS-00800: Cluster Ready Service aborted due to failure to allocate memory. Details at string in string.: Cause: Memory allocation failed.; Action: Restart Cluster Ready Service using 'crsctl stop crs -f' followed by 'crsctl start crs'. If the problem persists, contact Oracle Support Services.
CRS-00801: Cluster Ready Service aborted due to failure to obtain identity of the running process. Details at string in string.: Cause: Failed to retrieve user id.; Action: Check <crs_home> owner and restart Cluster Ready Service using 'crsctl stop crs -f' followed by 'crsctl start crs'. If the problem persists, contact Oracle Support Services.
CRS-00802: Cluster Ready Service aborted due to failure to run as privileged user. Details at string in string.: Cause: Cluster Ready Service was not running as privileged user.; Action: On Unix, restart Cluster Ready Service as privileged user using 'crsctl stop crs -f' followed by 'crsctl start crs'. On Windows, check the privileges of the Oracle High Availability Service and restart Cluster Ready Service using 'crsctl stop crs -f' followed by 'crsctl start crs' If the problem persists, contact Oracle Support Services.
CRS-00803: Cluster Ready Service aborted due to failure to initialize the communication context. Details at string in string.: Cause: The network layer initialization failed.; Action: Restart Cluster Ready Service using 'crsctl stop crs -f' followed by 'crsctl start crs'. If the problem persists, contact Oracle Support Services.
CRS-00804: Cluster Ready Service aborted due to Oracle Cluster Registry error [string]. Details at string in string.: Cause: Oracle Cluster Registry aborted with an error. Look at the associated error message to determine the underlying issue.; Action: Solve the underlying issue and restart Cluster Ready Service using 'crsctl stop crs -f' followed by 'crsctl start crs'. If the problem persists, contact Oracle Support Services.
CRS-00805: Cluster Ready Service aborted due to failure to communicate with Cluster Synchronization Service with error [number]. Details at string in string.: Cause: The Cluster Synchronization Service is unreachable.; Action: Restart Cluster Ready Service using 'crsctl stop crs -f' followed by 'crsctl start crs'. If the problem persists, contact Oracle Support Services.
CRS-00806: Cluster Ready Service aborted due to failure to retrieve the local node name. Details at string in string.: Cause: The Cluster Synchronization Service node name is not accessible.; Action: Restart Cluster Ready Service using 'crsctl stop crs -f' followed by 'crsctl start crs'. If the problem persists, contact Oracle Support Services.
CRS-00807: Cluster Ready Service aborted due to failure to check version compatibility. Details at string in string.: Cause: Oracle Cluster Registry content is not compatible with this version of Cluster Ready Service.; Action: Start the correct version of Cluster Ready Service. If the problem persists, contact Oracle Support Services.
CRS-00808: Cluster Ready Service aborted due to failure to retrieve ORA_CRS_HOME environment variable. Details at string in string.: Cause: An environment variable required by Cluster Ready Service failed to be set at initialization.; Action: Run 'rootcrs.pl -unlock' followed by 'rootcrs.pl -patch' and restart Cluster Ready Service using 'crsctl stop crs -f' followed by 'crsctl start crs'. If the problem persists, contact Oracle Support Services.
CRS-00809: Cluster Ready Service aborted due to failure to initialize ORA_CRS_HOME path. Details at string in string.: Cause: Cluster Ready Service ORA_CRS_HOME path could not be initialized.; Action: Check for execute permissions on the Grid Infrastructure home or <crs_home> and restart Cluster Ready Service using 'crsctl stop crs -f' followed by 'crsctl start crs'. If the problem persists, contact Oracle Support Services.
CRS-00810: Cluster Ready Service aborted due to failure to communicate with Event Management Service with error [number]. Details at string in string.: Cause: The Event Management Service is unreachable.; Action: Restart Cluster Ready Service using 'crsctl stop crs -f' followed by 'crsctl start crs'. If the problem persists, contact Oracle Support Services.
CRS-00811: Cluster Ready Service aborted due to failure to build dependency graph. Details at string in string.: Cause: There exists inconsistencies in the resources dependencies.; Action: Check the resources dependencies and restart Cluster Ready Service using 'crsctl stop crs -f' followed by 'crsctl start crs'. If the problem persists, contact Oracle Support Services.
CRS-00812: Cluster Ready Service aborted due to failure to initialize the network layer with error [number]. Details at string in string.: Cause: The network layer initialization failed.; Action: Restart Cluster Ready Service using 'crsctl stop crs -f' followed by 'crsctl start crs'. If the problem persists, contact Oracle Support Services.
CRS-00813: Cluster Ready Service aborted due to failure to initialize the network layer with error [string]. Details at string in string.: Cause: The network layer initialization failed.; Action: Restart Cluster Ready Service using 'crsctl stop crs -f' followed by 'crsctl start crs'. If the problem persists, contact Oracle Support Services.
CRS-00814: Cluster Ready Service aborted due to failure to start thread with error [number]. Details at string in string.: Cause: Thread creation failed.; Action: Restart Cluster Ready Service using 'crsctl stop crs -f' followed by 'crsctl start crs'. If the problem persists, contact Oracle Support Services.
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: 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-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.
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: Automatically repaired invalid Oracle Cluster Registry configuration on this node. 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; therefore, it was automatically repaired.; Action: If this occurs repeatedly, contact Oracle Support Services.
CRS-01019: The Oracle Cluster Registry (OCR) Service exited on host string. Details at string in string.: Cause: The OCR Service encountered an internal error.; Action: Collect the Oracle Clusterware alert log and the Cluster Ready Services Daemon (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: 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.; Action: The Cluster Ready Services on this node will be automatically restarted. If the problem persists, contact Oracle Support Services.
CRS-01025: Oracle Clusterware was upgraded to version [string] on all nodes, but the cluster active 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 active version has changed using the 'crsctl query crs activeversion' command. If the problem persists, run diagcollection.pl and contact Oracle Support Services.
CRS-01026: 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-01029: The Oracle Cluster Registry backup file string is corrupt. Details at string in string.: Cause: The backup file created by the periodic backup of the Oracle Cluster Registry (OCR) failed to pass the post-backup sanity check. Either the OCR was corrupted or the backup was faulty.; Action: If the fault was introduced during the backup generation, then it will be corrected during the next backup generation, and no action is required. If the subsequent backup is also faulty, then the Oracle Cluster Registry might be corrupt. Contact Oracle Support Services.
CRS-01030: The Oracle Cluster Registry backup file string could not be validated. Details at string in string.: Cause: The indicated Oracle Cluster Registry (OCR) backup file could not be validated due to validation process not starting or failing to run the validation check.; Action: If the backup was attempted as part of an automatic periodic backup, then no action is needed. If the backup was attempted as part of a manual backup, then try the backup again. If the problem persists, contact Oracle Support Services.
CRS-01031: The Oracle Cluster Registry operation encountered ASM error. Details at string in string.: Cause: The Oracle Cluster Registry (OCR) operation could not be completed due to the referenced ASM errors.; Action: Check the referenced log file for more detailed failure information.
CRS-01110: Oracle Clusterware upgrade is in unknown state [number].\n: 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 active version of Oracle Clusterware:\nstring.\n: Cause: There was an internal error upgrading the active version of Oracle Clusterware.; Action: Use the command 'crsctl check crs' to verify that the CRS Service is running. Retry the 'crsctl set crs activeversion' command. If the problem persists, contact Oracle Support Services.
CRS-01112: failed to set Oracle Clusterware active 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: 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.\n: Cause: Oracle Clusterware is already running in highest possible operating version.; Action: None
CRS-01116: Upgrade of the active version of Oracle Clusterware has been aborted.\n: 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 active version of Oracle Clusterware.\n: Cause: An attempt was made to change the Oracle Clusterware active 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.\n: Cause: An attempt was made to change the Oracle Clusterware active 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.\n: 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.: 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.\n: 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: Use the command 'crsctl check crs' to verify 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: Use the command 'srvctl status asm' to verify 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: Use the command 'srvctl status ioserver' to verify 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.: 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-01143: There was an error setting Oracle ACFS to rolling upgrade mode.: Cause: An attempt to initiate a rolling upgrade failed because an error occurred while attempting to set the Oracle ASM Cluster File System (Oracle ACFS) mode to 'rolling'. The accompanying Oracle ACFS specific messages provide further failure details.; Action: Use the command 'srvctl status filesystem' to verify that the Oracle ASM Cluster File System is active, and inspect the accompanying Oracle ACFS specific error messages to see if there is a correctable problem. If so, correct the problem and retry the command 'crsctl start rollingupgrade'. If the problem persists, contact Oracle Support Services.
CRS-01151: The cluster was successfully set to rolling patch mode.\n: 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: Use the command 'crsctl check crs' to verify 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-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: Use the command 'srvctl status asm' to verify 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: Use the command 'srvctl status ioserver' to verify 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].\n: 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.; Action: Make sure all the nodes in the cluster have been patched to the same patch level using the 'crsctl query crs softwarepatch host' 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: Use the command 'crsctl check crs' to verify 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: Use the command 'srvctl status asm' to verify 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: Use the command 'srvctl status ioserver' to verify 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-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 host' 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 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. The release patch string is [string].\n: 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.\n: 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. The release patch string is [string].\n: Cause: None, this is an informational message.; Action: None
CRS-01191: There was an error retrieving 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].\n: Cause: None, this is an informational message.; Action: None
CRS-01201: CRSD started on node string.: Cause: CRSD has started, possibly due to a CRS start, or a node reboot or a CRSD restart.; Action: None Required. You can run the command 'crsctl check crsd' to validate the health of the CRSD.
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 on the resource failed.; 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.: Cause: Cluster Ready Service failed to update the group private data with new leader.; 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.; 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.: 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.; 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 on the resource failed.; 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 leader.; 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.; 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.
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.: 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.; 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 has been shut down.: Cause: The CSS daemon on the listed node was terminated.; Action: None
CRS-01604: CSSD voting file is offline: string; details at string in string.: Cause: The indicated voting file became unusable on the local node either because it was being replaced or because it was not accessible.; Action: 1. No action necessary if the voting file was replaced. 2. If the voting file was not replaced then verify that the filesystem containing the indicated 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: Locate previous 1604, 1613, 1614 and 1615 messages and take 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-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) has been missing for 90%% of the timeout interval. If this persists, removal of this node from cluster will occur in number.number seconds: Cause: Heartbeat messages were not received from the node. This could be due to network problems or failure of the listed node.; Action: If the node was removed, check that the private interconnect network used by the cluster is functioning properly, including all the cables, network cards, switches, routers, and so forth between this node and listed node. Correct any problems discovered.
CRS-01611: Network communication with node string (number) has been missing for 75%% of the timeout interval. If this persists, removal of this node from cluster will occur in number.number seconds: Cause: Heartbeat messages were not received from the node. This could be due to network problems or failure of the listed node.; Action: If the node was removed, check that the private interconnect network used by the cluster is functioning properly, including all the cables, network cards, switches, routers, and so forth between this node and listed node. Correct any problems discovered.
CRS-01612: Network communication with node string (number) has been missing for 50%% of the timeout interval. If this persists, removal of this node from cluster will occur in number.number seconds: Cause: Heartbeat messages were not received from the node. This could be due to network problems or failure of the listed node.; Action: If the node was removed, check that the private interconnect network used by the cluster is functioning properly, including all the cables, network cards, switches, routers, and so forth between this node and listed node. Correct any problems discovered.
CRS-01613: No I/O has completed after 90%% of the maximum interval. If this persists, voting file string will be considered not functional in number milliseconds.: Cause: Voting device I/O did not complete for a long time. This could be due to some error with the device on which the voting file exists or in some element in the path of the I/O to the device.; Action: If the voting file was removed, verify that the device is working properly including all the elements in the I/O path. The voting file listed will be considered inactive in the number of milliseconds indicated. Failure of a majority of devices will result in node reboot.
CRS-01614: No I/O has completed after 75%% of the maximum interval. If this persists, voting file string will be considered not functional in number milliseconds.: Cause: Voting device I/O did not complete for a long time. This could be due to some error with the device on which the voting file exists or in some element in the path of the I/O to the device.; Action: If the voting file was removed, verify that the device is working properly including all the elements in the I/O path. The voting file listed will be considered inactive in the number of milliseconds indicated. Failure of a majority of devices will result in node reboot.
CRS-01615: No I/O has completed after 50%% of the maximum interval. If this persists, voting file string will be considered not functional in number milliseconds.: Cause: Voting device I/O did not complete for a long time. This could be due to some error with the device on which the voting file exists or in some element in the path of the I/O to the device.; Action: If the voting file was removed, verify that the device is working properly including all the elements in the I/O path. The voting file listed will be considered inactive in the number of milliseconds indicated. 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-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: 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-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: 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-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 from thread: string; 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. If this persists, a reboot will occur in number milliseconds; details are at string in string.: Cause: The Cluster Synchronization Service daemon (CSSD) Agent or Monitor was not receiving responses from the CSS daemon. This message was a warning that the node would be rebooted after the indicated time unless responses were received. If CSS responded before the time elapsed, no reboot would have occurred, and the timers would have been reset.; Action: If the reboot occurred, collect the Oracle 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\n: 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: 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. number ports reserved for clusterware process.\n: 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. Further reduction in voting files will result in eviction and loss of functionality: 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-01673: A Configuration change request failed because a node in the cluster is being patched; Details at string in string: Cause: An attempt to change configuration was rejected because a node in the cluster was being patched.; Action: Retry the command after the patching operation has completed.
CRS-01674: CSSD Reconfiguration completed for addition of the nodes string. Active nodes are string.: Cause: New nodes joined the cluster.; Action: None
CRS-01675: CSSD Reconfiguration completed for the removal of nodes string since the surviving cluster has access to the public network. Active nodes are string.: Cause: Reconfiguration was done for removal of the indicated nodes. The active nodes were a part of the surviving cluster because one or more of them were connected to the public network.; Action: None
CRS-01676: CSSD Reconfiguration completed for the removal of nodes string since the surviving cluster has a running ASM instance. Active nodes are string.: Cause: Reconfiguration was done for removal of the indicated nodes. The active nodes were a part of the surviving cluster because one or more of them had a running ASM instance.; Action: None
CRS-01677: CSSD Reconfiguration completed for the removal of nodes string since the surviving cluster has a larger number of nodes. Active nodes are string.: Cause: Reconfiguration was done for removal of the indicated nodes. The active nodes were a part of the surviving cluster because they had a larger number of nodes.; Action: None
CRS-01678: CSSD Reconfiguration completed for the removal of nodes string since the surviving cluster satisfies server pool configuration best. Active nodes are string.: Cause: Reconfiguration was done for removal of the indicated nodes. The active nodes were a part of the surviving cluster because they satisfied the server pool configuration best.; Action: None
CRS-01679: CSSD Reconfiguration completed for the removal of nodes string since the surviving cluster has a higher number number of CSS CRITICAL objects. Active nodes are string.: Cause: Reconfiguration was done for removal of the indicated nodes. The active nodes were a part of the surviving cluster because they had a higher number of resources and nodes marked as CSS CRITICAL.; Action: None
CRS-01680: CSSD Reconfiguration completed for the removal of nodes string. Active nodes are string.: Cause: Reconfiguration was done for removal of the indicated nodes.; Action: None
CRS-01681: CSSD on node string is going down because this node does not have access to the public network.: Cause: Removal of the node was done because this node was not a part of a cluster which had access to the public network.; Action: None
CRS-01682: CSSD on node string is going down because this node does not have a running ASM instance.: Cause: Removal of the node was done because this node was not a part of a cluster with a running ASM instance.; Action: None
CRS-01683: CSSD on node string is going down because this node is not a part of a cluster having a larger number of nodes.: Cause: Removal of the node was done because this node was not a part of a cluster that had the largest number of nodes.; Action: None
CRS-01684: CSSD on node string is going down because this node is not a part of cluster that satisfies server pool configuration best.: Cause: Removal of the node was done because this node was not in the part of the cluster that satisfied server pool configuration best.; Action: None
CRS-01685: CSSD on node string is going down because this node is not critical to CSSD.: Cause: Removal of the node was done because this node was not in the part of the cluster that is critical to CSSD.; Action: None
CRS-01686: CSSD on node string is going down.: Cause: CSSD on the indicated node went down.; Action: None
CRS-01687: CSSD on node string is going down because this node does not have the minimum number of voting files required to survive in the cluster.: Cause: Removal of the node was done because this node did not have the minimum number of voting files required to survive in the cluster.; Action: None
CRS-01688: CSSD on node string is going down because it got evicted by node string.: Cause: The indicated node was evicted by the other indicated node.; Action: None
CRS-01689: Cluster Synchronization Services daemon on node string is going down because another required clusterware component is not running on the node.: Cause: Removal of the indicated node was done because the node did not have all of the required clusterware components running.; Action: None
CRS-01690: The CRS home file system is not responsive. If this persists, a reboot occurs in number milliseconds; details are at string in string.: Cause: The Cluster Synchronization Service daemon (CSSD) agent detected that the Cluster Ready Services (CRS) home was not responsive. This message was a warning that the node would be rebooted after the indicated time unless responses were received. If CRS home recovered before the time elapsed, no reboot would have occurred and the timers would have been reset.; Action: If the reboot occurred, collect the Oracle 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-01691: CSSD reconfiguration completed for the configuration change of parameter string. Active nodes are string.: Cause: The reconfiguration resulting from the change to the indicated parameter was successfully completed.; Action: None
CRS-01692: CSSD reconfiguration completed for the addition of voting file string. Active nodes are string.: Cause: The reconfiguration resulting from the addition of the indicated voting file was successfully completed.; Action: None
CRS-01693: CSSD reconfiguration completed for the removal of voting file string. Active nodes are string.: Cause: The reconfiguration resulting from the removal of the indicated voting file was successfully completed.; Action: None
CRS-01694: CSSD reconfiguration completed for the replacement of voting file string with voting file string. Active nodes are string.: Cause: The reconfiguration resulting from the replacement of the indicated voting files was successfully completed.; Action: None
CRS-01695: CSSD recovery attempt failed for instance number started at number; details at string in string.: Cause: An internal error occurred.; Action: Collect the Oracle Clusterware alert log and the Cluster Synchronization Service daemon (CSSD) as well as all CSSD logs of all other nodes in the cluster and contact Oracle Support Services.
CRS-01696: CLSDADR string thread in CSSD is missing heartbeat attempting recovery; details in string.: Cause: An internal error occurred.; Action: Collect the Oracle Clusterware alert log and the Cluster Synchronization Service daemon (CSSD) as well as all CSSD logs of all other nodes in the cluster and contact Oracle Support Services.
CRS-01697: Member kill number issued for PID string by node number for number members, group string. Details at string in string.: Cause: A member kill request was issued for the indicated process for the members belonging to the indicated group by the indicated node.; Action: No action is required.
CRS-01698: CSSD received shutdown request string from client PID string, CSSD aborting from thread: string. Details in string.: Cause: SHUTDOWN has been received from the client due to failure in client side.; Action: Check the PID and analyze further the reason for client to send SHUTDOWN request. NOT CSS issue.
CRS-01699: Recovery procedure is waiting for old string PID number to terminate at 50string of recovery timeout. If this persists node will be rebooted in number ms. Details in string: Cause: An internal error occurred.; Action: Collect the Oracle clusterware alert log and the Cluster Synchronization Service daemon agent log along with CSSD logs.
CRS-01700: Group string has number maximum supported members registered. Details in string.: Cause: A member join request was received but the group has reached the maximum value.; Action: Check the client PID for each join request to determine the reason why the client send it. NOT CSS issue.
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.
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-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' or 'crsctl replace 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.; 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 ('string') 'string (ostid:number)' not scheduled for 'number' msecs.: Cause: Excessive system load prevented threads in the Cluster Synchronization Service daemon (CSSD/ONMD) from being scheduled for execution from the time indicated in the message. This indicates the system was overloaded.; Action: Take steps to reduce the system load or increase system resources to handle the load.
CRS-01720: Cluster Synchronization Services daemon (CSSD) is ready for operation.: Cause: Cluster Synchronization Services daemon (CSSD) is fully initialized and functional. CSSD group membership services has started. Services dependent on CSSD can start using cluster synchronization services.; Action: None
CRS-01721: Cluster Synchronization Service daemon (CSSD) was unable to complete initialization for fence type string.: Cause: The Cluster Synchronization Service daemon (CSSD) failed to complete initialization for the indicated fence type, most likely because of a failure in the associated support entity. The entities CSSD depends on are ASM, DISKMON. Messages in the alert log from DISKMON or ASM may supply additional details.; Action: Contact Oracle Support Services.
CRS-01722: Cluster Synchronization Service daemon encountered an internal error.: Cause: CSSD failed due to an internal error.; Action: Contact Oracle Support Services.
CRS-01723: Cluster Synchronization Services daemon (CSSD) exited because it failed to spawn thread string.: Cause: Cluster Synchronization Services failed to spawn the indicated critical thread due to an operating system error. The accompanying message provides additional details on failed system call.; Action: Contact Oracle Support Services.
CRS-01724: CSSD agent failed to spawn CSSD process: Cause: The Cluster Synchronization Services daemon could not be started because the operating system failed to spawn the process.; Action: Contact Oracle Support Services.
CRS-01725: Encountered operating system error 'string' while performing operation 'string'.: Cause: The operating system encountered an error for the indicated operation.; Action: Contact Oracle Support Services.
CRS-01726: Process failed to run in real-time priority. Details at string in string.: Cause: CSSD, CSSDMONITOR or CSSDAGENT failed to set real-time priority.; Action: Contact Oracle Support Services.
CRS-01727: Network communication between this node 'string' (number) and node 'string' (number) re-established. Node removal no longer imminent.: Cause: None.; Action: None
CRS-01728: The majority of voting files are accessible on number sites, however number sites are required, terminating to ensure data integrity; details at string in string: Cause: A check on voting file accessibility prompted by a voting file management operation, periodic voting file access or lease acquisition determined that a majority of voting files on a majority of sites were not accessible by the local node.; Action: Delete the voting files that are no longer available, as indicated by message CRS-01637, using the appropriate 'crsctl' commands. Run the crsctl command either on another node where the clusterware stack is active, or by starting the clusterware stack in exclusive mode.
CRS-01729: CSSD failed to start because the clusterware stack was not shutdown in the expected manner.: Cause: The possible reasons include: - A clusterware stack shutdown in Zero Downtime GI Patching mode was not issued prior to this start attempt - A clusterware stack shutdown in Zero Downtime GI Patching mode was issued but it failed; Action: Restart the clusterware stack normally without the Zero Downtime GI Patching mode option.
CRS-01730: Cluster Synchronization Service daemon failed to change process priority due to an operating system error 'string'.: Cause: An attempt to change the process priority failed.; Action: Contact Oracle Support Services.
CRS-01731: Storage cell 'string' is inaccessible from this node; however it is still accessible from node 'string'; terminating to ensure data integrity; details at 'string' in 'string'.: Cause: There was a connectivity problem between this node and the storage cell.; Action: Contact Oracle Support Services.
CRS-01732: CSSD-GPNPD handshake in unicast mode failed; details at 'string' in 'string'.: Cause: Initialization with Grid Plug and Play (GPNP) component failed causing Cluster Synchronization Service Daemon (CSSD) to fail during startup.; Action: Collect clusterware alert log, daemon logs, and contact Oracle Support Services.
CRS-01733: IPMIUTIL binary path not specified. Node incapable of IPMI operations; details at 'string' in 'string'.: Cause: The fully quantified path to the ipmiutil binary was not present.; Action: Make sure the fully quantified path to the ipmiutil binary is present. Use command 'crsctl set ipmi binaryloc' on every cluster node.
CRS-01734: Cluster Synchronization Services miscount setting was changed from number to number.: Cause: A configuration change request to change Cluster Synchronization Services miscount completed successfully.; Action: None
CRS-01735: Fence request issued for an entity node number with a timeout of number.: Cause: Fence requested from client.; Action: None
CRS-01736: Fence request from node string is being escalated to evict node string.: Cause: Fence requested was not successful.; Action: None
CRS-01737: Member kill from node string is being escalated to evict node string.: Cause: Member kill requested was not successful.; Action: None
CRS-01738: CSS is starting string recovery of thread string with a timeout of number millisecond.: Cause: A failure occurred in a Cluster Synchronization Service (CSS) daemon thread.; Action: None
CRS-01739: CSS has successfully completed string recovery in number millisecond.: Cause: Cluster Synchronization Service (CSS) daemon has recoverd from a failure.; Action: None
CRS-01740: Cluster Synchronization Services recovery of thread string has failed due to string.: Cause: A failure occurred during CSSD recovery.; Action: None
CRS-01741: Cluster Synchronization Services is starting special meltdown due to a failure in string during recovery.: Cause: A failure occurred during CSSD recovery.; Action: None
CRS-01742: Cluster Synchronization Services has successfully completed special meltdown due to a failure in string during recovery.: Cause: A failure occurred during CSSD recovery.; Action: None
CRS-01743: Cluster Synchronization Services is currently undergoing reconfig hence recovery will not be performed; details at string in string: Cause: A failure occurred in a CSSD thread while CSSD was undergoing reconfig.; Action: None
CRS-01744: Cluster Synchronization Services is currently undergoing reconfig hence ZIP will not be performed; details at string in string: Cause: ZIP action failed as CSSD was undergoing reconfig.; Action: None
CRS-01745: Cluster Synchronization Service will not undergo recovery due to string; details at 'string' in 'string'.: Cause: A fatal error occurred during CSS daemon processing.; Action: None
CRS-01801: Cluster string configured with nodes string.: Cause: None.; Action: None
CRS-01802: Node string added to cluster.: Cause: None.; Action: None
CRS-01803: Node string deleted from cluster.: Cause: None.; Action: None
CRS-01804: Node string upgraded to version string.: Cause: None.; Action: None
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-01808: Node-specific configuration for node string in Oracle Local Registry was upgraded to version string.: Cause: None.; Action: None
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-01810: Node-specific configuration for node string in Oracle Local Registry was patched to patch level number.: Cause: None.; Action: None
CRS-01811: Node string patched to patch level number.: Cause: None.; Action: None
CRS-01812: An attempt to use the same network as both public and private was rejected.: Cause: Distinct networks must be used as public and cluster interconnect.; Action: Retry install using distinct networks for public and private interconnect.
CRS-01901: CRS service setting (string) is changed from [string] to [string].: Cause: None.; Action: None
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-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 <string> 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 <number> 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.; 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-02119: The Oracle Local Registry (OLR) Service exited on host string. Details at string in string.: Cause: The OLR Service encountered an internal error.; Action: Collect the Oracle Clusterware alert log and the Oracle High Availability Services Daemon (OHASD) log indicated in the message, and contact Oracle Support Services.
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-02129: The Oracle Local Registry backup file string is corrupt. Details at string in string.: Cause: The backup file created by the periodic backup of the Oracle Local Registry (OLR) failed to pass the post-backup sanity check. Either the OLR was corrupted or the backup was faulty.; Action: If the fault was introduced during the backup generation, then it will be corrected during the next backup generation, and no action is required. If the subsequent backup is also faulty, then the Oracle Local Registry might be corrupt. Contact Oracle Support Services.
CRS-02130: The Oracle Local Registry backup file string could not be validated. Details at string in string.: Cause: The indicated Oracle Local Registry (OLR) backup file could not be validated due to validation process not starting or failing to run the validation check.; Action: Re-attempt to backup the Oracle Local Registry (OLR). If the problem persists, contact Oracle Support Services.
CRS-02301: Grid Plug and Play : string: Cause: This conveys a message from the Grid Plug and Play (GPnP) layer to the alert log.; Action: Look up the imbedded message and respond accordingly.
CRS-02302: Cannot get Grid Plug and Play (GPnP) profile. Error string (string).: Cause: Get Grid Plug and Play (GPNP) profile operation failed.; Action: n/a
CRS-02303: Grid Plug and Play Daemon (GPNPD) is not running on local node.: Cause: Grid Plug and play Daemon (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.: Cause: GPnP resource discovery failed.; Action: Make sure resource discovery service (MDNSD) runs on local node.
CRS-02306: Grid Plug and Play Daemon (GPNPD) on host "string" not found.: Cause: Remote Grid Plug and Play Daemon (GPNPD) 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-02307: No Grid Plug and Play services on requested remote hosts.: Cause: Failed to find operational GPnP services on remote host(s).; Action: Make sure GPnP services (MDNSD and GPNPD) are up and running on remote hosts, and network connection is operational.
CRS-02310: Failed to initialize security facility.: Cause: Error occurred while initializing Grid Plug and Play (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 Grid Plug and Play (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 Grid Plug and Play (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 Grid Plug and Play (GPnP), string (string).: Cause: General GPnP initialization failure.; Action: If the problem persists, contact Oracle Support Services.
CRS-02317: Cannot get local Grid Plug and Play (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: Grid Plug and Play Daemon(GPNPD) is not found.: Cause: Local Grid Plug and Play Daemon (Grid Plug and Play Daemon(GPNPD) is not found.; Action: Make sure Grid Plug and Play Daemon(GPNPD) is running.
CRS-02319: No cluster name found in Grid Plug and Play (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 Grid Plug and Play (GPnP) profile.: 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 Grid Plug and Play (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 Grid Plug and Play (GPnP) profile cache providers.: Cause: Local GPnP setup was invalid.; Action: Contact Oracle Support Services.
CRS-02324: Errors occurred while trying to push Grid Plug and Play (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 Grid Plug and Play (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: Grid Plug and Play (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: Grid Plug and Play Daemon(GPNPD) already running on node string. Terminating.: Cause: Grid Plug and Play Daemon (GPNPD) instance was already running on node.; Action: Bring down existing GPNPD instance first.
CRS-02328: Grid Plug and Play Daemon(GPNPD) started on node string.: Cause: Grid Plug and Play Daemon (GPNPD) started on node.; Action: None
CRS-02329: Grid Plug and Play Daemon(GPNPD) on node string shut down.: Cause: Grid Plug and Play Daemon (GPNPD) was shut down by request.; Action: None
CRS-02330: Grid Plug and Play Daemon(GPNPD) failed to start listening for GPnP peers.: Cause: Grid Plug and Play Daemon (GPNPD) failed to open server endpoint.; Action: Check GPNPD logs for the cause. If the problem persists, contact Oracle Support Services.
CRS-02331: Error getting Grid Plug and Play (GPnP) profile from "string".: Cause: Get remote GPnP profile from remote node operation failed.; Action: Retry request. If the problem persists, contact Oracle Support Services.
CRS-02332: Error pushing Grid Plug and Play (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 Grid Plug and Play (GPnP) profile to local cache.: Cause: Grid Plug and Play Daemon (GPNPD) 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 Grid Plug and Play (GPnP) profile from local cache.: Cause: Grid Plug and Play Daemon (GPNPD) cannot delete GPnP profile from local cache.; Action: If the problem persists, contact Oracle Support Services.
CRS-02335: Could not write pending Grid Plug and Play (GPnP) profile to local cache.: Cause: Grid Plug and Play Daemon (GPNPD) 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: Grid Plug and Play Daemon (GPNPD) failed get local GPnP profile and cannot continue. Check gpnpd/gpnp client logs.: Cause: Grid Plug and Play Daemon (GPNPD) cannot find a profile in local cache, and cannot continue.; Action: Contact Oracle Support Services.
CRS-02339: Grid Plug and Play Daemon(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 Grid Plug and Play (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: Grid Plug and Play Daemon (GPNPD) on node string shutting down on signal number.: Cause: Grid Plug and Play Daemon is shutting down due to received signal.; Action: Contact your cluster administrator.
CRS-02342: Grid Plug and Play (GPnP) messaging received error : string (string).: Cause: GPnP message error received.; Action: If the problem persists, contact Oracle Support Services.
CRS-02343: Grid Plug and Play Daemon(GPNPD) is unable resolve peer host name "string" to sync profile. Details at string in string.: Cause: Hostname of peer Grid Plug and Play Daemon (Grid Plug and Play Daemon(GPNPD) ) cannnot be resolved.; Action: Verify that DNS hostname resolution is working for the peer node or its IP address is defined in the /etc/hosts.
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
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-02409: The clock on host string differs from mean cluster time by number microseconds. No action has been taken because the Cluster Time Synchronization Service is running in observer mode.: Cause: The system clock on the indicated host differed from the mean cluster time by more than 1000 microseconds. No action was taken because the Cluster Time Synchronization Service was 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.; 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-02416: The Cluster Time Synchronization Service 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-02417: The Cluster Time Synchronization Service 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-02418: The clock on host string differs from mean cluster time by number microseconds. The Cluster Time Synchronization Service will not perform time synchronization because the time difference is beyond the permissible offset of number seconds. Details in string.: Cause: The Cluster Time Synchronization Service exited because it detected a time offset from mean cluster time on the indicated node of more than the indicated permissible value.; Action: Shutdown Oracle Clusterware on the indicated host. Adjust the clock using native platform or operating system methods, and then restart Oracle Clusterware on the indicated host.
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.; 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.
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: 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: 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.; 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.
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.; 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: n[s|d|m|w|h]: Cause: The value specification does not follow required format.; 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: 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.; 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.: 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.
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-02633: server pool 'string' not found in policy 'string': Cause: An attempt was made to change the configuration of a server pool in the policy set, but the server pool was not configured to be managed by the policy set.; Action: Modify the SERVER_POOLS attribute of the policy set to contain the name of the server pool.
CRS-02640: Required resource 'string' is missing.: Cause: A resource that's configured as required is not registered.; 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.
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': 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 was inappropriate or invalid.; Action: Refer to the documentation and retry the request specifying a valid value for the indicated attribute.
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.; 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-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.
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-02738: Unable to modify server pool 'string' as this will affect running resources and resource groups, but the force option was not specified: Cause: One or more running resources and/or resource groups would be affected by the operation.; Action: Add more servers to the cluster, stop or relocate the resources and resource groups 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: 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.: 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.
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.; 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.
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 server '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: 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.
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.; 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.; 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-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: Unless the clusterware stack was stopped or the server was rebooted, Cluster Ready Services will restart momentarily. The 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.: 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-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.; 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.; 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-02885: cannot stop the last server in Domain Service Cluster with active member cluster named 'string': Cause: An attempt to stop the last server in the Domain Service Cluster was rejected because this cluster was still serving the indicated client cluster and perhaps other member clusters."; Action: Stop the active member clusters that use this Domain Service Cluster first, or specify the '-f' option."
CRS-02886: Required component 'string' of Oracle Grid Infrastructure is missing.: Cause: An attempt to start the Oracle Grid Infrastructure stack failed because the indicated required resource was not found. This is an internal error.; Action: Contact Oracle Support Services.
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.: 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-02895: DEGREE attribute is desupported.: Cause: An attempt was made to add a resource with DEGREE attribute.; Action: Remove the DEGREE attribute from the add command.
CRS-02896: Cannot restart resource 'string' because the restart capability of this resource is disabled.: Cause: The resource did not restart automatically because the attribute "ALLOW_RESTART" of this resource was set to "useronly".; Action: Set the attribute "ALLOW_RESTART" of this resource to "default" or start the resource manually.
CRS-02897: attempt number of number to start resource string failed: Cause: An attempt to start the indicated resource failed. The resource was configured to attempt to start multiple times. When this failure was reported, there were more attempts remaining to start the resource.; Action: None
CRS-02898: Value of attribute 'string' cannot be greater than that of attribute 'string'.: Cause: An attempt to provide an incorrect attribute value combination failed.; Action: Reissue the command with the corrected value.
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.; 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.; 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-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-02930: The server category 'string' cannot be deleted because it is still a dependency for one or more resources.: Cause: An attempt was made to delete a server category that was still a dependency for one or more resources.; Action: Either modify the dependency attributes of the associated resources or delete those resources and try again.
CRS-02931: Server category 'string' used in dependency 'string' does not exist or is not registered.: Cause: An attempt was made for the current resource to have a dependency on a server category that does not exist.; Action: Check the specification of the dependency, fix the problem indicated, and resubmit the request.
CRS-02932: The dependency on server category 'string' is not supported for a resource type.: Cause: An attempt to specify a server category dependency for a resource type failed because server category dependency is only supported for a resource.; Action: Omit the server category dependency.
CRS-02933: The server category name for the relation 'string' is missing.: Cause: The server category name was expected for the resource dependency, but it was not supplied.; Action: Provide the server category name when resubmitting the request.
CRS-02949: The dispersion dependency 'string' is specified with mutliple modifiers.: Cause: An attempt to specify the dispersion dependency failed because multiple modifiers were specified where at most one is supported.; Action: Check the specification of the dependency, fix the problem indicated, and resubmit the request.
CRS-02961: Consistency problem in registry while processing category 'string'. Details at string in string.: Cause: This is an internal error.; Action: Contact Oracle Support Services.
CRS-02962: Consistency problem in registry while processing server pool 'string'. Details at string in string.: Cause: This is an internal error.; Action: Contact Oracle Support Services.
CRS-02963: Consistency check for all entities managed by the Cluster Ready Services has completed successfully.: Cause: None.; Action: None
CRS-02964: cannot run resource 'string' on server 'string' because the server needs an additional number MB of memory: Cause: An attempt to start a resource on a server failed because the server needed the indicated additional memory to satisfy the memory requirements of the resource.; Action: Change the placement policy of the resource to expand the server selections, change the memory requirement of the resource, or add more memory to the server to which the resource is directly assigned.
CRS-02965: cannot run resource 'string' on server 'string' because the server needs number additional CPUs: Cause: An attempt to start a resource on a server failed because the server needed additional CPUs to satisfy the CPU requirement of the resource.; Action: Change the placement policy of the resource to expand the server selections, change the CPU requirement of the resource, or add more CPUs to the server to which the resource is directly assigned.
CRS-02966: There are no servers satisfying the placement policy for resource 'string'.: Cause: An attempt to start a resource on servers that were available according to the placement policy failed because none of those servers could satisfy the requirements of the resource.; Action: Change the placement policy of the resource to expand the server selections, change the requirements of the resource, or upgrade the configurations of the eliminated servers.
CRS-02967: Resource instance 'string' is unable to start because it is scheduled for deletion.: Cause: An online relocate attempt on this resource failed to stop the specified resource instance. The resource instance is scheduled for deletion when it stops.; Action: Use 'crsctl stop resource' to stop the resource instance manually.
CRS-02968: authorization failure updating attribute 'string': Cause: Write access permission was not granted to this user to modify the attribute.; Action: Either omit the attribute, or issue the command from an operating system user who has the required permission.
CRS-02969: cannot add resource 'string' because a resource group exists with the same name: Cause: An attempt to add a resource failed because a resource group with the same name was already registered.; Action: Reissue the command specifying a different name for the new resource.
CRS-02970: Value 'string' is invalid, must be one of: 'string', 'string', 'string', or 'string'.: Cause: An attempt to change an attribute value of a resource was rejected because the indicated value was specified, when it must have been one of the other values indicated in the message.; Action: Retry modifying the resource attribute value specifying one of the allowed values as shown in the error message.
CRS-02971: cannot run resource ora.asm on server 'string' on quarantined site 'string': Cause: An attempt to run resource ora.asm on the indicated server was rejected because that server was in the specified site, which was quarantined so that no ASM client or instance could run there.; Action: Do the following: 1) Verify that all ASM disk groups are mounted on the site that is not quarantined. 2) Issue 'ALTER DISKGROUP name ONLINE ALL' for each disk group. 3) Verify that all disks from these disk groups are ONLINE. 4) Verify that all disks from these disk groups are accessible from the quarantined site. Once verified, issue the command 'crsctl modify cluster site <site_name> -s rejuvenate' on the quarantined site to rejuvenate it. If more information is needed, please refer to Oracle Clusterware Administration and Deployment Guide.
CRS-02972: There are no servers satisfying the CPU and memory requirements for resource 'string'.: Cause: An attempt to start the indicated resource failed because there were no servers available that meet the CPU-count and memory requirements of that resource.; Action: If possible, change the CPU or memory requirements of the resource or add more CPUs or memory to the servers in the cluster.
CRS-02973: The WORKLOAD_CPU 'number' exceeds the remaining value of 'number' on server 'string'.: Cause: An attempt to modify a resource failed because the specified CPU count exceeded the remaining available value indicated in the message.; Action: Retry modifying the resource attribute value specifying a value less than the available value as shown in the message.
CRS-02974: unable to act on resource 'string' on server 'string' because that would require stopping or relocating resource 'string' but the appropriate force flag was not specified: Cause: The attempted operation on the indicated resource and server was rejected because it would have required stopping or relocating the additional resource as shown. The appropriate force flag would have been required to allow the additional effects.; Action: Reevaluate the request, and if appropriate, retry the operation specifying the force flag appropriate for the tool.
CRS-02975: duplicate attempt to complete Transparent HA for resource 'string' rejected: Cause: An attempt to end the transparent High Availability (HA) action on the indicated resource instance was rejected because the same action was already pending on that resource instance."; Action: None
CRS-02976: The workload maximum memory 'number' MB exceeds the available memory size of 'number' MB.: Cause: An attempt to modify a resource failed because the specified workload maximum memory exceeded the available value indicated in the message.; Action: Retry modifying the resource attribute value specifying a value less than or equal to the available value as shown in the message.
CRS-02977: The specified value 'number' exceeds the available CPU capacity on node 'string': Cause: An attempt to modify the attribute WORKLOAD_CPU_CAP was rejected because the new value would have caused the total CPU utilization to exceed 100% on the node given in the message.; Action: Check the CPU utilization on the mentioned node and re-issue the modify command with an appropriate value.
CRS-02981: Value 'string' is invalid, must be one of: 'string', 'string', or 'string'.: Cause: An attempt to set a resource attribute to the indicated value was rejected because that value was invalid.; Action: Retry modifying the resource attribute value specifying one of the allowed values as shown in the error message.
CRS-02982: Reserved attribute 'string' cannot be specified as an attribute for a resource type.: Cause: An attempt to supply the indicated attribute to a resource type was rejected because the attribute was reserved. This would typically occur if the user attempted to reuse an attribute in use in another cluster.; Action: In case of the typical case above, do not specify the reserved attribute to add a resource type. The reserved attribute will be automatically set by CRS. If the specified attribute coincidentally conflicted with the reserved attribute, retry adding the resource type choosing an attribute name not reserved by Cluster Ready Services.
CRS-02983: There are no servers satisfying the CPU requirements for resource 'string'.: Cause: An attempt to start the indicated resource failed because there were no servers available that meet the available CPU requirements of that resource.; Action: If possible, change the CPU requirements of the resource or add more CPUs to the servers in the cluster.
CRS-02984: There are no servers satisfying the CPU requirements for resource group 'string'.: Cause: An attempt to start the indicated resource group failed because there were no servers available that meet the available CPU requirements of that resource group.; Action: If possible, change the CPU requirements of the resource group or add more CPUs to the servers in the cluster.
CRS-02985: Resource 'string' used in attribute link 'string' does not exist or is not registered.: Cause: The resource referenced by the attribute link specification was not found.; Action: Check the specification of the attribute link, fix the problem indicated, and resubmit the request.
CRS-02986: Resource 'string' used in attribute link 'string' does not have attribute 'string'.: Cause: The resource referenced by the attribute link specification did not have the desired attribute in its resource type.; Action: Check the specification of the attribute link, fix the problem indicated, and resubmit the request.
CRS-02989: Resource 'string' used in attribute link 'string' is part of a circular link.: Cause: The resource referenced by the attribute link specification referred to itself.; Action: Check the specification of the attribute link, fix the problem indicated, and resubmit the request.
CRS-02990: Resource 'string' is referenced by one or more resources.: Cause: An attempt to unregister a resource failed because another resource depended on it for an attribute link.; Action: Reissue the command after removing all attribute links referring to the resource to be unregistered.
CRS-02991: Resource 'string' used in attribute link 'string' uses a special value for attribute 'string'.: Cause: The resource referenced by the attribute link specification contained a special value.; Action: Check the specification of the attribute link, fix the problem indicated, and resubmit the request.
CRS-02992: insufficient permissions to modify attribute 'string' on resource 'string': Cause: Modification of the specified attribute required Oracle Grid Infrastructure user or root (UNIX) or Administrator (WINDOWS).; Action: Retry the modification with the correct permissions.
CRS-02993: Value 'number' is invalid for attribute 'string', must be greater than or equal to 'number'.: Cause: An attempt to set a value for the indicated attribute was rejected because the specified value was invalid.; Action: Retry modifying the resource attribute with a valid value.
CRS-02994: Value 'number' is invalid for attribute 'string', must be in increments of 'number'.: Cause: An attempt to set a value for the indicated attribute was rejected because the specified value was invalid.; Action: Retry modifying the resource attribute with a valid value.
CRS-02995: Attribute 'string' cannot be added to an existing resource type.: Cause: An attempt to add a new attribute with the FLEX_ prefix to an existing resource type was rejected.; Action: Use a different attribute name.
CRS-02996: Cluster Ready Services cannot shut down on node 'string' because that would require stopping the last running instance of resource 'string', which would affect resource 'string' on node 'string'.: Cause: Shutdown of Cluster Ready Services failed because of a resource dependency.; Action: Start another instance of the required resource or stop all dependent resources on other nodes.
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: 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.\n: Cause: Internal error.; Action: Contact Oracle Support Services.
CRS-04201: Hash context initialization failure during wallet IPMI credentials creation\n: Cause: Internal error.; Action: Contact Oracle Support Services.
CRS-04202: String hashing failed during wallet credentials creation\n: Cause: Internal error.; Action: Contact Oracle Support Services.
CRS-04203: Hashing creation error during wallet credentials creation\n: Cause: Internal error.; Action: Contact Oracle Support Services.
CRS-04204: Failed to initialize the IPMI credentials wallet: string\n: 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.\n: 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'\n: 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'\n: Cause: While trying to write 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-04208: Unexpected error encountered during lookup of IPMI credentials in the wallet\n: 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\n: 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.\n: 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\n: Cause: Insufficient system memory resources.; Action: Correct the system memory resources problem and retry.
CRS-04212: Failed to obtain the secret from the wallet.\n: 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\n: 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.\n: 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\n: Cause: Internal error.; Action: Contact Oracle Support Services.
CRS-04216: Unexpected error configuring the wallet contents\n: 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\n: 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.
CRS-04218: Unable to access an IPMI device on this system\n: 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\n: 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\n: 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\n: 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\n: 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.\n: 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\n: 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\n: 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 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: The configuration data is stored but IPMI IP address is required to complete the change. The change cannot be validated until the information is complete.\n: Cause: IPMI IP address was missing. To complete the clients's IPMI login change request, all of the information such as IPMI username, password, and IP address, must be present.; Action: Execute 'crsctl set css ipmiaddr'.
CRS-04228: Value of attribute 'string' is missing\n: Cause: The user did not provide a value for the attribute.; Action: Provide a value using the format attrName=value, where value may be empty single quotes.
CRS-04229: The IPMI information change was successful\n: 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\n: 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\n: 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: The configuration data is stored but IPMI authorization information is required to complete the change. The change cannot be validated until the information is complete.\n: Cause: IPMI authorization information was missing. To complete the clients's IPMI login change request, all of the information such as IPMI username, password, and IP address, must be present.; Action: Execute 'crsctl set css ipmiadmin'.
CRS-04233: New IPMI configuration data stored, but failed validation by remote node.\n: 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.\n: 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'\n: 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\n: Cause: The Oracle Registry contains complete configuration data for IPMI.; Action: None required.
CRS-04237: Oracle Clusterware is not fully configured to use IPMI\n: Cause: The Oracle Registry does not contain complete configuration data for IPMI.; Action: None required.
CRS-04238: failed to load the Oracle Home User wallet from the file system\n'string'\n: Cause: Could not load the wallet from the file system.; Action: Check whether the wallet file exists, and retry the operation.
CRS-04251: Failed to change the discovery string\n: 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\n: 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\n: 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\n: 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\n: 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\n: Cause: An update to the profile is being performed.; Action: None
CRS-04257: Voting file discovery string successfully replaced\n: 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\n: 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\n: 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\n: 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\n: 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\n: Cause: An internal error happened when accessing GPnP profile.; Action: Contact Oracle Support Services.
CRS-04263: This operation is not allowed\n: 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 vfile ... vfile'.
CRS-04264: The operation could not be validated\n: 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\n: Cause: Another operation on the profile is taking place.; Action: Let the other operation finish and retry.
CRS-04266: Voting file(s) successfully replaced\n: Cause: A request to replace a voting files(s) completed.; Action: None
CRS-04267: Error while updating the profile with ASM discovery string\n: Cause: An internal error happened while updating the ASM discovery string.; Action: Contact Oracle Support Services.
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.\n: 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.\n: Cause: An attempt was made to create voting files outside the ASM disk group.; Action: Specify an ASM disk group for voting file creation or replacement.
CRS-04272: error while identifying voting files in use\n: 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'.\n: 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.\n: 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-04275: Command 'crsctl add css votedisk' command is invalid.\n: Cause: An attempt to add a voting file using 'crsctl add css votedisk' was rejected because voting files are only supported on ASM disk group. Changes in configuration can be made only with 'crsctl replace votedisk'.; Action: Use 'crsctl replace votedisk' to add the voting files.
CRS-04276: Command 'crsctl delete css votedisk' command is invalid.\n: Cause: An attempt to delete a voting file using 'crsctl delete css votedisk' was rejected because voting files are present in ASM disk group.; Action: Use 'crsctl replace votedisk' to replace the voting files.
CRS-04399: Command no longer supported. Use 'crsctl get tracefileopts css' or 'crsctl set tracefileopts css' instead.\n: Cause: The specified command is no longer supported and has been replaced.; Action: Use command 'crsctl get tracefileopts css' or 'crsctl set tracefileopts css'. For the complete syntax enter 'crsctl get tracefileopts -help' or 'crsctl set tracefileopts -help'.
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: An attempt to start the CSS daemon in exclusive mode failed because an active CSS daemon was detected on the indicated node. Starting CSS in exclusive mode requires that the clusterware stack be down on all other nodes to ensure data integrity.; Action: If this message displays as part of the install process, no action is required. Otherwise, stop the Oracle Clusterware stack that is running on the indicated node. If vendor clusterware is in use, stop it on all nodes as well. After stopping all other clusterware, retry starting CSS in exclusive mode.
CRS-04404: The following nodes did not reply within the allotted time:\nstring: 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:\nstring: 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.\n: 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-04412: Attribute 'string' does not exist.: Cause: An attempt was made to obtain the value for a nonexistent attribute.; Action: Verify the attribute name was specified as intended or retry with a valid attribute.
CRS-04413: The following message was received from node 'string':: Cause: The mentioned node has sent a message indicating the status of the executed command.; Action: See the following message for the status.
CRS-04414: The specified 'crsctl set trace' or 'crsctl get trace' command is no longer supported.\n: Cause: A request was made to modify or acquire a component trace level which could not be carried out because the designated component tracing is no longer performed, making the concept of component trace level no longer applicable.; Action: None
CRS-04415: cannot stop all the Hub Nodes; clusterware stack is still up and running on a Leaf Node: Cause: An attempt to stop all the Hub Nodes was rejected because the clusterware stack was still running on a Leaf Node, which needs to be connected to a Hub Node."; Action: Stop all the stacks on the Leaf Nodes first, or keep at least one stack up and running on a Hub Node."
CRS-04416: Server attribute 'string' successfully changed. Restart Oracle High Availability Services for new value to take effect.: Cause: The 'crsctl set' command was run to change the server attribute of a node in a Flex Cluster, however the new value had not taken effect.; Action: To have the new value take effect restart Oracle High Availability Services on the node by running 'crsctl stop crs' and 'crsctl start crs'.
CRS-04417: cannot start Leaf Nodes; no clusterware stacks running on any Hub Nodes: Cause: An attempt to start one or more Leaf Nodes was rejected because no clusterware stack was running on any Hub Node. Leaf nodes need to be connected to a Hub Node.; Action: Retry after ensuring that stacks are running on Hub Nodes.
CRS-04468: could not retrieve the software patch level because host string is not a cluster member\n: Cause: The software patch level could not be retrieved for the indicated host because it is not a cluster member.; Action: Specify a host name that belongs to the cluster.
CRS-04477: Oracle Cluster Registry security attributes cannot be initialized.\n: Cause: An attempt to initialize the Oracle Cluster Registry (OCR) security attributes failed because CRS could not obtain either the user name or the user group name.; Action: Report the error to Oracle Support Services.
CRS-04481: Unable to spawn a process.\n: Cause: There was an internal error while spawning a process.; Action: Report the error to Oracle Support.
CRS-04482: A child process terminated abnormally.\n: 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.\n: 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
CRS-04608: Failure number with Cluster Synchronization Services while deleting voting disk.\n: 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 the last remaining voting disk; 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\n: Cause: Internal error.; Action: Contact Oracle Support Services.
CRS-04625: Failure to allocate number bytes for username.\n: 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.\n: 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\n: 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.\n: 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\n: 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.\n: 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.\n: 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.\n: 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.\n: Cause: CRS daemons is engaged in an activity take could potentially take a long time.; Action: None
CRS-04634: Retrying stop resources.\n: 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]\n: Cause: Output message, not an error.; Action: None
CRS-04646: Disk group string does not exist or is not mounted.\n: Cause: The indicated disk group was not found or was not mounted.; Action: Create or mount the Disk group before use.
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.\n: Cause: There is indication that the clusterware stack is still up.; Action: Shut down the entire clusterware stack before deleting the node.
CRS-04659: Error while trying to unpin node string.\n: Cause: An internal error happened during this operation.; Action: Contact Oracle Support Services.
CRS-04660: Could not find node string to delete.\n: 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.\n: Cause: A request to delete a node completed.; Action: None
CRS-04662: Error while trying to delete node string.\n: Cause: Some internal error happened during this operation.; Action: Contact Oracle Support Services.
CRS-04663: could not find node string to pin\n: 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.\n: Cause: A request to pin a node completed.; Action: None
CRS-04665: Error while trying to pin node string.\n: Cause: An internal error happened during this operation.; Action: Contact Oracle Support Services.
CRS-04666: Could not find node string to unpin.\n: 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.\n: Cause: A request to unpin a node completed.; Action: None
CRS-04668: This ASM diskgroup does not contain voting disks to be deleted\n: 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.\n: 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 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.\n: 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.\n: 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.\n: Cause: The backup of the voting file completed successfully.; Action: None
CRS-04673: Oracle High Availability Services version on the local node is [string]\n: 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-04677: Failed to get string for Cluster Synchronization Services.\n: 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.\n: Cause: The 'get' operation was performed successfully.; Action: None
CRS-04681: Failed to unset priority for Cluster Synchronization Services.\n: 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.\n: Cause: The 'unset' operation was performed successfully.; Action: None
CRS-04683: failed to set parameter 'string' to number for Cluster Synchronization Services with error number\n: Cause: A 'crsctl set' command failed. The number following "error" is a return code, which can be: 1 - internal OCSSD server error 15 - insufficient privileges for this operation; Action: Respond based on the return code as follows: 15 - Adjust privileges or use a different user ID. others - Contact Oracle Support Services.
CRS-04684: Successful set of parameter string to number for Cluster Synchronization Services.\n: 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-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.\n: 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.\n: 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.\n: 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.\n: 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.\n: 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.\n: Cause: Vendor time synchronization software is not detected on any of the nodes in the cluster.; Action: None
CRS-04702: Offset (in msec): string\n: Cause: None; Action: None
CRS-04703: The Cluster Time Synchronization Service is Offline.\n: Cause: The Cluster Time Synchronization Service is not running on the current node.; Action: None
CRS-04704: Shutdown of Clusterware failed on node string.\n: 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.\n: 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-04724: failed to get the attribute hubsize: Cause: An attempt to get the 'hubsize' attribute failed because the Oracle Clusterware stack was down.; Action: Start the Oracle Clusterware stack and retry the command.
CRS-04727: invalid type 'string' specified: Cause: An invalid resource or resource group type starting with 'ora.' was specified. Resource or resource group types starting with 'ora.' are reserved for Oracle internal resource types.; Action: Retry the command with a valid resource or resource group type.
CRS-04728: failed to get the attribute hubsize because CSSD is down: Cause: An attempt to retrieve the 'hubsize' attribute failed because the Cluster Synchronization Services daemon (CSSD) was not running. CSSD is required for retrieving this attribute.; Action: Start the CSSD and retry the command.
CRS-04729: Error code number in Oracle ASM Cluster File System (Oracle ACFS) upgrade API: Cause: An attempted software upgrade encountered the indicated error while setting the Oracle ACFS upgrade mode. This is an internal error.; Action: Contact Oracle Support Services and provide the indicated error code.
CRS-04730: Command aborted due to an internal error\n: Cause: An inconsistent internal state was detected.; Action: Call Oracle Support Services.
CRS-04731: Specified file string could not be created.\n: 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.\n: 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.\n: 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.\n: 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\n: Cause: An infrastructure error occurred because a required OCR key was missing.; Action: Call Oracle Support Services.
CRS-04736: Operation on OCR key failed\n: 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\n: 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\n: 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 \n: 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.\n: 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\n: 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),