Disk Is not Discovered in ASM, Diskgroup Creation Fails with Ora-15018 Ora-15031 Ora-15014
Last updated on OCTOBER 16, 2017
Applies to:Oracle Database - Enterprise Edition - Version 10.1.0.2 to 184.108.40.206 [Release 10.1 to 11.2]
Information in this document applies to any platform.
***Checked for relevance on 29-Nov-2014***
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:
SQL> create diskgroup <dg_name> EXTERNAL REDUNDANCY DISK '<path and name>'; create diskgroup <dg_name> EXTERNAL REDUNDANCY DISK '<path and name>' * ERROR at line 1: ORA-15018: diskgroup cannot be created ORA-15031: disk specification 'path and name' matches no disks ORA-15014: location 'path and name' is not in the discovery set
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.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms