PRCA-01000 to PRCA-01158

102 PRCA-01000 to PRCA-01158

PRCA-01000: ASM Disk Group {0} does not exist: Cause: An attempt failed to retrieve an ASM disk group that was not configured.; Action: Create the diskgroup using sqlplus if the specified diskgroup does not exist. Mount the diskgroup in ASM which registers the diskgroup with CRS.
PRCA-01001: ASM Disk Group resource does not exist: Cause: There was no disk group resource registered with CRS.; Action: Create the diskgroup using sqlplus and mount the diskgroup in ASM which registers the diskgroup with CRS.
PRCA-01002: Failed to remove CRS resource {0} for ASM Disk Group {1}: Cause: An attempt to remove the CRS resource for the specified ASM Disk Group failed.; Action: Examine the accompanying error messages for details.
PRCA-01003: Failed to create ASM {0} resource {1}: Cause: An attempt to add the CRS resource for ASM failed.; Action: Ensure that the CRS stack is running, the user running srvctl add asm is also the owner of the CRS home, and examine the accompanying error message for details.
PRCA-01005: Failed to retrieve server parameter file of ASM {0}: Cause: Cannot retrieve ASM server parameter file.; Action: Retry the request after ensuring that the CRS stack is running, the ASM resource has been configured, and the user has read permission on the ASM resource.
PRCA-01006: Failed to update server parameter file {0} of ASM {1}: Cause: Unable to update the ASM server parameter file.; Action: Retry the request after ensuring that the CRS stack is running, the ASM resource has been configured, and the user has update permission on the ASM resource.
PRCA-01007: ASM {0} is not using initialization parameters: {1}: Cause: The specified ASM instance does not use the initialization parameters shown.; Action: Examine the accompanying error messages for details.
PRCA-01016: Failed to remove ASM resource {0} for ASM instance {1}: Cause: An attempt to remove the specified ASM configuration failed.; Action: Examine the accompanying error message for details.
PRCA-01017: ASM {0} does not exist: Cause: ASM is not configured yet.; Action: Configure ASM and then retry.
PRCA-01018: Failed to retrieve ASM instance list for ASM {0}: Cause: Failed to retrieve the list of ASM instances.; Action: Make sure that the crs stack is up and the ASM resource has been configured.
PRCA-01019: ASM {0} is not running: Cause: The ASM resource does not have any running instances.; Action: Use 'srvctl start asm' command to start the asm resource.
PRCA-01020: Unable to create ACFS file system resource {0} for the volume device {1}: Cause: The ACFS file system resource for the specified volume device path could not be created. Possible causes: 1) CRS stack was not available. 2) ASM instance was not running. 3) User was not running with an account with administrative access. (root, Administrator, etc) 4) Was unable to identify the mount point that the user requested the resource to use.; Action: 1) Verify that the CRS stack is available. ( 'crsctl check crs' ) 2) Verify that ASM is running. (srvctl status asm) 3) Verify that the user is running with administrative access. 4) Verify that the mount point given to the create resource command exists.
PRCA-01021: Unable to retrieve ACFS file system for the volume device {0}: Cause: The ACFS file system resource for the specified volume device path could not be retrieved. Possible causes: 1) CRS stack was not available. 2) ASM instance was not running. 3) User was not running with an account with administrative access. (root, Administrator, etc) 4) Was unable to identify the mount point that the user requested the resource to use.; Action: 1) Verify that the CRS stack is available. ( 'crsctl check crs' ) 2) Verify that ASM is running. (srvctl status asm) 3) Verify that the user is running with administrative access. 4) Verify that the mount point given to the create resource command exists.
PRCA-01022: ACFS file system resource already exists for disk group {0} and volume {1}: Cause: The ACFS file system resource had already been created for the specified disk group and volume names.; Action: Take one of the following actions: 1) Supply a different volume device path to the 'srvctl add filesystem' command to create a different ACFS file system resource. -or- 2) Delete the previous resource ('srvctl remove filesystem -device <volume_device>') and run the command again.
PRCA-01023: Unable to add ACFS file system resource {0} for disk group {1} and volume {2}: Cause: The ACFS file system resource for the specified volume device path could not be added. Possible causes: 1) CRS stack was not available. 2) ASM instance was not running. 3) User was not running with an account with administrative access. (root, Administrator, etc) 4) Was unable to identify the mount point that the user requested the resource to use.; Action: 1) Verify that the CRS stack is available. ( 'crsctl check crs' ) 2) Verify that ASM is running. ( 'srvctl status asm' ) 3) Verify that the user is running with administrative access. 4) Verify that the mount point given to the create resource command exists.
PRCA-01024: Unable to retrieve the volume for disk group {0} and volume {1}: Cause: The ACFS file system resource for the specified volume device path was unable to be retrieved. Possible causes: 1) CRS stack was not available. 2) ASM instance was not running. 3) User was not running with an account with administrative access. (root, Administrator, etc); Action: 1) Verify that the CRS stack is available. ( 'crsctl check crs' ) 2) Verify that ASM is running. ( 'srvctl status asm' ) 3) Verify that the user is running with administrative access.
PRCA-01025: Unable to retrieve the mountpoint path for disk group {0} and volume {1}: Cause: The ACFS file system resource for the specified volume device path was unable to be retrieved. Possible causes: 1) CRS stack was not available. 2) ASM instance was not running. 3) User was not running with an account with administrative access. (root, Administrator, etc); Action: 1) Verify that the CRS stack is available. ( 'crsctl check crs' ) 2) Verify that ASM is running. ( 'srvctl status asm' ) 3) Verify that the user is running with administrative access.
PRCA-01026: Unable to set the user of the ACFS file system for disk group {0} and volume {1}: Cause: The user of the ACFS file system resource for the specified disk group and volume was unable to be modified. Possible causes: 1) CRS stack was not available. 2) ASM instance was not running. 3) User was not running with an account with administrative access. (root, Administrator, etc); Action: 1) Verify that the CRS stack is available. ( 'crsctl check crs' ) 2) Verify that ASM is running. ( 'srvctl status asm' ) 3) Verify that the user is running with administrative access.
PRCA-01027: Failed to remove ACFS file system configuration for disk group {0} and volume {1}: Cause: Cannot remove the ACFS file system configuration for the specified disk group and volume.; Action: 1) Verify that the CRS stack is available. ( 'crsctl check crs' ) 2) Verify that ASM is running. ( 'srvctl status asm' ) 3) Verify that the user is running with administrative access.
PRCA-01028: Failed to retrieve listener associated with ASM {0}: Cause: Failed to retrieve listener associated with ASM.; Action: Ensure that user has read permissions on ASM resource and then retry. Also, ensure that listener specified in ASM resource's start dependencies exists.
PRCA-01029: Failed to associate listener {0} with ASM {1}: Cause: Failed to associate given listener with ASM.; Action: Ensure that user has update permissions on ASM resource and then retry.
PRCA-01030: Failed to retrieve the diskgroup associated with the volume device {0}: Cause: Unable to retrieve the diskgroup associated with the given volume device using "asmcmd volinfo -g <volume_name>" command.; Action: Make sure that the asm instance is running; the asmcmd utility exists and the underlying ofs devices are accessible.
PRCA-01031: Unable to retrieve the diskgroup {0} associated with the volume device {1}: Cause: The ACFS file system resource for the specified volume device path was unable to be retrieved. Possible causes: 1) CRS stack was not available. 2) ASM instance was not running. 3) User was not running with an account with administrative access. (root, Administrator, etc) 4) Disk group is not mounted.; Action: 1) Verify that the CRS stack is available. ( 'crsctl check crs' ) 2) Verify that ASM is running. ( 'srvctl status asm' ) 3) Verify that the user is running with administrative access. 4) Verify that the disk group is mounted.
PRCA-01032: ASM listener {0} does not exist: Cause: The ASM listener was not registered with Oracle Clusterware.; Action: Add the listener with the 'srvctl add listener -listener <lsnr_name> -asmlistener' command or specify a listener name that is already registered.
PRCA-01033: ACFS file system resource does not exist for volume device {0}: Cause: The ACFS file system resource with the specified volume device was not registered with Oracle Clusterware.; Action: Use the command 'srvctl add filesystem' to create an ACFS file system resource.
PRCA-01034: ACFS file system resource does not exist in Oracle Clusterware: Cause: No ACFS file system resource was registered with Oracle Clusterware.; Action: Use the command 'srvctl add filesystem' to create an ACFS file system resource.
PRCA-01035: Unable to determine the databases that use the disk group {0}: Cause: Unable to retrieve databases that have dependencies on the disk group.; Action: Make sure that the crs stack is up; the user has read permissions on database CRS resources and then retry.
PRCA-01036: An Oracle Restart environment-specific API was invoked in an Oracle Clusterware environment.: Cause: Internal error.; Action: Contact Oracle Support Services.
PRCA-01037: Failed to retrieve the diskgroup discovery string of ASM {0}: Cause: An attempt to retrieve the diskgroup discovery string for ASM failed.; Action: Retry the request after ensuring that the CRS stack is running, the ASM resource has been configured, and the user has read permission on ASM resource.
PRCA-01038: Failed to update the diskgroup discovery string {0} of ASM {1}: Cause: An attempt to update the diskgroup discovery string for ASM failed.; Action: Retry the request after ensuring that the CRS stack is running, the ASM resource has been configured, and the user has update permission on ASM resource.
PRCA-01039: Volume device {0} does not exist: Cause: The supplied volume device does not exist.; Action: Use asmca to create the volume device and then run 'srvctl add filesystem' command again.
PRCA-01040: Failed to check the existence of volume device {0}: Cause: Failed to execute acfsutil command to check for the existence of the supplied volume device.; Action: Review the underlying error messages that provide the details of why acfsutil execution failed. Resolve the reported problem and retry the command.
PRCA-01041: Failed to validate disk group {0} of volume device {1}: Cause: Failed to execute acfsutil command to validate the disk group of the volume device.; Action: Review the underlying error messages that provide the details of why acfsutil execution failed. Resolve the reported problem and retry 'srvctl add filesystem' command.
PRCA-01042: Diskgroup {0} is not valid for volume device {1}: Cause: The supplied diskgroup does not match the underlying diskgroup created for the supplied volume device.; Action: Execute 'srvctl add filesystem' command with the correct disk group value.
PRCA-01043: Failed to validate volume {0} of volume device {1}: Cause: Failed to execute acfsutil command to validate the volume of the volume device.; Action: Review the underlying error messages that provide the details of why acfsutil execution failed. Resolve the reported problem and retry 'srvctl add filesystem' command.
PRCA-01044: Volume {0} is not valid for volume device {1}: Cause: The supplied volume does not match the underlying volume created for the supplied volume device.; Action: Execute 'srvctl add filesystem' command with the correct volume value.
PRCA-01045: ACFS is not supported on this platform: Cause: A filesystem operation was requested on an unsupported platform.; Action: Run srvctl filesystem command on a supported platform.
PRCA-01046: File system for volume device {0} exists in the ACFS registry: Cause: File system for the specified volume device was registered in the ACFS registry. File system can either be in the ACFS registry or registered as a CRS resource, but not both.; Action: Either run the command 'acfsutil registry -d' to delete the volume device from the ACFS registry or run the command 'srvctl add filesystem' with a different volume device.
PRCA-01047: Unable to find ACFS file system resource for volume device {0} because of inability to get the canonical form of the volume device: Cause: An internally-issued 'advmutil canonical' command failed and the volume device recorded in the ACFS file system resource did not match the specified volume device.; Action: Review the underlying error messages that provide the details of why advmutil execution failed. Resolve the reported problem and retry.
PRCA-01048: Invalid mount point path {0} because specified mount point path was a remote path: Cause: The specified mount point path was a remote path.; Action: Make sure that the mount point path was not a remote path.
PRCA-01049: The user "{0}" could not be found on the cluster: Cause: The user specified as the file system owner/user could not be found.; Action: Enter the name of an existing user or the owner of the specified file system.
PRCA-01050: Unable to retrieve the canonical form of the volume device for disk group {0} and volume {1}: Cause: The ACFS file system resource for the specified canonical form of the volume device path was not retrieved.; Action: 1) Make sure that the CRS stack is available. ( 'crsctl check crs' ) 2) Review the accompanying error messages for details about the failure. Retry after resolving those issues.
PRCA-01051: No volume resource registered with CRS for specified diskgroup or volume name or volume device: Cause: There was no volume resource registered with CRS for specified diskgroup and volume name.; Action: Create the volume using sqlplus which registers the volumes with CRS.
PRCA-01052: When attempting to create a volume resource in CRS, volume resource already exists for disk group {0} and volume {1}: Cause: The volume resource was already created for the specified disk group and volume names.; Action: Supply different volume name or diskgroup name to create a different volume resource.
PRCA-01053: Failed to add volume resource {0} for disk group {1} and volume {2}: Cause: The volume resource for the specified volume device path could not be added. Possible causes: 1) CRS stack was not available. 2) ASM instance was not running. 3) User was not running with an account with administrative access. (root, Administrator, etc); Action: 1) Verify that the CRS stack is available. ( 'crsctl check crs' ) 2) Verify that ASM is running. ( 'srvctl status asm' ) 3) Verify that the user is running with administrative access.
PRCA-01054: Failed to remove volume configuration for disk group {0} and volume {1}: Cause: Cannot remove the volume configuration for the specified disk group and volume.; Action: 1) Verify that the CRS stack is available. ( 'crsctl check crs' ) 2) Verify that ASM is running. ( 'srvctl status asm' ) 3) Verify that the user is running with administrative access.
PRCA-01055: Failed to retrieve the volume file system type for disk group {0} and volume {1}: Cause: The usage of the specified volume was unable to be retrieved. Possible causes: 1) CRS stack was not available. 2) ASM instance was not running. 3) User was not running with an account with administrative access. (root, Administrator, etc); Action: 1) Verify that the CRS stack is available. ( 'crsctl check crs' ) 2) Verify that ASM is running. ( 'srvctl status asm' ) 3) Verify that the user is running with administrative access.
PRCA-01056: Unable to upgrade ACFS from version {0} to version {1}: Cause: Failed to upgrade ACFS from one version to another version.; Action: Review the accompanying error messages for details about the failure. Retry after resolving those issues.
PRCA-01057: Failed to retrieve the password file location used by ASM {0}: Cause: An attempt to retrieve the password file attribute of the specified ASM failed.; Action: Retry the request after ensuring that the CRS stack is running, the ASM resource has been configured, and the user has read permission on the ASM resource.
PRCA-01058: Failed to update password file location {0} used by ASM {1}: Cause: An attempt to update the password file attribute of the specified ASM failed.; Action: Retry the request after ensuring that the CRS stack is running, the ASM resource has been configured, and the user has update permission on the ASM resource.
PRCA-01059: Invalid ASM type {0}: Cause: The ASM type supplied is not valid.; Action: Supply a valid ASM type.
PRCA-01060: Invalid ASM presence {0}: Cause: The ASM presence supplied is not valid.; Action: Supply a valid ASM presence (legacy or remote).
PRCA-01061: Failed to create ASM I/O Server resource {0}: Cause: An attempt to add the CRS resource for ASM I/O Server failed.; Action: Ensure that the CRS stack is running, the user running 'srvctl add asm' is also the owner of the CRS home, and examine the accompanying error message for details.
PRCA-01062: Failed to create cluster ASM resource {0}: Cause: An attempt to add the CRS resource for cluster ASM failed.; Action: Ensure that the CRS stack is running, the user running 'srvctl add asm' is also the owner of the CRS home, and examine the accompanying error message for details.
PRCA-01063: Failed to create ADVM proxy resource {0}: Cause: An attempt to add the CRS resource for ADVM proxy failed.; Action: Ensure that the CRS stack is running, the user running 'srvctl add asm' is also the owner of the CRS home, and examine the accompanying error message for details.
PRCA-01064: Failed to create leaf ASM resource {0}: Cause: An attempt to add the CRS resource for leaf ASM failed.; Action: Ensure that the CRS stack is running, the user running command 'srvctl add asm' is also the owner of the CRS home, and examine the accompanying error message for details.
PRCA-01065: No file system resource found in Oracle Clusterware: Cause: No ACFS or non-ACFS file system resource was registered with Oracle Clusterware.; Action: Use the command 'srvctl add filesystem' to create a file system resource.
PRCA-01066: File system resource already exists for disk group {0} and volume {1}: Cause: The file system resource was already created for the specified disk group and volume names.; Action: Take one of the following actions: 1) Supply a different volume device path to the 'srvctl add filesystem' command to create a different file system resource. -or- 2) Delete the existing resource ('srvctl remove filesystem -device <volume_device>') and run the command again.
PRCA-01067: Unable to add file system resource {0} for disk group {1} and volume {2}: Cause: The file system resource for the specified volume device path could not be added. Possible causes: 1) CRS stack was not available. 2) ASM instance was not running. 3) User was not running with an account with administrative access. (root, Administrator, etc) 4) Was unable to resolve the mount point path that the user requested the resource to use.; Action: 1) Verify that the CRS stack is available. ( 'crsctl check crs' ) 2) Verify that ASM is running. ( 'srvctl status asm' ) 3) Verify that the user is running with administrative access. 4) Verify that the mount point path given to the create resource command exists.
PRCA-01068: Failed to remove file system resource for disk group {0} and volume {1}: Cause: Failed to remove the file system resource for the specified disk group and volume.; Action: 1) Verify that the CRS stack is available. ( 'crsctl check crs' ) 2) Verify that ASM is running. ( 'srvctl status asm' ) 3) Verify that the user is running with administrative access.
PRCA-01069: Unable to set the user of the file system configuration for disk group {0} and volume {1}: Cause: The user of the FS file system resource for the specified disk group and volume was unable to be modified. Possible causes: 1) CRS stack was not available. 2) ASM instance was not running. 3) User was not running with an account with administrative access. (root, Administrator, etc); Action: 1) Verify that the CRS stack is available. ( 'crsctl check crs' ) 2) Verify that ASM is running. ( 'srvctl status asm' ) 3) Verify that the user is running with administrative access.
PRCA-01070: File system resource does not exist for volume device "{0}": Cause: The file system resource with the specified volume device was not registered with Oracle Clusterware.; Action: Use the command 'srvctl add filesystem' to create a file system resource.
PRCA-01071: Multiple file system resources found for volume device "{0}": Cause: More than one file system resources with the specified volume device were found.; Action: Internal error. Contact Oracle Support Services.
PRCA-01072: Either zero or multiple volume resources found for diskgroup "{0}" and volume "{1}": Cause: A single volume was expected to be found for the specified parameters.; Action: Internal error. Contact Oracle Support Services.
PRCA-01073: A resource for application with ID "{0}" that uses a different file system than "{1}" already exists: Cause: A resource with the same application ID was registered for a different file system type.; Action: Make sure that the file system being added uses the same type as the existing resource for the given application ID.
PRCA-01074: Unable to modify the file system resource {0} for disk group {1} and volume {2}: Cause: The ACFS file system resource for the specified volume device path could not modified. Possible causes: 1) CRS stack was not available. 2) ASM instance was not running. 3) User was not running with an account with administrative access. (root, Administrator, etc); Action: 1) Verify that the CRS stack is available. ( 'crsctl check crs' ) 2) Verify that ASM is running. ( 'srvctl status asm' ) 3) Verify that the user is running with administrative access.
PRCA-01075: The file system resource is running on nodes (e.g. node "{0}") which are not included in the node list: Cause: The attempt to modify the node list failed as the file system resource was running on one or more nodes of the existing node list that were not included in the new node list.; Action: Either stop the resource that is running and retry or add the node where the resource is running to the new node list.
PRCA-01076: The file system resource is running on server pools (e.g. server pool "{0}") which are not included in the server pool list: Cause: The attempt to modify the node list failed as the file system resource was running on one or more server pools of the existing server pool list that were not included in the new server pool list.; Action: Either stop the resource that is running and retry.
PRCA-01077: Unable to retrieve the file system type for disk group {0} and volume {1}: Cause: The file system resource for the specified volume device path was unable to be retrieved. Possible causes: 1) CRS stack was not available. 2) ASM instance was not running. 3) User was not running with an account with administrative access. (root, Administrator, etc); Action: 1) Verify that the CRS stack is available. ( 'crsctl check crs' ) 2) Verify that ASM is running. ( 'srvctl status asm' ) 3) Verify that the user is running with administrative access.
PRCA-01078: Unable to retrieve the file system mount options for disk group {0} and volume {1}: Cause: The file system resource for the specified volume device path was unable to be retrieved. Possible causes: 1) CRS stack was not available. 2) ASM instance was not running. 3) User was not running with an account with administrative access. (root, Administrator, etc); Action: 1) Verify that the CRS stack is available. ( 'crsctl check crs' ) 2) Verify that ASM is running. ( 'srvctl status asm' ) 3) Verify that the user is running with administrative access.
PRCA-01079: Unable to retrieve the file system node names for disk group {0} and volume {1}: Cause: The file system resource for the specified volume device path was unable to be retrieved. Possible causes: 1) CRS stack was not available. 2) ASM instance was not running. 3) User was not running with an account with administrative access. (root, Administrator, etc); Action: 1) Verify that the CRS stack is available. ( 'crsctl check crs' ) 2) Verify that ASM is running. ( 'srvctl status asm' ) 3) Verify that the user is running with administrative access.
PRCA-01080: Unable to retrieve the file system server pools for disk group {0} and volume {1}: Cause: The file system resource for the specified volume device path was unable to be retrieved. Possible causes: 1) CRS stack was not available. 2) ASM instance was not running. 3) User was not running with an account with administrative access. (root, Administrator, etc); Action: 1) Verify that the CRS stack is available. ( 'crsctl check crs' ) 2) Verify that ASM is running. ( 'srvctl status asm' ) 3) Verify that the user is running with administrative access.
PRCA-01081: Unable to retrieve the application ID for disk group {0} and volume {1}: Cause: The file system resource for the specified volume device path was unable to be retrieved. Possible causes: 1) CRS stack was not available. 2) ASM instance was not running. 3) User was not running with an account with administrative access. (root, Administrator, etc); Action: 1) Verify that the CRS stack is available. ( 'crsctl check crs' ) 2) Verify that ASM is running. ( 'srvctl status asm' ) 3) Verify that the user is running with administrative access.
PRCA-01082: Unable to retrieve the value for attribute 'TYPE' for the file system resource with disk group {0} and volume {1}: Cause: The file system resource for the specified volume device path was unable to be retrieved. Possible causes: 1) CRS stack was not available. 2) ASM instance was not running. 3) User was not running with an account with administrative access. (root, Administrator, etc); Action: 1) Verify that the CRS stack is available. ( 'crsctl check crs' ) 2) Verify that ASM is running. ( 'srvctl status asm' ) 3) Verify that the user is running with administrative access.
PRCA-01083: Invalid ASM mode {0}: Cause: The specified ASM mode was not valid.; Action: Specify a valid ASM mode LEGACY, REMOTE or CLIENT.
PRCA-01084: Failed to retrieve ASM Mode: Cause: An attempt to retrieve the configured ASM mode from the ASM resource failed.; Action: Retry the request after ensuring that the CRS stack is running, the ASM resource has been configured, and the user has read permission on the ASM resource.
PRCA-01085: Failed to check if OCR is on ASM, when attempting to create resource {0}: Cause: An attempt to retrieve the OCR locations and check if any of the locations is on ASM failed.; Action: Ensure that the CRS stack is running, the user running command 'srvctl add asm' is also the owner of the CRS home, and examine the accompanying error message for details.
PRCA-01086: Unable to retrieve the file system description for disk group {0} and volume {1}: Cause: The file system resource for the specified volume device path was unable to be retrieved. Possible cause: The CRS stack was not available.; Action: Verify that the CRS stack is available. ( 'crsctl check crs' )
PRCA-01087: Server pool "{0}" does not exist: Cause: No servepool was found for the specified server pool name.; Action: Make sure that the serverpool exists and retry.
PRCA-01088: Unable to retrieve information about server pool "{0}": Cause: An error occurred while trying to retrieve information about the specified server pool.; Action: Examine the accompanying error messages for details.
PRCA-01089: Unable to retrieve volume and disk group for volume device path {0}: Cause: The volume and disk group resources for the specified volume device path could not be retrieved. Possible causes: 1) The CRS stack was not available. 2) The volume device path does not exist.; Action: 1) Verify that the CRS stack is running. ( 'crsctl check crs' ) 2) Verify that the volume device path was previously created.
PRCA-01090: Unable to retrieve information about the server category for server pool "{0}": Cause: An error occurred while trying to retrieve information about the server category for the specified server pool.; Action: Examine the accompanying error messages for details.
PRCA-01091: The server category for server pool "{0}" is not "{1}": Cause: The server category for the specified server pool had not the indicated expected value.; Action: Execute the command 'srvctl modify srvpool' to set the server category for the specified server pool to the indicated value and retry.
PRCA-01092: Cannot retrieve ASM resource information on an ASM client cluster: Cause: An attempt was made to get reference to an ASM resource on an ASM client cluster, which is not allowed.; Action: Perform this action only on an ASM cluster in either the Standard mode or in the Remote mode.
PRCA-01093: ASM I/O Server {0} is not running: Cause: The ASM I/O Server resource did not have any running instances.; Action: Use the command 'srvctl start ioserver' to start the ASM I/O Server resource.
PRCA-01094: Failed to retrieve ASM I/O Server instance list for ASM I/O Server {0}: Cause: Failed to retrieve the list of ASM I/O Server instances.; Action: Make sure that the Clusterware stack is up and the ASM I/O Server resource has been configured.
PRCA-01095: Unable to create ASM resource because it already exists.: Cause: An attempt was made to add the ASM resource but the resource already exists.; Action: Either remove the ASM resource and then add it, or avoid adding an already existing resource.
PRCA-01096: failed to create the Network Attached Storage (NAS) resource {0} for mount point path {1}: Cause: An attempt to create a Network Attached Storage (NAS) resource failed for the specified mount point path.; Action: Examine the accompanying error messages for details.
PRCA-01097: failed to retrieve the Network Attached Storage (NAS) resource for the mount point path {0}: Cause: An attempt to retrieve the Network Attached Storage (NAS) resource failed for the specified mount point path.; Action: Examine the accompanying error messages for details.
PRCA-01098: A Network Attached Storage (NAS) resource already exists for mount point path {0}.: Cause: An attempt to create a Network Attached Storage (NAS) resource failed because a NAS resource already exists for the specified mount point path.; Action: Do one of the following: - Supply a different mount point path. - Delete the previous resource.
PRCA-01099: failed to set the user of the Network Attached Storage (NAS) for mount point path {0}: Cause: An attempt to modify the user for the Network Attached Storage (NAS) failed for the specified mount point path.; Action: Examine the accompanying error messages for details.
PRCA-01100: The Network Attached Storage (NAS) resource does not exist for mount point path {0}.: Cause: The Network Attached Storage (NAS) resource with the specified mount point path was not registered with Oracle Clusterware.; Action: Create a Network Attached Storage (NAS) resource with the specified mount point path.
PRCA-01101: failed to modify the Network Attached Storage (NAS) resource for mount point path {0}: Cause: An attempt to modify the Network Attached Storage (NAS) resource failed for the specified mount point path.; Action: Examine the accompanying error messages for details.
PRCA-01102: Mount point path {0} is in use by another file system resource.: Cause: The supplied mount point path was already used by an existing file system resource.; Action: Specify a mount point path not in use by ACFS and not in use by Network Attached Storage (NAS) resources.
PRCA-01103: Failed to validate export server {0}: Cause: An attempt to resolve the export server name failed because the specified server name does not exist in DNS.; Action: Specify a valid IP address or hostname.
PRCA-01104: failed to remove Network Attached Storage (NAS) resource for mount point path {0}: Cause: An attempt to remove the Network Attached Storage (NAS) resource failed for the specified mount point path.; Action: Examine the accompanying error messages for details.
PRCA-01105: The mount point path must be specified when adding a Network Attached Storage (NAS) resource.: Cause: An attempt to create a Network Attached Storage (NAS) resource failed because a value was not specified for the mount point path.; Action: Specify a valid mount point path.
PRCA-01106: Mount point path {0} is in use by another file system resource: Cause: The supplied mount point path was already used by an existing file system resource.; Action: Specify a mount point path that is not in use by a file system resource.
PRCA-01107: A Network Attached Storage (NAS) resource already exists with the name {0}.: Cause: The Network Attached Storage (NAS) resource was already created for the specified name.; Action: Supply a different name or delete the previous resource.
PRCA-01108: The file system resource is not node local.: Cause: The attempt to relocate the specified file system failed because the resource is not node local.; Action: Specify a node local file system resource.
PRCA-01109: The volume for the specified disk group {0} and volume name {1} is not registered with CRS.: Cause: There was no volume resource registered with CRS for the specified disk group and volume name.; Action: Create the volume for the specified disk group and volume name using SQL*Plus which registers the volumes with CRS.
PRCA-01110: The volume for the specified device path {0} is not registered with CRS.: Cause: There was no volume resource registered with CRS for the specified device path.; Action: Create the volume for the specified device path using SQL*Plus which registers the volumes with CRS.
PRCA-01111: Multiple volume resources were found for volume device "{0}".: Cause: This is an internal error. More than one volume resource with the specified volume device were found.; Action: Contact Oracle Support Services.
PRCA-01112: Mount point path {0} is in use by another file system resource on node {1}: Cause: An attempt to add a file system resource was rejected because the specified mount point path was already used by an existing file system resource on one of the specified nodes.; Action: Specify a mount point path not in use by a file system resource on any of the supplied nodes.
PRCA-01113: Unable to upgrade volume resources from version {0} to version {1}: Cause: An attempt to upgrade volume resources from one version to another version failed.; Action: Review the accompanying error messages for details about the failure. Retry after resolving those issues.
PRCA-01114: Unable to upgrade export file system resources from version {0} to version {1}: Cause: An attempt to upgrade export file system resources from one version to another version failed.; Action: Review the accompanying error messages for details about the failure. Retry after resolving those issues.
PRCA-01115: Volume device {0} is specified as both a primary and an accelerator volume: Cause: An attempt to add a file system resource was rejected because the specified accelerator volume devices included a volume device specified as a primary volume.; Action: Specify accelerator volume devices that are not also specified as a primary volume device.
PRCA-01116: Unable to define accelerator volumes for non-ACFS file systems: Cause: An attempt to add a file system resource was rejected because accelerator volume devices were specified for a non-ACFS file system resource.; Action: Specify accelerator volumes for an ACFS file system.
PRCA-01117: Unable to retrieve the accelerator volumes for file system resource {0}: Cause: An attempt to retrieve the accelerator volumes for the specified file system resource failed. Possible causes: 1) CRS stack was not available. 2) ASM instance was not running.; Action: 1) Verify that the CRS stack is available. ( 'crsctl check crs' ) 2) Verify that ASM is running. ( 'srvctl status asm' )
PRCA-01118: Multiple accelerator volumes are not supported.: Cause: An attempt to add a file system resource was rejected because multiple accelerator volume devices were specified for a file system resource.; Action: Specify only one accelerator volume.
PRCA-01119: Unable to get the users of the file system configuration for disk group {0} and volume {1}: Cause: 1) CRS stack was not running. 2) User was not running with an account with administrative access. (root or administrator); Action: 1) Verify that the CRS stack is running. ( 'crsctl check crs' ) 2) Verify that the user is running with administrative access.
PRCA-01120: Unable to use add (/+) or remove (/-) prefix with a list of operating system users for the file system.: Cause: The modify operation failed because a list of operating system users was specified using the add or remove prefix.; Action: Specify a single operating system user with the add or remove prefix, or specify a list of operating system users without any prefix to replace it entirely.
PRCA-01121: The file system type {0} is not supported for the current operating system platform.: Cause: An attempt to add a file system resource was rejected because the specified file system type is not supported for the current operating system platform.; Action: Specify a valid file system type for the operating system platform in use.
PRCA-01122: unable to modify the mount point path of a running file system resource: Cause: An attempt to modify the mount point path of the specified file system was rejected because the file system was mounted.; Action: Stop the file system resource and retry the operation.
PRCA-01123: The specified ASM cardinality {0} is less than the minimum cardinality of 2.: Cause: An attempt to set ASM cardinality was rejected because the specified cardinality was less than 2.; Action: Specify a number that is equal to or larger than 2 for the '-count' option.
PRCA-01124: The specified ASM cardinality {0} is larger than the maximum cardinality of 1024.: Cause: An attempt to set ASM cardinality was rejected because the specified cardinality was larger than 1024.; Action: Specify a number that is equal to or less than 1024 for the '-count' option.
PRCA-01125: The accelerator volumes are not supported on this operating system.: Cause: An attempt to add a file system resource was rejected because accelerator volumes are not supported for the current operating system.; Action: Do not specify accelerator volumes.
PRCA-01126: failed to retrieve information about server category "{0}": Cause: An error occurred while trying to retrieve information about the specified server category.; Action: Examine the accompanying error messages for details.
PRCA-01127: failed to find instances for database {0} that were running on nodes {1}: Cause: There were no running database instances on the specified nodes when the request to update the target instance was issued.; Action: Specify the nodes where database instances are running.
PRCA-01128: failed to create Oracle ACFS client cluster node membership and barrier resource {0}: Cause: An attempt to add the Cluster Ready Services (CRS) resource for an Oracle Automatic Storage Management Cluster File System (Oracle ACFS) client cluster node membership and barrier failed, possibly because the CRS stack was not running or the user running 'srvctl add ccmb' was not the owner of the CRS home.; Action: Examine the accompanying error messages for details and retry the command making sure that the CRS stack is running and the user running 'srvctl add ccmb' is the owner of the CRS home.
PRCA-01129: unable to create a non-ACFS file system in an ACFS-Remote environment: Cause: An attempt to create a file system in an ACFS-Remote environment was rejected because the requested file system was not Oracle Automatic Storage Management Cluster File System (Oracle ACFS). Only Oracle ACFS file systems are supported in clusters using ACFS-Remote.; Action: Retry specifying Oracle ACFS as the file system type.
PRCA-01130: volume name specification not permitted when creating a file system in a client cluster environment: Cause: An attempt to create a file system was rejected because it specified a volume name, which is not supported in a client cluster environment.; Action: Create an Oracle ACFS file system without specifying a volume name.
PRCA-01131: disk group name specification not permitted when creating a file system in a client cluster environment: Cause: An attempt to create a file system was rejected because it specified a disk group name, which is not supported in a client cluster environment.; Action: Create an Oracle ACFS file system without specifying a disk group name.
PRCA-01132: Instance names {0} are not active instances of database {1}.: Cause: A request to update database instances specified one or more that were not running.; Action: Specify instances of the database that are running.
PRCA-01133: Error updating the target instance for database {0}. Error: \n{1}: Cause: A request to update target instance for the list of database instances failed with the error shown.; Action: Review the accompanying error messages for more details.
PRCA-01134: Error updating the target instance for IOServer instances. Error: \n{0}: Cause: A request to update target instance for the list of IOServer instances failed with the error shown.; Action: Review the accompanying error messages for more details.
PRCA-01135: Instance names {0} are not active instances of IOServer.: Cause: A request to update IOServer instances specified one or more that were not running.; Action: Specify instances of the IOServer that are running.
PRCA-01136: failed to find instances for IOServer that were running on nodes {0}: Cause: There were no running IOServer instances on the specified nodes when the request to update the target instance was issued.; Action: Specify nodes where IOServer instances are running.
PRCA-01137: Oracle ACFS is not configured for mount point path {0}.: Cause: An attempt to query an Oracle Automatic Storage Management Cluster File System (Oracle ACFS) information attribute failed because Oracle ACFS was not configured for the specified mount point path (shown in the message).; Action: Retry, specifying a valid mount point path.
PRCA-01138: failed to start one or more file system resources:\n{0}: Cause: An attempt to start one or more file system resources failed because one or more file system resources were already running or disabled.; Action: Review accompanying messages and make sure that the file system resources are enabled and not running before starting them.
PRCA-01139: number of volume names and disk group names unequal: Cause: An attempt to start a list of file system resources failed because the number of volume names and disk group names differed.; Action: Retry 'srvctl start filesystem' specifying the same number of volume and disk group names.
PRCA-01140: Mount point path owner {0} is contained in the mount point user list.: Cause: An attempt to configure or modify the list of mount point users was rejected because the indicated mount point path owner was contained in the specified mount point users list.; Action: Remove the mount point path owner from the mount point users list.
PRCA-01141: User {0} is the mount point path owner.: Cause: An attempt to add or remove a user from the list of mount point users failed because the specified user was configured as the mount point path owner.; Action: Specify the new mount point path owner in the '-mountowner' option in the command 'srvctl modify filesystem'.
PRCA-01142: Volume device {0} is already configured as a primary volume device.: Cause: An attempt to add a file system resource was rejected because one or more of the specified volume devices were already configured as a primary volume device.; Action: Specify accelerator volume devices that are not configured as primary volume devices.
PRCA-01143: Volume device {0} is not formatted as an accelerator volume device for primary volume device {1}.: Cause: An attempt to add a file system resource was rejected because one or more of the specified volume devices were not formatted as accelerator volume devices for the specified primary volume device.; Action: Format the specified accelerator volume devices using the 'mkfs' command and retry the operation.
PRCA-01144: Mount point path {0} is not mounted.: Cause: An attempt to query file system information from the specified mount point path was rejected because the mentioned mount point path was not mounted in any node in the cluster.; Action: Specify a mount point path that is mounted or start the file system resource using the 'srvctl start filesystem' command.
PRCA-01145: error getting the client connection list for the ASM instances \n{0}: Cause: A request to get the client connection list for the ASM instances failed with the error shown.; Action: Review the accompanying error messages for more details. Address issues raised and retry.
PRCA-01146: error getting the client connection list for the I/O Server instances \n{0}: Cause: A request to get the client connection list for the I/O Server instances failed with the error shown.; Action: Review the accompanying error messages for more details. Address issues raised and retry.
PRCA-01147: CCMB is not supported on a cluster where an ASM instance is configured.: Cause: An attempt to create an Oracle ACFS Client Cluster Node Membership and Barrier (CCMB) resource was rejected because it is not supported for a cluster with configured ASM instances.; Action: Use the currently configured ASM instances and disk groups for this cluster.
PRCA-01148: unable to upgrade HAVIP resources from version {0} to version {1}: Cause: An attempt to upgrade high availability virtual IP resources from one version to another version failed. The accompanying error messages provide detailed information about the failure.; Action: Review the accompanying error messages for details about the failure. Retry after resolving those issues.
PRCA-01149: failure to create the Oracle Automatic Storage Management Cluster File System: Cause: An attempt to create an Oracle Automatic Storage Management Cluster File System (Oracle ACFS) failed. The accompanying error messages provide detailed failure information.; Action: Examine the accompanying error messages, address the issues raised, and retry.
PRCA-01150: failure to set ASM cardinality to a value other than ALL because the password file "{0}" is not on an ASM disk group: Cause: An attempt to update the ASM cardinality to a value other than ALL was rejected because the password file was not on an ASM disk group.; Action: Retry the request after moving the password file to an ASM disk group.
PRCA-01151: failed to retrieve the backup password file location used by ASM {0}: Cause: An attempt to retrieve the backup password file attribute of the specified ASM instance failed. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages and resolve the issues identified. Ensure that the CRS stack is running, the ASM resource has been configured, that the user has permission to read the ASM resource, and then retry the operation.
PRCA-01152: failed to create ASM resource group {0}: Cause: An attempt to add the Cluster Ready Services (CRS) resource group for an ASM Group failed. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages and resolve any issues indicated there. Ensure that the CRS stack is running, and then retry the command 'srvctl add asm' as the user that owns the CRS home.
PRCA-01153: The specified ASM Group cardinality {0} is less than the minimum cardinality of 2.: Cause: An attempt to set ASM Group cardinality was rejected because the specified cardinality was less than 2.; Action: Retry the operation, specifying a number that is equal to or larger than 2 for the '-count' option.
PRCA-01154: The specified ASM Group cardinality {0} is larger than the maximum cardinality of 1024.: Cause: An attempt to set ASM Group cardinality was rejected because the specified cardinality was larger than 1024.; Action: Retry the operation, specifying a number that is equal to or less than 1024 for the '-count' option.
PRCA-01155: Unable to create ASM resource group because it already exists.: Cause: An attempt to add an ASM resource group was rejected because the resource group already existed.; Action: None
PRCA-01156: failed to update backup password file location {0} used by ASM: Cause: An attempt to update the backup password file attribute of ASM failed, possibly because the Cluster Ready Services (CRS) stack was not running, the ASM resource was not configured, or the user does not have update permission on the ASM resource. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages and resolve the issues identified. Retry the request after ensuring that the Cluster Ready Services (CRS) stack is running, the ASM resource has been configured, and the user has update permission on the ASM resource.
PRCA-01157: The specified mount permissions value "{0}" is not valid.: Cause: An attempt to set mount permissions was rejected because the indicated value was not a valid permission specification.; Action: Retry the operation, specifying a valid permission specification.
PRCA-01158: The specified mount group "{0}" is not valid.: Cause: An attempt to set a mount group was rejected because the indicated group did not exist.; Action: Retry the operation, specifying a valid mount group.