Duplicate Disk Entry with HUNG/MISSING status after a failgroup is lost (Doc ID 417335.1)

Last updated on MARCH 02, 2009

Applies to:

Oracle Server Enterprise Edition - Version: 10.1 to 10.2
This problem can occur on any platform.
Oracle Server - Enterprise Edition - Version: 10.1.0.2 to 10.2.0.1

Symptoms

Diskgroup redundancy is defined as NORMAL. V$ASM_DISK contains a duplicate entry for the failed disks after all disks in a failgroup are lost.  There is only one failgroup remained in the diskgroup after the failure.


Before Failure

GROUP_NUMBER NAME       PATH       MOUNT_S HEADER_STATU MODE_ST STATE
------------ ---------- ---------- ------- ------------ ------- --------
           4 VOL1       ORCL:VOL1  CACHED  MEMBER       ONLINE  NORMAL
           4 VOL2       ORCL:VOL2  CACHED  MEMBER       ONLINE  NORMAL

 

After Failure
GROUP_NUMBER NAME       PATH       MOUNT_S HEADER_STATU MODE_ST STATE
------------ ---------- ---------- ------- ------------ ------- --------
                        ORCL:VOL2  CLOSED  PROVISIONED  ONLINE  NORMAL *
           4 VOL2                  MISSING CANDIDATE    OFFLINE HUNG **
           4 VOL1       ORCL:VOL1  CACHED  MEMBER       ONLINE  NORMAL

* ORCL:VOL2 header status is PROVISIONED as expected as it is former ASM disk. 
** However, VOL2 is still in v$asm_disk with actually no associated path (i.e physical disk).  So VOL2 seems to be duplicate.

Changes

Disks in a failgroup are lost after a disk/LUN failure.

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