ASM: ORA-15063 error handling method 1

idle> startupASM instance startedTotal System Global Area   83886080 bytesFixed Size                  1217836 bytesVariable Size              57502420 bytesASM Cache                  25165824 bytesORA-15032: not all alterations performedORA-15063: ASM discovered an insufficient number of disks for diskgroup "DATA"idle> select group_number,name,state,total_mb,free_mb from v$asm_diskgroup;GROUP_NUMBER NAME       STATE                               TOTAL_MB    FREE_MB------------ ---------- --------------------------------- ---------- ----------           0 DATA       DISMOUNTED                                 0          0           2 WATER      MOUNTED                                 2744        599idle> alter diskgroup data mount;alter diskgroup data mount*ERROR at line 1:ORA-15032: not all alterations performedORA-15063: ASM discovered an insufficient number of disks for diskgroup "DATA"idle> drop diskgroup data;drop diskgroup data*ERROR at line 1:ORA-15039: diskgroup not droppedORA-15001: diskgroup "DATA" does not exist or is not mountedidle> drop diskgroup data including contents;drop diskgroup data including contents*ERROR at line 1:ORA-15039: diskgroup not droppedORA-15001: diskgroup "DATA" does not exist or is not mounted

 

Query error information:

[oracle@localhost ~]$ oerr ora 1506315063, 00000, "ASM discovered an insufficient number of disks for diskgroup \"%s\""// *Cause:  ASM was unable to find a sufficient number of disks belonging to the//          diskgroup to continue the operation.// *Action: Check that the disks in the diskgroup are present and functioning, //          that the owner of the ORACLE binary has read/write permission to //          the disks, and that the ASM_DISKSTRING initialization parameter //          has been set correctly.  Verify that ASM discovers the appropriate //          disks by querying V$ASM_DISK from the ASM instance.

 

 

Procedure:

①/Etc/init. d/init.css d stop
②/Etc/init. d/init.css d start
③ Sleep 90
④ Restart ASM instance and shutdown immediate
⑤ Again restart ASM instance

 

idle> startupASM instance startedTotal System Global Area   83886080 bytesFixed Size                  1217836 bytesVariable Size              57502420 bytesASM Cache                  25165824 bytesASM diskgroups mounted

 

No error is thrown. However:

SQL> drop diskgroup data;drop diskgroup data*ERROR at line 1:ORA-15039: diskgroup not droppedORA-15001: diskgroup "DATA" does not exist or is not mounted

Since the drop diskgroup force syntax is not available for 10 Gb, we use the Linux dd AND dbca to force the old stubborn deletion.

Steps:

(I) the query shows that raw5 is mounted on data:

[root@localhost ~]# dd if=/dev/zero of=/dev/raw/raw5 bs=1024 count=55+0 records in5+0 records out5120 bytes (5.1 kB) copied, 0.011998 seconds, 427 kB/s

(Ii) In dbca ---> show all ---> select raw5 ---> click Cancel.

 

In fact, I already have the water diskgroup and mount it. For the data diskgroup, you don't have to worry about it.