CRS-00001 to CRS-29006

22 CRS-00001 to CRS-29006

CRS-00001: Message ID <varname>string</varname>-<varname>number</varname> 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: <varname>string</varname>:Internal list corruption. trace file: "<varname>string</varname>": 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 "<varname>string</varname>". Additional diagnostics: <varname>string</varname>: 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: "<varname>string</varname>": 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 "<varname>string</varname>" 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: "<varname>string</varname>": 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 "<varname>string</varname>\: 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 "<varname>string</varname>" after close failure: Cause: This message is informational. Log data are lost.; Action: None
CRS-00009: file "<varname>string</varname>" 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 "<varname>string</varname>" during file rotation. Additional diagnostics: <varname>string</varname>: 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 "<varname>string</varname>" to "<varname>string</varname>" during file rotation. Additional diagnostics: <varname>string</varname>: 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 "<varname>string</varname>" during file rotation. Additional diagnostics: <varname>string</varname>: 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 "<varname>string</varname>" during file rotation. Additional diagnostics: <varname>string</varname>: 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 "<varname>string</varname>" during file rotation. Additional diagnostics: <varname>string</varname>: 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 "<varname>string</varname>" during file rotation. Additional diagnostics: <varname>string</varname>: 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 "<varname>string</varname>" during file rotation. Additional diagnostics: <varname>string</varname>: 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 "<varname>string</varname>" during file rotation. Additional diagnostics: <varname>string</varname>: 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: "<varname>string</varname>": 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 "<varname>string</varname>" during file open processing. Additional diagnostics: <varname>string</varname>: 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 "<varname>string</varname>" during file open processing. Additional diagnostics: <varname>string</varname>: 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 "<varname>string</varname>" during file open processing. Additional diagnostics: <varname>string</varname>: 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 "<varname>string</varname>" during file open processing. Additional diagnostics: <varname>string</varname>: 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 "<varname>string</varname>" during file open processing. Additional diagnostics: <varname>string</varname>: 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 "<varname>string</varname>" during file open processing. Additional diagnostics: <varname>string</varname>: 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 "<varname>string</varname>" to "<varname>string</varname>" 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 "<varname>string</varname>" during file open processing. Additional diagnostics: <varname>string</varname>: 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 "<varname>string</varname>". Additional diagnostics: <varname>string</varname>: 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 "<varname>string</varname>" after the banner record was written. Additional diagnostics: <varname>string</varname>: 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: <varname>string</varname> ftype: <varname>number</varname>: 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 "<varname>string</varname>" during file synchronization processing. Additional diagnostics: <varname>string</varname>: 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 "<varname>string</varname>" during generate-file-name processing. Additional diagnostics: <varname>string</varname>: 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 "<varname>string</varname>" during generate-file-name processing. Additional diagnostics: <varname>string</varname>: 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 "<varname>string</varname>" during generate-file-name processing. Additional diagnostics: <varname>string</varname>: 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: <varname>string</varname>: 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 "<varname>string</varname>".: Cause: An error was encountered while attempting to open the specified file.; Action: Review preceding Alert log messages and attempt to resolve any file system environmental problems indicated. Otherwise, contact Oracle Support Services
CRS-00037: An error occurred while attempting to write to file "<varname>string</varname>". Additional diagnostics: <varname>string</varname>: 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: <varname>string</varname>: 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 "<varname>string</varname>".: Cause: An error was encountered while attempting to open the specified file. Tracing is disabled for the process.; Action: Review preceding Alert log messages and attempt to resolve any file system environmental problems indicated. Otherwise, contact Oracle Support Services
CRS-00040: Trace logging terminated for the process. trace file: "<varname>string</varname>": 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: "<varname>string</varname>": Cause: One or more file system errors were encountered which caused trace file rotation to be terminated for the process. Although trace file rotation has been terminated, tracing continues.; Action: Review Alert log messages that precede this alert log message that identify the file system error or errors encountered. If the additional diagnostic data in a preceding alert log message indicate a file system environmental problem, attempt to correct it. Otherwise contact Oracle Support Services. To reenable trace file rotation the process must be restarted.
CRS-00184: Cannot communicate with the CRS daemon.: Cause: The CRS daemon on the local node is either not running or there was an internal communication error with the CRS daemon.; Action: Check if the CRS daemon process is running on the local node.
CRS-00210: Could not find resource '<varname>string</varname>'.: 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 '<varname>string</varname>' 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 '<varname>string</varname>'.: Cause: There was an internal error while registering the resource.; Action: Check the CRS daemon log file.
CRS-00214: Could not unregister resource '<varname>string</varname>'.: Cause: There was an internal error while unregistering the resource.; Action: Check the CRS daemon log file.
CRS-00215: Could not start resource '<varname>string</varname>'.: Cause: There was an internal error while starting the resource.; Action: Check the CRS daemon log file.
CRS-00216: Could not stop resource '<varname>string</varname>'.: Cause: There was an internal error while stopping the resource.; Action: Check the CRS daemon log file.
CRS-00217: Could not relocate resource '<varname>string</varname>'.: Cause: There was an internal error while relocating the resource.; Action: Check the CRS daemon log file.
CRS-00218: Could not restart the resource '<varname>string</varname>' 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 '<varname>string</varname>'.: Cause: There was an internal error while updating the resource.; Action: Check the CRS daemon log file.
CRS-00220: Resource '<varname>string</varname>' 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 '<varname>string</varname>''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 '<varname>string</varname>' 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 '<varname>string</varname>' 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 '<varname>string</varname>': 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 '<varname>string</varname>': Cause: A deprecated command was issued.; Action: For all new use cases, use the replacement.
CRS-00275: This command is not supported in Oracle Restart environment.: Cause: One of the "crs_" commands was issued in an Oracle Restart environment.; Action: Use the corresponding crsctl command.
CRS-00402: Could not make safe directory('<varname>string</varname>'): 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('<varname>string</varname>'): 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 ('<varname>string</varname>'): 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 '<varname>string</varname>'.: 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 '<varname>string</varname>' while authenticating user '<varname>string</varname>'. Details at <varname>string</varname> in <varname>string</varname>.: 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 <varname>string</varname> in <varname>string</varname>.: 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 <varname>string</varname> in <varname>string</varname>.: 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 <varname>string</varname> in <varname>string</varname>.: 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 <varname>string</varname> in <varname>string</varname>.: 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 [<varname>string</varname>]. Details at <varname>string</varname> in <varname>string</varname>.: 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 <varname>string</varname> in <varname>string</varname>.: 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 <varname>string</varname> in <varname>string</varname>.: 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 [<varname>number</varname>]. Details at <varname>string</varname> in <varname>string</varname>.: 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 [<varname>number</varname>]. Details at <varname>string</varname> in <varname>string</varname>.: 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 <varname>number</varname>.<varname>number</varname>.<varname>number</varname>.<varname>number</varname>.<varname>number</varname>.: 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 <varname>nodelist</varname>"); 2. If the run level is correct, diagnose the reason for init.d not starting init.ohasd.
CRS-00800: Cluster Ready Service aborted due to failure to allocate memory. Details at <varname>string</varname> in <varname>string</varname>.: 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 <varname>string</varname> in <varname>string</varname>.: 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 <varname>string</varname> in <varname>string</varname>.: 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 <varname>string</varname> in <varname>string</varname>.: 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 [<varname>string</varname>]. Details at <varname>string</varname> in <varname>string</varname>.: 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 [<varname>number</varname>]. Details at <varname>string</varname> in <varname>string</varname>.: 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 <varname>string</varname> in <varname>string</varname>.: 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 <varname>string</varname> in <varname>string</varname>.: 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 <varname>string</varname> in <varname>string</varname>.: 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 <varname>string</varname> in <varname>string</varname>.: 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 [<varname>number</varname>]. Details at <varname>string</varname> in <varname>string</varname>.: 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 <varname>string</varname> in <varname>string</varname>.: 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 [<varname>number</varname>]. Details at <varname>string</varname> in <varname>string</varname>.: 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 [<varname>string</varname>]. Details at <varname>string</varname> in <varname>string</varname>.: 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 [<varname>number</varname>]. Details at <varname>string</varname> in <varname>string</varname>.: 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 <varname>number</varname>.: Cause: Successfully formatted the OCR location(s).; Action: None
CRS-01002: The OCR was restored from file <varname>string</varname>.: 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 <varname>number</varname>.: 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 <varname>string</varname>.: Cause: Successfully imported the OCR contents from a file.; Action: None
CRS-01005: The Oracle Clusterware upgrade was completed. Version has changed from [<varname>number</varname>, <varname>string</varname>] to [<varname>number</varname>, <varname>string</varname>]. Details in <varname>string</varname>.: Cause: The Oracle Clusterware was successfully upgraded to a version.; Action: None
CRS-01006: The OCR location <varname>string</varname> is inaccessible. Details in <varname>string</varname>.: 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 <varname>string</varname>.: Cause: The OCR location was successfully replaced as requested by the user.; Action: None
CRS-01008: Node <varname>string</varname> is not responding to OCR requests. Details in <varname>string</varname>.: 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 <varname>string</varname>.: 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 <varname>string</varname> 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 <varname>string</varname>.: 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 <varname>string</varname>.: Cause: The OCR was successfully started.; Action: None
CRS-01013: The OCR location in an ASM disk group is inaccessible. Details in <varname>string</varname>.: 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 <varname>string</varname>: 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 <varname>string</varname> completed successfully. Details at <varname>string</varname> in <varname>string</varname>.: 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 <varname>string</varname> in <varname>string</varname>.: 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 <varname>string</varname> in <varname>string</varname>.: Cause: There was a failure accessing the import file on this node. The Cluster Ready Service on this node may not have been active during the Oracle Cluster Registry format upgrade.; Action: The Oracle Cluster Registry format upgrade will be completed by another node in the cluster. The Cluster Ready Service on this node will be automatically restarted, and will be able to function as soon as the upgrade completes. If the problem persists, contact Oracle Support Services.
CRS-01018: The Cluster Ready Service on this node terminated because the OCR configuration on this node is invalid. Details at <varname>string</varname> in <varname>string</varname>.: Cause: The OCR configuration on this node did not match with the OCR configuration on the other nodes in the cluster.; Action: The OCR configuration on this node is automatically repaired and the Cluster Ready Service will be automatically restarted. If the problem persists, contact Oracle Support Services.
CRS-01019: The OCR Service exited on host <varname>string</varname>. Details in <varname>string</varname>: Cause: The OCR Service exited due to an internal error.; Action: Determine whether the service has restarted. Collect Clusterware alert log and the CRSD log indicated in the message and contact Oracle Support Services.
CRS-01020: The Oracle Cluster Registry has invalid contents. Details at <varname>string</varname> in <varname>string</varname>.: 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 <varname>string</varname>.: Cause: Oracle Cluster Registry backup location did not exists, wasn't mounted correctly, or did not have the required permissions.; Action: Ensure that the backup location exists, that it is mounted correctly and visible to all nodes in the cluster, and that its permissions are correct. Check the ASM entries in the alert log file for more details.
CRS-01022: The Oracle Clusterware was forcibly upgraded without upgrading nodes <varname>string</varname>. Version has changed from [<varname>number</varname>, <varname>string</varname>] to [<varname>number</varname>, <varname>string</varname>]. Details in <varname>string</varname>.: 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 <varname>string</varname> in <varname>string</varname>.: 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: The Oracle Clusterware was upgraded to [<varname>string</varname>] on all nodes, but the cluster operating version is still [<varname>string</varname>]. Details in [<varname>string</varname>].: Cause: The cluster upgrade did not complete because the root upgrade script failed on the last node, the root upgrade script was interrupted by the user, or the cluster upgrade is ongoing.; Action: Check the Oracle Clusterware alert log on all nodes for any problems. Rerun the root upgrade script on the last node to completion, and ensure that the cluster operating version has changed using the 'crsctl query crs activeversion' command. If the problem persists, run diagcollection.pl and contact Oracle Support Services.
CRS-01026: The Oracle Clusterware patch has completed. The patch level has changed from [<varname>number</varname>] to [<varname>number</varname>]. Details in <varname>string</varname>.: Cause: The Oracle Clusterware was successfully patched.; Action: None
CRS-01027: The Oracle Cluster Registry (OCR) location in an ASM disk group [<varname>string</varname>] does not have sufficient space. Details at <varname>string</varname> in <varname>string</varname>.: 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 <varname>string</varname> is inaccessible from node <varname>string</varname>. Details in <varname>string</varname>.: Cause: The backup location provided did not exist, was not mounted correctly, or did not have the required permissions.; Action: Ensure that the backup location exists, that it is mounted correctly and visible to all nodes in the cluster, and that the permissions are correct. If the backup location is an ASM disk group, check the ASM entries in the alert log file for more details.
CRS-01110: The Oracle Clusterware upgrade is in unknown state [<varname>number</varname>].\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 Oracle Clusterware. Details [<varname>string</varname>].\n: Cause: There was an internal error upgrading the Oracle Clusterware.; Action: Verify using the 'crsctl check crs' command that the CRS Service running. Retry the 'crsctl set crs activeversion' command. If the problem persists, contact Oracle Support Services.
CRS-01112: Failed to set the Oracle Clusterware operating version <varname>string</varname>: 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 [<varname>string</varname>] 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: Oracle Clusterware upgrade 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 Oracle Clusterware.\n: Cause: An attempt was made to change the Oracle Clusterware operating version before all nodes were upgraded.; Action: Run root.sh script on all nodes in the cluster. If the problem persists, contact Oracle Support Services.
CRS-01119: Unable to complete Oracle Clusterware upgrade while nodes <varname>string</varname> have not yet upgraded\n: Cause: An attempt was made to change the Oracle Clusterware operating version before all known nodes had been upgraded. Note that some of the nodes listed in the message may no longer be current or recent cluster members.; Action: Issue the 'olsnodes' command to list current and recent cluster members. Any nodes listed in the error message, but not listed by 'olsnodes' have not been active recently, and should be deleted using the procedure documented in the Oracle Clusterware documentation. The currently or recently active cluster members listed by 'olsnodes' should be upgraded, or, if no longer needed, deleted: 1) Run the rootupgrade.sh script on each node to be retained. 2) Delete nodes no longer desired using the procedure documented in the Oracle Clusterware documentation. Once all of the nodes listed in the message have been upgraded or deleted, run the rootupgrade.sh script on an upgraded node to complete the upgrade. If one or more nodes could not upgraded or deleted, forcibly upgrade the cluster using the procedure documented in the Oracle Clusterware documentation.
CRS-01121: Oracle Clusterware was forcibly upgraded without upgrading nodes <varname>string</varname>.\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 [<varname>string</varname>] 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: Verify using the 'crsctl check crs' command that the Cluster Ready Services (CRS) is active, and inspect the accompanying Clusterware-specific error messages to see if there is a correctable problem. If so, correct the problem and retry the 'crsctl start rollingupgrade' command. If the problem persists, contact Oracle Support Services.
CRS-01134: There was an error setting Oracle ASM to rolling upgrade mode.: Cause: There was an error setting Oracle ASM to rolling upgrade mode.; Action: Verify using the 'srvctl status asm' command that the Oracle ASM instance is active, and inspect the accompanying ASM-specific error messages to see if there is a correctable problem. If so, correct the problem and retry the 'crsctl start rollingupgrade' command. If the problem persists, contact Oracle Support Services.
CRS-01135: There was an error setting Oracle IOServer to rolling upgrade mode.: Cause: There was an error setting Oracle IOServer to rolling upgrade mode.; Action: Verify using the 'srvctl status ioserver' command that the Oracle IOServer instance is active, and inspect the accompanying IOServer-specific error messages to see if there is a correctable problem. If so, correct the problem and retry the 'crsctl start rollingupgrade' command. If the problem persists, contact Oracle Support Services.
CRS-01136: Rejecting the rolling upgrade mode change because the cluster is being patched.: Cause: The rolling upgrade mode change was rejected because the cluster was being patched.; Action: Complete applying the patch on all nodes in the cluster before retrying the 'crsctl start rollingupgrade' command.
CRS-01137: Rejecting the rolling upgrade mode change because the cluster was forcibly upgraded.: 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 [<varname>string</varname>] 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 [<varname>string</varname>] cannot be less than or equal to the release version [<varname>string</varname>].: 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 [<varname>string</varname>] cannot be less than or equal to the cluster active version [<varname>string</varname>].: Cause: A version was passed that was less than or equal to the cluster active version.; Action: Verify that the version of the Oracle Grid Infrastructure home to be upgraded to is greater than the cluster active version.
CRS-01142: The cluster cannot be set to rolling upgrade mode because Oracle Clusterware is not active on at least one remote node.: Cause: The cluster could not be set to rolling upgrade mode because Oracle Clusterware was not active on any of the remote nodes.; Action: Start Oracle Clusterware on at least one remote node and retry the 'crsctl start rollingupgrade' command, or retry upgrade using the non-rolling option.
CRS-01151: The cluster was successfully set to rolling patch mode.\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: Verify using the 'crsctl check crs' command that the Cluster Ready Services (CRS) is active, and inspect the accompanying Clusterware-specific error messages to see if there is a correctable problem. If so, correct the problem and retry the 'crsctl start rollingpatch' command. If the problem persists, contact Oracle Support Services.
CRS-01154: There was an error setting Oracle ASM to rolling patch mode.: Cause: There was an error setting Oracle ASM to rolling patch mode.; Action: Verify using the 'srvctl status asm' command that the Oracle ASM instance is active, and inspect the accompanying ASM-specific error messages to see if there is a correctable problem. If so, correct the problem and retry the 'crsctl start rollingpatch' command. If the problem persists, contact Oracle Support Services.
CRS-01155: There was an error setting Oracle IOServer to rolling patch mode.: Cause: There was an error setting Oracle IOServer to rolling patch mode.; Action: Verify using the 'srvctl status ioserver' command that the Oracle IOServer instance is active, and inspect the accompanying IOServer-specific error messages to see if there is a correctable problem. If so, correct the problem and retry the 'crsctl start rollingpatch' command. If the problem persists, contact Oracle Support Services.
CRS-01156: Rejecting the rolling patch mode change because the cluster is in the middle of an upgrade.: Cause: The rolling patch mode change was rejected because the cluster was undergoing an upgrade.; Action: None
CRS-01157: Rejecting the rolling patch mode change because the cluster was forcibly upgraded.: Cause: The rolling patch mode change was rejected because the cluster was forcibly upgraded.; Action: Delete the nodes that were not upgraded using the procedure documented in the Oracle Clusterware documentation. Retry the 'crsctl start rollingpatch' or 'crsctl stop rollingpatch' command after completing the above steps.
CRS-01158: There was an error setting the cluster to rolling patch mode.: Cause: There was an internal error setting the cluster to rolling patch mode.; Action: Retry the 'crsctl start rolling patch' command. If the problem persists, contact Oracle Support Services.
CRS-01159: The cluster cannot be set to rolling patch mode because Oracle Clusterware is not active on at least one remote node.: Cause: The cluster could not be set to rolling patch mode because Oracle Clusterware was not active on any of the remote nodes.; Action: Start Oracle Clusterware on at least one remote node and retry the 'crsctl start rollingpatch' command, or retry patching using the non-rolling option.
CRS-01161: The cluster was successfully patched to patch level [<varname>number</varname>].\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 <varname>string</varname> is not the same as the expected patch level [<varname>number</varname>] found on nodes <varname>string</varname>.: 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 <varname>host</varname>' command. Retry the 'crsctl stop rollingpatch' command after patching the required nodes.
CRS-01163: There was an error resetting Oracle Clusterware rolling patch mode.: Cause: There was an error resetting Oracle Clusterware rolling patch mode.; Action: Verify using the 'crsctl check crs' command that the Cluster Ready Services (CRS) is active, and inspect the accompanying Clusterware-specific error messages to see if there is a correctable problem. If so, correct the problem and retry the 'crsctl stop rollingpatch' command. If the problem persists, contact Oracle Support Services.
CRS-01164: There was an error resetting Oracle ASM rolling patch mode.: Cause: There was an error resetting Oracle ASM rolling patch mode.; Action: Verify using the 'srvctl status asm' command that the Oracle ASM instance is active, and inspect the accompanying ASM-specific error messages to see if there is a correctable problem. If so, correct the problem and retry the 'crsctl stop rollingpatch' command. If the problem persists, contact Oracle Support Services.
CRS-01165: There was an error resetting Oracle IOServer rolling patch mode.: Cause: There was an error resetting Oracle IOServer rolling patch mode.; Action: Verify using the 'srvctl status ioserver' command that the Oracle IOServer instance is active, and inspect the accompanying IOServer-specific error messages to see if there is a correctable problem. If so, correct the problem and retry the 'crsctl stop rollingpatch' command. If the problem persists, contact Oracle Support Services.
CRS-01166: Rejecting rolling patch mode change because Oracle ASM is in [<varname>string</varname>] 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 [<varname>string</varname>] 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 [<varname>number</varname>].: 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 [<varname>number</varname>] on this node is not the same as the expected patch level [<varname>number</varname>].: 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 <varname>host</varname>' 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 <varname>string</varname> is not the same as the patch level [<varname>number</varname>] found on nodes <varname>string</varname>.: Cause: The 'crsctl stop rollingpatch' command was rejected because all the nodes in the cluster were not patched to the same patch level.; Action: Verify the list of patches applied on a node by issuing the the 'crsctl query crs releasepatch' command. Apply the requisite patches. Make sure all the nodes in the cluster have been patched to the same patch level using the 'crsctl query crs softwarepatch' command. Retry the 'crsctl stop rollingpatch' command after patching the required nodes.
CRS-01181: There was an error retrieving the Oracle Clusterware release patch level.: Cause: There was an internal error retrieving the Oracle Clusterware release patch level.; Action: Contact Oracle Support Services.
CRS-01182: Oracle Clusterware release patch level is [<varname>number</varname>] and the complete list of patches [<varname>string</varname>] have been applied on the local node.\n: Cause: None, this is an informational message.; Action: None
CRS-01183: Oracle Clusterware release patch level is [<varname>number</varname>] and an incomplete list of patches [<varname>string</varname>] 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 [<varname>number</varname>] and no patches have been applied on the local node.\n: Cause: None, this is an informational message.; Action: None
CRS-01191: There was an error retrieving the Oracle Clusterware software patch level.: Cause: There was an internal error retrieving the Oracle Clusterware software patch level.; Action: Contact Oracle Support Services.
CRS-01192: Oracle Clusterware patch level on node <varname>string</varname> is [<varname>number</varname>].\n: Cause: None, this is an informational message.; Action: None
CRS-01201: CRSD started on node <varname>string</varname>.: 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 <varname>string</varname>. Error [<varname>string</varname>]. Details in <varname>string</varname>.: 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 <varname>string</varname>. Details in <varname>string</varname>.: 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 <varname>string</varname>.: 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 <varname>string</varname>. Details in <varname>string</varname>.: 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 <varname>string</varname> 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 <varname>string</varname>. 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 <varname>string</varname> in <varname>string</varname>.: 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 '<varname>string</varname>'. Details at <varname>string</varname> in <varname>string</varname>.: 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 <varname>string</varname> in <varname>string</varname>.: Cause: Cluster Ready Service failed to update the group private data with new master.; Action: Restart Cluster Ready Service using the command 'crsctl start clusterware'. If the problem persists, contact Oracle Support Services.
CRS-01211: Cluster Ready Service noticed abnormal termination by Cluster Synchronization Service. Details at <varname>string</varname> in <varname>string</varname>.: 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 <varname>string</varname> in <varname>string</varname>.: Cause: This is an internal error.; Action: Contact Oracle Support Services.
CRS-01213: Cluster Ready Service failed to retrieve user information. Details at <varname>string</varname> in <varname>string</varname>.: Cause: This is an internal error.; Action: Contact Oracle Support Services.
CRS-01214: Cluster Ready Service failed to initialize OLR context. Details at <varname>string</varname> in <varname>string</varname>.: 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 <varname>string</varname> in <varname>string</varname>.: 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 <varname>string</varname> in <varname>string</varname>.: Cause: This is an internal error.; Action: Contact Oracle Support Services.
CRS-01217: Cluster Ready Service unable to get node name. Details at <varname>string</varname> in <varname>string</varname>.: Cause: Cluster Ready Service could not determine node name.; Action: Contact Oracle Support Services.
CRS-01218: Cluster Ready Service error during initialization. Details at <varname>string</varname> in <varname>string</varname>.: Cause: Cluster Ready Service could not initialize underlying layers successfully.; Action: Contact Oracle Support Services.
CRS-01219: Cluster Synchronization Service not available. Details at <varname>string</varname> in <varname>string</varname>.: 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 <varname>string</varname> in <varname>string</varname>.: 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 <varname>string</varname> in <varname>string</varname>.: 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 <varname>string</varname> in <varname>string</varname>.: 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 <varname>string</varname> in <varname>string</varname>.: Cause: Could not retrieve cluster active version.; Action: Contact Oracle Support Services.
CRS-01224: Server authentication exception encountered, exception text is '<varname>string</varname>'. Details at <varname>string</varname> in <varname>string</varname>.: 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 '<varname>string</varname>'. Details at <varname>string</varname> in <varname>string</varname>.: 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 <varname>string</varname> in <varname>string</varname>.: 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 <varname>string</varname> in <varname>string</varname>.: 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 <varname>string</varname> in <varname>string</varname>.: 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 <varname>string</varname> in <varname>string</varname>.: Cause: Cluster Ready Service encountered communication error.; Action: This is an internal error. Contact Oracle Support Services.
CRS-01231: Failed to open key '<varname>string</varname>' in OCR. Details at <varname>string</varname> in <varname>string</varname>.: 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 '<varname>string</varname>' in OCR. Details at <varname>string</varname> in <varname>string</varname>.: 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 <varname>string</varname> in <varname>string</varname>.: 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 '<varname>string</varname>' in OCR. Details at <varname>string</varname> in <varname>string</varname>.: 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 <varname>string</varname> in <varname>string</varname>.: 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 '<varname>string</varname>' in OCR. Details at <varname>string</varname> in <varname>string</varname>.: 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 <varname>string</varname> in <varname>string</varname>.: 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 '<varname>string</varname>' to a batch in OCR. Details at <varname>string</varname> in <varname>string</varname>.: 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 [<varname>string</varname>]. Details at <varname>string</varname> in <varname>string</varname>.: 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 <varname>string</varname>.: 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 <varname>string</varname>. Error [<varname>string</varname>]. Details in <varname>string</varname>.: 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 <varname>string</varname>. Details in <varname>string</varname>.: 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 <varname>string</varname>.: 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 <varname>string</varname>. Details in <varname>string</varname>.: 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 <varname>string</varname> 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 <varname>string</varname>. 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 <varname>string</varname> in <varname>string</varname>.: 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 '<varname>string</varname>'. Details at <varname>string</varname> in <varname>string</varname>.: 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 <varname>string</varname> in <varname>string</varname>.: Cause: Oracle High Availability Service failed to update the group private data with new master.; Action: Restart your clusterware installation. If the problem persists, contact Oracle Support Services.
CRS-01311: Oracle High Availability Service noticed abnormal termination by Cluster Synchronization Service. Details at <varname>string</varname> in <varname>string</varname>.: 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 <varname>string</varname> in <varname>string</varname>.: Cause: This is an internal error.; Action: Contact Oracle Support Services.
CRS-01313: Oracle High Availability Service failed to retrieve user information. Details at <varname>string</varname> in <varname>string</varname>.: Cause: This is an internal error.; Action: Contact Oracle Support Services.
CRS-01314: Oracle High Availability Service failed to initialize OLR context. Details at <varname>string</varname> in <varname>string</varname>.: 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 <varname>string</varname> in <varname>string</varname>.: 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 <varname>string</varname> in <varname>string</varname>.: Cause: This is an internal error.; Action: Contact Oracle Support Services.
CRS-01317: Oracle High Availability Service unable to get node name. Details at <varname>string</varname> in <varname>string</varname>.: 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 <varname>string</varname> in <varname>string</varname>.: 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 <varname>string</varname> in <varname>string</varname>.: 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 <varname>string</varname> in <varname>string</varname>.: 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 <varname>string</varname> in <varname>string</varname>.: 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 <varname>string</varname> in <varname>string</varname>.: 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 <varname>string</varname> in <varname>string</varname>.: Cause: Could not retrieve cluster active version.; Action: Contact Oracle Support Services.
CRS-01324: Server authentication exception encountered, exception text is '<varname>string</varname>'. Details at <varname>string</varname> in <varname>string</varname>.: 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 '<varname>string</varname>'. Details at <varname>string</varname> in <varname>string</varname>.: 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 <varname>string</varname> in <varname>string</varname>.: 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 <varname>string</varname> in <varname>string</varname>.: 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 <varname>string</varname> in <varname>string</varname>.: 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 <varname>string</varname> in <varname>string</varname>.: 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 '<varname>string</varname>' in OLR. Details at <varname>string</varname> in <varname>string</varname>.: 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 '<varname>string</varname>' in OLR. Details at <varname>string</varname> in <varname>string</varname>.: 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 <varname>string</varname> in <varname>string</varname>.: 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 '<varname>string</varname>' in OLR. Details at <varname>string</varname> in <varname>string</varname>.: 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 <varname>string</varname> in <varname>string</varname>.: 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 '<varname>string</varname>' in OLR. Details at <varname>string</varname> in <varname>string</varname>.: 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 <varname>string</varname> in <varname>string</varname>.: 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 '<varname>string</varname>' to a batch in OLR. Details at <varname>string</varname> in <varname>string</varname>.: 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 [<varname>string</varname>]. Details at <varname>string</varname> in <varname>string</varname>.: Cause: Look at the associated error message to fix the underlying issue.; Action: If the problem persists, contact Oracle Support Services.
CRS-01340: Node '<varname>string</varname>' 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 <varname>string</varname>.: 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 <varname>string</varname>. Error [<varname>string</varname>]. Details in <varname>string</varname>.: 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 <varname>string</varname>. Listening port <varname>number</varname> is in use by another application. Details in <varname>string</varname>.: 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 <varname>string</varname>.: Cause: A node joined or left the cluster.; Action: None
CRS-01602: CSSD aborted on node <varname>string</varname>. Error [<varname>string</varname>]; details in <varname>string</varname>.: 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 <varname>string</varname> shutdown by user.: Cause: The CSS daemon on the listed node was terminated by a user.; Action: None
CRS-01604: CSSD voting file is offline: <varname>string</varname>; details at <varname>string</varname> in <varname>string</varname>.: Cause: The listed voting file became unusable on the local node.; Action: Verify that the filesystem containing the listed voting file is available on the local node.
CRS-01605: CSSD voting file is online: <varname>string</varname>; details in <varname>string</varname>.: Cause: The CSS daemon has detected a valid configured voting file.; Action: None
CRS-01606: The number of voting files available, <varname>number</varname>, is less than the minimum number of voting files required, <varname>number</varname>, resulting in CSSD termination to ensure data integrity; details at <varname>string</varname> in <varname>string</varname>: 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 <varname>string</varname> is being evicted in cluster incarnation <varname>number</varname>; details at <varname>string</varname> in <varname>string</varname>.: 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 <varname>number</varname>, <varname>string</varname>; details at <varname>string</varname> in <varname>string</varname>.: 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 <varname>string</varname> in <varname>string</varname>.: 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 <varname>string</varname> (<varname>number</varname>) missing for 90%% of timeout interval. Removal of this node from cluster in <varname>number</varname>.<varname>number</varname> seconds: Cause: Did not receive heartbeat messages from the node. This could be due to network problems or failure of the listed node.; Action: Check if the private interconnect network used by cluster is functioning properly, including all the cables, network cards, switches/routers etc. between this node and listed node. Correct any problems discovered.
CRS-01611: Network communication with node <varname>string</varname> (<varname>number</varname>) missing for 75%% of timeout interval. Removal of this node from cluster in <varname>number</varname>.<varname>number</varname> seconds: Cause: Did not receive heartbeat messages from the node. This could be due to network problems or failure of the listed node.; Action: Check if the private interconnect network used by cluster is functioning properly, including all the cables, network cards, switches/routers etc. between this node and listed node. Correct any problems discovered.
CRS-01612: Network communication with node <varname>string</varname> (<varname>number</varname>) missing for 50%% of timeout interval. Removal of this node from cluster in <varname>number</varname>.<varname>number</varname> seconds: Cause: Did not receive heartbeat messages from the node. This could be due to network problems or failure of listed node.; Action: Check if the private interconnect network used by cluster is functioning properly, including all the cables, network cards, switches/routers etc. between this node and listed node. Correct any problems discovered.
CRS-01613: No I/O has completed after 90%% of the maximum interval. Voting file <varname>string</varname> will be considered not functional in <varname>number</varname> milliseconds: Cause: Voting device I/O has not completed for a long time. This could be due some error with the device the voting file is on or in some element in the path of the I/O to the device.; Action: Verify that the device is working properly including all elements in the I/O path. The voting file listed will be considered inactive in the number of milliseconds specified. Failure of a majority of devices will result in node reboot.
CRS-01614: No I/O has completed after 75%% of the maximum interval. Voting file <varname>string</varname> will be considered not functional in <varname>number</varname> milliseconds: Cause: Voting device I/O has not completed for a long time. This could be due some error with the device the voting file is on or in some element in the path of the I/O to the device.; Action: Verify that the device is working properly including all elements in the I/O path. The voting file listed will be considered inactive in the number of milliseconds specified. Failure of a majority of devices will result in node reboot.
CRS-01615: No I/O has completed after 50%% of the maximum interval. Voting file <varname>string</varname> will be considered not functional in <varname>number</varname> milliseconds: Cause: Voting device I/O has not completed for a long time. This could be due some error with the device the voting file is on or in some element in the path of the I/O to the device.; Action: Verify that the device is working properly including all elements in the I/O path. The voting file listed will be considered inactive in the number of milliseconds specified. Failure of a majority of devices will result in node reboot.
CRS-01616: The BMC device used for IPMI at IP address <varname>string</varname> is not properly configured for ADMIN access; details at <varname>string</varname> in <varname>string</varname>: 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 <varname>string</varname> is incomplete; details at <varname>string</varname> in <varname>string</varname>: 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 <varname>string</varname>; details at <varname>string</varname> in <varname>string</varname>: 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 <varname>string</varname> could not be validated by this node due to failure in connecting to the IPMI device; details at <varname>string</varname> in <varname>string</varname>: 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 <varname>string</varname> could not be validated by this node due to invalid authorization information; details at <varname>string</varname> in <varname>string</varname>: 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 <varname>string</varname> in <varname>string</varname>: 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 <varname>string</varname>; details at <varname>string</varname> in <varname>string</varname>: 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 <varname>string</varname> could not be validated due to invalid authorization information. The BMC username provided is '<varname>string</varname>'; details at <varname>string</varname> in <varname>string</varname>: 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 <varname>string</varname>, number <varname>number</varname>, 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 <varname>string</varname> in <varname>string</varname>: 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 <varname>string</varname> in <varname>string</varname>: 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 <varname>string</varname> in <varname>string</varname>: 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 <varname>string</varname> in <varname>string</varname>: 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 <varname>string</varname> in <varname>string</varname>: 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 <varname>string</varname> is being removed from the cluster in cluster incarnation <varname>number</varname>: 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 <varname>string</varname> in vendor clusterware; details at <varname>string</varname> in <varname>string</varname>: 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 <varname>string</varname> in <varname>string</varname>: 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 <varname>string</varname> in <varname>string</varname>: 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 <varname>string</varname> and is terminating; details at <varname>string</varname> in <varname>string</varname>: 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 <varname>string</varname>; details at <varname>string</varname> in <varname>string</varname>: 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 <varname>string</varname> that is being added to the list of configured voting files; details at <varname>string</varname> in <varname>string</varname>: 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 <varname>number</varname>:<varname>number</varname> because another configuration change is already in progress; details at <varname>string</varname> in <varname>string</varname>: 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 <varname>number</varname>:<varname>number</varname> because one or more new voting files in the new configuration could not be found; details at <varname>string</varname> in <varname>string</varname>: 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 <varname>number</varname>:<varname>number</varname> because only <varname>number</varname> of the required <varname>number</varname> voting files of the new configuration were located; details at <varname>string</varname> in <varname>string</varname>: 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 <varname>number</varname> is using a different CSS configuration from the one used by this node; this node is terminating to preserve integrity; details at <varname>string</varname> in <varname>string</varname>: 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 <varname>string</varname>: 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-<varname>number</varname>; details at <varname>string</varname> in <varname>string</varname>: 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-<varname>number</varname>; details at <varname>string</varname> in <varname>string</varname>: 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-<varname>number</varname>; details at <varname>string</varname> in <varname>string</varname>: 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-<varname>number</varname>; details at <varname>string</varname> in <varname>string</varname>: 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-<varname>number</varname>; details at <varname>string</varname> in <varname>string</varname>: 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: <varname>string</varname>; details at <varname>string</varname> in <varname>string</varname>.: 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 <varname>number</varname>:<varname>number</varname> rejected by node <varname>number</varname> <varname>string</varname>; details at <varname>string</varname> in <varname>string</varname>: 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 <varname>number</varname>:<varname>number</varname> rejected because it would make the active version of node <varname>number</varname> lower than the current setting <varname>string</varname> of this node; details at <varname>string</varname> in <varname>string</varname>: 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 <varname>string</varname> detected a problem and started to shutdown.: Cause: The CSS daemon on the listed node detected a problem and started to shutdown.; Action: Check the CRS alert log.
CRS-01656: The CSS daemon is terminating due to a fatal error; Details at <varname>string</varname> in <varname>string</varname>: 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 <varname>string</varname> in <varname>string</varname>: 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 <varname>string</varname> in <varname>string</varname>: 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 <varname>string</varname> failed; Details at <varname>string</varname> in <varname>string</varname>: Cause: To protect data integrity a node kill was attempted for the indicated node, but it failed.; Action: Collect the Clusterware alert log and the CSSD log of this node as well as the CSS daemon logs of all other nodes in the cluster and contact Oracle Support Services.
CRS-01660: The CSS daemon shutdown has completed: Cause: A command to shut down the CSS daemon was issued by a user and the shutdown processing is completed. The CSS daemon is terminated.; Action: No action is required.
CRS-01661: The CSS daemon is not responding. Reboot will occur in <varname>number</varname> milliseconds; Details at <varname>string</varname> in <varname>string</varname>: Cause: The CSS daemon is failing to respond.; Action: Collect the Clusterware alert log and the CSSD log of this node as well as the CSS daemon logs of all other nodes in the cluster and contact Oracle Support Services.
CRS-01662: Member kill requested by node <varname>string</varname> for member number <varname>number</varname>, group <varname>string</varname>: 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 <varname>string</varname> for <varname>number</varname> members, group <varname>string</varname>. Details at <varname>string</varname> in <varname>string</varname>.: 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 <varname>string</varname> 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 <varname>number</varname> is less than the minimum number of voting files required <varname>number</varname>.: 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 <varname>string</varname> in <varname>string</varname>: 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 <varname>string</varname> is outside the allowed range of <varname>number</varname> to <varname>number</varname>\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 <varname>number</varname> has fallen to the minimum number of voting files required <varname>number</varname>.: Cause: The Cluster Synchronization Service daemon (CSSD) has detected that the number of voting files currently available is equal to the minimum number of voting files required on the node. There is risk of node eviction in the case of another voting disk failure.; Action: Restore access to voting files or configure additional voting disks so that the number of voting files currently available is more than the minimum number of voting files required.
CRS-01701: Initialization of the required component GIPC failed; details at <varname>string</varname> in <varname>string</varname>: 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 <varname>string</varname> in <varname>string</varname>: 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 <varname>string</varname> in <varname>string</varname>: 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 <varname>string</varname> failed; details at <varname>string</varname> in <varname>string</varname>: 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 <varname>number</varname> configured voting files but <varname>number</varname> voting files are required, terminating to ensure data integrity; details at <varname>string</varname> in <varname>string</varname>: 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 <varname>number</varname> of <varname>number</varname> voting files in a pending configuration change but <varname>number</varname> voting files are required, terminating to ensure data integrity; details at <varname>string</varname> in <varname>string</varname>: 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 <varname>string</varname> number <varname>number</varname> completed: Cause: CSSD acquired a node number through a lease acquisition procedure.; Action: None
CRS-01708: Lease acquisition failed for node <varname>string</varname> because all lease slots are in use; Details at <varname>string</varname> in <varname>string</varname>: 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 <varname>string</varname> because no voting file has been configured; Details at <varname>string</varname> in <varname>string</varname>: 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 <varname>string</varname> because CSSD failed to access majority of voting files; Details at <varname>string</varname> in <varname>string</varname>: 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 <varname>number</varname> to <varname>number</varname>: 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 <varname>string</varname>; Details at <varname>string</varname> in <varname>string</varname>: 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 <varname>string</varname> mode: Cause: CSSD has been started on the node.; Action: None
CRS-01714: Unable to discover any voting files, retrying discovery in <varname>number</varname> seconds; Details at <varname>string</varname> in <varname>string</varname>: Cause: No voting files were discovered. Possible reasons include: - The filesystems the voting files are on are not available - The voting files have been deleted - The voting files are corrupted; Action: Verify that the filesystems that the voting files are on are active and that the voting files have not been damaged. If necessary, start the clusterware stack in exclusive mode using 'crsctl start crs -excl' and add voting files using 'crsctl add css votedisk'
CRS-01715: A failure occurred in the CSS daemon during initialization; Details at <varname>string</varname> in <varname>string</varname>: 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 <varname>string</varname> is lower than the active version <varname>string</varname>; Details at <varname>string</varname> in <varname>string</varname>: 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 <varname>string</varname> in <varname>string</varname>: 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 <varname>string</varname>.: 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 (CSSD) <varname>string</varname> not scheduled for <varname>number</varname> msecs.: Cause: Excessive system load has prevented threads in the Cluster Synchronization Service daemon (CSSD) from being scheduled for execution for the time indicated in the message. This indicates the system is overloaded.; Action: Take steps to reduce the system load or increase system resources to handle the load.
CRS-01801: Cluster <varname>string</varname> configured with nodes <varname>string</varname>.: Cause: None.; Action: None
CRS-01802: Node <varname>string</varname> added to cluster.: Cause: None.; Action: None
CRS-01803: Node <varname>string</varname> deleted from cluster.: Cause: None.; Action: None
CRS-01804: Node <varname>string</varname> upgraded to version <varname>string</varname>.: Cause: None.; Action: None
CRS-01805: Unable to connect to the CSS daemon, return code <varname>number</varname>: 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 <varname>number</varname>: 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 <varname>string</varname> in <varname>string</varname>.: Cause: This is an internal error.; Action: Contact Oracle Support Services.
CRS-01808: Node-specific configuration for node <varname>string</varname> in Oracle Local Registry was upgraded to version <varname>string</varname>.: Cause: None.; Action: None
CRS-01809: The cluster configuration command failed to open OCR or OLR key <varname>string</varname>. Details at <varname>string</varname> in <varname>string</varname>.: 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 <varname>string</varname> in Oracle Local Registry was patched to patch level <varname>number</varname>.: Cause: None.; Action: None
CRS-01811: Node <varname>string</varname> patched to patch level <varname>number</varname>.: Cause: None.; Action: None
CRS-01901: CRS service setting (<varname>string</varname>) is changed from [<varname>string</varname>] to [<varname>string</varname>].: 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 <varname>string</varname> to <varname>string</varname> refused: Cause: User command cannot connect to the target process.; Action: The user may not have sufficient privilege to connect.
CRS-02003: error <varname>number</varname> encountered when connecting to <varname>string</varname>: 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 <varname>number</varname> encountered when sending messages to <varname>string</varname>: 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 <varname>string</varname>: Cause: the target process does not return acknowledgment in time.; Action: Retry again at a later time.
CRS-02006: error <varname>number</varname> encountered when receiving messages from <varname>string</varname>: 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 <<varname>string</varname>> 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 <<varname>number</varname>> used: Cause: an unrecognized message type was sent.; Action: Retry with a valid command again.
CRS-02009: unable to get authentication for user <varname>string</varname>: Cause: current user was not authenticated for connection.; Action: Log in as another user and try again.
CRS-02010: invalid response message from <varname>string</varname>: Cause: Response message has incorrect format.; Action: Retry again at a later time.
CRS-02011: no response at index <varname>number</varname> in response message from <varname>string</varname>: 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 <varname>string</varname> 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 <varname>number</varname>.: Cause: Successfully formatted the OLR location(s).; Action: None
CRS-02102: The OLR was restored from file <varname>string</varname>.: 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 <varname>number</varname>.: 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 <varname>string</varname>.: Cause: Successfully imported the OLR contents from a file.; Action: None
CRS-02105: The OLR upgrade was completed. Version has changed from <varname>number</varname> to <varname>number</varname>. Details in <varname>string</varname>.: Cause: The OLR was successfully upgraded to a newer block format.; Action: None
CRS-02106: The OLR location <varname>string</varname> is inaccessible. Details in <varname>string</varname>.: 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 <varname>string</varname>.: Cause: The OLR was successfully started.; Action: None
CRS-02114: Failed to import Oracle Local Registry from file <varname>string</varname>: Cause: Unable to read data from the import file and import to the local registry; Action: Check availability of the local registry and the details of the failure from the log file
CRS-02120: The Oracle Local Registry has invalid contents. Details at <varname>string</varname> in <varname>string</varname>.: Cause: Some of the Oracle Local Registry contents were invalid.; Action: Check the log file indicated in the message for more details. Use the 'ocrcheck -local' command to detect errors, and the 'ocrdump -local' command to review the registry contents. If problems exist, the registry may need to be recovered or restored. If the problem persists, contact Oracle Support Services.
CRS-02301: GPnP: <varname>string</varname>: Cause: This conveys a message from the GPnP layer to the alert log.; Action: Look up the imbedded message and respond accordingly.
CRS-02302: Cannot get GPnP profile. Error <varname>string</varname> (<varname>string</varname>).: Cause: Get GPnP profile operation failed.; Action: n/a
CRS-02303: GPNPD is not running on local node.: Cause: GPNPD is not running on local node. GPnP request cannot be completed.; Action: Make sure GPNPD is running and retry the operation.
CRS-02304: GPnP profile signature verification failed. <varname>string</varname> 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: GPnP service on host "<varname>string</varname>" not found.: Cause: Remote GPnP service on requested host were not found in resource discovery results.; Action: Make sure host is up, clusterware GPnP services (MDNSD and GPNPD) are up and running and network connection is operational.
CRS-02310: Failed to initialize security facility.: Cause: Error occurred while initializing GPnP security component.; Action: If the problem persists, contact Oracle Support Services.
CRS-02311: Failed to initialize Resource Discovery. RD error: <varname>string</varname>. Make sure RD providers installed properly.: Cause: Error occurred while initializing GPnP Resource Discovery (RD).; Action: If the problem persists, contact Oracle Support Services.
CRS-02312: Failed to initialize XML Developer's Kit (XDK). XDK error <varname>string</varname>.: 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: <varname>string</varname>.: Cause: Error occurred while initializing GIPC communication layer.; Action: If the problem persists, contact Oracle Support Services.
CRS-02314: Cannot initialize locking subsystem.: Cause: Error occurred while initializing locking subsystem.; Action: If the problem persists, contact Oracle Support Services.
CRS-02315: Failed to initialize GPnP certkey providers.: Cause: GPnP certkey provider(s) data was not found or corrupt.; Action: If the problem persists, contact Oracle Support Services.
CRS-02316: Cannot initialize GPnP, <varname>string</varname> (<varname>string</varname>).: Cause: General GPnP initialization failure.; Action: If the problem persists, contact Oracle Support Services.
CRS-02317: Cannot get local GPnP security keys (wallet).: Cause: GPnP wallet(s) directory or files were not found or corrupt.; Action: If the problem persists, contact Oracle Support Services.
CRS-02318: GPNPD is not found.: Cause: Local GPnP service is not found.; Action: Make sure GPNPD is running.
CRS-02319: No cluster name found in GPnP profile.: Cause: Profile is invalid - it must specify a mandatory clustername parameter.; Action: Contact Oracle Support Services.
CRS-02320: No sequence number found in GPnP profile.: Cause: Profile is invalid - it must specify a mandatory profile sequence parameter.; Action: Contact Oracle Support Services.
CRS-02321: Flex Cluster mode configuration not found in Grid Plug and Play (GPnP) profile.: Cause: The Profile did not have Flex Cluster mode configuration and could not be used to bring up the stack in Flex Cluster mode.; Action: Contact Oracle Support Services.
CRS-02322: Cannot get local GPnP profile. Error initializing GPnP profile cache providers.: Cause: Local GPnP setup was invalid.; Action: Contact Oracle Support Services.
CRS-02323: Error initializing one of the GPnP profile cache providers.: Cause: Local GPnP setup was invalid.; Action: Contact Oracle Support Services.
CRS-02324: Errors occurred while trying to push GPnP profile.: Cause: GPnP profile update partially failed.; Action: Try to repeat the update. If the problem persists, contact Oracle Support Services.
CRS-02325: Unable to get GPnP profile from requested cluster nodes.: Cause: Get GPnP profile from remote nodes failed.; Action: Try to repeat the update. If the problem persists, contact Oracle Support Services.
CRS-02326: GPnP profile is different across cluster nodes. <varname>string</varname>.: Cause: GPnP profile was different across cluster nodes.; Action: Try to repeat the update. If the problem persists, contact Oracle Support Services.
CRS-02327: GPNPD already running on node <varname>string</varname>. Terminating.: Cause: GPnP service instance was already running on node.; Action: Bring down existing GPNPD instance first.
CRS-02328: GPNPD started on node <varname>string</varname>.: Cause: GPnP service started on node.; Action: None
CRS-02329: GPNPD on node <varname>string</varname> shut down.: Cause: GPnP service was shut down by request.; Action: None
CRS-02330: GPNPD failed to start listening for GPnP peers.: Cause: GPnP service failed to open server endpoint.; Action: Check GPNPD logs for the cause. If the problem persists, contact Oracle Support Services.
CRS-02331: Error getting GPnP profile from "<varname>string</varname>".: 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 GPnP profile to "<varname>string</varname>".: Cause: Push GPnP profile to remote node operation failed.; Action: Retry request. If the problem persists, contact Oracle Support Services.
CRS-02333: Could not write GPnP profile to local cache.: Cause: GPNPD service cannot save GPnP profile to local cache.; Action: Make sure there is at least 10MB of free disk space in Clusterware home. If the problem persists, contact Oracle Support Services.
CRS-02334: Could not delete pending GPnP profile from local cache.: Cause: GPNPD service cannot delete GPnP profile from local cache.; Action: If the problem persists, contact Oracle Support Services.
CRS-02335: Could not write pending GPnP profile to local cache.: Cause: GPNPD service cannot save GPnP profile to local cache.; Action: Make sure there is at least 10MB of free disk space in Clusterware home. If the problem persists, contact Oracle Support Services.
CRS-02336: GPNPD failed get local GPnP profile and cannot continue. Check gpnpd/gpnp client logs.: Cause: GPnP service cannot find a profile in local cache, and cannot continue.; Action: Contact Oracle Support Services.
CRS-02339: GPNPD advertisement with <varname>string</varname> failed. This may block some cluster configuration changes. Advertisement attempts will continue.: Cause: Grid Plug and Play Daemon (GPNPD) failed to advertise itself with a specified service (for example, Multicast Domain Name Service Daemon (MDNSD) or Oracle Grid Naming Service (GNS)). Advertisement attempts will continue at regular intervals, and alerts will periodically be issued.; Action: Make sure the specified service is running and wait for the success message CRS-2337 before changing the cluster configuration.
CRS-02340: Errors occurred while processing received gpnp message.: Cause: Invalid GPnP message received.; Action: Check gpnp client and GPNPD logs for details. If the problem persists, contact Oracle Support Services.
CRS-02341: GPNPD on node <varname>string</varname> shutting down on signal <varname>number</varname>.: Cause: GPnP service shutting down due to received signal.; Action: Contact your cluster administrator.
CRS-02342: GPnP messaging received error : <varname>string</varname> (<varname>string</varname>).: Cause: GPnP message error received.; Action: If the problem persists, contact Oracle Support Services.
CRS-02401: The Cluster Time Synchronization Service started on host <varname>string</varname>.: Cause: The Cluster Time Synchronization Service successfully started on the listed node.; Action: None
CRS-02402: The Cluster Time Synchronization Service aborted on host <varname>string</varname>. Details at <varname>string</varname> in <varname>string</varname>.: 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 <varname>string</varname> 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 <varname>string</varname>.: 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 <varname>string</varname> 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 <varname>string</varname>. Details in <varname>string</varname>.: 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 <varname>string</varname>.: Cause: A new Cluster Time Synchronization Service reference node has been elected.; Action: None
CRS-02408: The clock on host <varname>string</varname> 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 <varname>string</varname> is not synchronous with the mean cluster time. No action has been taken as the Cluster Time Synchronization Service is running in observer mode.: Cause: The clock was not in sync with the mean cluster time. No action has been taken as Cluster Time Synchronization Service is running in observer mode.; Action: Verify correct operation of the vendor time synchronization service on the node.
CRS-02410: The Cluster Time Synchronization Service on host <varname>string</varname> 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 <varname>string</varname>.: 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 <varname>string</varname>.: 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 '<varname>string</varname>' cannot be registered because its owner '<varname>string</varname>' is not the same as the Oracle Restart user '<varname>string</varname>'.: Cause: The resource indicated in the message could not be registered because it was owned by a user other than the Oracle Restart user.; Action: Resubmit as the Oracle Restart user.
CRS-02500: Cannot stop resource '<varname>string</varname>' 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 '<varname>string</varname>' 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 '<varname>string</varname>' has dependency error because of resource '<varname>string</varname>': 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 '<varname>string</varname>' 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 '<varname>string</varname>' 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 '<varname>string</varname>'. 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 '<varname>string</varname>' has been cancelled: Cause: A scheduled or running operation has been cancelled.; Action: None
CRS-02507: Unsupported modifier '<varname>string</varname>' in dependency '<varname>string</varname>': 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 '<varname>string</varname>': 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 '<varname>string</varname>' used in dependency '<varname>string</varname>' 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 '<varname>string</varname>' used in dependency '<varname>string</varname>' 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 '<varname>string</varname>' cannot be specified on per-X basis for resource '<varname>string</varname>': 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 '<varname>string</varname>' is invalid in resource '<varname>string</varname>': Cause: The specification does not follow valid format.; Action: Correct the specification and re-submit the request.
CRS-02513: Attribute format for '<varname>string</varname>' is invalid: Cause: The specification does not follow valid format.; Action: Correct the specification and re-submit the request.
CRS-02514: Dependency attribute specification '<varname>string</varname>' is invalid in resource '<varname>string</varname>': 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 '<varname>string</varname>': 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 '<varname>string</varname>': 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 '<varname>string</varname>' is not specified for resource '<varname>string</varname>': 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 '<varname>string</varname>' or '<varname>string</varname>' must be specified when '<varname>string</varname>' is '<varname>string</varname>': Cause: Neither or both of the parameters was specified.; Action: Specify exactly one of the two and re-submit.
CRS-02520: Invalid value '<varname>string</varname>' for attribute '<varname>string</varname>': 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 '<varname>string</varname>' 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 '<varname>string</varname>'/'<varname>string</varname>'/'<varname>string</varname>'/'<varname>string</varname>'/'<varname>string</varname>'/'<varname>string</varname>': 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 '<varname>string</varname>' 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 '<varname>string</varname>' to start on '<varname>string</varname>': 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 '<varname>string</varname>' because it has a '<varname>string</varname>' dependency on '<varname>string</varname>': 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 '<varname>string</varname>' 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 '<varname>string</varname>' because that would require stopping or relocating '<varname>string</varname>', 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 '<varname>string</varname>' because '<varname>string</varname>' has a stop-time '<varname>string</varname>' 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 '<varname>string</varname>': 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 '<varname>string</varname>': 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 '<varname>string</varname>' is down. Unable to perform the operation on '<varname>string</varname>': Cause: The server is down and therefore the operation cannot be performed.; Action: Try using a different server.
CRS-02534: Resource type '<varname>string</varname>' is not registered: Cause: The specified resource type is not registered.; Action: Re-evaluate the request.
CRS-02535: Resource type '<varname>string</varname>' does not have attribute '<varname>string</varname>' and thus it cannot be updated: Cause: An non-existing attribute cannot be modified.; Action: Re-evaluate the request.
CRS-02536: Required attribute '<varname>string</varname>' is not specified for '<varname>string</varname>': 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 '<varname>string</varname>' 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 '<varname>string</varname>' 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 '<varname>string</varname>' 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 '<varname>string</varname>' 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 '<varname>string</varname>' is not registered: Cause: The specified server pool is not registered.; Action: Re-evaluate the request.
CRS-02542: The tag '<varname>string</varname>' is mentioned in both '<varname>string</varname>' and '<varname>string</varname>' 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 '<varname>string</varname>': Cause: Value type specification is missing for the attribute.; Action: Specify a proper type and re-submit.
CRS-02544: The name '<varname>string</varname>' is longer than the allowed maximum of '<varname>number</varname>' characters: Cause: The name is too long.; Action: Use a shorter name.
CRS-02545: Cannot operate on '<varname>string</varname>'. <varname>string</varname>: Cause: The entity specified is currently locked as part of another operation.; Action: Re-submit the request later.
CRS-02546: Server '<varname>string</varname>' 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 '<varname>string</varname>' for resource '<varname>string</varname>' 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 '<varname>string</varname>' is detected from '<varname>string</varname>': Cause: There is a cycle in the dependency graph. Cycles are disallowed.; Action: Re-evaluate the dependency graph.
CRS-02549: Resource '<varname>string</varname>' cannot be placed on '<varname>string</varname>' 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 '<varname>string</varname>' cannot be failed-over because it has other non-OFFLINE instances on the server '<varname>string</varname>': 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 '<varname>string</varname>' cannot be failed-over because it is of type '<varname>string</varname>', 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 '<varname>string</varname>' 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 '<varname>string</varname>' 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 '<varname>string</varname>' cannot be unregistered as it is referenced by resource '<varname>string</varname>': 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 '<varname>string</varname>' 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 '<varname>string</varname>' 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 '<varname>string</varname>' cannot be unregistered as it is referenced by server pool '<varname>string</varname>': 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 '<varname>string</varname>' 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 '<varname>string</varname>' may not be unregistered as it has the following resources:<varname>string</varname>: 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 '<varname>string</varname>' does not exist: Cause: The resource type referenced does not exist.; Action: Specify a correct type.
CRS-02561: Resource type '<varname>string</varname>' may not be unregistered as it is referenced by resource '<varname>string</varname>': 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 '<varname>string</varname>' 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 '<varname>string</varname>' on '<varname>string</varname>' has failed. Will re-retry on '<varname>string</varname>' 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 '<varname>string</varname>'. Will attempt to restore it on '<varname>string</varname>' 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 '<varname>string</varname>' to '<varname>string</varname>' has failed. Will re-retry on '<varname>string</varname>' 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 '<varname>string</varname>' does not have sufficient permissions to operate on resource '<varname>string</varname>', 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 '<varname>string</varname>': Cause: The default value specified is not proper.; Action: Make sure the value is proper for its type.
CRS-02568: Base resource type name '<varname>string</varname>' 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 '<varname>string</varname>': 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 '<varname>number</varname>' is different from number of lists '<varname>number</varname>': Cause: This is an internal error.; Action: Contact Oracle Support Services.
CRS-02571: Dependency kind '<varname>string</varname>' is specified more than once for resource '<varname>string</varname>': 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: '<varname>string</varname>' 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 '<varname>string</varname>' is not a member of group '<varname>string</varname>': 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 '<varname>string</varname>' in attributes and values is not allowed: Cause: A disallowed character was detected.; Action: Retry without the disallowed character.
CRS-02578: Value of '<varname>string</varname>' (<varname>number</varname>) may not be greater than that of '<varname>string</varname>' (<varname>number</varname>): Cause: The specified values do not make sense - one may not be less than the other.; Action: Use valid values.
CRS-02579: Value '<varname>number</varname>' may not be less than '<varname>number</varname>': Cause: The value is less than the allowed minimum.; Action: Use a proper value.
CRS-02580: Value '<varname>number</varname>' is neither '<varname>number</varname>' nor '<varname>number</varname>': Cause: The value must be one of the two and it is neither.; Action: Use a proper value.
CRS-02581: Value '<varname>string</varname>' is not any of the following '<varname>string</varname>', '<varname>string</varname>', '<varname>string</varname>': Cause: The value must be one of the ones specified and it is not.; Action: Use a proper value.
CRS-02582: Value '<varname>string</varname>' does not follow expected format: <varname>n</varname>[s|d|m|w|h]: Cause: The value specification does not follow required format.; Action: Use a proper value.
CRS-02583: Value '<varname>number</varname>' must be in the '<varname>number</varname>' - '<varname>number</varname>' range: Cause: The value is not within the allowed range.; Action: Use a proper value.
CRS-02584: Value '<varname>string</varname>' 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 '<varname>string</varname>' 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 '<varname>string</varname>' is internal and thus may not be overridden in type '<varname>string</varname>': 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 '<varname>string</varname>' is detected from '<varname>string</varname>' via type '<varname>string</varname>': 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 '<varname>string</varname>' is invalid for relation kind '<varname>string</varname>': 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 '<varname>string</varname>' in the filter specification is not supported: Cause: An unsupported comparator was supplied.; Action: Use a supported value.
CRS-02594: Filter specification '<varname>string</varname>' 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 '<varname>string</varname>' 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 '<varname>string</varname>' 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 '<varname>string</varname>' may not be moved to pool '<varname>string</varname>': 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 '<varname>string</varname>' is already at its maximum size of '<varname>number</varname>': Cause: The pool is already at the maximum.; Action: The request is impossible to execute.
CRS-02599: Server '<varname>string</varname>' is not in a parent pool of '<varname>string</varname>': Cause: The server is not in a parent pool of the pool in question.; Action: The request is impossible to execute.
CRS-02600: Server '<varname>string</varname>' 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 '<varname>string</varname>' is not explicitly mentioned as a candidate by server pool '<varname>string</varname>': 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 '<varname>string</varname>' is in server pool '<varname>string</varname>' which is exclusive with server pool '<varname>string</varname>': 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 '<varname>string</varname>' cannot be assigned to server pool '<varname>string</varname>' 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 '<varname>string</varname>' is already assigned to server pool '<varname>string</varname>': Cause: Server movement makes no sense: the server is already in the target pool.; Action: Check the request validity.
CRS-02605: Server '<varname>string</varname>' cannot be relocated from server pool '<varname>string</varname>' because the pool disallows transfers: Cause: The server pool is configured not to allow server transfers.; Action: Check the request validity.
CRS-02606: Server '<varname>string</varname>' may not be relocated from server pool '<varname>string</varname>' 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 '<varname>string</varname>' has not been specified on per-X basis for resource '<varname>string</varname>': 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 '<varname>string</varname>' 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 '<varname>string</varname>' may not be relocated to server pool '<varname>string</varname>' as the pool disallows transfers: Cause: The server pool is configured not to allow server transfers.; Action: Check the request validity.
CRS-02610: Server '<varname>string</varname>' 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 '<varname>string</varname>' 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 '<varname>string</varname>': 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 '<varname>string</varname>'.: 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 '<varname>string</varname>'.: 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 '<varname>string</varname>'.: 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 '<varname>string</varname>' does not have sufficient permissions to operate on resource type '<varname>string</varname>', 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 <varname>string</varname>. 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 <varname>string</varname> of existing attribute <varname>string</varname> to type <varname>string</varname>.: 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 '<varname>string</varname>' may not be edited: Cause: The pool's attributes may not be edited.; Action: None
CRS-02620: Attribute '<varname>string</varname>' of server pool '<varname>string</varname>' may not be edited: Cause: Editing of the attribute of the server pool is not allowed.; Action: None
CRS-02621: Server '<varname>string</varname>' is assigned to '<varname>string</varname>' 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 '<varname>string</varname>' 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 '<varname>string</varname>' cannot accept server '<varname>string</varname>' because its name is not specified in '<varname>string</varname>': Cause: Only servers whose names are mentioned in the attribute may be assigned to the pool.; Action: None
CRS-02624: One of '<varname>string</varname>', '<varname>string</varname>' must be specified when '<varname>string</varname>' is '<varname>string</varname>': Cause: Neither of the parameters was specified.; Action: Specify either of the two and re-submit.
CRS-02625: Owner of resource '<varname>string</varname>' does not have execute permission to pool '<varname>string</varname>' 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 '<varname>string</varname>' does not have execute permission to parent server pool '<varname>string</varname>': 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 '<varname>string</varname>' to relocate server '<varname>string</varname>': 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 '<varname>string</varname>' 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 '<varname>string</varname>' on that would satisfy its placement policy: Cause: After one or more attempts, the system ran out of servers that can be used to place the resource and satisfy its placement policy.; Action: None
CRS-02640: Required resource '<varname>string</varname>' 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 '<varname>string</varname>' cannot override that defined in the resource's type: '<varname>string</varname>': 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 '<varname>string</varname>' 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 '<varname>string</varname>' 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 '<varname>string</varname>': Cause: The type is abstract.; Action: Only concrete extensions of the type can be created.
CRS-02646: '<varname>string</varname>' 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 '<varname>string</varname>' 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 '<varname>string</varname>' 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 '<varname>string</varname>' of '<varname>string</varname>' 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 '<varname>string</varname>' is configured to run only on '<varname>string</varname>' and cannot be started on '<varname>string</varname>': 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 '<varname>string</varname>' 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: <varname>string</varname> 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 '<varname>string</varname>' 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 '<varname>string</varname>' 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 '<varname>string</varname>' is disabled on server '<varname>string</varname>': Cause: The resource was disabled on the specified server.; Action: Either re-enable, or use a different server.
CRS-02663: Resource instance of '<varname>string</varname>' with <varname>string</varname>=<varname>number</varname>, <varname>string</varname>=<varname>number</varname> 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 '<varname>string</varname>' is already running on '<varname>string</varname>': Cause: The resource is already running everywhere it may run.; Action: None
CRS-02665: Resource '<varname>string</varname>' is disabled on '<varname>string</varname>': Cause: The resource is disabled on every server it is configured to start on.; Action: None
CRS-02666: Resource '<varname>string</varname>' is disabled on '<varname>string</varname>' and is already running on '<varname>string</varname>': Cause: The resource is disabled on every server it is configured to start on.; Action: None
CRS-02667: Resource '<varname>string</varname>' with <varname>string</varname>=<varname>string</varname> may only run on servers assigned to <varname>string</varname> and <varname>string</varname>, 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 '<varname>string</varname>' (<varname>number</varname>) may not not be above '<varname>number</varname>': 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 '<varname>number</varname>': 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 '<varname>string</varname>' because '<varname>string</varname>' has a stop-time '<varname>string</varname>' 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 '<varname>string</varname>': <varname>string</varname>: Cause: The value specified for the attribute is inappropriate or invalid.; Action: Review the value, correct the problem and re-submit the request.
CRS-02672: Attempting to start '<varname>string</varname>' on '<varname>string</varname>': Cause: This is a status message.; Action: None
CRS-02673: Attempting to stop '<varname>string</varname>' on '<varname>string</varname>': Cause: This is a status message.; Action: None
CRS-02674: Start of '<varname>string</varname>' on '<varname>string</varname>' failed: Cause: This is a status message.; Action: None
CRS-02675: Stop of '<varname>string</varname>' on '<varname>string</varname>' failed: Cause: This is a status message.; Action: None
CRS-02676: Start of '<varname>string</varname>' on '<varname>string</varname>' succeeded: Cause: This is a status message.; Action: None
CRS-02677: Stop of '<varname>string</varname>' on '<varname>string</varname>' succeeded: Cause: This is a status message.; Action: None
CRS-02678: '<varname>string</varname>' on '<varname>string</varname>' 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 '<varname>string</varname>' on '<varname>string</varname>': Cause: This is a status message.; Action: None
CRS-02680: Clean of '<varname>string</varname>' on '<varname>string</varname>' failed: Cause: This is a status message.; Action: None
CRS-02681: Clean of '<varname>string</varname>' on '<varname>string</varname>' succeeded: Cause: This is a status message.; Action: None
CRS-02682: It is locked by '<varname>string</varname>' for command '<varname>string</varname>' issued from '<varname>string</varname>': Cause: This message is generated for operations that have a locking conflict.; Action: None
CRS-02683: It is locked by '<varname>string</varname>' for command '<varname>string</varname>': Cause: This message is generated for operations that have a locking conflict.; Action: None
CRS-02714: '<varname>string</varname>' is specified multiple times in '<varname>string</varname>' of '<varname>string</varname>': 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 '<varname>string</varname>': 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 '<varname>string</varname>' is not in any of the server pool(s) hosting resource '<varname>string</varname>': 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 '<varname>string</varname>' is not a hosting member of resource '<varname>string</varname>': 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 '<varname>string</varname>' may not be started on server '<varname>string</varname>' because the server is not in either '<varname>string</varname>' or '<varname>string</varname>' 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: '<varname>string</varname>' is a resource alias for '<varname>string</varname>' 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: '<varname>string</varname>' is a resource alias for '<varname>string</varname>' 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 '<varname>string</varname>' may only run on '<varname>string</varname>'; check on '<varname>string</varname>' 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 '<varname>string</varname>' found on '<varname>string</varname>': 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 '<varname>string</varname>' 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 <varname>string</varname> does not have permission to operate on resource <varname>string</varname>.: 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 '<varname>string</varname>' 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 '<varname>string</varname>' 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 '<varname>string</varname>' 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 '<varname>string</varname>' depends on resource '<varname>string</varname>': 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 '<varname>string</varname>' is already running on server '<varname>string</varname>': Cause: The resource is already running on the server; relocate is impossible.; Action: Select another server.
CRS-02732: Resource '<varname>string</varname>' is already starting on server '<varname>string</varname>': 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 '<varname>string</varname>'; 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 '<varname>string</varname>'; 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 '<varname>string</varname>' from server '<varname>string</varname>': 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 '<varname>string</varname>' on server '<varname>string</varname>': 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 '<varname>string</varname>' 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 '<varname>string</varname>' as this will affect running resources, but the force option was not specified: Cause: One or more running resources would be affected by the operation.; Action: Add more servers to the cluster, stop or relocate the resources mentioned right before this error, or use the force option for the same command.
CRS-02739: Unable to relocate server '<varname>string</varname>' 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 '<varname>string</varname>' to server pool '<varname>string</varname>'. 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 '<varname>string</varname>': Cause: The attribute was not given a value.; Action: Provide a value and retry.
CRS-02742: The update of resource '<varname>string</varname>' 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 '<varname>string</varname>' 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 '<varname>string</varname>' 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 <varname>string</varname> because it results in violation of a pool <varname>string</varname> 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 '<varname>string</varname>' which is last known to have run on '<varname>string</varname>' 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 '<varname>string</varname>' on server '<varname>string</varname>'. Resources that did not stop must be stopped or unregistered manually. Details at <varname>string</varname> in <varname>string</varname>.: 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 '<varname>string</varname>' during server reconfiguration on server '<varname>string</varname>'.: 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 '<varname>string</varname>' failed. Details at <varname>string</varname> in <varname>string</varname>.: 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 '<varname>string</varname>', resource '<varname>string</varname>' is in unexpected state. Details at <varname>string</varname> in <varname>string</varname>.: Cause: The specified resource was in an unexpected state.; Action: Manually restart the resource.
CRS-02751: Cannot create new resource, the resource type '<varname>string</varname>' is not supported. Details at <varname>string</varname> in <varname>string</varname>.: 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 <varname>string</varname> in <varname>string</varname>.: 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 '<varname>string</varname>'. Details at <varname>string</varname> in <varname>string</varname>.: Cause: This is an internal error.; Action: Contact Oracle Support Services.
CRS-02755: Error reading type definition for type '<varname>string</varname>'. Details at <varname>string</varname> in <varname>string</varname>.: Cause: This is an internal error.; Action: Contact Oracle Support Services.
CRS-02756: Invalid tag for command '<varname>string</varname>'. Details at <varname>string</varname> in <varname>string</varname>.: Cause: An invalid command was received by the CRS daemon.; Action: Contact Oracle Support Services.
CRS-02757: Command '<varname>string</varname>' timed out waiting for response from the resource '<varname>string</varname>'. Details at <varname>string</varname> in <varname>string</varname>.: 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 '<varname>string</varname>' 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 '<varname>string</varname>'. Details at <varname>string</varname> in <varname>string</varname>.: 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 <varname>string</varname> in <varname>string</varname>.: 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 '<varname>string</varname>'. Details at <varname>string</varname> in <varname>string</varname>.: Cause: This is an internal error.; Action: Contact Oracle Support Services.
CRS-02762: Unable to find type '<varname>string</varname>' in registry while processing resource '<varname>string</varname>'. Details at <varname>string</varname> in <varname>string</varname>.: Cause: This is an internal error.; Action: Contact Oracle Support Services
CRS-02763: Error while reading resources. Details at <varname>string</varname> in <varname>string</varname>.: Cause: This is an internal error.; Action: Contact Oracle Support Services.
CRS-02764: CRSADMIN and CRSUSER keys are not in repository. Details at <varname>string</varname> in <varname>string</varname>.: 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 '<varname>string</varname>' has failed on server '<varname>string</varname>'.: 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 '<varname>string</varname>' from server '<varname>string</varname>'.: Cause: Received command to change state for a resource that was disabled.; Action: None
CRS-02767: Resource state recovery not attempted for '<varname>string</varname>' 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 '<varname>string</varname>'.: 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 '<varname>string</varname>'.: Cause: Could not failover the specified resource.; Action: Restart the resource manually.
CRS-02770: Resource target '<varname>string</varname>' 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 '<varname>string</varname>'; 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 '<varname>string</varname>' has been assigned to pool '<varname>string</varname>'.: Cause: The specified server had been assigned to a server pool.; Action: None
CRS-02773: Server '<varname>string</varname>' has been removed from pool '<varname>string</varname>'.: Cause: The specified server had been removed from a server pool.; Action: None
CRS-02774: Failed to save resource '<varname>string</varname>' to the repository. Details at <varname>string</varname> in <varname>string</varname>.: 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 '<varname>string</varname>'. Details at <varname>string</varname> in <varname>string</varname>.: 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 '<varname>string</varname>'. Details at <varname>string</varname> in <varname>string</varname>.: 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 '<varname>string</varname>' from repository. Details at <varname>string</varname> in <varname>string</varname>.: 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 '<varname>string</varname>' from repository. Details at <varname>string</varname> in <varname>string</varname>.: 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 '<varname>string</varname>' from repository. Details at <varname>string</varname> in <varname>string</varname>.: 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 '<varname>string</varname>'. Details at <varname>string</varname> in <varname>string</varname>.: Cause: This is an internal error.; Action: Contact Oracle Support Services.
CRS-02781: Error during registration for resource '<varname>string</varname>'. Details at <varname>string</varname> in <varname>string</varname>.: Cause: Error occurred during registration callback of new resource.; Action: Contact Oracle Support Services.
CRS-02782: Unable to find attributes for resource '<varname>string</varname>'. Details at <varname>string</varname> in <varname>string</varname>.: Cause: This is an internal error.; Action: Contact Oracle Support Services.
CRS-02783: Internal error in local placement policy for resource '<varname>string</varname>'. Details at <varname>string</varname> in <varname>string</varname>.: Cause: Internal error in CRS Policy Engine.; Action: Contact Oracle Support Services.
CRS-02784: Internal error, invalid server '<varname>string</varname>' in local placement policy. Details at <varname>string</varname> in <varname>string</varname>.: Cause: Internal error in CRS Policy Engine.; Action: Contact Oracle Support Services.
CRS-02785: Failed to register resource '<varname>string</varname>'. Details at <varname>string</varname> in <varname>string</varname>.: 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 '<varname>string</varname>'. Details at <varname>string</varname> in <varname>string</varname>.: 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 '<varname>string</varname>' has fallen below its minimum size. Details at <varname>string</varname> in <varname>string</varname>.: 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 '<varname>string</varname>'. The server '<varname>string</varname>' 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 '<varname>string</varname>' as it is not running on server '<varname>string</varname>': 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 '<varname>string</varname>': 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 '<varname>string</varname>': 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 '<varname>string</varname>' 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 '<varname>string</varname>' 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 '<varname>string</varname>' 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 '<varname>string</varname>' 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 '<varname>string</varname>', 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 '<varname>string</varname>' from unexpected server '<varname>string</varname>'. Details at '<varname>string</varname>' in '<varname>string</varname>'.: 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 '<varname>string</varname>' on '<varname>string</varname>': 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 '<varname>string</varname>' as it is already in the INTERMEDIATE state on server '<varname>string</varname>': 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 '<varname>string</varname>' 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 '<varname>string</varname>' has already been declared in a derived type '<varname>string</varname>': 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 '<varname>string</varname>' because it has a '<varname>string</varname>' dependency on resource type '<varname>string</varname>' 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 '<varname>string</varname>': 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 '<varname>string</varname>' 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 <varname>string</varname> in <varname>string</varname>.: 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 <varname>string</varname> in <varname>string</varname>.: 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 '<varname>string</varname>' 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 '<varname>string</varname>' 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 '<varname>string</varname>' cannot be unregistered as it is referenced by resource '<varname>string</varname>'.: 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 '<varname>string</varname>' cannot be unregistered as it is referenced by server pool '<varname>string</varname>'.: 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 '<varname>string</varname>' from repository. Details at <varname>string</varname> in <varname>string</varname>.: 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 '<varname>string</varname>'. Details at <varname>string</varname> in <varname>string</varname>.: 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 '<varname>string</varname>' is missing for configuration policy '<varname>string</varname>'.: Cause: A required attribute was not specified.; Action: Make sure the attribute is specified.
CRS-02821: Fatal error while validating configuration policy '<varname>string</varname>'.: 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 '<varname>string</varname>' 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 '<varname>string</varname>' was not found.: Cause: An attempt to activate non-existent policy was made.; Action: Use a registered policy's name instead.
CRS-02824: '<varname>string</varname>' 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 '<varname>string</varname>' 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 '<varname>string</varname>' or '<varname>string</varname>' 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 '<varname>string</varname>' or '<varname>string</varname>' 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 '<varname>string</varname>', '<varname>string</varname>' or '<varname>string</varname>' must be specified when '<varname>string</varname>' is '<varname>string</varname>'.: Cause: One attribute of the three is required for this configuration.; Action: Specify a value for one attribute of the three.
CRS-02835: Resource '<varname>string</varname>' cannot start on server '<varname>string</varname>' 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 '<varname>string</varname>' attribute set to '<varname>string</varname>'.: 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 '<varname>string</varname>' of resource '<varname>string</varname>'.: 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: '<varname>string</varname>' 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 '<varname>string</varname>'.: 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 '<varname>string</varname>' 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: '<varname>string</varname>' 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 '<varname>string</varname>' on resource '<varname>string</varname>' timed out.: Cause: The action did complete within the allotted time.; Action: None
CRS-02843: Unable to complete processing of the '<varname>string</varname>' action for resource '<varname>string</varname>' on server '<varname>string</varname>' 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 '<varname>string</varname>' to start on server '<varname>string</varname>'.: Cause: The resource is now expected to start on the server.; Action: None
CRS-02845: Waiting for resource '<varname>string</varname>' to stop on server '<varname>string</varname>'.: Cause: The resource is now expected to stop on the server.; Action: None
CRS-02846: There is no active action on resource instance '<varname>string</varname>': 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 '<varname>string</varname>' does not exist on server '<varname>string</varname>': 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: <varname>string</varname> . Error: <varname>string</varname> Details at <varname>string</varname> in <varname>string</varname>.: Cause: This is an internal error.; Action: Contact Oracle Support Services.
CRS-02849: Authorization failure: Resource [ <varname>string</varname> ]: 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 '<varname>string</varname>' on '<varname>string</varname>' has been delayed to maintain concurrency limit of <varname>number</varname>.: Cause: The configured concurrent start action limit was reached.; Action: The start action will automatically resume as soon as possible.
CRS-02851: Stop of '<varname>string</varname>' on '<varname>string</varname>' has been delayed to maintain concurrency limit of <varname>number</varname>.: 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: '<varname>string</varname>' .: Cause: The server pool name given to start/stop command did not exist.; Action: Specify a valid server pool name.
CRS-02854: Resource '<varname>string</varname>' 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 '<varname>string</varname>' is not configured to run in server pool '<varname>string</varname>'.: 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 '<varname>string</varname>' because it is not running in server pool '<varname>string</varname>'.: 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 '<varname>string</varname>' does not have permission to run action '<varname>string</varname>' on resource '<varname>string</varname>'.: 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 '<varname>string</varname>' on resource '<varname>string</varname>' 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 '<varname>string</varname>' 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 '<varname>string</varname>' cannot be started on server '<varname>string</varname>' because it has an exclusion dependency with resources of type '<varname>string</varname>'.: 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 '<varname>string</varname>' cannot be started on server '<varname>string</varname>' because it has an exclusion dependency with resources of type '<varname>string</varname>' 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 '<varname>string</varname>' 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: '<varname>string</varname>' 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: '<varname>string</varname>' 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 '<varname>string</varname>' cannot be started on server '<varname>string</varname>' because it has an exclusion dependency with resource '<varname>string</varname>'.: 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 '<varname>string</varname>' cannot be started on server '<varname>string</varname>' because it has an exclusion dependency with resource '<varname>string</varname>' 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 '<varname>string</varname>' on server '<varname>string</varname>'.: 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 '<varname>string</varname>' 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 '<varname>string</varname>' of the entity '<varname>string</varname>' does not belong to the '<varname>string</varname>' 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 '<varname>string</varname>': 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 '<varname>string</varname>', 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 '<varname>string</varname>' 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 '<varname>string</varname>' due to an exclusion dependency on '<varname>string</varname>'.: 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 '<varname>string</varname>' 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 '<varname>string</varname>' cannot be used for resource placement currently.: Cause: The server is currently configured such that it cannot be used for resource placement.; Action: Use a different server.
CRS-02890: An administrator-managed database cannot be configured on a non-Hub server '<varname>string</varname>'.: 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 '<varname>string</varname>' 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 '<varname>string</varname>' in resources of '<varname>string</varname>' type, '<varname>string</varname>' must be set to '<varname>string</varname>' and '<varname>string</varname>' must be set to '<varname>string</varname>'.: 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 '<varname>string</varname>' 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-02900: User '<varname>string</varname>' does not exist on node '<varname>string</varname>'.: 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 '<varname>string</varname>' 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 '<varname>string</varname>' cannot be unregistered as it is referenced by server pool '<varname>string</varname>' in policy '<varname>string</varname>'.: 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 '<varname>string</varname>' 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 '<varname>string</varname>' cannot be assigned to server pool '<varname>string</varname>' because its current role is not '<varname>string</varname>'.: 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 '<varname>string</varname>' 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 '<varname>string</varname>' 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 '<varname>string</varname>' on server '<varname>string</varname>' 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 '<varname>string</varname>' 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 '<varname>string</varname>' 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' (<varname>string</varname>) or 'autostart servercount' (<varname>string</varname>). Details at <varname>string</varname> in <varname>string</varname>.: 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 '<varname>string</varname>' 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 '<varname>string</varname>' does not exist on server '<varname>string</varname>': 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 '<varname>string</varname>' 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 '<varname>string</varname>' 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 '<varname>string</varname>' for resource '<varname>string</varname>' 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 '<varname>string</varname>' is not supported for resource type '<varname>string</varname>'.: 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 '<varname>string</varname>' 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 '<varname>string</varname>' for server configuration attribute '<varname>string</varname>'.: 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 '<varname>string</varname>' for the targets '<varname>string</varname>' 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 '<varname>string</varname>' in the modification list for dependency '<varname>string</varname>'.: 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 '<varname>string</varname>' 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 '<varname>string</varname>' 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 '<varname>string</varname>' cannot be accepted because it is specified multiple times.: Cause: A duplicate resource was assigned as a dependency to a resource.; Action: Revise the dependency list to ensure that no duplicate resources exist.
CRS-03501: The Cluster Health Analysis service started on host <varname>string</varname>.: 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 <varname>string</varname>. Details at <varname>string</varname> in <varname>string</varname>.: 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 <varname>string</varname> is shutting down.: Cause: The Cluster Health Analysis service on the listed node was terminated.; Action: None
CRS-04000: Command <varname>string</varname> 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 '<varname>string</varname>' is missing in the OCR.: Cause: Internal error.; Action: Contact Oracle Support Services.
CRS-04017: Failed to get the value for key '<varname>string</varname>' from OCR.: Cause: Internal error.; Action: Contact Oracle Support Services.
CRS-04038: Cannot delete invalid user '<varname>string</varname>' 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 '<varname>string</varname>' contains the following invalid characters: '<varname>string</varname>': 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: <varname>string</varname>: 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 [<varname>string</varname>] is less than the required cluster active version [<varname>string</varname>]: 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: <varname>string</varname>\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: '<varname>string</varname>'\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: '<varname>string</varname>'\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 <varname>string</varname> and <varname>string</varname> 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: <varname>string</varname>\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: <varname>string</varname>\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 <varname>number</varname> 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 <varname>number</varname> 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: <varname>string</varname>\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: <varname>string</varname>\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: Configuration data stored but IPMI IP address is required to complete the change. The change cannot be validated until the information is complete.\n: Cause: Not proceeding with Client's IPMI login change request because all information such as IPMI username, password and IP address need to be present.; Action: Execute 'crsctl set css ipmiaddr' from crsctl.
CRS-04228: Value of attribute '<varname>string</varname>' is missing\n: Cause: The user did not provide a value for the attribute.; Action: Provide a value using the format <varname>attrName</varname>=<varname>value</varname>, where <varname>value</varname> 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: Configuration data stored but IPMI authorization information is required to complete the change. The change cannot be validated until the information is complete.\n: Cause: Not proceeding with Client's IPMI login change request because all information (IPMI username, password and IP address) need to be present.; Action: Execute 'crsctl set css ipmiadmin' from crsctl.
CRS-04233: New IPMI configuration data stored, but failed validation by remote node.\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: '<varname>string</varname>'\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-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 <varname>string</varname> 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 <varname>string</varname> 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 <varname>vfile</varname> ... <varname>vfile</varname>'.
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 <varname>number</varname> <varname>string</varname> 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 of the ASM disk group in a client cluster.; Action: Specify an ASM disk group for voting file creation or replacement.
CRS-04272: error while identifying voting files in use\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-04402: The CSS daemon was started in exclusive mode but found an active CSS daemon on node <varname>string</varname>, number <varname>string</varname>, and is terminating: Cause: The CSS daemon was started in exclusive mode, which requires that the clusterware stack is down on all other nodes to ensure data integrity. A CSS daemon was detected on another node, so the CSS daemon on this node is terminating.; Action: 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. The name and number of the active node may be unknown.
CRS-04404: The following nodes did not reply within the allotted time:\n<varname>string</varname>: 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:\n<varname>string</varname>: 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 <varname>string</varname>.\n: Cause: This parameter does not allow values higher than 10.; Action: Use a value between 0 and 10.
CRS-04408: Node '<varname>string</varname>' 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 '<varname>string</varname>' is already configured in '<varname>string</varname>' 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 <varname>string</varname> cannot be converted to 'leaf'.: Cause: An attempt was made to modify the role of the last remaining configured 'hub' node to 'leaf' node, which is not allowed or the node is already a 'leaf' node."; Action: If role of this node must to be modified to 'leaf', first bring up another node as a 'hub' node to ensure that there is always at least one 'hub' node.
CRS-04481: Unable to spawn a process.\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 <varname>number</varname> to add voting file <varname>string</varname>.\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 <varname>number</varname> 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 a majority of voting disks; 19- version incompatibility between client and server;; Action: Respond based on the return code as follows: 15 - adjust privileges or use a different userid 16 - review the voting disk configuration displayed by 'crsctl query css votedisk' and correct your request accordingly 19 - ensure that compatible versions are installed others - report to Oracle Support Services
CRS-04615: Software version query failed for node <varname>string</varname>\n: Cause: Internal error.; Action: Contact Oracle Support Services.
CRS-04625: Failure to allocate <varname>number</varname> 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 <varname>number</varname> and <varname>number</varname>.\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. <varname>number</varname>\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 <varname>number</varname> to mark unformat information on voting file <varname>string</varname>\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 <varname>string</varname>.\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 <varname>number</varname> 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 <varname>number</varname> 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 '<varname>number</varname>' while attempting to send shutdown request: Cause: This is an internal error.; Action: If retrying does not work, contact Oracle support
CRS-04636: Failure <varname>number</varname> in clsvrelversion: Cause: Internal error.; Action: Contact Oracle Support Services.
CRS-04637: Oracle High Availability Services release version on the local node is [<varname>string</varname>]\n: Cause: Output message, not an error.; Action: None
CRS-04651: No resources found on server '<varname>string</varname>'.: Cause: The server has no resources associated with it.; Action: Provide a server with resources running.
CRS-04652: Failure <varname>number</varname> in clsvswversion for the local node: Cause: Internal error.; Action: Contact Oracle Support Services.
CRS-04653: Server name '<varname>string</varname>' contains invalid characters.: Cause: The name provided contains invalid characters.; Action: Use a server name with only alphanumeric characters.
CRS-04654: Server '<varname>string</varname>' 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 '<varname>string</varname>' 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 '<varname>string</varname>' is not running on server '<varname>string</varname>'.: 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 <varname>string</varname> 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 <varname>string</varname>.\n: Cause: An internal error happened during this operation.; Action: Contact Oracle Support Services.
CRS-04660: Could not find node <varname>string</varname> 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 <varname>string</varname> successfully deleted.\n: Cause: A request to delete a node completed.; Action: None
CRS-04662: Error while trying to delete node <varname>string</varname>.\n: Cause: Some internal error happened during this operation.; Action: Contact Oracle Support Services.
CRS-04663: could not find node <varname>string</varname> 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 <varname>string</varname> successfully pinned.\n: Cause: A request to pin a node completed.; Action: None
CRS-04665: Error while trying to pin node <varname>string</varname>.\n: Cause: An internal error happened during this operation.; Action: Contact Oracle Support Services.
CRS-04666: Could not find node <varname>string</varname> 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 <varname>string</varname> 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 <varname>string</varname> to <varname>number</varname> due to conflicting parameter <varname>string</varname>; the new value for <varname>string</varname> must be less than <varname>number</varname>.\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 <varname>string</varname> due to conflicting parameter <varname>string</varname> currently set to <varname>number</varname>.\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 [<varname>string</varname>]\n: Cause: Output message, not an error.; Action: None
CRS-04674: Cannot add invalid user '<varname>string</varname>' to CRS Admin list.: Cause: An attempt was made to add an invalid username to the CRS Admin list.; Action: Reissue the command with a valid username.
CRS-04675: Failed to get logfilesize for Cluster Synchronization Services.\n: Cause: An internal error happened during this operation for Cluster Synchronization Services.; Action: Contact Oracle Support Services.
CRS-04676: Successful get logfilesize <varname>number</varname> for Cluster Synchronization Services.\n: Cause: The operation is done successfully for Cluster Synchronization Services.; Action: None
CRS-04677: Failed to get <varname>string</varname> 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 <varname>string</varname> <varname>number</varname> for Cluster Synchronization Services.\n: Cause: The 'get' operation was performed successfully.; Action: None
CRS-04679: Failed to unset logfilesize for Cluster Synchronization Services.\n: Cause: An internal error happened during this operation for Cluster Synchronization Services.; Action: Contact Oracle Support Services.
CRS-04680: Successful unset logfilesize for Cluster Synchronization Services.\n: Cause: The 'unset' 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 <varname>string</varname> to <varname>number</varname> for Cluster Synchronization Services.\n: Cause: An internal error happened during this operation for Cluster Synchronization Services.; Action: Contact Oracle Support Services.
CRS-04684: Successful set of parameter <varname>string</varname> to <varname>number</varname> for Cluster Synchronization Services.\n: Cause: The 'set' operation was performed successfully for Cluster Synchronization Services.; Action: None
CRS-04685: Failed to set logfilesize <varname>number</varname> for Cluster Synchronization Services.\n: Cause: An internal error happened during this operation for Cluster Synchronization Services.; Action: Contact Oracle Support Services.
CRS-04686: Successful set logfilesize <varname>number</varname> 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 '<varname>string</varname>': 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 '<varname>string</varname>': 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 <varname>number</varname>. 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 <varname>string</varname> is a duplicate of an existing voting disk with matching File Universal ID <varname>string</varname>.\n: Cause: This disk is already a part of the current cluster.; Action: None needed.
CRS-04696: Failed to set parameter <varname>string</varname> to <varname>number</varname> due to conflicting parameter <varname>string</varname>; the new value for <varname>string</varname> must be greater than <varname>number</varname>.\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 '<varname>string</varname>'.: 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 <varname>number</varname> in retrieving the patch level: Cause: Internal error.; Action: Contact Oracle Support Services.
CRS-04699: Error code <varname>number</varname> 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): <varname>string</varname>\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 <varname>string</varname>.\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 <varname>string</varname>.\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-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 <varname>string</varname> 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 <varname>string</varname>.\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 <varname>string</varname> 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 <varname>number</varname> 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 <varname>string</varname> 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 <varname>string</varname> \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 <varname>string</varname> 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 <varname>string</varname> (New = <varname>number</varname>, Old = <varname>number</varname> bytes): Cause: set jazn command was issued and OCR key was updated.; Action: None Required.
CRS-04743: File <varname>string</varname> was updated from OCR(Size: <varname>number</varname>(New), <varname>number</varname>(Old) bytes): Cause: get jazn command was issued and specified file was updated with the contents from OCR key.; Action: None Required.
CRS-04839: Required attribute '<varname>string</varname>' is missing for '<varname>string</varname>'.: Cause: A required attribute was not specified.; Action: Make sure the attribute is specified.
CRS-04840: Attribute '<varname>string</varname>' cannot be specified using this command.: Cause: An attribute was specified that cannot be used with this command.; Action: Server pool configuration can be changed or created using 'crsctl modify policyset' and 'crsctl modify serverpool -policy' commands.
CRS-04843: Policy '<varname>string</varname>' does not exist.: Cause: An invalid policy name was specified.; Action: Verify the name.
CRS-04846: Configuration policy set has an invalid profile.: Cause: An invalid policy set definition was specified. Missing elements or duplicate elements may be present in the profile.; Action: Verify the contents of the policy set profile and resubmit the command.
CRS-04847: File '<varname>string</varname>' does not exist.: Cause: The specified for the comamnd did not exist or could not be opened.; Action: Verify the filename and resubmit the command.
CRS-04848: Policy '<varname>string</varname>' appears more than once in a policy set file.: Cause: A policy was defined more than once in the profile.; Action: Verify the contents of the policy and remove the duplicate policy.
CRS-04849: Server pool '<varname>string</varname>' appears more than once for policy '<varname>string</varname>' in the policy set file.: Cause: A server pool was defined more than once in the profile for the same policy.; Action: Verify the contents of the policy and remove the duplicate server pool.
CRS-04873: At least one attribute must be specified for this command.: Cause: The 'crsctl eval modify' command was run without specifying any attributes.; Action: Rerun the command with at least one attribute specified.
CRS-04891: Invalid value of level specified.: Cause: An invalid value for output level was specified. Output level can only be 1, 2 or 3.; Action: Rerun the command with a level of 1, 2 or 3.
CRS-04922: Module <varname>string</varname>: <varname>string</varname> ignored; module level out of bounds (valid range <varname>number</varname> - <varname>number</varname>): Cause: An attempt to set a log or trace level supplied a level that is out of range for the module.; Action: Specify a log or trace level within the valid range.
CRS-04923: <varname>string</varname> module: <varname>string</varname> ignored; module level is invalid (range 0 - 65535): Cause: Module log/trace level was invalid (range 0 - 65535).; Action: Specify a log/trace level within the valid range (0 - 65535).
CRS-04925: 'all' module keyword was specified with other module names: Cause: The module keyword 'all' already refers to all module names.; Action: When referring to all modules, use 'all' without duplicate references to other module names.
CRS-04932: Failed to get the current cluster mode: Cause: There was an internal error while getting cluster mode.; Action: Contact Oracle Support Services.
CRS-04933: Cluster mode set to "flex"; restart Oracle High Availability Services on all nodes for cluster to run in "flex" mode.: Cause: Cluster mode was changed to "flex", which requires a cluster restart.; Action: Restart Oracle High Availability Services on all nodes for cluster to run in "flex" mode.
CRS-04934: Failed to set the cluster mode: Cause: There was an internal error while setting cluster mode.; Action: Contact Oracle Support Services.
CRS-04937: Unable to set the cluster mode.: Cause: An attempt was made to set the cluster mode to 'flex' but Grid Naming Service(GNS) was not configured.; Action: Configure GNS and try again to set the cluster mode to 'flex'.
CRS-04940: Cluster must run in standard or flex mode to use this command: Cause: An attempt was made to set the cluster mode but machine is not running as a cluster.; Action: Cluster must be in standard or flex mode to change the cluster mode.
CRS-04942: Cluster mode set to "standard": Cause: Cluster mode is changed. Cluster will shut down now.; Action: None
CRS-04953: CSS already running in nonexclusive mode: Cause: An exclusive mode CRS stack start was attempted when CSS was already running in nonexclusive mode.; Action: Stop the CRS stack first and then start in exclusive mode.
CRS-04954: CRSD already running in nonexclusive mode: Cause: An exclusive mode CRS stack start was attempted when CRSD was already running in nonexclusive mode.; Action: Stop the CRS stack first and then start in exclusive mode.
CRS-04955: CSS failed to start in exclusive mode: Cause: An exclusive mode CRS stack start was attempted but CSS failed to start in exclusive mode.; Action: Check the Clusterware alert log for errors. Correct the reported error(s) and retry.
CRS-04956: CRSD failed to start in exclusive mode: Cause: An exclusive mode CRS stack start was attempted but CRSD failed to start in exclusive mode.; Action: Check the Clusterware alert log for errors. Correct the reported error(s) and retry.
CRS-04967: Input values are out of range for parameter <varname>string</varname>: Cause: A value was provided which was out of range for this parameter.; Action: Specify a value which is appropriate for this parameter.
CRS-04968: Invalid values for parameter <varname>string</varname>. Specify either 0 or 1.: Cause: A value was provided which was out of range for this parameter.; Action: Specify a value which is appropriate for this parameter.
CRS-04969: Specified server attribute <varname>string</varname> does not exist: Cause: A nonexistent attribute was specified for get/set command.; Action: Specify an attribute that exists.Run 'crsctl stat res <varname>resourcename</varname> -p' to list all the attributes of that resource.
CRS-04973: Flex ASM must be enabled before switching the cluster mode to 'flex': Cause: An attempt to change the cluster mode to 'flex' failed because Flex ASM is not enabled.; Action: Enable Flex ASM before changing the cluster mode. Refer to Oracle Automatic Storage Management Administrator's Guide for configuring Flex ASM.
CRS-04977: Cluster cannot be converted from 'flex' mode to 'standard' mode: Cause: An attempt was made to set the cluster mode to standard from flex mode.; Action: If a cluster needs to be converted to standard mode, reinstall Clusterware.
CRS-04980: Duplicate value <varname>string</varname> specified for resource attribute <varname>string</varname>: Cause: A duplicate value was specified for a resource attribute.; Action: Specify only one value for a resource attribute.
CRS-04981: Duplicate value <varname>string</varname> specified for type attribute keyword <varname>string</varname>: Cause: A duplicate value was specified for a type attribute keyword.; Action: Specify only one value for DEFAULT_VALUE, FLAGS and TYPE per type attribute.
CRS-04982: Valid type attribute keyword <varname>string</varname> specified outside a type attribute: Cause: A valid type attribute keyword was specified outside a type attribute.; Action: Specify the ATTRIBUTE type attribute keyword before specifying the DEFAULT_VALUE, FLAGS or TYPE type attribute keywords.
CRS-04983: Invalid type attribute keyword <varname>string</varname> specified: Cause: An invalid type attribute keyword was specified.; Action: Specify only the valid type attribute keywords ATTRIBUTE, DEFAULT_VALUE, FLAGS and TYPE.
CRS-04984: Duplicate definition for type attribute <varname>string</varname>: Cause: The same type attribute was named on more than one ATTRIBUTE keyword.; Action: Define a type attribute only once.
CRS-04985: The value '<varname>string</varname>' of FLAGS attribute is invalid.: Cause: An invalid flag value was specified.; Action: Flag values may be combined using the '|' character as a separator.
CRS-04986: This command is for Oracle's internal use only: Cause: A command meant for internal use was specified.; Action: Refer to 'crsctl -h' for list of commands available for use.
CRS-04989: Module <varname>string</varname>: <varname>string</varname> ignored; module level out of bounds (valid range <varname>number</varname> - <varname>number</varname>): Cause: An attempt to set a log or trace level supplied a level that is out of range for the module.; Action: Specify a log or trace level within the valid range.
CRS-04990: Issued command does not support filter in this version of CRS.: Cause: The command was rejected because a filter (-w) was specified. Filters are not currently supported for this command.; Action: Reissue the command without the filter.
CRS-04991: Could not delete the resource because it does not exist.: Cause: An attempt to delete a resource failed because the resource specification did not identify an existing resource. Either there was no resource with the specified name, or no resource satisfied the specified filter.; Action: Reissue the command specifying the name of an existing resource or a filter that will select an existing resource.
CRS-04992: Could not delete the server pool because it does not exist.: Cause: An attempt to delete a server pool failed because the server pool specification did not identify an existing server pool. Either there was no server pool with the specified name, or no server pool satisfied the specified filter.; Action: Reissue the command specifying the name of an existing server pool or a filter that will select an existing server pool.
CRS-04993: Could not delete the server category because it does not exist.: Cause: An attempt to delete a server category failed because the server category specification did not identify an existing server category. Either there was no server category with the specified name, or no server category satisfied the specified filter.; Action: Reissue the command specifying the name of an existing server category or a filter that will select an existing server category.
CRS-04994: Could not delete the resource type because it does not exist.: Cause: An attempt to delete a resource type failed because the resource type specification did not identify an existing resource type. Either there was no resource type with the specified name, or no resource type satisfied the specified filter.; Action: Reissue the command specifying the name of an existing resource type or a filter that will select an existing resource type.
CRS-04995: The command '<varname>string</varname>' is invalid in crsctl. Use srvctl for this command.: Cause: An attempt was made to use an unsupported command in crsctl.; Action: Use srvctl for the mentioned command.
CRS-04996: Command ('crsctl <varname>string</varname> policyset') is not supported in this version of CRS.: Cause: The command was rejected because policy-based management is not a supported feature in this release.; Action: If this error occurs during rolling upgrade, wait for the upgrade to finish. Otherwise, upgrade to the required release or higher.
CRS-04997: Command ('crsctl <varname>string</varname> category') is not supported in this version of CRS.: Cause: The command was rejected because the server category is not a supported feature in this release.; Action: If this error occurs during rolling upgrade, wait for the upgrade to finish. Otherwise, upgrade to the required release or higher.
CRS-04998: Command ('crsctl eval <varname>string</varname>' ) is not supported in this version of CRS.: Cause: The command was rejected because What-If is not a supported feature in this release.; Action: If this error occurs during rolling upgrade, wait for the upgrade to finish. Otherwise, upgrade to the required release or higher.
CRS-04999: Command ('crsctl <varname>string</varname> policy') is not supported in this version of CRS.: Cause: The command was rejected because policy-based management is not a supported feature in this release.; Action: If this error occurs during rolling upgrade, wait for the upgrade to finish. Otherwise, upgrade to the required release or higher.
CRS-05000: Expected resource <varname>string</varname> does not exist in agent process: Cause: The expected resource must have been created by Oracle Configuration tools.; Action: Check that the resource was not manually deleted. If not the case call Oracle Support.
CRS-05001: Expected dependency in resource <varname>string</varname> on a resource of type <varname>string</varname> does not exist: Cause: The expected resource dependency must have been created by Oracle Configuration tools.; Action: Check that the resource dependency was not manually removed.
CRS-05002: Agent action was aborted: Cause: Agent action was aborted either due to action timeout expiry or the user canceled the action.; Action: Retry the operation.
CRS-05003: Invalid attribute value: '<varname>string</varname>' for attribute <varname>string</varname>: Cause: An attribute value passed to the Agent was NULL or invalid.; Action: Give the correct value to the attribute and retry.
CRS-05004: Cannot find listener endpoint for listener <varname>string</varname>: Cause: listener endpoint not found.; Action: Check listener.ora for that listener.
CRS-05005: IP Address: <varname>string</varname> is already in use in the network: Cause: The VIP resource attempted to use an IP address already in use in the network.; Action: Use srvctl to re-create vip or scanvip specifying an IP address which is not being used in the network and retry the operation.
CRS-05006: Unable to automatically select a network interface which has subnet mask <varname>string</varname> and subnet number <varname>string</varname>: Cause: The subnet mask and subnet number configured for the resource did not match the subnet mask and subnet number of any network interface on this node.; Action: Provide a subnet mask and subnet number which matches at least one network interface's subnet mask and subnet number using srvctl remove and add vip and retry the operation.
CRS-05007: Cannot remove the primary IP <varname>string</varname> from the network interface: Cause: The primary IP of the network interface was incorrectly configured as the VIP.; Action: Use 'srvctl remove' and 'srvctl add vip' or 'srvctl remove' and 'srvctl add scan' to provide the correct IP address for the VIP and retry the operation.
CRS-05008: Invalid attribute value: <varname>string</varname> for the network interface: Cause: The network interface value did not match the subnet mask and subnet number of any network interface on the node.; Action: Modify the network interface's value such that the subnet mask and subnet number matches the subnet mask and subnet number of at least one network interface on the node using 'srvctl remove' and 'srvctl add vip' and retry the operation.
CRS-05009: The VIP address <varname>string</varname> does not belong to the subnet <varname>string</varname>: Cause: The VIP's subnet number and the network interface's subnet number did not match.; Action: Make the VIP's subnet number match the network interface's subnet number using 'srvctl remove' and 'srvctl add vip' or 'srvctl remove' and 'srvctl add scan' and retry the operation.
CRS-05010: Update of configuration file "<varname>string</varname>" failed: details at "<varname>string</varname>" in "<varname>string</varname>": Cause: An attempt to open the specified file failed. Common causes are that the file does not exist, or the file permissions prohibit access.; Action: Check that the file exists and has the proper permissions.
CRS-05011: Check of resource "<varname>string</varname>" failed: details at "<varname>string</varname>" in "<varname>string</varname>": Cause: The check of the database or Automatic Storage Management instance failed.; Action: Check the database or ASM instance alert log and the referenced Oracle Clusterware trace file for additional information. Recover the instance if necessary.
CRS-05012: Check of service resource "<varname>string</varname>" failed: details at "<varname>string</varname>" in "<varname>string</varname>": Cause: The check of the preconnect service failed because it could not run on the same node as the main service.; Action: Check the referenced Oracle Clusterware trace file for additional information. Start the preconnect service on a different node.
CRS-05013: Agent "<varname>string</varname>" failed to start process "<varname>string</varname>" for action "<varname>string</varname>": details at "<varname>string</varname>" in "<varname>string</varname>": Cause: The named agent failed to start the named process for the named action.; Action: Check the referenced Oracle Clusterware trace file for additional operating system specific information. Refer to operating system documentation to correct the error.
CRS-05014: Agent "<varname>string</varname>" timed out starting process "<varname>string</varname>" for action "<varname>string</varname>": details at "<varname>string</varname>" in "<varname>string</varname>": Cause: The named agent aborted the named process because the process failed to respond within the timeout period.; Action: Check the agent log files for further information
CRS-05015: Agent timed out waiting for a response from the DHCP server: Cause: Agent and the DHCP server were not able to communicate with each other. Common causes of this failure are due to the DHCP server not running, or improper DHCP server configuration, or the DHCP server running out of DHCP leases.; Action: Identify the cause of the problem from the DHCP server log files. If the problem is due to the DHCP server running out of leases, increase the number of addresses which can be served by the DHCP server.
CRS-05016: Process "<varname>string</varname>" spawned by agent "<varname>string</varname>" for action "<varname>string</varname>" failed: details at "<varname>string</varname>" in "<varname>string</varname>": Cause: The named process failed to complete succesfully.; Action: Check details in the agent log for error information from the spawned process.
CRS-05017: The resource action "<varname>string</varname> <varname>string</varname>" encountered the following error: \n<varname>string</varname>. For details refer to "<varname>string</varname>" in "<varname>string</varname>".: Cause: An error occurred during the resource action.; Action: Examine the accompanying error messages and respond accordingly.
CRS-05018: Clusterware has disabled an IP route associated with destination "<varname>string</varname>" and interface "<varname>string</varname>". For details, refer to "<varname>string</varname>" in "<varname>string</varname>".: Cause: A potentially conflicting route in the same subnet used by the address for the redundant interconnect was found and removed to prevent routing conflicts.; Action: Validate that the route described was not actually in use.
CRS-05019: All OCR locations are on ASM disk groups [<varname>string</varname>], and none of these disk groups are mounted. Details are at "<varname>string</varname>" in "<varname>string</varname>".: Cause: OCR was configured on ASM disk groups, and all of the listed disk groups failed to mount. The possible causes are: 1. A disk was not accessible. 2. A disk in a normal or high redundancy disk group failed after the most recent dismount. 3. The ASM_DISKSTRING in the SPFILE or the GPnP profile was incorrect.; Action: Check the ASM alert logs for more information. To correct disk access or failure issues either: a) restore access to the disks in the disk group and mount the disk group (via ASMCMD or SQL). or b) Issue a force mount to the disk group to offline missing disks and mount a normal or high redundancy disk group. To correct the ASM_DISKSTRING in the SPFILE and propagate the change to the GPnP profile, in sqlplus, issue the SQL command "ALTER SYSTEM SET ASM_DISKSTRING <discovery_string> ...", see Setting Oracle ASM Initialization Parameters in the Automatic Storage Management Administrator's Guide
CRS-05020: Not all endpoints are registered for listener <varname>string</varname>: Cause: Listener agent failed to register all endpoints to listener.; Action: Check listener log file for that listener.
CRS-05021: Check of storage failed: details at "<varname>string</varname>" in "<varname>string</varname>": Cause: The check of ASM storage failed because the storage was not accessible.; Action: Check Clusterware alert log and the referenced Oracle Clusterware trace file for additional information.
CRS-05022: Stop of resource "<varname>string</varname>" failed: current state is "<varname>string</varname>": Cause: The named resource failed to stop.; Action: Ensure there are no users of the resource and reissue the stop.
CRS-05023: Failed to unmount file system "<varname>string</varname>"; details at "<varname>string</varname>" in "<varname>string</varname>": Cause: The named file system resource failed to unmount.; Action: Determine which OS processes are accessing the mount point using an OS command such as 'fuser' or 'lsof' for Unix based platforms or 'handle' for Windows. Close, shut down, or terminate applications and processes accessing the mount point, then retry.
CRS-05024: Unmounting file system "<varname>string</varname>": Cause: A 'stop' of the file system resource mounted on the indicated path started.; Action: This is an informational message only.
CRS-05025: File system "<varname>string</varname>" unmounted: Cause: A 'stop' of the file system resource mounted on the indicated path completed normally.; Action: This is an informational message only.
CRS-05026: Failed to clean mount point "<varname>string</varname>"; details at "<varname>string</varname>" in "<varname>string</varname>": Cause: The clean of the volume failed because one or more processes on the system were accessing the mount point.; Action: Determine which OS processes are accessing the mount point using an OS command such as 'fuser' or 'lsof' for Unix based platforms or 'handle' for Windows. Close, shut down, or terminate applications and processes accessing the mount point, then retry.
CRS-05027: The ASM instance on node "<varname>string</varname>" cannot be stopped because it is currently being used by Cluster Ready Services.: Cause: An attempt to stop the ASM instance on the indicated server failed because Cluster Ready Services was using that ASM instance.; Action: Use 'crsctl stop crs' or 'crsctl stop cluster' to stop the Cluster Ready Services on the node.
CRS-05028: Cannot start resource "<varname>string</varname>" because the resource it depends on, "<varname>string</varname>", failed to start on the same node: Cause: The resource could not be started because the resource on which it depends failed to start on the same node.; Action: Manually start the dependency resource and then the resource on the same node.
CRS-05029: Agent failed to initialize ARP devices required for starting the HAIP resource: Cause: The resource could not be started because the ARP devices failed to start on the same node.; Action: Manually check the ARP devices on the same node and then start the resource.
CRS-05030: The resource action "<varname>string</varname> <varname>string</varname>" completed with the following error: <varname>string</varname>: Cause: An error occurred during the resource action.; Action: Examine the accompanying error messages and respond accordingly.
CRS-05031: invalid instance open mode: '<varname>string</varname>': Cause: The instance open mode passed to the Agent was invalid.; Action: Provide a correct instance open mode and retry.
CRS-05032: incompatible instance open mode: '<varname>string</varname>' with the role of the database in an Oracle Data Guard configuration: '<varname>string</varname>': Cause: The instance open mode passed to the Agent was invalid for the role of the database in an Oracle Data Guard configuration.; Action: Provide a correct instance open mode or change the role of the database in an Oracle Data Guard configuration and retry.
CRS-05033: Open mode '<varname>string</varname>' is incompatible with the current instance state '<varname>string</varname>'.: Cause: An attempt to change the instance to the specified open mode failed because the specified mode was incompatible with the current instance state.; Action: Reissue the command with a correct instance open mode.
CRS-05034: failed to get instance connection: Cause: Agent process failed to get an instance connection. Internal error.; Action: If error persists, contact Oracle Support Services.
CRS-05100: One or more attributes were not found for the entity.: Cause: The operation failed because the entity lacked one or more attributes.; Action: Provide the required attributes and retry the operation.
CRS-05101: The specified entity was not found in the entity list.: Cause: The Cluster Ready Services daemon was unable to locate the input entity in its entity list.; Action: Retry the operation after deleting the entity and registering it again.
CRS-05102: The entity is already registered.: Cause: An attempt was made to register an entity that was already registered.; Action: If the specification of the entity was incorrect, retry the operation with the correct entity specification.
CRS-05103: The entity is not registered.: Cause: An attempt was made to operate on an entity that was not registered.; Action: If the specification of the entity was incorrect, retry specifying the correct entity otherwise register the entity and retry the operation.
CRS-05104: The registration of the entity failed.: Cause: An attempt to register an entity failed. The preceding error messages provide additional details.; Action: Correct the issues described in the accompanying error messages and retry the registration.
CRS-05105: Unregistering the entity failed.: Cause: An attempt to unregister an entity failed. The preceding error messages provide additional details.; Action: Correct the issues described in the accompanying error messages and try to unregister the entity again.
CRS-05106: The entity failed to start.: Cause: An attempt to start an entity failed. The preceding error messages provide additional details.; Action: Correct the issues described in the accompanying error messages and try to start the entity again.
CRS-05107: The entity failed to stop.: Cause: An attempt to stop an entity failed. The preceding error messages provide additional details.; Action: Correct the issues described in the accompanying error messages and try to stop the entity again.
CRS-05108: The entity failed to relocate.: Cause: An attempt to relocate an entity failed. The preceding error messages provide additional details.; Action: Correct the issues described in the accompanying error messages and try to relocate the entity again.
CRS-05109: The status code is invalid.: Cause: The status code was not of the type enum CLSCRS_STAT.; Action: Verify that the status code argument is a valid code returned from the CLSCRS API and retry.
CRS-05110: The entity failed to update.: Cause: An attempt to update an entity failed. The preceding error messages provide additional details.; Action: Correct the issues described in the accompanying error messages and try to update the entity again.
CRS-05111: The entity has an invalid profile.: Cause: There were invalid attributes in the entity profile.; Action: Check the entity profile, remove any invalid attributes and retry the operation.
CRS-05112: The action script of the entity cannot be found.: Cause: The action script of the entity specified by the attribute ACTION_SCRIPT could not be located.; Action: Ensure that the attribute ACTION_SCRIPT exists and specifies a valid script for the entity.
CRS-05113: The entity has a dependency error.: Cause: An attempt to operate on an entity failed because of the resulting effect on one or more dependent entities. Preceding messages provide details on the nature of the problem.; Action: Take the corrective action as suggested by the preceding messages and resubmit the operation.
CRS-05114: A placement error was encountered while attempting to operate on the entity.: Cause: Based on the placement policy for the entity, there was no available server to which the entity could failover or start.; Action: Check the target server for the entity and restart the entity using the 'crsctl start' command.
CRS-05115: The specified server is not in the cluster.: Cause: The specified server name did not designate a server in the cluster.; Action: Check the server names in the cluster and retry the operation specifying a server that is a member of the cluster.
CRS-05116: The operation on the entity has been cancelled.: Cause: A scheduled or running operation was cancelled.; Action: None
CRS-05117: An internal error occurred while operating on the entity.: Cause: There was an internal error. This message will be preceded by another message with a more specific problem description.; Action: Review the accompanying error messages and contact Oracle Support Services.
CRS-05118: The entity or all of its instances are disabled.: Cause: The attempted request could not be serviced because the entity was disabled.; Action: Enable the entity and retry the operation.
CRS-05119: The active version of Cluster Ready Services is below the required level.: Cause: An attempt was made to use the functionality that has only been available beginning with the active version specified in the preceding message.; Action: Upgrade to the minimum required version stated in the preceding message.
CRS-05120: The requested action for the entity was aborted due to a timeout.: Cause: The timeout specified for a custom action was reached before the action could complete.; Action: Revise the timeout setting and retry the action.
CRS-05121: The operation cannot be completed due to invalid arguments.: Cause: Invalid arguments were specified to execute the CRS command.; Action: Check the arguments and specify only valid arguments to the command.
CRS-05122: The entity could not be registered due to a type mismatch.: Cause: The registration of an entity failed because the input entity type to the API did not match the type of the entity to be registered.; Action: Specify the correct entity type to register the entity.
CRS-05123: The resource validity check failed due to an invalid resource type.: Cause: The value of the attribute TYPE for the resource was not 'application'.; Action: Specify the value 'application' for the resource attribute TYPE.
CRS-05124: The entity has one or more attributes missing.: Cause: The validity check failed to find one or more of the attributes NAME, TYPE or ACTION_SCRIPT for the entity.; Action: Update the entity to have the missing attributes.
CRS-05125: The action script does not exist for the entity.: Cause: The validity check on the entity failed to find the file specified in the attribute ACTION_SCRIPT of the entity.; Action: Provide the full path to an existing file for the attribute ACTION_SCRIPT.
CRS-05126: The entity has invalid hosting servers for the placement policy.: Cause: Either the attribute HOSTMEM_REQ was not set or was empty for the entity.; Action: Either set the attribute HOSTMEM_REQ or set the attribute PLACEMENT to 'balanced'.
CRS-05127: The attribute HOSTING_MEMBERS must not be specified for the entity.: Cause: The attribute HOSTING_MEMBERS was specified for the entity with the balanced placement policy.; Action: Either unset the attribute HOSTING_MEMBERS or set the entity's placement policy to be 'favored' or 'restricted'.
CRS-05128: The value of the attribute HOSTING_MEMBERS for the entity is invalid.: Cause: The value of the attribute HOSTING_MEMBERS for the entity contained one or more of the characters: ',', ';' or ':'.; Action: Remove the invalid characters from the value of the attribute HOSTING_MEMBERS.
CRS-05129: An invalid placement policy was specified for the entity.: Cause: The attribute PLACEMENT for the entity was set to an invalid value.; Action: Set the attribute PLACEMENT to either 'favored','restricted', or 'balanced'.
CRS-05130: An invalid value was specified for the attribute AUTO_START.: Cause: The attribute AUTO_START of the entity was set to an invalid value.; Action: Set the attribute AUTO_START to either 'always', 'never', or 'restore'.
CRS-05131: One or more attribute of the entity are set to invalid values.: Cause: An attempt was made to set the attribute to a value of different type.; Action: Check the attributes and set the value to the appropriate type.
CRS-05132: The entity list is not empty.: Cause: The entity list passed to receive the information for the queried CRS entities was not empty.; Action: Create an empty list to pass as the output argument and retry.
CRS-05133: The generated connection key is too long.: Cause: The size of the environment variables HOST and HOSTNAME were greater than 255 characters.; Action: Set the environment variables HOST and HOSTNAME to values whose length is no more than 255 characters.
CRS-05151: Memory could not be allocated.: Cause: An attempt to allocate memory for an entity failed.; Action: Check the system logs, correct the condition and retry the operation.
CRS-05152: The pointer to the context is invalid.: Cause: A null pointer was passed as a pointer to the context.; Action: Create a valid context and pass its address to the requested operation.
CRS-05153: The entity pointer is invalid.: Cause: A null pointer was passed to the API for the entity name or the entity value."; Action: Allocate memory for the entity name and the entity value and pass in the valid pointers to the API.
CRS-05154: The input attribute name not found in the entity's attribute list.: Cause: An attempt was made to modify a nonexistent attribute of an entity.; Action: Provide an existing attribute of the entity and retry the operation.
CRS-05155: The end of the entity list was reached.: Cause: An attempt was made to search beyond the end of the entity list.; Action: None
CRS-05156: The entity has no attributes.: Cause: An attempt was made to get the attribute list for an entity that has no attributes.; Action: Check the entity name that is being passed. If it's correct then delete the entity, register it with correct attributes and retry the operation.
CRS-05157: The pointer to the operation status message in the entity structure is null.: Cause: The message pointer in the entity structure was null. The entity maybe corrupted.; Action: Delete the entity, register the entity and retry the operation.
CRS-05158: The entity list could not be found.: Cause: An attempt was made to perform an operation on an entity list, but no valid entity list was passed.; Action: None
CRS-05159: The specified entity already exists.: Cause: An attempt was made to add an entity that already exists.; Action: Check the entity name to be added. If it is correct and the existing entity must be recreated, then delete the entity and retry the operation.
CRS-05160: The entity list is empty.: Cause: The query failed because the entity list was empty.; Action: Retry the query supplying the intended list of entities.
CRS-05161: The entity name contains invalid characters.: Cause: An attempted operation was rejected because the specified entity name contained invalid characters.; Action: Retry the operation specifying a valid entity name.
CRS-05162: The name of a resource or a filter contains invalid characters.: Cause: An attempted operation was rejected because the specified resource name or the filter name contained invalid characters.; Action: Retry the operation specifying a valid resource name or the filter name.
CRS-05164: The attribute name is longer than 255 characters.: Cause: An attempt was made to use an attribute name with a length of more than 255 characters.; Action: Use an attribute name shorter than 255 characters and retry the operation.
CRS-05165: The supplied buffer is too small for the filter to string conversion.: Cause: The buffer supplied to the API was too small to hold the output string.; Action: Increase the buffer size and pass it to the API.
CRS-05166: The specified return code is invalid.: Cause: The return code was not of the type 'enum clscrsret'.; Action: Verify that the return code argument is a valid code returned from the CLSCRS API and retry.
CRS-05501: Unable to connect to eONS server on port <varname>number</varname>: Cause: The eONS server may not be active or listening on a different port.; Action: Ensure that the eONS resource is ONLINE and listening on the above port.
CRS-05502: Invalid event template <varname>string</varname>: Cause: The event template specified is invalid.; Action: The event template format must be <PROPERTY|ELEMENT>(<varname>attribute name</varname>=<literal|%resource attribute name%>) ...
CRS-05503: Error creating the eONS subscriber: Cause: The eONS server may not be active.; Action: Ensure that the CRS eONS resource is in ONLINE state.
CRS-05504: Node down event reported for node '<varname>string</varname>'.: Cause: The specified node was not responsive.; Action: Restart the specified node.
CRS-05601: MDNS: <varname>string</varname>: Cause: None, generic bypass mdns message.; Action: None
CRS-05602: mDNS service stopping by request.: Cause: MDNSD stopping by OHASD request.; Action: None
CRS-05705: Failed to get required resources: Cause: There was an internal error while evaluating the required resources for the subject resource.; Action: Contact Oracle Support Services.
CRS-05706: No more members to consider: Cause: There was no host found on which to start the resource based on the placement policy.; Action: Check the placement policy and the required resources for the subject resource.
CRS-05707: Failed after successful dependency consideration: Cause: There was no host found on which to start the resource based on the placement policy.; Action: Check the placement policy and the required resources for the subject resource.
CRS-05709: Resource '<varname>string</varname>' is already running on member '<varname>string</varname>': Cause: An attempt was made to start a resource on a host while it is already running on that host.; Action: This is an insignificant error. Check the operation being performed.
CRS-05801: Agent path is null or does not resemble a filesystem path: Cause: Unable to spawn the agent program because of incorrect agent path.; Action: Fix the agent path using 'crsctl modify type'.
CRS-05802: Unable to start the agent process: Cause: An attempt to start the agent process failed.; Action: Ensure that the agent path is correct and has the proper permissions, and retry the command.
CRS-05805: Missing the required action callback in agent: Cause: Unable to execute resource's command.; Action: Ensure that agent executable or action script contains the missing function.
CRS-05809: Failed to execute '<varname>string</varname>' value of '<varname>string</varname>' for '<varname>string</varname>'. Error information '<varname>string</varname>', Category : <varname>number</varname>, OS error : <varname>number</varname>: Cause: Unable to spawn the resource action script due to incorrect path value or incorrect permissions or other OS error.; Action: Correct the action script path and permissions or check and fix the reported OS error.
CRS-05810: Attempt to add a duplicate resource '<varname>string</varname>'. Details at <varname>string</varname> in <varname>string</varname>.: Cause: An identical resource was already being monitored.; Action: Rename the resource and retry the operation.
CRS-05811: Failed to read ORA_CRS_HOME from environment. Details at <varname>string</varname> in <varname>string</varname>.: Cause: The ORA_CRS_HOME environment variable was not set correctly.; Action: This variable is set during CRS installation. If necessary, reinstall CRS.
CRS-05812: Could not get local hostname. Details at <varname>string</varname> in <varname>string</varname>.: Cause: The hostname could not be read.; Action: Check that the hostname for the local machine is valid. If the problem persists, contact Oracle Support Services.
CRS-05813: Could not change directory to '<varname>string</varname>'. Details at <varname>string</varname> in <varname>string</varname>.: Cause: The specified path is inaccessible to the agent process.; Action: Check that the specified path exists.
CRS-05814: Agent '<varname>string</varname>' started with invalid arguments. Details at <varname>string</varname> in <varname>string</varname>.: Cause: An invalid parameter was supplied to the agent.; Action: Contact Oracle Support Services.
CRS-05815: Agent '<varname>string</varname>' could not find any base type entry points for type '<varname>string</varname>'. Details at <varname>string</varname> in <varname>string</varname>.: Cause: Action entry points were not defined for this agent.; Action: No action necessary if this is a script agent. If this is not a script agent, define action points in your agent code.
CRS-05816: Agent '<varname>string</varname>' could not start implicit monitoring for resource '<varname>string</varname>'. Details at <varname>string</varname> in <varname>string</varname>.: Cause: The resource was currently disabled and hence could not be monitored.; Action: Enable the resource.
CRS-05817: Caught exception from user code for command '<varname>string</varname>'. Details at <varname>string</varname> in <varname>string</varname>.: Cause: An exception was thrown from the user code when an action entry point was called.; Action: This is due to an error in the agent user code. Modify the agent's code to resolve this.
CRS-05818: Aborted command '<varname>string</varname>' for resource '<varname>string</varname>'. Details at <varname>string</varname> in <varname>string</varname>.: Cause: Execution of the specified command was aborted due to a timeout.; Action: Restart the resource manually. If the problem persists, contact Oracle Support Services.
CRS-05819: Could not abort command '<varname>string</varname>' for resource '<varname>string</varname>'. Details at <varname>string</varname> in <varname>string</varname>.: Cause: Attempt to abort the specified command failed.; Action: Define an abort action entry point for the agent.
CRS-05820: Agent '<varname>string</varname>' failed to initialize server process address. Details at <varname>string</varname> in <varname>string</varname>.: Cause: Agent could not connect to the server process.; Action: Contact Oracle Support Services.
CRS-05821: Agent '<varname>string</varname>' is started with wrong user '<varname>string</varname>'. Details at <varname>string</varname> in <varname>string</varname>.: Cause: An incorrect owner was specified for the agent.; Action: Make sure CRSD has enough privileges to spawn programs as the value specified as the 'owner' in the ACL attribute.
CRS-05822: Agent '<varname>string</varname>' disconnected from server. Details at <varname>string</varname> in <varname>string</varname>.: Cause: Agent could not connect to server process.; Action: Contact Oracle Support Services.
CRS-05823: Could not initialize agent framework. Details at <varname>string</varname> in <varname>string</varname>.: Cause: Initialization of the agent failed.; Action: Contact Oracle Support Services.
CRS-05824: Could not initialize server connect string '<varname>string</varname>'. Details at <varname>string</varname> in <varname>string</varname>.: Cause: Incorrect server connect string was specified in the environment.; Action: Contact Oracle Support Services.
CRS-05825: Agent '<varname>string</varname>' is unresponsive and will be restarted. Details at <varname>string</varname> in <varname>string</varname>.: Cause: The specified agent did not respond and will be restarted automatically.; Action: None
CRS-05826: Agent '<varname>string</varname>' could not read environment variable '<varname>string</varname>'. Details at <varname>string</varname> in <varname>string</varname>.: Cause: The agent could not read a required environment variable.; Action: Contact Oracle Support Services.
CRS-05827: Could not find information for resource '<varname>string</varname>'. Details at <varname>string</varname> in <varname>string</varname>.: Cause: The specified resource was not found in the internal list of resources.; Action: Check the agent parameters and restart the resource manually.
CRS-05828: Could not start agent '<varname>string</varname>'. Details at <varname>string</varname> in <varname>string</varname>.: Cause: Creation of the agent process failed.; Action: Contact Oracle Support Services.
CRS-05829: Failed to get definition for resource '<varname>string</varname>'. Details at <varname>string</varname> in <varname>string</varname>.: Cause: The definition of the resource could not be determined.; Action: Delete the resource and add it again using the crsctl command.
CRS-05830: Invalid path '<varname>string</varname>' found for agent filename. Details at <varname>string</varname> in <varname>string</varname>.: Cause: The path that was specified for the agent was incorrect.; Action: Check that the path exists and is readable.
CRS-05831: Agent '<varname>string</varname>' has exceeded maximum failures and has been disabled. Details at <varname>string</varname> in <varname>string</varname>.: Cause: The specified agent has failed too many times.; Action: Contact Oracle Support Services.
CRS-05832: Agent '<varname>string</varname>' was unable to process commands. Details at <varname>string</varname> in <varname>string</varname>.: Cause: Agent was unable to process commands.; Action: Contact Oracle Support Services.
CRS-05833: Cleaning resource '<varname>string</varname>' failed as part of reboot-less node fencing: Cause: A resource 'clean' action associated with reboot-less node eviction encountered an error. This is an expected occurence in most cases.; Action: None
CRS-05834: Resource '<varname>string</varname>' monitoring disabled due to repeated agent failures. Details at <varname>string</varname> in <varname>string</varname>.: Cause: A cluster resource was disabled because it was causing repeated agent failures.; Action: Restart the resource after resolving the problems with the agent.
CRS-05835: Agent version incapable of processing this command: Cause: A request encountered an older agent version that is not capable of processing that request.; Action: Upgrade the agent to the Clusterware version.
CRS-05836: Agent '<varname>string</varname>' version '<varname>string</varname>' cannot process command. Details at <varname>string</varname> in <varname>string</varname>.: Cause: A request encountered an older agent version that is not capable of processing that request.; Action: Upgrade the agent to the Clusterware version.
CRS-05837: Unable to open environment file '<varname>string</varname>'.: Cause: The environment file specified could not be opened.; Action: Verify that the filename, its location and its permsissions are correct.
CRS-05838: Syntax error in environment file '<varname>string</varname>'.: Cause: The environment file specified did not have key value pairs in the correct format.; Action: Correct the key value format and retry. Consult the administration document for the correct format.
CRS-05839: The requested action '<varname>string</varname>' for the resource '<varname>string</varname>' on server '<varname>string</varname>' was aborted due to a timeout.: Cause: The timeout specified for a custom action was reached before the action could complete.; Action: Revise the timeout setting and retry the action.
CRS-06001: User does not have permission to start CRSD.: Cause: Unable to start CRSD due to insufficient permissions.; Action: Start CRSD as a privileged user.
CRS-06007: Could not communicate with Event Manager.: Cause: Unable to communicate with Event Manager daemon.; Action: Run the 'crsctl check evmd' command to determine whether Event Manager daemon is properly configured and is running.
CRS-06015: Oracle Clusterware has experienced an internal error. Details at <varname>string</varname> in <varname>string</varname>.: Cause: This is an internal error.; Action: Contact Oracle Support Services.
CRS-06016: Resource auto-start has completed for server <varname>string</varname>: Cause: CRS has completed startup of resources on the specified server.; Action: None
CRS-06017: Processing resource auto-start for servers: <varname>string</varname>: Cause: The blocking start of Oracle High Availability Services has updated its list of servers to process.; Action: None
CRS-06021: Could not set system resource limits for Clusterware: "ulimit -<varname>string</varname> <varname>string</varname>".: Cause: A ulimit command issued internally to set system resource limits failed.; Action: Ensure that the correct resource limit values are set in the user profile and limits.conf.
CRS-06022: Starting Oracle High Availability Services-managed resources: Cause: Oracle High Availability Services is attempting to start resources for the local server.; Action: None
CRS-06023: Starting Oracle Cluster Ready Services-managed resources: Cause: Oracle Cluster Ready Services is attempting to start resources for the cluster.; Action: None
CRS-06024: Completed start of Oracle Cluster Ready Services-managed resources: Cause: Oracle Cluster Ready Services has started resources for the cluster.; Action: None
CRS-06504: '<varname>string</varname>' cannot be specified as an attribute.: Cause: An effort was made to explicitly specify an attribute that cannot be specified by the user; Action: Remove the mentioned attribute, and re-issue the command.
CRS-06505: Format of the EXPRESSION attribute '<varname>string</varname>' is invalid: Cause: The EXPRESSION attribute is invalid.; Action: Provide a valid value for the EXPRESSION attribute.
CRS-06530: cannot set node role because cluster is not configured in "flex" mode: Cause: An attempt to set a node's role using 'crsctl set node role' was rejected because the cluster is not running in "flex" mode. Node roles can only be set for nodes in "flex" clusters.; Action: Reissue the command after the cluster is configured in "flex" mode."
CRS-06531: Issued command is not supported in this version of CRS.: Cause: The command was rejected because related feature is not supported in this release.; Action: If this error occurs during rolling upgrade, wait for the upgrade to finish. Otherwise, upgrade to the required release or higher.
CRS-06602: No password specified.\n: Cause: A password was not entered in response to the password prompt.; Action: Enter a password.
CRS-06603: Cannot modify '<varname>string</varname>' policy.: Cause: An attempt was made to modify a read-only policy.; Action: Specify a policy that is not read-only.
CRS-06705: Oracle Clusterware Release Version ('<varname>string</varname>') does not match Software Version ('<varname>string</varname>'). Oracle Clusterware cannot be started.: Cause: Oracle Clusterware was started from an older home that has since been upgraded.; Action: Start Oracle Clusterware from the upgraded home. Also, check the CRS home configured in olr.loc and the /etc/init.d/ohasd script to make sure they have not been accidentally changed.
CRS-06706: Oracle Clusterware Release patch level ('<varname>number</varname>') does not match Software patch level ('<varname>number</varname>'). Oracle Clusterware cannot be started.: Cause: Oracle Clusterware was started from an older home that has since been patched.; Action: Start Oracle Clusterware from the patched home. Also, check the CRS home configured in olr.loc and the /etc/init.d/ohasd script to make sure they have not been accidentally changed.
CRS-06749: unable to get the software version: Cause: The crsctl query failed because the software version could not be retrieved. Either the clusterware stack was down, or the user was not root (UNIX) or Administrator (WINDOWS).; Action: Bring up the clusterware stack or run the query as a privileged user.
CRS-06750: unable to get the active version: Cause: The crsctl query failed because the active version could not be retrieved. Either the clusterware stack was down, or the user was not root (UNIX) or Administrator (WINDOWS).; Action: Bring up the clusterware stack or run the query as a privileged user.
CRS-06751: unable to get the software patch version: Cause: The crsctl query failed because the software patch version could not be retrieved. Either the clusterware stack was down, or the user was not root (UNIX) or Administrator (WINDOWS).; Action: Bring up the clusterware stack or run the query as a privileged user.
CRS-06752: Active version query failed.: Cause: The crsctl query failed because the active version could not be retrieved.; Action: See the accompanying error message and respond.
CRS-06753: Software patch query failed.: Cause: The crsctl query failed because the software patch version could not be retrieved.; Action: See the accompanying error message and respond.
CRS-06754: Software version query failed for node <varname>string</varname>.: Cause: The crsctl query failed to retrieve the software version.; Action: See the accompanying error message and respond.
CRS-06761: Invalid value for QoS Management policy management key '<varname>string</varname>' in OCR.: Cause: An invalid value for Quality of Service Management policy management key was found in the OCR.; Action: Contact Oracle Support Services.
CRS-06762: Unable to use CRSCTL for Policy Management because Quality of Service Management (QoS) is managing the Clusterware policies.: Cause: CRSCTL cannot be used for Policy Management because Quality of Service Management is configured to manage Clusterware policies.; Action: Use Quality of Service Management for Policy Management.
CRS-07000: Generic GPnP success: Cause: This is an internal error.; Action: Contact Oracle Support Services.
CRS-07001: Generic GPnP error: Cause: This is an internal error.; Action: Contact Oracle Support Services.
CRS-07002: Not enough memory: Cause: This is an internal error.; Action: Contact Oracle Support Services.
CRS-07003: GPnP facility initialization failed: Cause: This is an internal error.; Action: Contact Oracle Support Services.
CRS-07004: This feature is unsupported or not implemented: Cause: This is an internal error.; Action: Contact Oracle Support Services.
CRS-07005: Requested item not found: Cause: This is an internal error.; Action: Contact Oracle Support Services.
CRS-07006: Insufficient buffer size: Cause: This is an internal error.; Action: Contact Oracle Support Services.
CRS-07007: Error in file I/O operation: Cause: This is an internal error.; Action: Contact Oracle Support Services.
CRS-07008: Invalid permissions for the operation: Cause: This is an internal error.; Action: Contact Oracle Support Services.
CRS-07009: Bad authority id: Cause: This is an internal error.; Action: Contact Oracle Support Services.
CRS-07010: Key does not exist: Cause: This is an internal error.; Action: Contact Oracle Support Services.
CRS-07011: Bad key: Cause: This is an internal error.; Action: Contact Oracle Support Services.
CRS-07012: Hostname not found: Cause: This is an internal error.; Action: Contact Oracle Support Services.
CRS-07013: GPNPD daemon is not running: Cause: This is an internal error.; Action: Contact Oracle Support Services.
CRS-07014: Attempting to set a bad value: Cause: This is an internal error.; Action: Contact Oracle Support Services.
CRS-07015: Bad hostname value: Cause: This is an internal error.; Action: Contact Oracle Support Services.
CRS-07016: Bad authority id value: Cause: This is an internal error.; Action: Contact Oracle Support Services.
CRS-07025: Duplicate profile: Cause: This is an internal error.; Action: Contact Oracle Support Services.
CRS-07026: Profile is not given or not available: Cause: This is an internal error.; Action: Contact Oracle Support Services.
CRS-07027: Badly formed profile: Cause: This is an internal error.; Action: Contact Oracle Support Services.
CRS-07028: Profile is too big to be valid: Cause: This is an internal error.; Action: Contact Oracle Support Services.
CRS-07029: Profile is older than the current: Cause: This is an internal error.; Action: Contact Oracle Support Services.
CRS-07030: Profile exists in memory only, not saved: Cause: This is an internal error.; Action: Contact Oracle Support Services.
CRS-07031: Request retry message from GPNPD: Cause: This is an internal error.; Action: Contact Oracle Support Services.
CRS-07032: Value already set in profile: Cause: This is an internal error.; Action: Contact Oracle Support Services.
CRS-07040: Generic XML error: Cause: This is an internal error.; Action: Contact Oracle Support Services.
CRS-07041: GPnP XML profile is not well formed: Cause: This is an internal error.; Action: Contact Oracle Support Services.
CRS-07047: Communication timeout: Cause: This is an internal error.; Action: Contact Oracle Support Services.
CRS-07053: Resource discovery error: Cause: This is an internal error.; Action: Contact Oracle Support Services.
CRS-07056: OCR Init error: Cause: This is an internal error.; Action: Contact Oracle Support Services.
CRS-07057: Reinit OCR to a different bootlevel: Cause: This is an internal error.; Action: Contact Oracle Support Services.
CRS-07058: OCR error: Cause: This is an internal error.; Action: Contact Oracle Support Services.
CRS-07065: GPnP wallet error: Cause: This is an internal error.; Action: Contact Oracle Support Services.
CRS-07066: Requested GPnP wallet is not found: Cause: This is an internal error.; Action: Contact Oracle Support Services.
CRS-07067: Invalid GPnP wallet password given: Cause: This is an internal error.; Action: Contact Oracle Support Services.
CRS-07068: GPnP wallet is too big to be valid: Cause: This is an internal error.; Action: Contact Oracle Support Services.
CRS-07069: GPnP wallet is corrupted or invalid: Cause: This is an internal error.; Action: Contact Oracle Support Services.
CRS-07070: Bad or missing private key in GPnP wallet: Cause: This is an internal error.; Action: Contact Oracle Support Services.
CRS-07071: Bad or missing public key in GPnP wallet: Cause: This is an internal error.; Action: Contact Oracle Support Services.
CRS-07076: Failed to init crypto libraries: Cause: This is an internal error.; Action: Contact Oracle Support Services.
CRS-07085: GPnP profile unsigned: Cause: This is an internal error.; Action: Contact Oracle Support Services.
CRS-07086: GPnP profile signature invalid: Cause: This is an internal error.; Action: Contact Oracle Support Services.
CRS-07087: GPnP profile valid peer signature: Cause: This is an internal error.; Action: Contact Oracle Support Services.
CRS-07088: GPnP profile valid PA signature: Cause: This is an internal error.; Action: Contact Oracle Support Services.
CRS-07089: GPnP profile was signed with a different wallet: Cause: This is an internal error.; Action: Contact Oracle Support Services.
CRS-07090: Grid Naming Service (GNS) error: Cause: This is an internal error.; Action: Contact Oracle Support Services.
CRS-07095: GPnP tool usage: Cause: This is an internal error.; Action: Contact Oracle Support Services.
CRS-07096: GPnP tool version: Cause: This is an internal error.; Action: Contact Oracle Support Services.
CRS-08000: unable to obtain local host name for reboot advisory log file scan: Cause: An attempt to retrieve the local host name failed. The scan for reboot advisory files will not use host name criteria and so may report occurrences for other nodes as well as this one.; Action: Report this error to Oracle Support Services.
CRS-08001: an error occurred accessing reboot advisory log file location: <varname>string</varname>: Cause: The scan for reboot advisory log files was unable to access the indicated file system location. The location was skipped, so any reboot advisory files that it contains will not be reported. This message is accompanied by CLSU- messages containing details of the access error.; Action: Respond based on the error described by the accompanying CLSU- messages. This may involve re-creating the directory or changing its permissions.
CRS-08002: an error occurred searching reboot advisory log file location: <varname>string</varname>: Cause: The scan for reboot advisory log files was unable to read the next file name from the indicated file system location. No further processing of reboot advisory files from that location occurs. This message is accompanied by CLSU- messages containing details of the access error.; Action: Respond based on the error described by the accompanying CLSU- messages.
CRS-08003: reboot advisory log file: <varname>string</varname> is unexpectedly empty: Cause: The scan for reboot advisory log files encountered a file that was empty. This might happen (rarely) if a component is initializing its use of reboot advisory at the same time the scan is running. Processing of other files in the location continues.; Action: Frequent occurrence of this message should be reported to Oracle Support Services.
CRS-08004: an error occurred reading reboot advisory log file: <varname>string</varname>: Cause: The scan for reboot advisory log files experienced a read error on a reboot advisory file. No further processing is done for that file, but the scan continues with other files. This message is accompanied by CLSU- messages containing details of the read error.; Action: Respond based on the accompanying CLSU- messages.
CRS-08005: an error occurred closing reboot advisory log file: <varname>string</varname>: Cause: The scan for reboot advisory log files experienced a close error on a reboot advisory file. The scan continues with other files. This message is accompanied by CLSU- messages containing details of the close error.; Action: Report this error to Oracle Support Services.
CRS-08006: an error occurred opening reboot advisory log file: <varname>string</varname>: Cause: The scan for reboot advisory log files experienced an error when it opened a reboot advisory file. The scan continues with other files. This message is accompanied by CLSU- messages containing details of the open error.; Action: If the error indicated in the accompanying CLSU- messages is one that can be corrected, do so. Otherwise, report this error to Oracle Support Services.
CRS-08007: an error occurred closing reboot advisory log file location: <varname>string</varname>: Cause: The scan for reboot advisory log files experienced an error when it closed the indicated file system location. Processing of other reboot advisory locations (if any) continues normally. This message is accompanied by CLSU- messages containing details of the close error.; Action: Report this error to Oracle Support Services.
CRS-08008: <varname>string</varname>: Cause: Operating system error data related to reboot advisory file processing was returned. The error data is packaged in a CLSU- message that follows "CRS-08008:". One or more of these messages appears after a message announcing the error condition.; Action: Look up the embedded CLSU- message for an explanation of the operating system error data. If there is no CLSU- message ID present, contact Oracle Support Services.
CRS-08009: reboot advisory log file: <varname>string</varname> contains invalid data (length <varname>number</varname>, error code <varname>number</varname>): Cause: A reboot advisory log record read from the indicated file contained incorrect data.; Action: Report this error to Oracle Support Services.
CRS-08010: invalid network reboot advisory message detected (length <varname>number</varname>, error code <varname>number</varname>): Cause: A reboot advisory record received over the network was improperly formed or contained incorrect data.; Action: Report this error to Oracle Support Services.
CRS-08011: reboot advisory message from host: <varname>string</varname>, component: <varname>string</varname>, with time stamp: <varname>string</varname>: Cause: A reboot advisory message was detected. During Oracle Clusterware startup on a given host, messages recently written to disk on that host before a reset or reboot are detected and announced. Subsequently, network reboot advisory messages may be announced as they occur. These are reported by hosts other than the one being reset or rebooted. This message is accompanied by other messages containing details on what led to the reset or reboot. The time stamp in this message begins with either 'U' (denoting UTC time) or 'L' (denoting local time as viewed by the issuing host). Note that a given reset or reboot event can produce multiple occurrences of these messages on multiple hosts in the cluster.; Action: Use the reboot advisory message(s) to determine why Oracle Clusterware caused a reset or reboot of the affected host, and respond accordingly. Refer to the discussion of reboot advisories in the Oracle Clusterware administration documentation for additional guidance.
CRS-08012: reboot advisory message from a higher Oracle Clusterware version detected: Cause: A reboot advisory message from a higher version installation of Oracle Clusterware was detected. This is an expected occurrence with network reboot advisories when there are nodes with a higher Oracle Clusterware version than this node (such as during an upgrade). It is an unexpected condition with file reboot advisories.; Action: The reboot advisory message is displayed in a following CRS-08013 message in a "raw" text form. In the case of network reboot advisories, the explanatory message text should be readable and useful to determine the cause of the node reboot. If the reboot advisory message is from a file, report this message to Oracle Support Services.
CRS-08013: reboot advisory message text: <varname>string</varname>: Cause: An explanatory text message associated with a reboot advisory announced in a preceding CRS-08011 or CRS-08012 message was displayed. These text messages are always written in US English locale.; Action: Refer to the descriptions of messages CRS-08011 and -08012, and to the Oracle Clusterware documentation on reboot advisories.
CRS-08014: reboot advisory binary data (<varname>number</varname> bytes<varname>string</varname>) follows:: Cause: Binary data associated with a reboot advisory message was displayed. It is followed by one or more lines of CRS-08015 message containing the binary data formatted in hexadecimal. If an asterisk appears inside the parentheses, an invalid data length was detected.; Action: Refer to the description of message CRS-08011 and -08012, and to the Oracle Clusterware documentation on reboot advisories.
CRS-08015: <varname>number</varname> <varname>string</varname>: Cause: Hexadecimal display of binary data included in a reboot advisory log message was displayed. The first number is an offset and is followed by up to 16 bytes of data.; Action: Refer to the description of message CRS-08011 and -08012, and to the Oracle Clusterware documentation on reboot advisories.
CRS-08016: an error occurred determining the location for reboot advisory log files: Cause: The search for reboot advisory log files was unable to determine the file system location used for those files. Processing of reboot advisory files is skipped. This message is accompanied by CLSU- messages containing failure details. This is an internal error.; Action: Report this error to Oracle Support Services.
CRS-08017: location: <varname>string</varname> has <varname>number</varname> reboot advisory log files, <varname>number</varname> were announced and <varname>number</varname> errors occurred: Cause: This summary message is written during Oracle Clusterware startup if one or more reboot advisory log files was found and examined.; Action: This message is informational, but if the error count is nonzero the associated messages (earlier in the alert log) should be examined.
CRS-08018: warning: missing cluster identity data for reboot advisory message validation: Cause: During Oracle Clusterware start up, an attempt to obtain the identity of the cluster failed. Processing continues normally, but network reboot advisories from nodes in other clusters may be reported in this cluster's alert log.; Action: Report this error to Oracle Support Services.
CRS-08019: warning generated by the initialization of the reboot advisory in the CSS agent, <varname>string</varname>: Cause: During initialization of the reboot advisory, a warning was generated; Action: Report this warning to Oracle Support Services.
CRS-08020: error generated by the initialization of the reboot advisory in the CSS agent, <varname>string</varname>: Cause: During initialization of the reboot advisory, an error was generated.; Action: Report this error to Oracle Support Services.
CRS-08500: Oracle Clusterware <varname>string</varname> process is starting with operating system process ID <varname>string</varname>: Cause: The indicated service or component of Oracle Clusterware began execution.; Action: None
CRS-08501: Oracle Clusterware <varname>string</varname> process with operating system process ID <varname>string</varname> is ending with return value <varname>number</varname>: Cause: The indicated service or component of Oracle Clusterware ended execution.; Action: None
CRS-08502: Oracle Clusterware <varname>string</varname> process with operating system process ID <varname>string</varname> failed in initialization: Cause: The indicated service or component of Oracle Clusterware was unable to complete initialization.; Action: Report this error to Oracle Support Services.
CRS-08503: Oracle Clusterware <varname>string</varname> process with operating system process ID <varname>string</varname> experienced fatal signal or exception code <varname>number</varname>: Cause: The indicated service or component of Oracle Clusterware encountered a fatal exception.; Action: Report this error to Oracle Support Services.
CRS-08504: Oracle Clusterware <varname>string</varname> process with operating system process ID <varname>string</varname> is exiting: Cause: The indicated service or component of Oracle Clusterware ended execution using the operating system 'exit' function.; Action: None
CRS-08505: Oracle Clusterware <varname>string</varname> process with operating system process ID <varname>string</varname> experienced fatal error <varname>string</varname>-<varname>number</varname>: Cause: The indicated service or component of Oracle Clusterware encountered an internal error, causing an ADR incident to be raised.; Action: Report this error to Oracle Support Services.
CRS-09000: Failed to allocate memory.: Cause: During intialization, memory could not be allocated.; Action: Report this error to Oracle Support Services.
CRS-09001: Internal Error: Cause: An internal error occurred.; Action: Report this error to Oracle Support Services.
CRS-09003: Cluster Health Monitor is not supported in this configuration.: Cause: Grid Infrastructure Management Repository was not configured.; Action: Re-Install Grid Infrastructure and ensure that Grid Infrastructure Management Repository is configured.
CRS-09004: Error reading from standard input: Cause: Could not read commands from the command line.; Action: Report this error to Oracle Support Services.
CRS-09005: Quoted string not ended: Cause: An unmatched " was found in the command entered.; Action: Put in the corresponding quote or remove the unmatched quote.
CRS-09008: Unknown verb <varname>string</varname>: Cause: Unknown or invalid verb passed to oclumon.; Action: Use 'oclumon -h' in command line or help command in interactive mode to see the supported verbs.
CRS-09009: Error <varname>string</varname>: Parsing error. Invalid arguments specified.: Cause: Invalid or unknown arguments passed.; Action: Refer to product documentation or to command online help for an explanation of verbs and arguments.
CRS-09010: Error <varname>string</varname>: mandatory data not supplied: Cause: Mandatory data not supplied to the command.; Action: Refer to product documentation or to command online help for an explanation of verbs and arguments.
CRS-09011: Error <varname>string</varname>: Failed to initialize connection to the Cluster Logger Service: Cause: Error occurred while connecting to the Cluster Logger Service.; Action: Ensure that Cluster Logger Service is running and reachable from the client node by using the 'ping' command for the given node.
CRS-09012: Error <varname>string</varname>: Error sending query to the Cluster Logger Service: Cause: Error occurred while sending query to the Cluster Logger Service.; Action: Ensure that the Cluster Logger Service is running and reachable from the client node by using the 'ping' command for the specified node.
CRS-09013: Error <varname>string</varname>: Invalid data received from the Cluster Logger Service: Cause: Invalid or unknown data received from the Cluster Logger Service.; Action: Ensure that the Cluster Logger Service is running and reachable from the client node by using the 'ping' command for the specified node.
CRS-09014: Error: Corrupt reply from the Cluster Logger Service: Cause: Invalid or unknown data received from the Cluster Logger Service.; Action: Make sure that the version of both master and client installation is same. Also, check the connectivity between master and client using the 'ping'.
CRS-09017: Error: Invalid or unknown reply received from the Cluster Logger Service: Cause: Error occurred in the data received.; Action: Make sure that the version of both master and client installation is same. Also, check the connectivity between master and client.
CRS-09018: Error <varname>string</varname>: No arguments supplied: Cause: No argument was supplied with the command.; Action: Some commands need arguments with them. Refer to the product documentation or to the online help display.
CRS-09019: Error <varname>string</varname>: No parameter <varname>string</varname> supported: Cause: A wrong parameter was passed with the command.; Action: Refer to the command help and pass the correct parameters.
CRS-09020: Error <varname>string</varname>: No master node name specified: Cause: The master node name was not specified in the command.; Action: Pass the appropriate master node name with the command.
CRS-09021: Error <varname>string</varname>: Invalid or no start time specified: Cause: A start time was not specified or the time was passed in the wrong format.; Action: Pass the correct start time. For correct format, refer to command help.
CRS-09022: Error <varname>string</varname>: Invalid or no end time specified: Cause: A end time was not specified or the time was passed in the wrong format.; Action: Pass the correct end time. For correct format, refer to command help.
CRS-09023: Error <varname>string</varname>: Time not specified or in wrong format or invalid: Cause: Time was not specified or was invalid.; Action: Pass the correct and valid time. For correct format, refer to command help.
CRS-09024: Error <varname>string</varname>: No node name specified: Cause: Node name not specified.; Action: Provide a node name in the command. Refer to the product documentation or to the command online help for information.
CRS-09025: Error <varname>string</varname>: No disk ID name specified: Cause: Disk ID was not specified in the command with -diskid.; Action: Pass a valid disk ID with -diskid option.
CRS-09026: Error <varname>string</varname>: No parameter specified: Cause: The parameter was not specified in the query.; Action: Pass appropriate parameter for query. Refer to the product documentation or to the command online help for information.
CRS-09027: Error <varname>string</varname>: Parameter <varname>string</varname> is not supported with this verb: Cause: Invalid or unknown parameter passed.; Action: Pass the correct parameter. Refer to the product documentation or to the command online help for information.
CRS-09028: Error <varname>string</varname>: No NIC ID specified: Cause: NIC ID was not specified in the command with -nicid.; Action: Pass a valid NIC ID with -nic option.
CRS-09029: Error <varname>string</varname>: No PID specified: Cause: PID was not specified in the command with -pid.; Action: Pass a valid PID with -pid option.
CRS-09030: Error <varname>string</varname>: No region specified: Cause: Incorrect or no region specified with -c option.; Action: Pass a valid region with -c option. Refer to the product documentation or to the command online help for information.
CRS-09031: Error <varname>string</varname>: Argument <varname>string</varname> not supported with this verb: Cause: Unknown or invalid argument passed with the command.; Action: Refer to the product documentation or to the command online help for information on supported arguments.
CRS-09032: Invalid hour specified in the time argument: Cause: Invalid hour in the time string was passed.; Action: Pass a valid time string in accordance with the format. Refer to the product documentation or to the command online help for information on supported arguments.
CRS-09033: Invalid minutes specified in the time argument: Cause: Invalid minutes in the time string was passed.; Action: Pass a valid time string in accordance with the format. Refer to the product documentation or to the command online help for information on supported arguments.
CRS-09034: Invalid seconds specified in the time argument: Cause: Invalid seconds in the time string was passed.; Action: Pass a valid time string in accordance with the format. Refer to the product documentation or to the command online help for information on supported arguments.
CRS-09035: Arguments not in proper format, or invalid arguments: Cause: Invalid arguments specified.; Action: Pass a valid verb and correct arguments for it. Refer to the product documentation or to the command online help for information on supported arguments.
CRS-09036: Invalid Cluster Health Monitor repository size specified: Cause: Non-numeric value or value out of range specified for Cluster Health Monitor repository size.; Action: Specify Cluster Health Monitor repository size in the valid range. Refer to the product documentation or to the command online help for information on supported arguments.
CRS-09037: <varname>string</varname> Error: Node name not specified. -disk, -nic or -proc need node name: Cause: The required node name was not specified for -disk, -nic or -proc.; Action: Provide a node name with -n option. Refer to the product documentation or to the command online help for information on supported arguments.
CRS-09038: Error: -s and -e need to be specified together: Cause: Either -s or -e is missing.; Action: Start and end time need to be specified together for range queries, which cannot be unbounded. Refer to the product documentation or to the command online help for information on supported arguments.
CRS-09039: Error <varname>string</varname>: -i is not allowed with the range query: Cause: The -i option was specified on a oclumon range query.; Action: Use -i only in continuous mode. Refer to the command inline help or product documentation for more information.
CRS-09040: Error <varname>string</varname>: Band value not specified or incorrect: Cause: The band value was not specified with -t option or was invalid.; Action: Provide a valid band value. Refer to the product documentation or to the command online help for information on supported arguments..
CRS-09041: Error <varname>string</varname>: The -repos argument was specified without an option.: Cause: -repos was not specified with the option, generating a parsing error.; Action: Provide a valid option to -repos. Refer to the product documentation or to the command online help for information on supported arguments.
CRS-09042: Error <varname>string</varname>: No size specified with 'checkretentiontime': Cause: A valid value was not specified with 'checkretentiontime'.; Action: Provide a valid numerical value with 'checkretentiontime'. Refer to the product documentation or to the command online help for information on supported arguments.
CRS-09043: Error <varname>string</varname>: Non-numeric or invalid value for size: <varname>string</varname>: Cause: An invalid or non-numeric value was specified for size.; Action: Provide a valid numeric size. Refer to the product documentation or to the command online help for information on supported arguments.
CRS-09044: No key specified with -getkey: Cause: An option was not specified with -getkey.; Action: Provide a valid key as an option with -getkey.
CRS-09045: No key specified for -get: Cause: An option was not specified with -get.; Action: Provide a valid option with -get. Refer to the product documentation or to the command online help for information on supported arguments.
CRS-09046: Invalid key specified: Cause: An unknown key was specified with -get.; Action: Provide a supported key with -get. Refer to the product documentation or to the command online help for information on supported arguments.
CRS-09047: Error <varname>string</varname>: Error Dumping Log (return code:<varname>number</varname> ) for node <varname>string</varname>: Cause: An error occurred while dumping local log.; Action: Report this error to Oracle Support Services. Cluster Health Monitor repository directory may be unreachable, unreadable or incorrect.
CRS-09048: Error <varname>string</varname>: No data received from the Cluster Logger Service after <varname>number</varname> attempts: Cause: Data was not received from the Cluster Logger Service after the specified number of attempts or data was not available.; Action: None
CRS-09049: Error <varname>string</varname>: Cannot get environment variable CRFHOME: Cause: An internal error occurred.; Action: Report this error to Oracle Support Services.
CRS-09050: Error <varname>string</varname>: Too many host names: Cause: Too many host names were specified.; Action: Provide valid number of host names. Refer to the product documentation or to the command online help for information.
CRS-09051: Error <varname>string</varname>: Invalid interval size specified: Cause: Non-numeric or invalid interval specified.; Action: Provide a valid numerical value for interval size. Refer to the product documentation or to the command online help for information
CRS-09052: Error <varname>string</varname>: <varname>string</varname> control not supported: Cause: The specified debug control was not supported.; Action: Provide a supported control. Refer to the product documentation or to the command online help for information.
CRS-09053: Key:value pair missing: Cause: A required key:value pair was missing.; Action: Provide a valid key:value pair. Refer to the product documentation or to the command online help for information
CRS-09054: Incomplete or invalid parameters <varname>string</varname>: Cause: Incomplete or invalid parameters supplied.; Action: Provide the complete and correct parameters. Refer to the product documentation or to the command online help for information
CRS-09055: module:level specified in invalid format or invalid value: Cause: Invalid format or value specified for module:level.; Action: Provide correct module:level. Refer to the product documentation or to the command online help for information
CRS-09056: Error <varname>string</varname>: Invalid Cluster Health Monitor repository location specified: Cause: Invalid Cluster Health Monitor repository location specified.; Action: Provide a directory with read and write permissions for Cluster Health Monitor repository location. Refer to the product documentation or to the command online help for information.
CRS-09057: Error <varname>string</varname>: No response received from the Cluster Logger Service: Cause: No data received from the Cluster Logger Service for the query.; Action: Ensure that the Cluster Logger Service is running and reachable from the client node by using the 'ping' command for the specified node.
CRS-09058: Error <varname>string</varname>: Changing log level failed due to authentication failure: Cause: Log level could not be changed due to authentication failure.; Action: Ensure that this command is run as root.
CRS-09059: Error <varname>string</varname>: Changing log level failed due to connection failure: Cause: A connection failure occurred while changing the log.; Action: Ensure that the daemons are running and are reachable.
CRS-09060: Error <varname>string</varname>: Unable to send message due to memory allocation failure: Cause: Memory could not be allocated for debug message.; Action: Report this error to Oracle Support Services.
CRS-09061: Error <varname>string</varname>: Changing log level failed due to response time-out: Cause: A time out happened while waiting for response.; Action: Report this error to Oracle Support Services.
CRS-09062: Error <varname>string</varname>: Error in changing log level: Cause: An error occurred while changing log level.; Action: Report this error to Oracle Support Services.
CRS-09063: Given time range is more than 1 hour: Cause: The time range specified with showtrail command was more than one hour.; Action: Provide a range of less than 1 hour for showtrail.
CRS-09064: Error <varname>string</varname>: Changing log level failed due to connection failure. Cannot connect to daemon <varname>string</varname>.: Cause: A connection failure occurred while changing the log level.; Action: Ensure that the specified daemon is running and reachable.
CRS-09065: Disk ID not found: Cause: Given disk ID was not found or not present in the interesting list.; Action: Provide a disk ID which is available at the start of the query range.
CRS-09066: Process ID not found: Cause: Given process ID was not found.; Action: Provide a process ID which is available at the start of the query range.
CRS-09067: NIC ID not found: Cause: Given NIC ID was not found.; Action: Provide a correct NIC ID.
CRS-09068: Error <varname>string</varname>: -allnodes and -n must not be used together: Cause: Both -allnodes and -n were supplied on a dumpnodeview command.; Action: Specify either -allnodes or -n with specific nodes.
CRS-09069: The new Cluster Health Monitor repository location is <varname>string</varname>.: Cause: The Cluster Health Monitor repository location was successfully replaced.; Action: None
CRS-09070: The new Cluster Health Monitor repository retention time is <varname>number</varname> seconds.: Cause: The Cluster Health Monitor repository retention time was successfully modified.; Action: None
CRS-09071: Internal error in Cluster Health Analysis during problem analysis: Cause: An internal error occurred during problem analysis.; Action: Contact Oracle Support Services.
CRS-09072: Internal error in Cluster Health Analysis report output: Cause: An internal error occurred while reporting a problem.; Action: Contact Oracle Support Services.
CRS-09073: No problems to display: Cause: No problems were found that matched the selection criteria specified to the 'oclumon analyze' command.; Action: None
CRS-09074: No component specified to the component argument: Cause: An 'oclumon analyze' command was issued without a component.; Action: Provide a component to the 'oclumon analyze' command. Refer to the product documentation or to the command online help for information.
CRS-09075: Invalid component name '<varname>string</varname>' specified as the component argument: Cause: An 'oclumon analyze' command was issued with an invalid component.; Action: Pass a valid component to the 'oclumon analyze' command. Refer to the product documentation or to the command online help for information on supported arguments.
CRS-09076: Error loading the required Cluster Health models: Cause: The required Cluster Health models did not exist, did not have the required permission, or had an invalid format.; Action: Ensure that the Cluster Health models are present in the 'cdata/model' subdirectory of the Oracle Grid Infrastructure home, and that their permissions are correct. If the problem persists, check for entries in the oclumon log file for more details.
CRS-09077: Invalid path '<varname>string</varname>' was specified as the data directory argument: Cause: An 'oclumon analyze' command was issued specifying a data directory that does not exist or is not accessible to the user.; Action: Pass a valid path to the 'oclumon analyze' command. Look at accompanying messages for more information.
CRS-09078: Invalid severity value '<varname>string</varname>' provided as the severity argument: Cause: An 'oclumon analyze' command was issued with an invalid severity value.; Action: Pass a valid severity value to the 'oclumon analyze' command. Refer to the product documentation or to the command online help for information.
CRS-09079: No instance name specified for the instance argument: Cause: An 'oclumon' command was issued without an instance name.; Action: Provide an instance name with the 'oclumon' command. Refer to the product documentation or to the command online help for information.
CRS-09080: data for other nodes of cluster cannot be viewed from this node: Cause: An 'oclumon dumpnodeview -n' command was issued for other nodes from a leaf node.; Action: Refer to the Cluster Health Monitor documentation for more information.
CRS-09081: Internal error in Cluster Health calibration: Cause: An internal error occurred during cluster health model calibration.; Action: Contact Oracle Support Services.
CRS-09082: Insufficient permission to execute command. Require privileged user: Cause: A non-privileged user attempted to execute a command requiring privilege.; Action: Issue the command again as a privileged user.
CRS-09083: No database name specified for the database argument: Cause: An 'oclumon' command was issued without a database name.; Action: Provide a database name with the 'oclumon' command. Refer to the product documentation or to the command online help for information.
CRS-09084: Error <varname>string</varname>: Node name is greater than <varname>string</varname> bytes: Cause: An 'oclumon' command was issued with a node name that was too long.; Action: Supply a node name no greater than the indicated size with the 'oclumon' command and retry. Refer to the product documentation or to the command online help for information.
CRS-09085: Model name missing or invalid for the model argument: Cause: The previous oclumon command was rejected because it did not include a valid model name.; Action: Reissue the oclumon command providing a valid model name. Refer to the product documentation or to the command online help for information.
CRS-09086: Server pool name missing or invalid for the server pool argument: Cause: The previous oclumon command was rejected because it did not include a valid server pool name.; Action: Reissue the oclumon command providing a valid server pool name. Refer to the product documentation or to the command online help for information.
CRS-09087: Server pool name specified in a cluster without user-defined server pools: Cause: The previous oclumon command was rejected because it was issued with a server pool name on a cluster without user-defined server pools.; Action: Reissue the oclumon command without a server pool name. Refer to the product documentation or to the command online help for information.
CRS-09088: Node name specified in a cluster with user-defined server pools: Cause: The previous oclumon command was rejected because it was issued with a node name on a cluster with user-defined server pools.; Action: Reissue the oclumon command without a node name. Refer to the product documentation or to the command online help for information.
CRS-09089: Parameter '<varname>string</varname>' is not supported in combination with parameter '<varname>string</varname>'.: Cause: The command was rejected because the combination of parameters passed was invalid.; Action: Refer to the product documentation or to the online help for the command and reissue the command with the correct parameters.
CRS-09090: Error <varname>string</varname>: Parameter '<varname>string</varname>' is specified multiple times.: Cause: The previous 'oclumon' command was rejected because the parameter listed in the message was specified multiple times.; Action: Refer to the product documentation or to the online help for the command and reissue the command with the correct parameters.
CRS-09091: database name '<varname>string</varname>' is invalid: Cause: An 'oclumon' command was issued with an invalid database name.; Action: Provide a valid database name with the 'oclumon' command. Refer to the product documentation or to the online help for the command for information.
CRS-09092: No instance of database '<varname>string</varname>' is active on this node.: Cause: The 'oclumon calibrate' command was rejected because no instance of the above listed database was active on the local node.; Action: Issue the 'srvctl start database' command to start the above listed database. Issue the 'srvctl status database' command to retrieve a list of nodes on which the database instances are online. Issue the 'oclumon calibrate' command again from a node on which the database instance is online. Refer to the product documentation or to the online help for the command for information.
CRS-09093: Database '<varname>string</varname>' of type '<varname>string</varname>' is not supported in a cluster with user-defined server pools.: Cause: An 'oclumon' command was issued with an administrator-managed database in a cluster with user-defined server pools.; Action: Reconfigure the database to be policy-managed using the 'srvctl modify database' command to enable monitoring by the Oracle Cluster Health Analysis service. Verify the monitoring status using the 'srvctl status cha' command. Re-issue the 'oclumon calibrate' command. Refer to the product documentation or to the online help for the command for information.
CRS-09100: Error setting Cluster Health Monitor repository size: Cause: An error occurred while setting Cluster Health Monitor repository size on the Cluster Logger Service.; Action: Report this error to Oracle Support Services.
CRS-09101: Error updating Cluster Health Monitor repository size in configuration file.: Cause: An error occurred while writing the Cluster Health Monitor repository size to configuration files.; Action: Report this error to Oracle Support Services.
CRS-09102: No data for the node at the specified time: Cause: Data was not found for the specified node.; Action: This is an informational message only.
CRS-09103: No data available: Cause: Data was not available for the query.; Action: Make sure the System Monitor Service is running on the specified node.
CRS-09104: No data available for the specified nodes: Cause: Data was not available for specified nodes.; Action: Make sure the System Monitor Service is running on the specified nodes.
CRS-09105: Internal Error on master: Cause: An internal error on master caused this error.; Action: Report this error to Oracle Support Services.
CRS-09106: Data requested was outside Cluster Health Monitor retention time limits.: Cause: A request for data outside Cluster Health Monitor repository limit caused this error.; Action: Data needs to be requested in the proper Cluster Health Monitor repository limits. Refer to the product documentation for more information.
CRS-09107: Start time greater than end time: Cause: A start time greater [or later] than end time caused an error.; Action: Make sure the start time is less than the end time for the specified range query.
CRS-09108: Threshold out of acceptable range: Cause: A threshold was specified that is outside the allowed range.; Action: Make sure threshold is within the acceptable range. Refer documentation or online help for more information
CRS-09109: New Cluster Health Monitor repository location same as the old location on node <varname>string</varname>: Cause: The new location specified for Cluster Health Monitor repository is same as the old location.; Action: Provide a different location for Cluster Health Monitor repository. Refer documentation or online help for more information.
CRS-09110: Cluster Health Monitor repository location not changed as the location specified does not exist on node <varname>string</varname>.: Cause: The new location specified for Cluster Health Monitor repository does not exist.; Action: Provide a different location for Cluster Health Monitor repository. Refer documentation or online help for more information.
CRS-09111: Error updating Cluster Health Monitor repository location <varname>string</varname> in configuration file.: Cause: An error occurred while writing the Cluster Health Monitor repository location to configuration files.; Action: Report this error to Oracle Support Services.
CRS-09114: Cluster Health Monitor repository location change failed on one or more nodes. Aborting location change.: Cause: An error occurred while setting Cluster Health Monitor repository location on the Cluster Logger Service.; Action: Retry specifying a valid location.
CRS-09116: Cluster Health Monitor repository retention change failed on one or more nodes. Aborting retention change.: Cause: An error occurred while setting Cluster Health Monitor repository size on the Cluster Logger Service.; Action: Retry specifying a valid location.
CRS-09117: Grid Infrastructure Management Repository configuration error \n <varname>string</varname>: Cause: Grid Infrastructure Management Repository configuration error occurred.; Action: Take the following steps. 1) Examine the accompanying ORA-nnnnn or CRS-nnnn error messages. If possible, correct the issue reported. 2) Issue a 'srvctl status mgmtdb' command to determine the status of the Grid Infrastructure Management Repository database. If it is not online, examine the database instance alert log to determine what happened. 3) If you are unable to determine or correct the problem, run 'diagcollection.pl' and contact Oracle Support Services.
CRS-09118: Grid Infrastructure Management Repository connection error \n <varname>string</varname>: Cause: Grid Infrastructure Management Repository connection error occurred.; Action: Take the following steps. 1) Examine the accompanying ORA-nnnnn or CRS-nnnn error messages. If possible, correct the issue reported. 2) Issue a 'srvctl status mgmtdb' command to determine the status of the Grid Infrastructure Management Repository database. If it is not online, examine the database instance alert log to determine what happened. 3) If you are unable to determine or correct the problem, run 'diagcollection.pl' and contact Oracle Support Services.
CRS-09119: Warning: <varname>string</varname> option has been deprecated and will be ignored.: Cause: A deprecated option was specified on the command line. The option was ignored.; Action: Check the documentation for the new syntax of the command.
CRS-09120: oclumon was not able to connect to the Grid Infrastructure Management Repository because an authorization failure occurred. \n<varname>string</varname>: Cause: An authorization failure occurred when connecting to the Grid Infrastructure Management Repository.; Action: Run the 'srvctl config mgmtdb' command to verify that Grid Infrastructure Management Repository has been created successfully. If not, run the 'mgmtca' command to reset the passwords in the wallet. If the problem persists, run 'diagcollection.pl' and contact Oracle Support Services.
CRS-09121: oclumon was not able to connect to the Grid Infrastructure Management Repository because no listener was available.: Cause: An attempt to connect to the Grid Infrastructure Management Repository failed because no Grid Infrastructure Management Repository listener was running.; Action: Use the 'srvctl status mgmtlsnr' command to confirm that Grid Infrastructure Management Repository listener is running. If it is not, start it using the 'srvctl start mgmtlsnr' command. If the problem persists, run 'diagcollection.pl' and contact Oracle Support Services.
CRS-09122: oclumon was not able to retrieve the security keys from the wallet.: Cause: An attempt to retrieve the security keys from the wallet failed.; Action: Run the 'crsctl query wallet -type MGMTDB' command to verify that the wallet exists. If the problem persists, contact Oracle Support Services.
CRS-09123: oclumon was not able to connect to the Grid Infrastructure Management Repository because a Cluster Synchronization Services request failed.: Cause: An attempt to connect to the Grid Infrastructure Management Repository failed due to a Cluster Synchronization Services failure.; Action: If the problem persists, run 'diagcollection.pl' and contact Oracle Support Services.
CRS-09124: Cluster Health Monitor repository retention change failed. Aborting retention change. Error: <varname>string</varname>: Cause: An error occurred while setting the Cluster Health Monitor repository size on the cluster logger service.; Action: Take the following steps. 1) Examine the accompanying ORA-nnnnn or CRS-nnnn error messages. If possible, correct the issue reported. 2) Issue a 'srvctl status mgmtdb' command to determine the status of the Grid Infrastructure Management Repository database. If it is not online, examine the database instance alert log to determine what happened. 3) If you are unable to determine or correct the problem, run 'diagcollection.pl' and contact Oracle Support Services.
CRS-09125: Error <varname>string</varname>: <varname>string</varname> is an invalid node name.: Cause: The 'oclumon' command could not be carried out as entered because the node name cited in the message was invalid. The cited node name was ignored and the query executed with any remaining names.; Action: Reissue the 'oclumon' command, if desired, supplying a valid name for the node name cited in the message. Refer to the product documentation or to command online help for information.
CRS-09500: The System Monitor Service aborted on host <varname>string</varname>. Details at <varname>string</varname> in <varname>string</varname>.: Cause: The System Monitor Service aborted due to an internal error.; Action: If the problem persists, run 'diagcollection.pl' and contact Oracle Support Services.
CRS-09501: The Cluster Logger Service aborted on host <varname>string</varname>. Details at <varname>string</varname> in <varname>string</varname>.: Cause: The Cluster Logger Service aborted due to an internal error.; Action: If the problem persists, run 'diagcollection.pl' and contact Oracle Support Services.
CRS-09502: The Cluster Health Monitor repository location <varname>string</varname> is inaccessible. Details at <varname>string</varname> in <varname>string</varname>.: Cause: An error occurred while accessing the Cluster Health repository.; Action: Check that the Cluster Health Monitor repository location in question has the correct permissions. Determine whether this behavior is limited to one node or whether it occurs across all of the nodes in the cluster. Use the 'oclumon manage -repos reploc <varname>location</varname>' command to replace the Cluster Health Monitor repository location.
CRS-09503: The System Monitor Service on this host is unable to communicate with the Cluster Logger Service on host <varname>string</varname>, and will log the Cluster Health Monitor data to the local repository.: Cause: Communication was lost with the Cluster Logger Service node.; Action: Verify all network connections between cluster nodes and repair any problematic connections. If network problems are not found, execute the following steps: 1. Run diagcollection.pl. 2. Contact Oracle Support Services.
CRS-09504: The Cluster Logger Service on host <varname>string</varname> is dropping the Cluster Health Monitor node view. Details at <varname>string</varname> in <varname>string</varname>.: Cause: The Cluster Logger Service was unable to insert Cluster Health Monitor node view into Cluster Health Monitor repository .; Action: Contact Oracle Support Services.
CRS-09505: The Cluster Health Monitor repository is deleted due to corruption and the Cluster Logger Service is disabled on <varname>string</varname>. Details at <varname>string</varname> in <varname>string</varname>.: Cause: A critical error occurred while operating on Cluster Health Monitor repository.; Action: Contact Oracle Support Services.
CRS-09506: The System Monitor Service local repository is disabled on the host <varname>string</varname>. Details at <varname>string</varname> in <varname>string</varname>.: Cause: An internal error occurred while writing to the System Monitor Service local repository.; Action: Contact Oracle Support Services.
CRS-09507: The maximum Cluster Health Monitor repository retention time is reached. Deleting the oldest Cluster Health Monitor node views in age order.: Cause: The maximum time for which the oldest Cluster Health Monitor node view will be available on Cluster Health Monitor repository was reached.; Action: If necessary, use 'oclumon manage -repos changerepossize <varname>size</varname>' command to change the retention time.
CRS-09508: The Cluster Health Monitor repository retention time cannot be changed due to lack of disk space on node <varname>string</varname>.: Cause: The Cluster Health Monitor retention time condition could not be fulfilled because the Cluster Health Monitor repository ran out of disk space at run time at the repository location.; Action: Use the 'oclumon manage -repos reploc <varname>location</varname>' command to replace the Cluster Health Monitor repository with a disk location that has at least 1GB of available space per cluster node.
CRS-09509: The new Cluster Logger Service master is <varname>string</varname>.: Cause: A new Cluster Logger Service master node was elected.; Action: None
CRS-09510: The new Cluster Logger Service replica is <varname>string</varname>.: Cause: A new Cluster Logger Service replica node was elected.; Action: None
CRS-09511: The System Monitor Service was not able to collect disk information on node <varname>string</varname>.: Cause: There was a problem in reading the disk-related information.; Action: Confirm that disks are properly configured and usable on the indicated node. If no issues are found and the problem persists, run 'diagcollection.pl' and contact Oracle Support Services.
CRS-09512: The System Monitor Service was not able to collect network interface card information on node <varname>string</varname>.: Cause: There was a problem in reading the network interface card related information.; Action: Confirm that network interface cards are properly configured and usable on the indicated node. If no issues are found and the problem persists, run 'diagcollection.pl' and contact Oracle Support Services.
CRS-09513: The version of the Grid Infrastructure Management Repository [<varname>string</varname>] is incompatible with the version of the Oracle Clusterware [<varname>string</varname>].: Cause: During startup, the Cluster Logger Service found that the version of Grid Infrastructure Management Repository was older than that of the Oracle Clusterware.; Action: Upgrade the Grid Infrastructure Management Repository to a version which is at least that of the Oracle Clusterware.
CRS-09514: The Cluster Logger Service encountered an unexpected error during inserting the data into the Grid Infrastructure Management Repository. \n<varname>string</varname>.: Cause: An unexpected Oracle error was returned by the Grid Infrastructure Management Repository.; Action: 1) Examine the accompanying ORA-nnnnn error messages. If possible, correct the issue reported. 2) Issue a 'srvctl status mgmtdb' command to determine the status of the Grid Infrastructure Management Repository database. If it is not online, examine the database instance alert log to determine what happened. 3) If you are unable to determine or correct the problem, contact Oracle Support Services.
CRS-09515: The Cluster Logger Service encountered an unexpected error during deleting the data from Grid Infrastructure Management Repository. \n<varname>string</varname>.: Cause: An unexpected Oracle error was returned by the Grid Infrastructure Management Repository.; Action: 1) Examine the accompanying ORA-nnnnn error messages. If possible, correct the issue reported. 2) Issue a 'srvctl status mgmtdb' command to determine the status of the Grid Infrastructure Management Repository database. If it is not online, examine the database instance alert log to determine what happened. 3) If you are unable to determine or correct the problem, contact Oracle Support Services.
CRS-09516: Encountered an unexpected error during querying the data from Grid Infrastructure Management Repository. \n<varname>string</varname>.: Cause: An unexpected Oracle error was returned by the Grid Infrastructure Management Repository.; Action: 1) Examine the accompanying ORA-nnnnn error messages. If possible, correct the issue reported. 2) Issue a 'srvctl status mgmtdb' command to determine the status of the Grid Infrastructure Management Repository database. If it is not online, examine the database instance alert log to determine what happened. 3) If you are unable to determine or correct the problem, contact Oracle Support Services.
CRS-09517: An unrecoverable configuration error occurred in the Grid Infrastructure Management Repository. Details at <varname>string</varname> in <varname>string</varname>. \n<varname>string</varname>: Cause: An unexpected condition happened in the Grid Infrastructure Management Repository.; Action: 1) Examine the accompanying ORA-nnnnn error messages. If possible, correct the issue reported. 2) Issue a 'srvctl status mgmtdb' command to determine the status of the Grid Infrastructure Management Repository database. If it is not online, examine the database instance alert log to determine what happened. 3) If you are unable to determine or correct the problem, contact Oracle Support Services.
CRS-09518: The Cluster Logger Service was not able to connect to the Grid Infrastructure Management Repository because an authorization failure occurred. \n<varname>string</varname>: Cause: An authorization failure occurred when connecting to the Grid Infrastructure Management Repository.; Action: Run the 'srvctl config mgmtdb' command to verify that Grid Infrastructure Management Repository has been created successfully. If not, run the 'mgmtca' command to reset the passwords in the wallet. If the problem persists, run 'diagcollection.pl' and contact Oracle Support Services.
CRS-09519: The Cluster Logger Service was not able to connect to the Grid Infrastructure Management Repository because no listener was available.: Cause: An attempt to connect to the Grid Infrastructure Management Repository failed because no Grid Infrastructure Management Repository listener was running.; Action: Use the 'srvctl status mgmtlsnr' command to confirm that Grid Infrastructure Management Repository listener is running. If it is not, start it using the 'srvctl start mgmtlsnr' command. If the problem persists, run 'diagcollection.pl' and contact Oracle Support Services.
CRS-09520: The storage of Grid Infrastructure Management Repository is <varname>number</varname>%% full. The storage location is '<varname>string</varname>'.: Cause: The storage of Grid Infrastructure Management Repository was close to full. This storage can be a shared file system or an Oracle ASM disk group.; Action: Make sure there is sufficient free space in repository location.
CRS-09521: Grid Infrastructure Management Repository was not available on the node <varname>string</varname>. The System Monitor Service will store the data in its local repository on all nodes. \n<varname>string</varname>: Cause: Grid Infrastructure Management Repository was initializing or was shutting down when the Cluster Logger Service tried to connect, insert or delete the data.; Action: Check if the Grid Infrastructure Management Repository is online using the 'srvctl status mgmtdb' command. If it is offline, start it using the 'srvctl start mgmtdb' command.
CRS-09522: The Cluster Logger Service was not able to retrieve the security keys from the wallet.: Cause: The Cluster Logger Service could not get the security keys due a wallet read failure.; Action: Run the 'crsctl query wallet -type MGMTDB' command to verify that the wallet exists. If the problem persists, contact Oracle Support Services.
CRS-09523: The Cluster Logger Service was not able to connect to the Grid Infrastructure Management Repository because a Cluster Synchronization Services request failed.: Cause: An attempt to connect to the Grid Infrastructure Management Repository failed due to a Cluster Synchronization Services failure.; Action: If the problem persists, run 'diagcollection.pl' and contact Oracle Support Services.
CRS-09524: The System Monitor Service on this host is unable to communicate with the Cluster Logger Service on host <varname>string</varname>, and will log the Cluster Health Analysis data to the local repository.: Cause: Communication was lost with the Cluster Logger Service node.; Action: Verify all network connections between cluster nodes and repair any problematic connections. If network problems are not found, execute the following steps: 1. Run diagcollection.pl. 2. Contact Oracle Support Services.
CRS-09525: The Cluster Health Analysis local repository is disabled on host <varname>string</varname>. Details at <varname>string</varname> in <varname>string</varname>.: Cause: An internal error occurred while writing to the Cluster Health Analysis local repository.; Action: Contact Oracle Support Services.
CRS-09526: The Cluster Logger Service was unable to reset the password for Cluster Health Monitor.: Cause: A password reset failure occurred when the Cluster Logger Service tried to reset the Cluster Health Monitor password after finding that the password had expired.; Action: Run the 'srvctl config mgmtdb' command to verify that Grid Infrastructure Management Repository has been created successfully. If not, run the 'mgmtca setpasswd -user CHM' command to reset the password for Cluster Health Monitor. If the problem persists, run 'diagcollection.pl' and contact Oracle Support Services.
CRS-09527: The Cluster Logger Service was unable to reset the password for Cluster Health Analysis.: Cause: A password reset failure occurred when the Cluster Logger Service tried to reset the Cluster Health Analysis password after finding that the password had expired.; Action: Run the 'srvctl config mgmtdb' command to verify that Grid Infrastructure Management Repository has been created successfully. If not, run the 'mgmtca setpasswd -user CHA' command to reset the password for Cluster Health Analysis. If the problem persists, run 'diagcollection.pl' and contact Oracle Support Services.
CRS-09600: Failed to initialize <varname>string</varname> daemon: Cause: An error occurred during initialization.; Action: Report this error to Oracle Support Services.
CRS-09603: Failed to read configuration files: Cause: An error encountered while retrieving information from configuration files.; Action: Report this error to Oracle Support Services.
CRS-09607: Cannot spawn thread for <varname>string</varname>: Cause: An error encountered while spawning thread.; Action: Report this error to Oracle Support Services.
CRS-09608: ASM disk method failed: Cause: An error encountered with ASM disks configuration.; Action: Report this error to Oracle Support Services.
CRS-09609: Encountered cssd failure. Reinitializing CSSD layer.: Cause: An error was encountered with CSSD layer while retrieving information.; Action: Report this error to Oracle Support Services.
CRS-09610: Encountered a fatal internal error. Daemon <varname>string</varname> exiting.: Cause: A fatal error occurred with CSSD layer.; Action: Report this error to Oracle Support Services.
CRS-09611: Mark <varname>string</varname> disks encountered errors: Cause: An error occurred while accessing disk.; Action: Report this error to Oracle Support Services.
CRS-09612: Mark <varname>string</varname> disks failed: Cause: A fatal error occurred while accessing disk.; Action: Report this error to Oracle Support Services.
CRS-09615: Disk method Failure : <varname>string</varname>: Cause: Internal error occurred.; Action: Report this error to Oracle Support Services.
CRS-09616: Daemon started : <varname>string</varname>: Cause: A daemon process started successfully.; Action: None
CRS-09617: Invalid message type encountered: Cause: An invalid or corrupted message was received.; Action: Report this error to Oracle Support Services.
CRS-09618: Daemon stopped : <varname>string</varname>: Cause: A daemon process stopped successfully.; Action: None
CRS-10002: failed to allocate memory\n: Cause: Memory allocation failed.; Action: Correct the system memory problem and retry.
CRS-10004: unable to reach <varname>string</varname> address from local node: Cause: An attempt to reach the IP address specified failed.; Action: Make sure that the specified IP address is a valid IP address and is assigned to an interface. Make sure that there are no firewalls between local node and node on which specified IP address is hosted.
CRS-10005: unable to determine local hostname: Cause: The hostname could not be determined.; Action: Check that the hostname for the local machine is valid. Look at the accompanying messages. If the problem persists, contact Oracle Support Services.
CRS-10006: APPVIP type needs a VIP name. Specify a VIP name using -vip commandline option.: Cause: VIP resource name was missing in the command line for APPVIP type.; Action: Specify a VIP name using -vip option.
CRS-10008: unable to generate client ID for VIP type <varname>string</varname>, cluster name <varname>string</varname>, VIP resource name <varname>string</varname>: Cause: An attempt to generate client ID for specified cluster name, VIP type and resource name failed.; Action: Make sure that cluster name and VIP resource name do not exceed 252 characters. Make sure that VIP type is a valid VIP type. Refer to 'crsctl get clientid -help' for more information.
CRS-10010: unable to discover DHCP server in the network listening on port <varname>number</varname> for client ID <varname>string</varname>: Cause: An attempt to discover DHCP server listening on port specified failed.; Action: Make sure that DHCP servers exist on the network and are listening on port specified. If they are listening on a different port then specify that port using the -port option. For more information refer to help for 'crsctl discover dhcp' command.
CRS-10011: unable to request DHCP lease for client ID <varname>string</varname> on port <varname>number</varname>: Cause: An attempt to request DHCP lease for the specified client ID on specified port failed.; Action: Make sure that there are DHCP servers with IP addresses available on the network. If other DHCP servers are available which are listening on a different port specify an alternative port using the -port option. For more information refer to help for 'crsctl request dhcp' command.
CRS-10013: unable to release DHCP lease for client ID <varname>string</varname>, on port <varname>number</varname>: Cause: An attempt to release DHCP lease for the specified client ID on specified port failed.; Action: Make sure that there are DHCP servers listening on port specified. If the DHCP server is listening on a different port specify an alternative port using -port option. For more information refer to help for 'crsctl release dhcp' command.
CRS-10014: HOSTVIP type needs a node name. Specify a node name using -n option.: Cause: Node name was missing in the command line for HOSTVIP type.; Action: For HOSTVIP type node name needs to be specified via -n option.
CRS-10015: VIP type <varname>string</varname> is invalid: Cause: An invalid VIP type was specified for DHCP client ID generation.; Action: Make sure that VIP type is a valid VIP type. Refer to 'crsctl get clientid -help' for more information.
CRS-10016: error obtaining local host DNS resolver configuration: Cause: An attempt to obtain local host DNS configuration failed.; Action: Make sure that the user executing the command has sufficient permission to read local system configuration.
CRS-10017: the <varname>number</varname> name servers configured on this system exceeds the <varname>number</varname> maximum allowed: Cause: An attempt to obtain local host DNS configuration failed because more name servers were found then allowed on this operating system.; Action: Reduce the number of name servers configured to the maximum allowed.
CRS-10023: Domain name look up for name <varname>string</varname> failed. Operating system error: <varname>string</varname>: Cause: An attempt to query DNS servers for name specified failed.; Action: Look at accompanying messages for more information on the failure.
CRS-10029: could not verify if port <varname>number</varname> at address <varname>string</varname> is in use: Cause: An attempt to verify if port at address specified is in use failed.; Action: Make sure that the user has permission to create socket at port specified. For ports < 1024 user should be root. Also look at the accompanying messages for more information.
CRS-10030: could not verify if port <varname>number</varname> on local node is in use: Cause: An attempt to verify if port specified on local node is in use failed.; Action: Make sure that the user has permission to create socket at port specified. For ports < 1024 the user should be root. Also look at the accompanying messages for more information.
CRS-10033: could not stop the DNS listening daemon running on port <varname>number</varname> at address <varname>string</varname>: Cause: An attempt to stop the DNS listening daemon running on port and address specified failed.; Action: Make sure that the user has permission to send packets at the port specified. For ports < 1024 the user should be root. Also look at the accompanying messages for more information.
CRS-10034: could not stop the DNS listening daemon running on port <varname>number</varname> on local node: Cause: An attempt to stop the DNS listening daemon on local node running on port specified failed.; Action: Make sure that the user has permission to send packets at the port specified. For ports < 1024 the user should be root. Also look at the accompanying messages for more information.
CRS-10035: invalid name server '<varname>string</varname>' specified in command line: Cause: An invalid IPv4 address was specified on the command line for -dnsserver option.; Action: Specify a valid IPv4 address on the command line.
CRS-10036: value for command line parameter '<varname>string</varname>' is not an integer: Cause: An invalid value was specified for the specified command line parameter.; Action: Re-submit the request with an integer value.
CRS-10038: invalid IP address '<varname>string</varname>' specified: Cause: An invalid IPv4 or IPv6 address was supplied on command line.; Action: Supply an IP address that conforms to IETF RFC-791 or IETF RFC-2373.
CRS-10039: invalid subnet '<varname>string</varname>' specified: Cause: An invalid IPv4 or IPv6 subnet was supplied to crsctl.; Action: Supply a subnet address that conforms to IETF RFC-950 or IETF RFC-5942.
CRS-10040: unable to get list of network interfaces: Cause: An attempt to get the list of network interfaces failed.; Action: Look at the accompanying messages for more information.
CRS-10041: subnet '<varname>string</varname>' is not configured on the node: Cause: The subnet specified did not match subnet of any network interface on this node.; Action: Specify a subnet that matches at least one network interface's subnet on this node.
CRS-10043: DNS daemon is not listening on port <varname>number</varname> at address <varname>string</varname>: Cause: An attempt to check if the DNS daemon is listening on port and address specified failed.; Action: Make sure that the address specified is reachable. Make sure that there is no firewall between the node on which this command was run and the address specified. Also look at the accompanying messages for more information.
CRS-10044: invalid cluster name '<varname>string</varname>' specified: Cause: An invalid cluster name was supplied to the CRSCTL utility.; Action: Specify a cluster name which is at least one character but no more than 15 characters in length. The cluster name must be alphanumeric, it cannot begin with a numeric character, and it may contain hyphen (-) characters. However, it cannot end with a hyphen (-) character.
CRS-10045: invalid node name '<varname>string</varname>' specified: Cause: An invalid node name was supplied to the CRSCTL utility.; Action: Specify a node name which is at least one character but no more than 63 characters in length. The node name must be alphanumeric, it cannot begin with a numeric character, and it may contain hyphen (-) characters. However, it cannot end with a hyphen (-) character.
CRS-10046: invalid client ID '<varname>string</varname>' specified: Cause: An invalid client ID was supplied to the CRSCTL utility.; Action: The client ID can be obtained by running the command 'crsctl get clientid dhcp'.
CRS-10051: CVU found following errors with Clusterware setup : <varname>string</varname>: Cause: A resource-specific error was detected by the Clusterware Verification Utility (CVU). This message is accompanied by others providing details of the error condition.; Action: Respond based on the accompanying messages.
CRS-10100: Execution of crswrapexece.pl script with arguments '<varname>string</varname>' fails.: Cause: crswrapexece.pl script failed when executed with the specific arguments.; Action: Check system log and crswrapexece.log for more details. Contact Oracle Support Services.
CRS-10101: Internal Error: Cause: Execution of crswrapexece.pl script failed due to missing argument.; Action: Contact Oracle Support Services.
CRS-10102: Failure to open environment file <varname>string</varname>.: Cause: The crswrapexece.pl script failed to open the environment file, which might be caused by hostname change or user edits.; Action: Check for the existence and permission of the environment file.
CRS-10103: Found <varname>string</varname> syntax errors in environment file <varname>string</varname>.: Cause: crswrapexece.pl found syntax errors in the provided environment file.; Action: Check and fix syntax error in the indicated environment file. If the problem persists, contact Oracle Support Services.
CRS-10131: Failure to create named pipe <varname>string</varname>. Details [<varname>string</varname>].: Cause: The specified named pipe could not be created. Oracle High Availability Service would not be able to restart if crashes.; Action: Check for the existence and permission of the parent directory, where the named pipe was created.
CRS-10132: Oracle High Availability Service was restarted at least <varname>string</varname> times within the last <varname>string</varname> seconds. Stop auto-restarting Oracle High Availability Service.: Cause: Oracle High Availability Service was restarted too rapidly within a short period of time.; Action: Check the Oracle High Availability Service log file to determine the cause. If the problem persists, contact Oracle Support Services.
CRS-10201: Internal error: Cause: An unexpected condition was detected in the cluster event module.; Action: Contact Oracle Support Services.
CRS-10202: Failed to allocate process memory: Cause: Insufficient system memory resources.; Action: Correct the system memory resources problem and retry. If this does not appear to be caused by an operating system issue, contact Oracle Support Services.
CRS-10203: Could not connect to the Event Manager daemon: Cause: Unable to communicate with Event Manager daemon.; Action: Run the 'crsctl check evmd' command to determine whether Event Manager daemon is properly configured and is running.
CRS-10250: Database name is required to access database wallets. Use -name option to supply a database name.: Cause: The option -name was missing on the command line.; Action: For APPQOSDB wallet types -name is a mandatory parameter. Retry the command with -name option.
CRS-10251: User name is required to create OSUSER wallets. Use -user option to supply a username.: Cause: The option -user was missing on the command line.; Action: For OSUSER wallet types -user is a mandatory parameter. Retry the command with -user option.
CRS-10301: Unable to contact Oracle high availability service on peer nodes for cluster wide commands. Details at <varname>string</varname> in <varname>string</varname>.: Cause: Multicast Domain Name Server (mDNS) or Grid Plug and Play (GPnP) or both daemons on the local node were not running.; Action: If you are shutting down the Clusterware stack, this is expected. If you had issued a cluster wide command, reissue the command after the stack has been restarted. If you are not shutting down the stack, the missing component(s) may have failed and may restart automatically. Any cluster wide commands can be retried after a few seconds. However, the failure should be investigated and reported to Oracle Support Services.
CRS-10302: Oracle high availability service on peer nodes is reachable. Details at <varname>string</varname> in <varname>string</varname>.: Cause: Oracle high availability service on peer nodes was reachable.; Action: None
CRS-10401: Internal error in credentials processing.: Cause: An unexpected condition was detected in the credentials module.; Action: Contact Oracle Support Services.
CRS-10402: Failed to allocate process memory.: Cause: There were insufficient system memory resources.; Action: Correct the system memory resources problem and retry. If this does not appear to be caused by an operating system issue, contact Oracle Support Services.
CRS-10403: Could not connect to credential storage: <varname>string</varname>.: Cause: An attempt to communicate with Oracle Cluster Registry (OCR) or Oracle Local Registry (OLR) credential storage failed.; Action: Run the 'crsctl check crs' command to determine whether Cluster Ready Services or Oracle High Availability Services are online.
CRS-10405: Credential domain already exists.: Cause: The provided credential domain already existed.; Action: Specify another credential domain path.
CRS-10406: Authorization error.: Cause: The user did not have permissions to view or modify the provided credential information.; Action: Use a different user to view or modify the credential information.
CRS-10407: Credential domain does not exist.: Cause: The provided credential domain did not exist.; Action: Specify another credential domain path or create the credential domain.
CRS-10408: Credential set already exists.: Cause: The provided credential set already existed.; Action: Specify another credential domain path to which the credential set will be added.
CRS-10409: Credential target already exists.: Cause: The provided credential target already existed.; Action: Specify another credential target name, or modify the value of the existing one.
CRS-10410: Credential set member does not exist.: Cause: The provided credential set member did not exist.; Action: Specify another credential set member or create a new member.
CRS-10411: Credential set does not exist.: Cause: The provided credential set did not exist.; Action: Specify another credential set or create a new member.
CRS-10412: Security layer returned failure: <varname>string</varname>.: Cause: Credential operation failed due to error from security layer.; Action: Depending on the reason, this operation may be retried after correcting the situation.
CRS-10413: Invalid argument specified for attribute.: Cause: An invalid argument was found for a given attribute.; Action: Rerun the command using correct value.
CRS-10414: User name or group name does not match the owner or group of the credential object.: Cause: Credential permissions for the owner could not be modified because the user name did not match the owner of the credential.; Action: Specify the owner's user ID in the argument to change owner's permission.
CRS-10415: ACL string is missing the user or group modifier.: Cause: The access control list (ACL) string did not specify whether user's or group's permission needs to be changed.; Action: Specify the correct format in the argument and rerun the command.
CRS-10416: Credentials target does not exist.: Cause: The provided credentials target did not exist.; Action: Specify another credentials target.
CRS-10417: The directory '<varname>string</varname>' does not exist.: Cause: The specified directory did not exist.; Action: Provide a directory for which the user has read and write permissions.
CRS-10418: The directory '<varname>string</varname>' is not accessible.: Cause: An attempt to access the specified directory failed.; Action: Ensure that the user has read and write permissions on the directory.
CRS-10419: Unable to open file '<varname>string</varname>' for read access.: Cause: An attempt to open the specified file for read access failed.; Action: Ensure that the user has read access permission on the file.
CRS-10420: Unable to open file '<varname>string</varname>' for write access.: Cause: An attempt to open the specified file for write access failed.; Action: Ensure that the user has write access permission on the file.
CRS-10421: Section name does not exist.: Cause: The credentials could not be imported because the provided section name did not exist in the XML file.; Action: Verify the sections included in the credentials file and retry the import supplying the correct section name.
CRS-29000: Oracle VM Manager job failed with the following error:\n<varname>string</varname>: Cause: The Oracle Virtual Machine (Oracle VM) Manager was unable to complete the action due to the indicated error.; Action: Consult Oracle Virtual Machine (Oracle VM) documentation if the problem persists.
CRS-29001: could not find Grid Infrastructure virtual machine '<varname>string</varname>': Cause: The name specified for the Grid Infrastructure virtual machine was not found.; Action: Specify a known virtual machine, or create a new virtual machine with the specified name and add it to the Oracle Clusterware cluster.
CRS-29002: could not find a virtual machine with the ID '<varname>string</varname>': Cause: The ID specified for the virtual machine was not found.; Action: Specify a known virtual machine, or create a new virtual machine with the specified ID.
CRS-29003: could not find a virtual machine with the name or ID '<varname>string</varname>': Cause: Either the name or the ID provided for the virtual machine was not found.; Action: Specify a known virtual machine, or create a new virtual machine with the specified name or ID.
CRS-29004: not authorized to perform the Oracle VM Manager operation: Cause: The Oracle Virtual Machine (Oracle VM) user name and password combination did not work, or the user did not have permission to perform the action requested.; Action: Update the user's password using the 'srvctl modify ovmm' command, or specify a different user who has the correct permissions.
CRS-29005: could not connect to the Oracle VM Manager on host <varname>string</varname> at port <varname>string</varname>: Cause: A connection to the Oracle Virtual Machine (Oracle VM) Manager could not be established or timed out.; Action: Start the Oracle VM Manager on the appropriate host and port, or specify a different host or port using the 'srvctl modify ovmm' command.
CRS-29006: could not find Oracle VM Manager credentials: Cause: Authentication credentials were not found for the Oracle Virtual Machine (Oracle VM) Manager.; Action: Create or modify the credentials by using the 'srvctl {add | modify} ovmm' command.