Mounting Diskgroup Fails With ORA-15063 and V$ASM_DISK Shows PROVISIONED (Doc ID 1487443.1)

Last updated on OCTOBER 31, 2016

Applies to:

Oracle Database - Enterprise Edition - Version 10.2.0.1 to 11.2.0.4 [Release 10.2 to 11.2]
Information in this document applies to any platform.

Symptoms

 1. ASM is restarted and some ASM diskgroups will not be mounted with the following similar error.

SQL> alter diskgroup DATA mount;
alter diskgroup DATA mount
*
ERROR at line 1:
ORA-15032: not all alterations performed
ORA-15017: diskgroup "DATA" cannot be mounted
ORA-15063: ASM discovered an insufficient number of disks for diskgroup "DATA"

 
 

2. v$asm_disk view returns all ASM device information but v$asm_disk.header_status colume shows the status as "PROVISIONED".

SQL> select group_number gn,disk_number dn, mount_status, header_status,mode_status,state, total_mb, free_mb, label, path from v$asm_disk order by group_number, disk_number;

  GN   DN MOUNT_STATUS HEADER_STATU MODE_STATUS  STATE         TOTAL_MB    FREE_MB        LABEL          PATH                                     
---- ---- ----------------------------------------------------------------------------------------------------------------------------------------  
   0    0 CLOSED              PROVISIONED        ONLINE            NORMAL                  0                0       CRS             ORCL:CRS  
   0    1 CLOSED              PROVISIONED        ONLINE            NORMAL                  0                0       DATA           ORCL:DATA

 

3. kfed output for the affected device shows unexpected value on some spare columns.

Example #1>  0xaa55 on kfdhdb.acdb.ub2spare field ( 2 bytes at 510th location ).

$ kfed read /dev/oracleasm/disks/DATA

kfbh.endian:                          1 ; 0x000: 0x01
kfbh.hard:                          130 ; 0x001: 0x82
..
kfdhdb.acdb.ents:                   0 ; 0x1dc: 0x0000
kfdhdb.acdb.ub2spare:     43605 ; 0x1de: 0xaa55                          <<<<<<<<------------ Should be "0"
                                                             

 

Example #2>

kfdhdb.ub4spare[39]:         3465798583 ; 0x198: 0xce93e3b7        <<<<<<<<------------ Should be "0"
kfdhdb.ub4spare[40]:                  0 ; 0x19c: 0x00000000

 

Cause

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