ASM REACTING TO PARTITION ERRORS

(Doc ID 1062954.1)

Last updated on FEBRUARY 07, 2014

Applies to:

Oracle Database - Enterprise Edition - Version 10.1.0.4 to 11.2.0.1.0 [Release 10.1 to 11.2]
Linux x86
Haansoft Linux x86-64

Symptoms

Randomly disks that belonged to ASM disk groups show as PROVISIONED or at times as CANDIDATE in v$asm_disk.header_status. Upon dismount, disk groups with those disks will not mount.

From ASM alert log:

ERROR: diskgroup was not mounted
ORA-15032: not all alterations performed
ORA-15063: ASM discovered an insufficient number of disks for diskgroup ""

Or

ORA-15032: not all alterations performed
ORA-15040: diskgroup is incomplete
ORA-15042: ASM disk "disk number here>" is missing
ORA-15063: ASM discovered an insufficient number of disks for diskgroup ""

This seems to occur when new LUNs are either added or configured on the cluster, but this behavior has occurred several times (10+), on more than one cluster and across separate data centers.

At times the disks' v$asm_header_status is of member but still the disk groups will not mount, upon attempt to re-mount the disk group.

While troubleshooting the issue, it has been noticed that the OS partition table for the devices employed by the ASM disks, is wiped out (does not exist). This issue is similarly reproduced when dd is used to wiped the devices although this does not explain why some times the disks will show with v$asm_disk.header_status=member, and still cannot be mountable.

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