Disk Is not Discovered in ASM, Diskgroup Creation Fails with Ora-15018 Ora-15031 Ora-15014
(Doc ID 431013.1)
Last updated on JUNE 24, 2024
Applies to:
Oracle Database Cloud Exadata Service - Version N/A and laterOracle Database Cloud Service - Version N/A and later
Oracle Database - Enterprise Edition - Version 10.1.0.2 to 11.2.0.3 [Release 10.1 to 11.2]
Oracle Database Cloud Schema Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Information in this document applies to any platform.
Symptoms
Some of the devices that should be available for the ASM to use are not discovered by the ASM instance, the rest of the them are discovered and can be used without problems.
When trying to create a diskgroup on such a problematic device, the statement fails as follows:
The following have been checked:
+ ownership and permissions on the device are correct, ie oracle:dba and 660 respectively
+ kfod discovers the device without problems
+ asm_diskstring includes the path to the device
+ OS tracing (truss, strace) on the ASM startup shows no problem accessing the disk.
+ restarting the ASM instance is without positive results.
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |