53 CRS-00184 to CRS-02292

CRS-00184: Cannot communicate with the CRS daemon.: Cause: The CRS daemon on the local node is either not running or there was an internal communication error with the CRS daemon.; Action: Check if the CRS daemon process is running on the local node.

CRS-00210: Could not find resource 'string'.: Cause: An attempt was made to operate on a resource that is not registered.; Action: Check if the resource is registered using crs_stat.

CRS-00211: Resource 'string' has already been registered.: Cause: An attempt was made to register a resource that is already registered.; Action: Check if the resource is registered using crs_stat.

CRS-00213: Could not register resource 'string'.: Cause: There was an internal error while registering the resource.; Action: Check the CRS daemon log file.

CRS-00214: Could not unregister resource 'string'.: Cause: There was an internal error while unregistering the resource.; Action: Check the CRS daemon log file.

CRS-00215: Could not start resource 'string'.: Cause: There was an internal error while starting the resource.; Action: Check the CRS daemon log file.

CRS-00216: Could not stop resource 'string'.: Cause: There was an internal error while stopping the resource.; Action: Check the CRS daemon log file.

CRS-00217: Could not relocate resource 'string'.: Cause: There was an internal error while relocating the resource.; Action: Check the CRS daemon log file.

CRS-00218: Could not restart the resource 'string' on the original node.: Cause: There was an internal error while restarting the resource.; Action: Check the CRS daemon log file.

CRS-00219: Could not update resource 'string'.: Cause: There was an internal error while updating the resource.; Action: Check the CRS daemon log file.

CRS-00220: Resource 'string' has invalid resource profile.: Cause: Invalid attributes in the resource profile.; Action: Run crs_profile -validate to identify the invalid attributes.

CRS-00221: Resource 'string''s action script cannot be found.: Cause: The action script has been deleted from the file system.; Action: Run crs_stat -p to determine the action script location and to check for its existence.

CRS-00223: Resource 'string' has placement error.: Cause: There was no host available to on which failover/start the resource based on the Placement Policy for the resource.; Action: Check the target host for the resource and restart the resource using the crs_start command.

CRS-00230: Member 'string' is not in the cluster.: Cause: The hostname was not found in the cluster.; Action: Check the hostnames in the cluster.

CRS-00232: Cluster member is down. Cannot perform operation.: Cause: The node on which CRS is attempting to start the resource is down.; Action: Start the node and retry the operation.

CRS-00233: Resource or relatives are currently involved with another operation.: 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 crs_getperm.

CRS-00255: CRSD is not running in privileged mode. Insufficient permissions to run this command.: Cause: The CRS daemon was not running as the privileged user.; Action: Check if the CRS daemon is running as root (Unix) or Administrator (Windows).

CRS-00256: Username conflicts with the owner of the resource.: Cause: An attempt was made to give separate user level permissions for the owner of the resource.; Action: Check the owner of the resource and the user being given permissions.

CRS-00257: Groupname conflicts with the primary group of the resource.: Cause: An attempt was made to give separate group level permissions for the primary group of the resource.; Action: Check the primary group of the resource and the group being given permissions.

CRS-00258: Invalid ACL string format.: Cause: An invalid permission string (ACL) was supplied.; Action: Check the syntax of the permission string (ACL).

CRS-00259: Owner of the resource does not belong to the group.: Cause: The owner of the resource does not belong to the expected group.; Action: If this resource is owned by the root user, check if the root user belongs to the dba group.

CRS-00271: CRSD shutdown is already in progress.: Cause: crsctl stop command is issued before waiting for a prior stop command to finish.; Action: Wait for the currently running shutdown command to complete before issuing subsequent command.

CRS-00402: Could not make safe dir('string'): Cause: Unable to create safe directory('%s'); Action: Please check if you have proper permissions and sufficient space on the disk to create the directory.

CRS-00403: Could not chdir to safe dir('string'): Cause: Unable to change directory to safe dir('%s'); Action: Please check if safe dir exists and if you have proper permissions.

CRS-00406: Could not create lock dir ('string'): Cause: Unable to create lock directory ('%s'); Action: Please check if you have proper permissions and sufficient space on the disk to create the directory.

CRS-00407: Another CRSD may be running, could not obtain lock file 'string'.: Cause: Unable to obtain lock file as another CRSD may be running; Action: Please 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 CRS configuration. If necessary reinstall CRS.

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 initialised.; Action: Check the CRS configuration. If necessary reinstall CRS.

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 initialised.; Action: Add the instance using srvctl.

CRS-00471: Node number 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-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-01005: Failed to get required resources: Cause: There was an internal error while evaluating the required resources for the subject resource.; Action: Check if the status of any resource is UNKONOWN using crs_stat -t.

CRS-01006: 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-01007: 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-01009: Resource 'string' is already running on member 'string': Cause: An attempt was made to start a resource on a host while it is already running on that host.; Action: This is an insignificant error. Check the operation being performed.

CRS-02001: User does not have permission to start CRSD.: Cause: Unable to start CRSD due to insufficent permissions; Action: Start CRSD as a privileged user.

CRS-02007: 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-02282: Failure to allocate number bytes for username.: Cause: System is out of memory.; Action: Free up memory on system and retry.

CRS-02283: The requested setting must be between number and number.: Cause: An attempt to change a setting to an out of bounds value.; Action: Retry with the setting within the proper limits.

CRS-02284: Unable to lock the configuration before making changes. number: Cause: Failure in a CSS API acquiring a lock.; Action: Retry or contact support for information on the error code.

CRS-02285: Change to configuration failed, but was successfully rolled back.: Cause: See accompanying messages for explanation of cause.; Action: No action is required. This indicates that no damage was done.

CRS-02286: Unable number to mark unformat information on voting disk string: Cause: Probably an unreadable / unwritable voting disk was being removed.; Action: If cause is correct, this is ignorable, but not ideal.

CRS-02287: Unable number to apply correct permissions to new voting disk string.: Cause: Attempted to create and apply permissions changes to new disk.; Action: Examine OS-specific error and try again with another disk.

CRS-02288: Unable number to undo initialization of voting disk.: Cause: Could not roll back format of voting disk.; Action: Disk should be cleaned out before an attempt to add again.

CRS-02289: Unable number to roll back OCR settings for voting disk.: Cause: Could not remove temporary changes to OCR adding voting disk.; Action: Shut down the cluster and restart. New voting disk must be removed with "crsctl delete css votedisk".

CRS-02290: This could take several minutes.: Cause: CRS daemons is engaged in an activity take could potentially take a long time.; Action: None

CRS-02291: Retrying stop resources.: Cause: crsctl command is trying again to stop resources.; Action: None

CRS-02292: All resources could not be stopped.: Cause: CRSD could not stop all resources when trying to shut the stack down.; Action: The resources may have to be stopped manually.