114 PRCR-01000 to PRCR-01220
- PRCR-01000: Resource {0} already exists
-
Cause: An attempt was made to create a resource that already exists.
- PRCR-01001: Resource {0} does not exist
-
Cause: An attempt was made to operate on a resource that does not exist.
- PRCR-01002: Resource {0} is already enabled
-
Cause: An attempt was made to enable a resource that is already enabled.
- PRCR-01003: Resource {0} is already disabled
-
Cause: An attempt was made to disable a resource that is already disabled.
- PRCR-01004: Resource {0} is already running
-
Cause: An attempt was made to start a resource that is already running.
- PRCR-01005: Resource {0} is already stopped
-
Cause: An attempt was made to stop a resource that is already stopped.
- PRCR-01006: Failed to add resource {0} for {1}
-
Cause: An attempt to add the specified resource failed.
- PRCR-01007: Failed to check status of resource {0}
-
Cause: An attempt to check status of specified resource has failed.
- PRCR-01008: Failed to retrieve version of resource {0}
-
Cause: An attempt to retrieve version of the specified resource has failed.
- PRCR-01009: Failed to retrieve permissions of resource {0}, ACL {1}
-
Cause: Internal error.
- PRCR-01010: Failed to update permissions of resource {0}
-
Cause: An attempt to update permissions of specified resource has failed.
- PRCR-01011: Failed to enable resource {0}
-
Cause: An attempt to enable specified resource has failed.
- PRCR-01012: Failed to disable resource {0}
-
Cause: An attempt to disable specified resource has failed.
- PRCR-01013: Failed to start resource {0}
-
Cause: An attempt to start specified resource on several nodes failed.
- PRCR-01014: Failed to stop resource {0}
-
Cause: An attempt to stop specified resource on several nodes failed.
- PRCR-01015: Failed to relocate resource {0}
-
Cause: An attempt to relocate specified resource has failed.
- PRCR-01016: Failed to modify resource {0}
-
Cause: An attempt to modify specified resource has failed.
- PRCR-01024: Failed to remove resource {0} on nodes {1}
-
Cause: An attempt to remove the resource on the specified nodes failed.
- PRCR-01025: Resource {0} is still running
-
Cause: The specified resource is not stopped.
- PRCR-01026: Resource {0} is not running
-
Cause: The specified resource is not started.
- PRCR-01028: Failed to remove resource {0}
-
Cause: An attempt to remove specified resource failed.
- PRCR-01029: Attribute {0} does not exist in resource {1} definition
-
Cause: An attempt was made to get an attribute which is not defined for that resource type.
- PRCR-01030: Resource attribute name {0} is not valid
-
Cause: Internal error.
- PRCR-01031: Resource attribute {0} value {1} is not valid
-
Cause: Specified resource attribute value is not valid.
- PRCR-01032: Current state of resource {0} is not valid
-
Cause: Internal error.
- PRCR-01033: Resource type {0} does not exist
-
Cause: An attempt to retrieve the type has failed.
- PRCR-01035: Failed to look up CRS resource {0} for {1}
-
Cause: An attempt to access the specified resource failed because it did not exist.
- PRCR-01036: Failed to retrieve cardinality of the resource {0}
-
Cause: An attempt to retrieve cardinality of resource has failed.
- PRCR-01037: Failed to update cardinality of the resource {0} to {1}
-
Cause: An attempt to set cardinality of the resource has failed.
- PRCR-01039: Server pool {0} does not exist
-
Cause: An attempt was made to retrieve the server pool which does not exists.
- PRCR-01040: Resource {0} is already enabled on node(s) {1}
-
Cause: An attempt was made to enable a resource that is already enable on nodes.
- PRCR-01041: Resource {0} is already disabled on node(s) {1}
-
Cause: An attempt was made to disable a resource that is already disabled on nodes.
- PRCR-01042: Failed to get dependent resources {0} of resource {1}: {2}
-
Cause: Failed to retrieve dependent resources of the given resource.
- PRCR-01043: Failed to update dependent resources {0} of resource {1} to resource {2}
-
Cause: Failed to update dependent resources of the given resource.
- PRCR-01050: Resource {0} is not configured in Oracle cluster environment
-
Cause: The environment for the specified resource is not Oracle Clusterware.
- PRCR-01051: OracleCM Cluster is not found on node {0}
-
Cause: The OracleCM Cluster was not found on the specified node because the library for OracleCM Cluster was not found.
- PRCR-01052: Failed to find OracleCM Cluster library on node {0}
-
Cause: Failed to check OracleCM Cluster because of the error in executingthe command to find the file /etc/ORCLcluster/oracm/lib/libskgxn2.so.
- PRCR-01053: Vendor Cluster is not found on node {0}
-
Cause: The Vendor Cluster was not installed and configured on the specified node.
- PRCR-01054: Failed to find Vendor Cluster library on node {0}
-
Cause: Failed to check OracleCM Cluster because of the error in executing the command to find the file /etc/ORCLcluster/lib/libskgxn2.so.
- PRCR-01055: Cluster membership check failed for node {0}
-
Cause: The specified node does not belong to the cluster.
- PRCR-01061: User permissions are insufficient
-
Cause: User permissions are insufficient to register resource/type.
- PRCR-01062: Failed to retrieve attributes of resource {0} on node {1}
-
Cause: An attempt to retrieve attributes of the resource has failed.
- PRCR-01063: Failed to create context
-
Cause: Internal error.
- PRCR-01064: Failed to start resource {0} on node {1}
-
Cause: An attempt to start the resource has failed.
- PRCR-01065: Failed to stop resource {0}
-
Cause: An attempt to stop the resource failed because the resource wasn't running or the running resource had dependent resources also running.
- PRCR-01067: Failed to create a filter
-
Cause: An attempt to create a filter has failed.
- PRCR-01068: Failed to query resources
-
Cause: An attempt to query the resource failed.
- PRCR-01069: Attribute {0} of {1} {2} not found
-
Cause: Internal error.
- PRCR-01070: Failed to check if {0} {1} is registered
-
Cause: Failed to check if resource is registered.
- PRCR-01071: Failed to register or update {0} {1}
-
Cause: An attempt to register or update the resource failed.
- PRCR-01072: Failed to unregister {0} {1}
-
Cause: An attempt to unregister specified Oracle clusterware entity failed.
- PRCR-01074: Failed to retrieve attributes for {0} {1}
-
Cause: Failed to retrieve attributes for specified resource.
- PRCR-01075: Failed to retrieve status for resource {0}
-
Cause: Failed to retrieve status for specified resource.
- PRCR-01076: Failed to retrieve status for resource {0}: {1} is missed
-
Cause: Internal error.
- PRCR-01077: Failed to calculate status for resource {0}: {1}/{2}
-
Cause: Internal error.
- PRCR-01078: Failed to retrieve attributes of resource {0}
-
Cause: An attempt to retrieve attributes of the resource has failed.
- PRCR-01079: Failed to start resource {0}
-
Cause: An attempt to start the resource has failed.
- PRCR-01085: Unknown typeAsString: {0}
-
Cause: Internal error.
- PRCR-01086: {0} {1} is already registered
-
Cause: An attempt to register specified resource failed.
- PRCR-01087: Failed to retrieve resource {0} instances
-
Cause: Internal error.
- PRCR-01088: Failed to stop resource {0}: it was not started on node {1}
-
Cause: The resource was not started on the node..
- PRCR-01089: Failed to relocate resource {0}.
-
Cause: An attempt to relocate specified resource failed.
- PRCR-01090: Failed to relocate resource {0}. It is not running.
-
Cause: The resource was not started.
- PRCR-01091: Failed to relocate resource {0}. It is not running on node {1}.
-
Cause: The resource was not started on the node.
- PRCR-01092: Failed to relocate resource {0}. It is running on more than one node
-
Cause: The resource was started on more than one node.
- PRCR-01093: Failed to relocate resource {0}. It is already running on node {1}
-
Cause: The resource is running that node.
- PRCR-01094: Failed to start resources on node {0}: {1}
-
Cause: Resources defined by filter cannot be started on the node.
- PRCR-01095: Failed to start resources using filter {0}
-
Cause: Resources defined by filter cannot be started.
- PRCR-01096: Filter cannot be null
-
Cause: An attempt to use filter has failed.
- PRCR-01097: Resource attribute not found: {0}
-
Cause: Requested resource attribute not found.
- PRCR-01098: Could not set rolling upgrade mode {0}
-
Cause: An attempt to start the resource in rolling upgrade mode has failed.
- PRCR-01099: Cannot start resource {0} on {1} additional nodes because it would exceed the resource cardinality {2}. Resource is already running on {3} nodes
-
Cause: Resource cannot be started because of its cardinality restriction.
- PRCR-01100: Cannot start resource {0} on {1} nodes because it would exceed the resource cardinality {2}
-
Cause: Resource cannot be started because of its cardinality restriction.
- PRCR-01101: Cannot stop resource {0} on {1} nodes, it is running on {2} nodes.
-
Cause: The resource does not have enough running instances to stop.
- PRCR-01102: Failed to verify if user {0} has CRS administrator role
-
Cause: Failed to verify if the user has CRS administrator role.
- PRCR-01104: Unsupported relocate option {0}
-
Cause: Internal error.
- PRCR-01105: Failed to relocate resource {0} to node {1}
-
Cause: An attempt to relocate the resource to the specified node has failed.
- PRCR-01106: Failed to relocate resource {0} from node {1} to node {2}
-
Cause: An attempt to relocate the resource from the specified node to another has failed.
- PRCR-01107: Error while trying to set default network as dependent resource for {0}
-
Cause: An attempt to set default network dependency for the specified resource failed.
- PRCR-01108: ONS cannot be created because default network is not configured.
-
Cause: An attempt was made to create ONS resource with out creating the dependent default network resource.
- PRCR-01109: Failed to remove attributes "{1}" from resource {0}
-
Cause: Possible reasons: Oracle Clusterware stack might not be active, CRS resource may not exist, or the CRS resource may not have given attributes set.
- PRCR-01110: Failed to retrieve processed attributes of resource {0} for node {1}
-
Cause: Oracle Clusterware stack was not active or CRS resource did not not exist.
- PRCR-01111: Failed to retrieve processed attributes of resource {0} for node {1}
-
Cause: requested CRS resource did not exist.
- PRCR-01112: Failed to retrieve current event sequence number
-
Cause: Oracle Clusterware stack was not active.
- PRCR-01113: Failed to create detailed error message, rc = {0}
-
Cause: Internal error
- PRCR-01114: Failed to relocate servers {0} into server pool {1}
-
Cause: Failed to relocate servers into the given server pool. This message may be accompanied by others providing additional details. A likely cause is violation of defined configuration attributes such as pool MIN_SIZE, SERVER_NAMES etc.
- PRCR-01115: Failed to find entities of type {0} that match filters {1} and contain attributes {2}
-
Cause: Failed to look up entitites of given type that match given filters. This message may be accompanied by others providing additional details. A likely cause is that current user does not have permissions to read attributes of entities of given type.
- PRCR-01116: {0} {1} cannot be created and registered now
-
Cause: Oracle Clusterware stack could not create and register an object.
- PRCR-01117: Failed to stop resources using filter {0}
-
Cause: An attempt to stop resources using specified filter failed.
- PRCR-01118: Failed to generate resource permissions for the resource
-
Cause: Creation of the Access Control List (permission) structures for the resource failed. This message is accompanied by others providing details of the error.
- PRCR-01119: Failed to look up CRS resources of {0} type
-
Cause: An attempt to find the resource for the specified resource type failed because it did not exist.
- PRCR-01120: Resources are already running. {0}
-
Cause: An attempt to start resources failed because they are already running. For detailed information about resources review the accompanying error messages.
- PRCR-01121: Value of parameter "{0}" cannot be null or empty
-
Cause: An attempt to construct ACFS resource name failed due to null or empty value for the indicated parameter.
- PRCR-01122: Resource type {0} is not registered with Oracle Clusterware
-
Cause: Given resource type was not registered.
- PRCR-01123: Failed to rename resource type {0}
-
Cause: An attempt was made to change name of the given resource type. Resource types cannot be renamed.
- PRCR-01124: Failed to check resource {0}
-
Cause: An attempt to check the resource failed.
- PRCR-01125: Failed to check resource {0} on node {1}
-
Cause: An attempt to check the resource on specified node failed.
- PRCR-01126: Failed to relocate resource {0} from node {1}
-
Cause: An attempt to relocate the resource from the specified node has failed.
- PRCR-01127: Resource {0} does not have attributes {1} on per node basis
-
Cause: An attempt to remove given attributes failed because these attributes do not exist on per node basis.
- PRCR-01128: Resource {0} does not have attributes {1} on node {2}
-
Cause: An attempt to remove given attributes failed because these attributes do not exist on the given node.
- PRCR-01129: Failed to upgrade resource type {0}
-
Cause: An attempt to upgrade specified resource type failed.
- PRCR-01130: Failed to get the name for resource type {0} from resource type enum class
-
Cause: An attempt to get the name of the resource type for the given resource type enum class.
- PRCR-01131: CVU resource cannot be created because default network is not configured.
-
Cause: An attempt was made to create CVU resource without creating the dependent default network resource.
- PRCR-01132: Failed to stop resources using a filter
-
Cause: An attempt to stop resources failed because resources were not running or running resources had dependent resources also running.
- PRCR-01133: Failed to stop database {0} and its running services
-
Cause: An attempt to stop given database and its running services failed.
- PRCR-01134: Failed to stop database {0} and its running services on nodes {1}
-
Cause: An attempt to stop the given database and its running services failed on the specified nodes.
- PRCR-01135: Failed to check if node with node number 0 exists
-
Cause: An attempt failed to determine whether a node numbered 0 exists.
- PRCR-01136: Action {0} is not allowed for snapshot entities
-
Cause: Internal error.
- PRCR-01137: Action {0} is not allowed for CRS local entities
-
Cause: Internal error.
- PRCR-01138: Failed to get cached attributes for entity {0} on node {1}
-
Cause: Internal error.
- PRCR-01139: Cache is not ready to generate a snapshot
-
Cause: Internal error.
- PRCR-01140: Wrong sequence number {0}, expected {1} or more
-
Cause: Internal error.
- PRCR-01141: Attribute {0} is not set for local entity {1}
-
Cause: Internal error.
- PRCR-01142: Failed to build a snapshot
-
Cause: Internal error.
- PRCR-01143: Snapshot does not have information about database {0}
-
Cause: Internal Error: An attempt was made to operate on a database that does not exist in a snapshot.
- PRCR-01144: failed to evaluate the effects of the proposed request on the following entities: {0}
-
Cause: An error occurred during processing of the proposed request.
- PRCR-01145: The proposed operation being evaluated would result in an error \n{0}
-
Cause: The effect of the proposed WhatIf request resulted in an error.
- PRCR-01146: The cluster active version doesn't allow the requested action
-
Cause: CRS failed to perform a request because the cluster upgrade is not completed.
- PRCR-01147: Snapshot support was interrupted
-
Cause: Internal error.
- PRCR-01149: Failed to initialize snapshot subsystem
-
Cause: An attempt to initialize snapshot subsystem failed.
- PRCR-01150: Snapshot subsystem was not initialized
-
Cause: An attempt was made to create a snapshot but snapshot subsystem is not initialized.
- PRCR-01151: Snapshot does not have information about server {0}
-
Cause: An attempt was made to operate on a server that does not exist in a snapshot. Either the server name was misspelled or the server has not been registered at the time of snapshot creation.
- PRCR-01152: Invalid CRS cache mode: {0}
-
Cause: CRS cache does not support requested mode.
- PRCR-01153: Snapshot internal error: {0}
-
Cause: Internal error.
- PRCR-01154: failed to create file output stream file name with {0} due to an I/O exception ({1})
-
Cause: An attempt to create file output failed because of the indicated problem in the underlying I/O system. This is an internal error.
- PRCR-01155: Failed to create file output stream with file name: {0} due to security manager does not allowed to permit the operation
-
Cause: An attempt to create file output failed due to security manager does not allowed to permit the operation.
- PRCR-01156: Failed to create file output stream with file name: {0} because 'count' or 'limit' is invalid
-
Cause: An attempt to create file output failed because of illegal arguments 'count' < 1 or 'limit' < 0.
- PRCR-01157: Failed to close the file output stream with file name: {0} due to security manager does not allow to close
-
Cause: An attempt to create file output failed due to security manager does not permit the operation.
- PRCR-01158: Directory {0} in file path does not exist
-
Cause: An attempt was made to operate on a directory that does not exist.
- PRCR-01159: Failed to create file output stream because of empty file name
-
Cause: An attempt to create file output stream failed because of empty file name.
- PRCR-01160: Output stream does not exist
-
Cause: An attempt was made to operate on an output stream that does not exist.
- PRCR-01161: Failed to write to output stream
-
Cause: An attempt to write to an output stream failed.
- PRCR-01162: Failed to format a message
-
Cause: An attempt to format a log message failed.
- PRCR-01163: Failed to open or create the output stream with file name: {0}
-
Cause: An attempt to open or create an output file failed.
- PRCR-01164: Failed to flush an output stream
-
Cause: An attempt to flush a log output stream failed.
- PRCR-01165: Failed to close the output stream
-
Cause: An attempt to close a log file failed.
- PRCR-01166: An operation on output stream failed
-
Cause: An operation on output stream failed.
- PRCR-01169: Mismatch between the number of attribute names ({0}) and the number of the corresponding attribute values ({1})
-
Cause: Internal error.
- PRCR-01170: Failed to add resource {0}
-
Cause: An attempt to add the specified resource failed.
- PRCR-01171: Insufficient number of arguments while executing "{0}"
-
Cause: An attempt was made to execute the specified script with insufficient number of arguments.
- PRCR-01172: Failed to execute "srvmhelper" for {0}
-
Cause: Failed to execute srvmhelper for the specified API.
- PRCR-01173: Failed to look up CRS resource for type {0}
-
Cause: An attempt to search for resource of the specified type failed.
- PRCR-01174: Resource {0} is not running on nodes: {1}.
-
Cause: The specified resource was not started or not running on the specified nodes.
- PRCR-01175: Failed to add ASM Listener "{0}" because a dependent resource does not exist.
-
Cause: During creation of an ASM listener resource, internal updates to associated ASM or IOServer resources could not be made because the resource(s) did not exist.
- PRCR-01176: A software exception has occurred.
-
Cause: An internal exception occurred while attempting to update resource dependencies during creation of an ASM Listener configuration.
- PRCR-01177: Failed to update dependency on related resources when adding ASM listener "{0}"
-
Cause: During creation of an ASM listener resource, updates to associated ASM or IOServer resources failed.
- PRCR-01178: Execution of command failed on one or more nodes
-
Cause: Execution of a command through the administrator helper resource failed.
- PRCR-01179: Failed to retrieve nodes suitable for configuring an administrator-managed database
-
Cause: An attempt to execute the command 'olsnodes -a' has failed.
- PRCR-01180: No response received
-
Cause: A response was not received while executing the command through the administrator helper resource.
- PRCR-01181: Failed to request action {0} on resource {1}
-
Cause: An attempt to request the action on the resource failed.
- PRCR-01182: Failed to request action {0} on resource {1} on nodes {2}
-
Cause: An attempt to request the action on the resource failed on the specified nodes.
- PRCR-01183: Failed to request action {0} on multiple resources
-
Cause: An attempt to request the action on multiple resources failed.
- PRCR-01184: Response from the resource on which the action was requested was not in the correct format
-
Cause: An internal error occurred. The callback message for the requested action was not in the correct format during an attempt to request the action.
- PRCR-01185: failed to execute "srvmhelper" for command "{0}" with the following errors:\n{1}
-
Cause: An attempt to execute the command has failed.
- PRCR-01186: Multiple final messages for the requested action were received for node {0}
-
Cause: An internal error occurred. Multiple final messages for the requested action were received during an attempt to request the action.
- PRCR-01187: No final message for the requested action was received.
-
Cause: An internal error occurred. No final message for the requested action was received during an attempt to request the action.
- PRCR-01188: The requested action cannot be executed because there is no resource instance.
-
Cause: The resource has no instance on the specified nodes or, if nodes were not specified, in the cluster.
- PRCR-01189: The user {1} does not have read and execute permissions for the ACFS file system resource associated with path {0}.
-
Cause: A check on the permissions for the ACFS file system resource associated with the indicated path failed because the user indicated in the message did not have read and execute permissions for the resource.
- PRCR-01190: The specified VIP name {0} resolves to multiple {1} addresses.
-
Cause: The specified VIP name did not resolve to a single IPv4 or IPv6 address.
- PRCR-01191: The stop request failed because the resource is not running on nodes {0}.
-
Cause: A request to stop a resource was rejected because the resource did not have a running instance on the specified nodes.
- PRCR-01192: Resource {0} is not hosted by server pool {1}.
-
Cause: An attempt to start or stop the specified resource on the specified server pool failed because the resource is not hosted by the server pool.
- PRCR-01193: The specified instance on cardinality ID {0} of resource {1} is already enabled.
-
Cause: An attempt to enable the specified resource instance was rejected because the resource instance was already enabled.
- PRCR-01194: The specified instance on cardinality ID {0} of resource {1} is already disabled.
-
Cause: An attempt to disable the specified resource instance was rejected because the resource instance was already disabled.
- PRCR-01195: Resource {0} does not have attributes {1} on cardinality ID {2}.
-
Cause: An attempt to remove the specified attributes failed because these attributes did not exist on the specified cardinality.
- PRCR-01196: The specified instances of resource {0} are already enabled.
-
Cause: An attempt to enable the resource instances was rejected because the resource instances were already enabled.
- PRCR-01197: The specified instances of resource {0} are already disabled.
-
Cause: An attempt to disable the resource instances was rejected because the resource instances were already disabled.
- PRCR-01198: failed to relocate resources using a filter
-
Cause: An attempt to relocate resources using the filter shown in the message failed.
- PRCR-01199: timed out waiting for the spawned process to complete
-
Cause: An attempt to move the Oracle Grid Infrastructure home failed because the detached process timed out. The accompanying error messages provide details of the error.
- PRCR-01200: failed to execute the detached process
-
Cause: An attempt to move the Oracle Grid Infrastructure home failed because the detached process failed with an error. The accompanying error messages provide details of the error.
- PRCR-01201: The specified node "{0}" is not part of a cluster.
-
Cause: An attempt to obtain the Oracle Grid Infrastructure home was rejected because the specified node was not part of the cluster.
- PRCR-01202: Value "{0}" is invalid for the CSS_CRITICAL resource attribute.
-
Cause: An attempt was made to set a value other than 'yes' or 'no' for the CSS_CRITICAL resource attribute. The indicated resource attribute can be set to either 'yes' or 'no' only.
- PRCR-01203: failed to copy the directory contents for directory "{0}"
-
Cause: An attempt to copy the directory contents for the specified directory failed.
- PRCR-01204: Failed to execute "srvmhelper" binary on node "{0}". Detailed error:\n{1}
-
Cause: An attempt to execute srvmhelper failed on the specified node.
- PRCR-01205: failed to execute "srvmhelper" binary on node "{0}"
-
Cause: An attempt to execute srvmhelper failed on the specified node.
- PRCR-01206: failed to copy the directory contents for directory "{0}" because it is the same as the destination directory and the local node "{1}" was included in the list of nodes where the copy has to occur
-
Cause: An attempt to copy the directory contents was rejected because the destination directory path and source directory path were the same and the local node was part of the list of nodes where the copy had to occur.
- PRCR-01207: There are no running resources to stop.
-
Cause: An attempt to stop the resources failed because they were already stopped. For detailed information about the resources, review the accompanying error messages.
- PRCR-01208: File "{0}" on node "{1}" was empty.
-
Cause: The indicated file, which was expected to contain information about the Cluster Ready Services (CRS) configuration, was empty. This is an internal error.
- PRCR-01209: failed to upgrade the dependencies for resource {0}
-
Cause: An attempt to upgrade the dependencies for the specified resource failed. Accompanying error messages provide detailed error information.
- PRCR-01213: Resource group {0} does not exist.
-
Cause: An attempt was made to operate on a resource group that did not exist.
- PRCR-01214: failed to stop resource group {0}
-
Cause: An attempt to stop the indicated resource group failed because the resource group was not running or the resource group was running and had dependent resource groups also running.
- PRCR-01215: The resource group was not running.
-
Cause: An attempt to stop a resource group was rejected because the group was not running. For detailed information about the resource group, review the accompanying error messages.
- PRCR-01216: The stop request failed because the resource group is not running on nodes {0}.
-
Cause: A request to stop a resource group was rejected because the resource group did not have a running instance on the specified nodes.
- PRCR-01217: Failed to relocate resource group {0}
-
Cause: An attempt to relocate the specified resource group failed.
- PRCR-01218: Failed to relocate resource group {0} from node {1}
-
Cause: An attempt to relocate the resource group from the specified node failed.
- PRCR-01219: Failed to relocate resource group {0} from node {1} to node {2}
-
Cause: An attempt to relocate the resource group from the specified node to another failed.
- PRCR-01220: Failed to relocate resource group {0} to node {1}
-
Cause: An attempt to relocate the resource group to the specified node failed.