ORA-15124: ASM file name string contains an invalid alias name

ORA-15124: ASM file name string contains an invalid alias name

Cause: A file name was specified which did not contain a valid ASM alias name. The ASM alias name, if present, follows immediately after the diskgroup name, in place of the ASM file number. It must be preceeded by a slash, start with an alphabetic character, and consist of up to 48 characters which are alphabetic, numeric, or the characters $ , _ , - , or # . A space can separate two parts of an alias name.

Action: Correct the file name specification.

ORA-15123: ASM file name string contains an invalid incarnation number

ORA-15123: ASM file name string contains an invalid incarnation number

Cause: A numeric file name was specified which did not contain a valid ASM incarnation number. The ASM incarnation number follows immediately after the ASM file number. It must be preceeded by a . character, and contain only numeric characters.

Action: Correct the file name specification.

ORA-15122: ASM file name string contains an invalid file number

ORA-15122: ASM file name string contains an invalid file number

Cause: A numeric file name was specified which did not contain a valid ASM file number. The ASM file number follows immediately after the diskgroup name. It must be preceeded by a . character, and contain only numeric characters.

Action: Correct the file name specification.

ORA-15121: ASM file name string contains an invalid diskgroup name

ORA-15121: ASM file name string contains an invalid diskgroup name

Cause: A file name was specified that did not contain a valid diskgroup name. The diskgroup name follows immediately after the ASM prefix character. It must start with an alphabetic character, and consist of up to 30 characters which are alphabetic, numeric, or the characters $ and _ .

Action: Correct the file name specification.

ORA-15120: ASM file name string does not begin with the ASM prefix character

ORA-15120: ASM file name string does not begin with the ASM prefix character

Cause: A file name was specified to ASM which did not begin with the ASM prefix character (currently + ). ASM uses the prefix to determine that a file specification is in fact an ASM file.

Action: Correct the file name specification.

ORA-15117: command only operates on one diskgroup

ORA-15117: command only operates on one diskgroup

Cause: An ALTER DISKGROUP, CREATE DISKGROUP, or DROP DISKGROUP command specified a list of diskgroups or the keyword ALL in a context where only a single diskgroup was permitted.

Action: Issue separate ALTER DISKGROUP, CREATE DISKGROUP, or DROP DISKGROUP commands to accomplish the desired action.

ORA-15116: invalid combination of ALTER DISKGROUP options

ORA-15116: invalid combination of ALTER DISKGROUP options

Cause: The ALTER DISKGROUP options may not be combined in this manner.

Action: Issue separate ALTER DISKGROUP commands to accomplish the desired action.

ORA-15115: missing or invalid ASM disk size specifier

ORA-15115: missing or invalid ASM disk size specifier

Cause: The command did not specify a valid ASM disk size.

Action: Specify a valid ASM disk size.

ORA-15114: missing or invalid ASM file name

ORA-15114: missing or invalid ASM file name

Cause: The command did not specify a valid ASM file name identifier.

Action: Specify a valid ASM file name identifier.

ORA-15113: alias name string refers to a directory

ORA-15113: alias name string refers to a directory

Cause: The name specified referred to a directory in the alias directory and not a valid alias entry.

Action: Check the alias name and retry.

ORA-15112: No diskgroups are currently mounted.

ORA-15112: No diskgroups are currently mounted.

Cause: An ALTER DISKGROUP ALL command did not find any mounted diskgroups upon which to operate. Either instance shutdown or an ALTER DISKGROUP ALL DISMOUNT command did not dismount any diskgroups, or an ALTER DISKGROUP ALL UNDROP DISKS command did not undrop any disks.

Action: Mount the diskgroups on which you wish to operate or ignore the error.

ORA-15111: conflicting or duplicate STRIPE options

ORA-15111: conflicting or duplicate STRIPE options

Cause: The command contained both a FINE and COARSE keyword, or contained the FINE keyword more than once, or contained the COARSE keyword more than once.

Action: Specify only one keyword.

ORA-15110: no diskgroups mounted

ORA-15110: no diskgroups mounted

Cause: No diskgroups were specified in the ASM_DISKGROUPS parameter, so instance startup or the ALTER DISKGROUP ALL MOUNT command did not mount any diskgroups.

Action: Specify valid diskgroups in the ASM_DISKGROUPS parameter or ignore the error.

ORA-15109: conflicting protection attributes specified

ORA-15109: conflicting protection attributes specified

Cause: The command contained an invalid combination of the UNPROTECTED, MIRROR, or PARITY keywords.

Action: Specify only one keyword.

ORA-15108: missing or invalid template name

ORA-15108: missing or invalid template name

Cause: The command did not specify a valid template name identifier.

Action: Specify a valid template name identifier.

ORA-15107: missing or invalid ASM disk name

ORA-15107: missing or invalid ASM disk name

Cause: The command did not specify a valid ASM disk name identifier.

Action: Specify a valid ASM disk name identifier.

ORA-15106: missing or invalid operating system disk locator string

ORA-15106: missing or invalid operating system disk locator string

Cause: The command did not specify a valid operating system path for the device as a string.

Action: Specify a valid operating system path for the device.

ORA-15105: missing or invalid FAILGROUP name

ORA-15105: missing or invalid FAILGROUP name

Cause: The command did not specify a valid failure group name.

Action: Specify a valid failure group name.

ORA-15104: conflicting CONTENTS options

ORA-15104: conflicting CONTENTS options

Cause: The command specified conflicting or duplicate INCLUDING CONTENTS or EXCLUDING CONTENTS options.

Action: Specify only one option.

ORA-15103: conflicting or duplicate REPAIR options

ORA-15103: conflicting or duplicate REPAIR options

Cause: The command specified conflicting or duplicate REPAIR keywords.

Action: Specify only one REPAIR action.

ORA-15102: invalid POWER expression

ORA-15102: invalid POWER expression

Cause: The syntax of the POWER expression was invalid.

Action: Specify a valid POWER expression.

ORA-15101: no action specified

ORA-15101: no action specified

Cause: The ALTER DISKGROUP command did not specify any alterations.

Action: Specify at least one operation clause.

ORA-15100: invalid or missing diskgroup name

ORA-15100: invalid or missing diskgroup name

Cause: The command did not specify a valid diskgroup name.

Action: Specify a valid diskgroup name.

ORA-15097: cannot SHUTDOWN ASM instance with connected RDBMS instance

ORA-15097: cannot SHUTDOWN ASM instance with connected RDBMS instance

Cause: A SHUTDOWN command was issued to an ASM instance that had one or more connected RDBMS instances.

Action: Connect to each RDBMS instance and shut it down, and then reissue the SHUTDOWN command to the ASM instance. Alternatively, use the SHUTDOWN ABORT command. Note that issuing the SHUTDOWN ABORT command to an ASM instance results in abormal termination of all RDBMS instances connected to that ASM instance.

ORA-15096: lost disk write detected

ORA-15096: lost disk write detected

Cause: A failure either by disk hardware or disk software caused a disk write to to be lost, even though ASM received acknowledgement that the write completed. Alternatively, a clustering hardware failure or a clustering software failure resulted in an ASM instance believing that another ASM instance had crashed, when in fact it was still active.

Action: The disk group is corrupt and cannot be recovered. The disk group must be recreated, and its contents restored from backups.

ORA-15095: reached maximum ASM file size (string GB)

ORA-15095: reached maximum ASM file size (string GB)

Cause: An ASM file creation or file resize operation exceeded the maximum file size permitted by ASM.

Action: Use smaller files.

ORA-15094: attempted to write to file opened in read only mode

ORA-15094: attempted to write to file opened in read only mode

Cause: The file handle passed to DBMS_DISKGROUP.WRITE() did not have write privileges.

Action: Obtain a file handle in read-write mode and retry the write operation.

ORA-15093: buffer only contains string bytes, I or O requested is string bytes

ORA-15093: buffer only contains string bytes, I or O requested is string bytes

Cause: The buffer supplied for write was too small to satisfy the request.

Action: Correct the error and retry the operation.

ORA-15092: I or O request size string is not a multiple of logical block size string

ORA-15092: I or O request size string is not a multiple of logical block size string

Cause: The length of the request was not a multiple of logical block size.

Action: Correct the error and retry the operation.

ORA-15091: operation incompatible with open handle in this session

ORA-15091: operation incompatible with open handle in this session

Cause: The current session contained an open handle from the DBMS_ DISKGROUP PL or SQL package which precluded performing the command.

Action: Close the hanlde with DBMS_DISKGROUP.CLOSE() before executing the command, or execute the command in a different session.

ORA-15090: handle string is not a valid descriptor

ORA-15090: handle string is not a valid descriptor

Cause: The file handle was not valid in this session.

Action: Submit a handle obtained from a successful call to DBMS_ DISKGROUP.OPEN().

ORA-15083: failed to communicate with ASMB background process

ORA-15083: failed to communicate with ASMB background process

Cause: A database instance failed to communicate with its ASMB background process when attempting to access an ASM file.

Action: Check the alert log for more information on the reason for the failure.

ORA-15082: ASM failed to communicate with database instance

ORA-15082: ASM failed to communicate with database instance

Cause: There was a failure when ASM tried to communicate with a database instance (most likely because the connection went down).

Action: Check the accompanying error messages for more information on the reason for the failure. Note that the ASM instances may return this error when a database instance is terminated abnormally.

ORA-15081: failed to submit an I or O operation to a disk

ORA-15081: failed to submit an I or O operation to a disk

Cause: A submission of an I or O operation to a disk has failed.

Action: Make sure that all the disks are operational.

ORA-15080: synchronous I or O operation to a disk failed

ORA-15080: synchronous I or O operation to a disk failed

Cause: A synchronous I or O operation invoked on a disk has failed.

Action: Make sure that all the disks are operational.

ORA-15079: ASM file is closed

ORA-15079: ASM file is closed

Cause: The file to which the I or O request was issued was closed. This could have been a consequence of the diskgroup being dismounted.

Action: Make sure the diskgroup is mounted and the file is open.

ORA-15078: ASM diskgroup was forcibly dismounted

ORA-15078: ASM diskgroup was forcibly dismounted

Cause: The diskgroup to which the I or O request was issued was forcibly dismounted (with the ALTER DISKGROUP DISMOUNT FORCE command) so that it could not be accessed.

Action: Mount the diskgroup to allow access again.

ORA-15077: could not locate ASM instance serving a required diskgroup

ORA-15077: could not locate ASM instance serving a required diskgroup

Cause: The instance failed to perform the specified operation because it could not locate a required ASM instance.

Action: Start an ASM instance and mount the required diskgroup.

ORA-15076: Emulating I or O errors on the OSM disk

ORA-15076: Emulating I or O errors on the OSM disk

Cause: The disk to which the I or O request was issued is in an error emulation mode.

Action: Bring the disk online for I or Os to get through.

ORA-15075: disk(s) are not visible cluster-wide

ORA-15075: disk(s) are not visible cluster-wide

Cause: An ALTER DISKGROUP ADD DISK command specified a disk that could not be discovered by one or more nodes in a RAC cluster configuration.

Action: Determine which disks are causing the problem from the GV$OSM_DISK fixed view. Check operating system permissions for the device and the storage sub-system configuration on each node in a RAC cluster that cannot identify the disk.

ORA-15074: diskgroup string requires rebalance completion

ORA-15074: diskgroup string requires rebalance completion

Cause: An attempt was made to repeatedly add or drop disks from a diskgroup. ASM could not perform the operation given the current state of the diskgroup.

Action: Manually invoke the ALTER DISKGROUP REBALANCE command and allow the rebalance to run to completion. Alternatively, invoke the ALTER DISKGROUP UNDROP DISKS command and allow the rebalance to run to completion. After the rebalance has completed, retry the operation.

ORA-15073: diskgroup string is mounted by another ASM instance

ORA-15073: diskgroup string is mounted by another ASM instance

Cause: An attempt was made to drop a diskgroup that is still mounted somewhere in the cluster by another instance.

Action: dismount the diskgroup from all nodes except the one performing the drop diskgroup command.

ORA-15072: command requires at least string failure groups, discovered only string

ORA-15072: command requires at least string failure groups, discovered only string

Cause: An attempt was made to create either a normal redundancy diskgroup for which fewer than two failure groups were both specified and discovered, or a high redundancy diskgroup for which fewer than three failure groups were both specified and discovered.

Action: Check the that the command does specify the required number of failure groups, and that all of the specified disks are discovered by ASM. A query of the V$ASM_DISK fixed view will show which disks are discovered by ASM.

ORA-15071: ASM disk string is already being dropped

ORA-15071: ASM disk string is already being dropped

Cause: An attempt was made to drop a disk from a diskgroup which was already in the process of being dropped from the diskgroup. Alternatively, an attempt was made to forcibly drop a disk from a diskgroup using the FORCE option which was already being forcibly dropped from the diskgroup.

Action: Check the ASM disk name and FORCE option as specified in the command.

ORA-15070: maximum number of files string exceeded in diskgroup string

ORA-15070: maximum number of files string exceeded in diskgroup string

Cause: The diskgroup ran out of space.

Action: Delete some existing ASM files or create files in a new diskgroup.

ORA-15069: ASM file string not accessible; timed out waiting for lock

ORA-15069: ASM file string not accessible; timed out waiting for lock

Cause: An attempt was made to access an ASM file, but the file is currently being created, resized, or deleted and therefore cannot be accessed.

Action: No action required, or try again later, after the create or resize has completed.

ORA-15068: maximum number of diskgroups string already mounted

ORA-15068: maximum number of diskgroups string already mounted

Cause: An attempt was made to mount more diskgroups than the instance is capable of mounting at one time.

Action: Dismount a mounted diskgroup and retry the command.

ORA-15067: command or option incompatible with diskgroup redundancy

ORA-15067: command or option incompatible with diskgroup redundancy

Cause: An attempt was made to use a feature which is not permitted by the diskgroup s redundancy policy. Common examples are forcibly dropping a disk from an EXTERNAL REDUNDANCY diskgroup, using the FAILGROUP clauses with an EXTERNAL REDUNDANCY diskgroup, or using invalid template attributes.

Action: Omit the option from the command.

ORA-15066: offlining disk string may result in a data loss

ORA-15066: offlining disk string may result in a data loss

Cause: Following I or O failures, the disks holding all copies of a data block were attempted to be taken offline.

Action: Check the accompanying error messages for more information on the reason for the disk I or O failures.

ORA-15065: hash collision for diskgroup names string and string

ORA-15065: hash collision for diskgroup names string and string

Cause: There was a collision in the group name used for the diskgroup. The diskgroup(s) cannot be mounted using colliding names.

Action: Use a different diskgroup name and also report to Oracle Support Services the two diskgroup names which collided.

ORA-15064: communication failure with ASM instance

ORA-15064: communication failure with ASM instance

Cause: There was a failure to communicate with the ASM instance, most likely because the connection went down.

Action: Check the accompanying error messages for more information on the reason for the failure. Note that database instances will always return this error when the ASM instance is terminated abnormally.

ORA-15063: ASM discovered an insufficient number of disks for diskgroup string

ORA-15063: ASM discovered an insufficient number of disks for diskgroup string

Cause: ASM was unable to find a sufficient number of disks belonging to the diskgroup to continue the operation.

Action: Check that the disks in the diskgroup are present and functioning, that the owner of the ORACLE binary has read or write permission to the disks, and that the ASM_DISKSTRING initialization parameter has been set correctly. Verify that ASM discovers the appropriate disks by querying V$ASM_DISK from the ASM instance.

ORA-15062: ASM disk is globally closed

ORA-15062: ASM disk is globally closed

Cause: The disk to which the I or O request was issued has gone offline or has been globally closed by the background process. Check other messages in the trace files for more information.

Action: Bring the disk online for I or Os to get through.

ORA-15061: ASM operation not supported (string(

ORA-15061: ASM operation not supported (string(

Cause: An ASM operation was attempted that is invalid or not supported by this version of the ASM instance.

Action: This is an internal error code that is used for maintaining compatibility between software versions and should never be visible to the user; contact Oracle support Services.

ORA-15060: template string does not exist

ORA-15060: template string does not exist

Cause: A command specified a template name, either directly or as part of an ASM file name, which did not exist.

Action: Check the template specifier in the command.

ORA-15059: invalid device type for ASM disk

ORA-15059: invalid device type for ASM disk

Cause: The device type of the discovered disk was not valid for use as an ASM disk.

Action: Check the file path and retry or exclude it from the discovery set. See the accompanying operating system error for additional information.

ORA-15058: disk string belongs to an incompatible diskgroup

ORA-15058: disk string belongs to an incompatible diskgroup

Cause: An attempt was made to ADD to a diskgroup a disk which was already part of another diskgroup. The other diskgroup was written by a more recent software release.

Action: Check the path specifier for the disk. If it is certain that the disk is not in use by another diskgroup, the FORCE option may be used to override this check.

ORA-15057: specified size of string MB is larger than actual size of string MB

ORA-15057: specified size of string MB is larger than actual size of string MB

Cause: A disk size expression exceeded the amount of storage actually availalable, as reported by the operating system.

Action: Specify a valid size.

ORA-15056: additional error message

ORA-15056: additional error message

Cause: An operating system error occured.

Action: Correct the operating system error and retry the operation.

ORA-15055: unable to connect to ASM instance

ORA-15055: unable to connect to ASM instance

Cause: When accessing a diskgroup for the first time, the database was unable to connect to the required ASM instance.

Action: Check the additional error messages. May need to configure correct ASM sid or make sure the database instance has OS privileges for ASM SYSDBA.