7 ASMCMD-08001 to ASMCMD-09601
- ASMCMD-08001: diskgroup 'string' does not exist or is not mounted
-
Cause: An operation failed because the diskgroup specified did not exist or was not mounted by the current Oracle Automatic Storage Management (Oracle ASM) instance.
- ASMCMD-08002: entry 'string' does not exist in directory 'string'
-
Cause: The specified path contained elements that did not exist.
- ASMCMD-08003: command disallowed by current instance type
-
Cause: ASMCMD was connected to an instance with an instance type other than Oracle Automatic Storage Management (Oracle ASM).
- ASMCMD-08004: Oracle ASM file path 'string' contains an invalid alias name
-
Cause: The path specified contained an invalid alias name.
- ASMCMD-08005: directory 'string' is ambiguous
-
Cause: The directory on which the command was executed translated to multiple matches.
- ASMCMD-08006: entry 'string' does not refer to an existing directory
-
Cause: The 'cd' command failed as the specified path did not exist.
- ASMCMD-08007: unclosed single quotation mark
-
Cause: The input did not contain a closing single quotation mark.
- ASMCMD-08008: both source 'string' and target 'string' cannot be from remote instances
-
Cause: The 'copy' command specified both source and target files that were on remote instances.
- ASMCMD-08009: more than one source file specified, one of which is remote
-
Cause: The 'copy' command specified multiple source files, at least one of which was remote.
- ASMCMD-08010: user name is not specified in remote instance connect string 'string'
-
Cause: The user name was not specified in the remote instance connect string.
- ASMCMD-08011: instance identifier is not specified in the remote instance connect string 'string'
-
Cause: An instance identifier was not specified in the remote instance connect string.
- ASMCMD-08012: cannot determine file type for file
-
Cause: The file type was incompatible with the copy operation.
- ASMCMD-08013: cannot determine logical block size for file 'string'
-
Cause: During the copy operation, the logical block size of the indicated file could not be determined. The file is corrupted or it is an internal error.
- ASMCMD-08014: file 'string' does not exist
-
Cause: The file specified did not exist.
- ASMCMD-08015: child 'string' cannot be on remote instance
-
Cause: The 'setsparseparent' command specified a child file that was on a remote instance.
- ASMCMD-08016: copy source 'string' and target 'string' failed
-
Cause: The 'copy' command was not successful.
- ASMCMD-08017: setting parent of child 'string' to new parent 'string' failed
-
Cause: The 'setsparseparent' command was not successful.
- ASMCMD-08018: more than one child file specified, one of which is remote
-
Cause: The 'setsparseparent' command specified multiple child files, at least one of which was remote.
- ASMCMD-08019: parent 'string' cannot be on remote instance
-
Cause: The 'setsparseparent' command specified a parent file that was on a remote instance.
- ASMCMD-08020: could not write into trace file
-
Cause: Writing to the trace file failed.
- ASMCMD-08021: password cannot contain the following characters $%%^&*()'" or tab
-
Cause: Invalid characters were found in the specified password.
- ASMCMD-08022: unknown command 'string' specified
-
Cause: An unknown command was specified.
- ASMCMD-08023: copying password file using Oracle ASM requires software version 'string' or later on host 'string'
-
Cause: A request to copy a password file was issued to an Oracle Automatic Storage Management (Oracle ASM) instance whose version did not support that operation.
- ASMCMD-08024: file number could not be determined for alias name 'string'
-
Cause: The attempt to determine the file number for the specified alias was unsuccessful.
- ASMCMD-08025: Invalid file name specified. Absolute path name is required when there is no connection to Oracle ASM instance.
-
Cause: The specified file name did not begin with '+'. It is therefore treated as a relative path name which requires a connection to Oracle Automatic Storage Management.
- ASMCMD-08026: Password file 'string' is in use. Use the force option.
-
Cause: A password file was specified, but it is used by other resources.
- ASMCMD-08027: Password file 'string' already exists. Use the force option to overwrite.
-
Cause: An attempt to create a password file failed because it already existed.
- ASMCMD-08028: Password file 'string' is associated with 'string' already. Use the force option.
-
Cause: A password file was specified for a CRS resource, which already has a password file associated with it.
- ASMCMD-08029: Cannot change diskgroup redundancy from 'string' to 'string'
-
Cause: The disk group redundancy must be either NORMAL or HIGH to perform this operation.
- ASMCMD-08030: file 'string' specified with 'sparse_merge_end' cannot be on remote instance
-
Cause: The 'copy' command with the 'sparse_merge_end' option specified a file that was on a remote instance.
- ASMCMD-08031: more than one file specified with 'sparse_merge_begin' option
-
Cause: The 'copy' command specified multiple files with the 'sparse_merge_begin' option.
- ASMCMD-08032: target 'string' cannot be on remote instance
-
Cause: The 'copy' command with the 'sparse_merge_begin' and 'sparse_merge_end' options specified a target file that was on a remote instance.
- ASMCMD-08033: failure merging sparse files 'string' through 'string' to target 'string'
-
Cause: The 'copy' command with the 'sparse_merge_begin' and 'sparse_merge_end' options was not successful.
- ASMCMD-08034: sparse merge copy operation failure due to incorrect command syntax
-
Cause: The 'copy' command with the 'sparse_merge_begin' and 'sparse_merge_end' options was not successful due to incorrect command syntax.
- ASMCMD-08035: file specified with sparse_merge_begin and sparse_merge_end are the same - 'string'
-
Cause: The 'copy' command specified same files for both the 'sparse_merge_begin' and 'sparse_merge_end' options.
- ASMCMD-08036: file 'string' specified with 'sparse_merge_begin' cannot be on remote instance
-
Cause: The 'copy' command with the 'sparse_merge_begin' option specified a file that was on a remote instance.
- ASMCMD-08037: invalid system alias root path name 'string'
-
Cause: An invalid system alias root path name was specified.
- ASMCMD-08038: invalid path to ASM system file name 'string'
-
Cause: An invalid file path to an ASM system file name was specified.
- ASMCMD-08102: no connection to Oracle ASM; command requires Oracle ASM to run
-
Cause: A command that requires Oracle Automatic Storage Management (Oracle ASM) processing was issued but there was no connection to an Oracle ASM instance.
- ASMCMD-08103: failed to connect to ASM; ASMCMD running in non-connected mode, ORACLE_SID='%0!s'
-
Cause: An attempt to connect to Oracle Automatic Storage Management (Oracle ASM) was made using ORACLE_SID='%0!s' but the connection failed.
- ASMCMD-08201: Oracle ASM not available\n string
-
Cause: During a copy operation, connection to the Oracle Automatic Storage Management (Oracle ASM) instance on the remote node failed.
- ASMCMD-08202: internal error: string
-
Cause: There was an internal error.
- ASMCMD-08303: invalid SPFILE 'string'
-
Cause: The specified server parameter file did not have a valid file type, a valid file size, or a valid block size.
- ASMCMD-08305: GPNPTOOL executable not found at 'string'
-
Cause: The GPNPTOOL executable was not found at the indicated location.
- ASMCMD-08306: could not edit the GPnP profile
-
Cause: A 'gpnptool edit' command failed.
- ASMCMD-08307: could not sign the GPnP profile
-
Cause: A 'gpnptool sign' command failed.
- ASMCMD-08308: -f option cannot be used when Oracle Clusterware stack is up
-
Cause: The force option was supplied when the Oracle Clusterware stack was up.
- ASMCMD-08309: could not check the status of cluster
-
Cause: The command 'crsctl check css' failed.
- ASMCMD-08310: could not get the GPnP profile sequence number
-
Cause: An error occurred while retrieving the sequence number of the GPnP profile.
- ASMCMD-08313: CRSCTL executable not found at 'string'
-
Cause: The CRSCTL executable was not found at the indicated location.
- ASMCMD-08314: could not set the disk string
-
Cause: The command 'srvctl modify asm -d diskstring' failed.
- ASMCMD-08315: could not determine the mode in which Oracle Clusterware is running
-
Cause: The command 'crsctl status resource ora.crsd -init -g' failed.
- ASMCMD-08316: SRVCTL executable not found at 'string'
-
Cause: The SRVCTL executable was not found at the indicated location.
- ASMCMD-08317: could not get the Oracle ASM disk string
-
Cause: The command 'srvctl config asm' to get the Oracle Automatic Storage Management (Oracle ASM) disk string failed.
- ASMCMD-08318: environment variable 'string' not set
-
Cause: The environment variable HOSTNAME was not set before running this command.
- ASMCMD-08319: could not locate the GPnP profile
-
Cause: The Grid Plug and Play (GPnP) profile did not exist.
- ASMCMD-08402: operation was not performed on the file string
-
Cause: Altering the diskgroup to change the owner, group, or permissions failed.
- ASMCMD-08406: cannot accept null password
-
Cause: A null password was passed.
- ASMCMD-08409: 'chmod' operation not allowed for string
-
Cause: A 'chmod' command specified the write-only permission.
- ASMCMD-08552: invalid diskgroup name 'string'
-
Cause: An invalid diskgroup name was specified.
- ASMCMD-08554: invalid volume name 'string'
-
Cause: An invalid volume name was specified.
- ASMCMD-08557: diskgroup 'string' volume 'string' not found
-
Cause: The specified diskgroup or volume was not found.
- ASMCMD-08558: invalid size multiplier specified
-
Cause: An invalid size multiplier was specified.
- ASMCMD-08559: invalid size specified
-
Cause: The size specified contained a valid size multiplier but contained other non-numeric characters.
- ASMCMD-08601: could not create the analyze directory
-
Cause: An internally issued 'mkdir' command failed to create the analyze directory.
- ASMCMD-08602: time stamp format is not recognized
-
Cause: The format for time stamp was invalid.
- ASMCMD-08603: invalid value specified for 'tracedirectory'
-
Cause: The specified trace directory did not exist.
- ASMCMD-08604: Start time is later than end time. Please specify end time later than start time.
-
Cause: Inconsistent values for --startime and --endtime options.
- ASMCMD-08605: cannot read the event list file.\n
-
Cause: The event list file did not exist or could not be read
- ASMCMD-08608: invalid value for 'string' option: string
-
Cause: The provided value was not valid for the specified option.
- ASMCMD-08609: file group 'string' does not exist
-
Cause: The specified file group name did not exist.
- ASMCMD-08610: cannot access 'string', no such XML file
-
Cause: The specified file did not exist.
- ASMCMD-08611: cannot read 'string', permission denied
-
Cause: The permission to read the specified file or directory was not granted.
- ASMCMD-08612: failed to create member cluster 'string' because plugging in the GIMR PDB from a directory requires configuring the GIMR component
-
Cause: An attempt to configure the indicated member cluster failed because the Grid Infrastructure Management Repository (GIMR) component was not specified.
- ASMCMD-09345: could not open intermediate file 'string'\n
-
Cause: During Oracle Automatic Storage Management (Oracle ASM) metadata backup operation, an attempt to open the intermediate file failed.
- ASMCMD-09347: invalid intermediate file 'string'
-
Cause: The intermediate file did not begin with string '@diskgroup_set' or there was an error while evaluating the file contents.
- ASMCMD-09349: diskgroup 'string' not discovered by Oracle ASM instance; skipping...
-
Cause: A non-existent diskgroup was specified during execution of the 'md_backup' command.
- ASMCMD-09350: diskgroup 'string' not mounted by Oracle ASM instance; skipping...
-
Cause: The diskgroup specified was not mounted in an Oracle Automatic Storage Management (Oracle ASM) instance.
- ASMCMD-09351: Oracle ASM instance has no diskgroup mounted
-
Cause: Oracle Automatic Storage Management (Oracle ASM) instance had no diskgroups mounted.
- ASMCMD-09352: CREATE DISKGROUP failed\nstring
-
Cause: SQL command execution failed.
- ASMCMD-09353: ADD or ALTER TEMPLATE failed\nstring
-
Cause: SQL command execution failed.
- ASMCMD-09354: ADD ALIAS failed\nstring
-
Cause: SQL command execution failed.
- ASMCMD-09355: could not find information for diskgroup 'string' in backup file
-
Cause: Information about the diskgroup specified was not present in the backup file.
- ASMCMD-09356: backup file 'string' is either empty or cannot be interpreted
-
Cause: Incorrect backup file was specified.
- ASMCMD-09357: file with name 'string' already exists
-
Cause: The specified file already exists.
- ASMCMD-09358: source and target files are the same - 'string'
-
Cause: The source and target file were the same.
- ASMCMD-09359: invalid diskgroup name 'string' specified in override options
-
Cause: The old diskgroup name specified in the override options was not found in the backup file.
- ASMCMD-09360: ADD or ALTER ATTRIBUTE failed\nstring
-
Cause: SQL command execution failed.
- ASMCMD-09361: backup version not supported\nstring
-
Cause: The COMPATIBLE.ASM value of the diskgroup in the backup file was greater than the Oracle Automatic Storage Management (Oracle ASM) instance version executing the command.
- ASMCMD-09362: ADD or ALTER VOLUME failed\nstring
-
Cause: SQL command execution failed.
- ASMCMD-09363: disk group containing auxiliary volume not found
-
Cause: Disk recovery log did not exist.
- ASMCMD-09364: volume device for VOLUME: 'string' in DG: 'string' does not exist
-
Cause: Volume was not restored or was not listed for restore.
- ASMCMD-09365: failed to make file system\nstring
-
Cause: The command execution failed.
- ASMCMD-09366: invalid user name 'string' specified for string
-
Cause: The specified user name did not exist on the host.
- ASMCMD-09367: invalid group name 'string' specified for string
-
Cause: The specified group name did not exist on the host.
- ASMCMD-09368: ACFS is not loaded
-
Cause: ACFS was not loaded.
- ASMCMD-09369: Could not open file 'string'
-
Cause: During Oracle Automatic Storage Management (Oracle ASM) metadata scan operation, an attempt to open the output file failed.
- ASMCMD-09370: cannot read the Oracle ACFS list file
-
Cause: The Oracle Automatic Storage Management Cluster File System (Oracle ACFS) list file did not exist or could not be read.
- ASMCMD-09371: disk 'string' does not exist in diskgroup 'string'
-
Cause: The disk specified was not part of the diskgroup.
- ASMCMD-09372: physical blocks string-string do not map to a valid Oracle ASM file
-
Cause: The physical blocks specified were not part of any Oracle Automatic Storage Management (Oracle ASM) file.
- ASMCMD-09373: not all physical blocks submitted for remapping
-
Cause: An attempt to submit all of the physical blocks for remapping failed.
- ASMCMD-09374: KFED executable not found at 'string'
-
Cause: The KFED executable was not found at the indicated location.
- ASMCMD-09375: error occurred when executing\n string\n\nstring
-
Cause: The 'lsdsk' command was not successful.
- ASMCMD-09378: scanning of disk headers is supported on UNIX platforms only
-
Cause: The 'lsdsk' command failed because scanning of disk headers is supported on UNIX platforms only.
- ASMCMD-09381: 'remap' command requires Oracle ASM software version string or later.
-
Cause: The Oracle Automatic Storage Management (Oracle ASM) instance did not support the 'remap' command.
- ASMCMD-09382: physical blocks string-string map to an unmirrored file
-
Cause: Oracle Automatic Storage Management (Oracle ASM) couldnot remap an unmirrored file.
- ASMCMD-09383: 'mapextent' command requires Oracle ASM software version string or later
-
Cause: The Oracle Automatic Storage Management (Oracle ASM) instance did not support the 'mapextent' command.
- ASMCMD-09384: 'mapau' command requires Oracle ASM software version string or later
-
Cause: The current Oracle Automatic Storage Management (Oracle ASM) version did not support this command.
- ASMCMD-09385: 'lsblk' command requires Oracle ASM software version string or later
-
Cause: The current version of Oracle Automatic Storage Management (Oracle ASM) instance did not support this command.
- ASMCMD-09386: 'chblk' command requires Oracle ASM software version string or later
-
Cause: The current version of Oracle Automatic Storage Management (Oracle ASM) instance did not support this command.
- ASMCMD-09390: invalid XML tag 'string'
-
Cause: An invalid XML tag was specified.
- ASMCMD-09391: invalid XML file
-
Cause: Certain parameters were not defined or had invalid values in the file.
- ASMCMD-09392: provided XML file cannot be read
-
Cause: The provided XML file could not be read.
- ASMCMD-09395: error parsing XML file: string
-
Cause: An error occurred while parsing the XML file.
- ASMCMD-09398: element string is empty
-
Cause: No disks were found in the element.
- ASMCMD-09399: argument 'string' is not a valid number
-
Cause: A numeric value was expected in the argument.
- ASMCMD-09401: command syntax error
-
Cause: Incorrect command syntax was specified.
- ASMCMD-09412: Invalid option: string
-
Cause: An invalid option was specified.
- ASMCMD-09450: missing '--dbuniquename' or '--asm' option for password file located on a diskgroup
-
Cause: When trying to update the CRSD resource for a password file located on a diskgroup, the '--dbuniquename' parameter or the '--asm' option was not specified.
- ASMCMD-09451: 'orapwd' executable was not found at 'string'
-
Cause: 'orapwd' executable was not found at the location.
- ASMCMD-09452: The password file was not found at 'string' or the path specified does not exist.
-
Cause: The password file could not be located at the specified path or the path to the password file did not exist.
- ASMCMD-09453: failed to register password file as a CRS resource
-
Cause: An internally issued 'srvctl' command to register the password file as a CRS resource failed.
- ASMCMD-09454: could not create new password file
-
Cause: An internally issued 'orapwd' command to create the password file failed.
- ASMCMD-09455: location for the new password file was not valid
-
Cause: An invalid path was specified to create the password file. ASMCMD can be used to create password files only on disk groups.
- ASMCMD-09456: password file should be located on an ASM disk group
-
Cause: An invalid path for the password file was specified. The password file should be located on an ASM disk group.
- ASMCMD-09457: an internally issued srvctl command failed with errors
-
Cause: An internally issued 'srvctl' command failed. The location of the password file could not be retrieved from the Cluster Ready Services (CRS) resource.
- ASMCMD-09458: user tried to move a password file within Operating System file system
-
Cause: ASMCMD 'pwmove' or 'pwcopy' was used to move a password file to a different location on an Operating Systen file system. This action is not supported by the command.
- ASMCMD-09459: user tried to move or copy a password file within the same disk group
-
Cause: ASMCMD 'pwmove' or 'pwcopy' command was used to move or copy a password file within the same disk group. This action is not supported by the command.
- ASMCMD-09460: ASMCMD 'string' command was used on a file which is not a password file
-
Cause: This particular ASMCMD command was used on a file which is not a password file. This command supports only operations on password files.
- ASMCMD-09461: invalid password file 'string'
-
Cause: The specified password file did not have a valid file type, a valid file size, or a valid block size.
- ASMCMD-09462: could not delete password file
-
Cause: An internally issued 'orapwd' command to delete the password file failed.
- ASMCMD-09463: operation failed due to lack of write permissions
-
Cause: An ASMCMD command failed because the user lacks write permissions necessary for the operation. Either the target directory or file does not have write permissions or the target already exists and cannot be overwritten.
- ASMCMD-09464: invalid format for password file
-
Cause: The specified format for the password file was not valid.
- ASMCMD-09470: ASM proxy instance unavailable
-
Cause: An ASM proxy instance was detected but was not ONLINE.
- ASMCMD-09471: cannot enable or disable volumes
-
Cause: Could not communicate with the ASM proxy.
- ASMCMD-09472: failed to connect to the ASM proxy
-
Cause: An ONLINE ASM proxy was detected but the connection failed.
- ASMCMD-09473: volume STATE will show as REMOTE
-
Cause: An ASM proxy instance was detected but was not ONLINE. An Oracle Flex ASM instance cannot display the volume state.
- ASMCMD-09474: volume statistics cannot be queried
-
Cause: An ASM proxy instance was detected but was not ONLINE. An Oracle Flex ASM instance cannot display the volume statistics.
- ASMCMD-09475: ASM proxy SID not found
-
Cause: An ONLINE ASM proxy was found but the SID could not be determined.
- ASMCMD-09476: failed to create the Cluster Manifest File for member cluster 'string'
-
Cause: Creation of the Cluster Manifest File for the member cluster failed.
- ASMCMD-09477: delete member cluster 'string' failed
-
Cause: Deletion of the member cluster failed.
- ASMCMD-09478: Create or delete member cluster 'string' failed because the Domain Services Cluster is in 'string' state.
-
Cause: An attempt to configure or deconfigure the indicated member cluster was rejected because the Domain Services Cluster was in the middle of upgrading or patching.
- ASMCMD-09479: invalid GUID 'string' specified
-
Cause: The operation was rejected because the supplied Globally Unique Identifier (GUID) was syntactically invalid.
- ASMCMD-09480: There are too many connection strings for Oracle Flex ASM.
-
Cause: While fetching connection strings for Oracle Flex ASM, there were too many connection strings.
- ASMCMD-09481: There are no connection strings available for Oracle Flex ASM.
-
Cause: While fetching connection strings for Oracle Flex ASM, there were no connection strings available.
- ASMCMD-09482: Unknown error happened while fetching connection strings for FlexASM
-
Cause: While fetching connection string for FlexASM, unknown error reported.
- ASMCMD-09485: Operations on the ASM SPFILE require the SYSASM privilege.
-
Cause: An attempt to modify the ASM SPFILE was made without the SYSASM privilege.
- ASMCMD-09487: 'string' cannot be run with 'string' privilege
-
Cause: Command was executed with lower privilege
- ASMCMD-09488: operations on member cluster require SYSASM privilege
-
Cause: An attempt was made to create or delete a member cluster without the SYSASM privilege.
- ASMCMD-09490: member cluster 'string' is not configured
-
Cause: The specified member cluster was not configured.
- ASMCMD-09491: failed to list the configured member clusters
-
Cause: A failure occurred while attempting to display the member cluster configuration. The accompanying error message provides the details.
- ASMCMD-09492: The configuration for member cluster 'string' is inconsistent between components 'string' and 'string'.
-
Cause: There were multiple member clusters identified by the indicated name with mismatched versions or GUIDs.
- ASMCMD-09493: The 'string' feature is not supported on this operating system.
-
Cause: The command was rejected because the indicated feature is not supported on this operating system.
- ASMCMD-09494: failed to create component 'string' credentials for member cluster 'string'
-
Cause: A failure occurred while attempting to create credentials for the member cluster.
- ASMCMD-09495: Directory 'string' does not exist.
-
Cause: An attempt was made to access a nonexistent directory."
- ASMCMD-09496: The Cluster Manifest File 'string' does not contain any components.
-
Cause: A Cluster Manifest File that does not contain any components was provided.
- ASMCMD-09497: File 'string' is not a Cluster Manifest File.
-
Cause: The file provided was not a Cluster Manifest File.
- ASMCMD-09498: The command is only supported on the Domain Services Cluster.
-
Cause: An attempt was made to run a command that is only supported on the Domain Services Cluster.
- ASMCMD-09499: invalid member cluster version 'string'
-
Cause: An attempt to create a configuration for a member cluster failed because an invalid cluster version was provided for the cluster.
- ASMCMD-09500: member cluster version 'string' is incompatible with Domain Services Cluster version 'string'
-
Cause: The specified member cluster version was not supported by the Domain Services Cluster.
- ASMCMD-09501: Clear timestamp for OS trail type requires RAC instance number
-
Cause: There was no RAC instance number specified to clear timestamp for OS trailtype
- ASMCMD-09502: Set timestamp for OS trail type requires RAC instance number
-
Cause: RAC instance number was not specified while OS trail type was specified.
- ASMCMD-09511: failed to obtain required AFD disk string from Oracle Local Repository
-
Cause: The AFD disk string required for this operation could not be retrieved from the Oracle Local Repository (OLR).
- ASMCMD-09512: failed to update AFD disk string in Oracle Local Repository.
-
Cause: An error occurred while setting AFD disk string.
- ASMCMD-09513: ASM disk label set operation failed.\n
-
Cause: An error occurred while setting the ASM label.
- ASMCMD-09514: ASM disk label clear operation failed.\n
-
Cause: An error occurred while clearing the ASM label.
- ASMCMD-09515: KFOD executable not found at 'string'
-
Cause: The KFOD executable was not found at the indicated location.
- ASMCMD-09516: AFDTOOL executable not found at 'string'
-
Cause: The AFDTOOL executable was not found at the indicated location.
- ASMCMD-09517: AFDROOT executable not found at 'string'
-
Cause: The AFDROOT executable was not found at the indicated location.
- ASMCMD-09518: AFDDRIVERSTATE executable not found at 'string'
-
Cause: The AFDDRIVERSTATE executable was not found at the indicated location.
- ASMCMD-09519: ASMLib is present with ASM disk string 'string'; command requires default ASM disk string
-
Cause: An attempt was made to configure AFD when ASMLib was present. To configure AFD when ASMLib is present, the ASM disk string needs to be a default string. Otherwise, when the Oracle Clusterware stack is restarted, the AFD devices cannot be discovered.
- ASMCMD-09520: AFD is not 'string'
-
Cause: The Oracle ASM Filter Driver (AFD) was either not supported, not installed, or not loaded.
- ASMCMD-09521: AFD is already configured
-
Cause: AFD was already configured and loaded on the node.
- ASMCMD-09522: Insufficient permission to execute the command. Require privileged user
-
Cause: A non-privileged user attempted to execute a command requiring privileges.
- ASMCMD-09523: command cannot be used when Oracle Clusterware stack is up
-
Cause: The command was executed when the Oracle Clusterware stack was up.
- ASMCMD-09524: AFD configuration failed 'string'
-
Cause: The afd_configure command was not successful.
- ASMCMD-09525: AFD deconfiguration failed 'string'
-
Cause: The afd_deconfigure command was not successful.
- ASMCMD-09526: The AFD state is 'string' and filtering is 'string' on host 'string'
-
Cause: User requested to retrieve the status of AFD on the node.
- ASMCMD-09527: AFD is loaded, but resource ora.driver.afd does not exist
-
Cause: The command was executed with AFD loaded on the node but its OHASD resource ora.driver.afd did not exist.
- ASMCMD-09528: disk 'string' does not exist
-
Cause: The disk specified did not exist.
- ASMCMD-09529: The executable 'string' is either not found or non-executable in the\nlocation(s) string
-
Cause: The executable file is either not found or non executable in the specified location(s). It must be available in any one of the specified location(s).
- ASMCMD-09530: The AFD state is 'string'
-
Cause: User requested to retrieve the status of AFD.
- ASMCMD-09531: External redundancy disk groups cannot contain sites.
-
Cause: The tag site was not compatible with the external redundancy disk groups.
- ASMCMD-09532: command cannot be used when Oracle Clusterware stack is down
-
Cause: The command was executed when the Oracle Clusterware stack was down.
- ASMCMD-09533: resource ora.driver.afd does not exist
-
Cause: The command was executed when OHASD resource ora.driver.afd did not exist.
- ASMCMD-09534: Discovery string is not provided.
-
Cause: The discovery string was not provided and the stamp operation was not permitted.
- ASMCMD-09535: Failure group label is not provided.
-
Cause: An attempt was made to stamp a site label without providing a failure group label.
- ASMCMD-09536: The site label 'string' is invalid.
-
Cause: An invalid site label was supplied.
- ASMCMD-09537: The failure group label 'string' is invalid.
-
Cause: An invalid failure group label was supplied.
- ASMCMD-09538: The disk label 'string' is invalid.
-
Cause: An invalid disk label was supplied.
- ASMCMD-09539: No disks were discovered using the string 'string'.
-
Cause: The supplied discovery string did not match any disk.
- ASMCMD-09540: Disks are managed by AFD or ASMLIB.
-
Cause: An attempt was made to stamp the disk label on disks that are managed by Oracle ASM Filter Driver (AFD) or ASMLIB."
- ASMCMD-09541: Disk string belongs to mounted disk group string.
-
Cause: An attempt was made to stamp a disk that belongs to a mounted disk group.
- ASMCMD-09542: Disk string is member of disk group string and ASMCMD is not connected to an instance.
-
Cause: An attempt was made to stamp a disk that is a member of an ASM disk group, and ASMCMD was not connected to an ASM instance to verify if that disk group was mounted.
- ASMCMD-09543: cannot rename the site and the failgroup for a disk
-
Cause: An attempt was made to rename the site and the failgroup for a disk. The operation was not permitted because these options are mutually exclusive, since the failgroup can be renamed only if the disk group redundancy is external and the site cannot be renamed if the disk group redundancy is external.
- ASMCMD-09544: The command is not supported on a member cluster.
-
Cause: An attempt was made to run a command that was not supported on a member cluster.
- ASMCMD-09545: The installed AFD drivers are not correct for this operating system.
-
Cause: A request to retrieve the status of Oracle ASM Filter Driver (AFD) was made. The installed AFD drivers and the current running operating system were not compatible.
- ASMCMD-09546: Insufficient permission to execute the command. The command requires an Oracle Grid Infrastructure user.
-
Cause: An attempt was made to execute a command by a user who was not an Oracle Grid Infrastructure user.
- ASMCMD-09601: Member Cluster creation failed because the access mode specified is invalid.
-
Cause: An invalid access mode was supplied in an attempt to create a Member Cluster for Oracle Database Appliance.