Oracle Database Errors or Warnings from Error ORA-15059 to ORA-15068
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-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-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-15062: ASM disk is globally closed
Cause: The disk to which the I/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/Os to get through.
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/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-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-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-15066: offlining disk “string” may result in a data loss
Cause: Following I/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/O failures.
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-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.
Above are list of Oracle Database Errors or Warnings from Error ORA-15059 to ORA-15068 received while performing certain operation against Oracle Database or related products.
What are Oracle Database Error Messages?
Oracle Error Messages may be returned while using products which are part of Oracle Database. Each Oracle Database Error or Warning Message mentioned above contains the Warning or Error Message Statement, a short explanation of the probable causes of the Error message, and a recommended action.
Hope this was helpful.
Information about Oracle Database Error Messages or Warning Messages on Windows and Linux Operating Systems.