ASM: how to deal with ORA-15063 errors

ASM: How to Handle ORA-15063 errors [SQL] www.2cto.com idle> startup ASM instance started Total System Global Area 83886080 bytes Fixed Size 1217836 bytes Variable Size 57502420 bytes ASM Cache 25165824 bytes ORA-15032: not all alterations shortmed ORA-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_NUMBE R name state TOTAL_MB FREE_MB ---------- tables ---------- 0 data dismounted 0 0 2 water mounted 2744 599 idle> alter diskgroup data mount; alter diskgroup data mount * ERROR at line 1: ORA-15032: not all alterations shortmed ORA-15063: ASM discovered an insufficient number of disks for diskgroup "DATA" idle> drop diskgroup data; drop diskgroup d Ata * ERROR at line 1: ORA-15039: diskgroup not dropped ORA-15001: diskgroup "DATA" does not exist or is not mounted idle> drop diskgroup data including contents; drop diskgroup data including contents * ERROR at line 1: ORA-15039: diskgroup not dropped ORA-15001: diskgroup "DATA" does not exist or is not mounted query ERROR message: [SQL] [oracle @ localhost ~] $ Oerr ora 15063 15063,000 00, "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_DI SKSTRING initialization parameter // has been set correctly. verify that ASM discovers the appropriate // disks by querying V $ ASM_DISK from the ASM instance. processing steps: ①/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 [SQL] idle> startup ASM instance started Total System Global Area 83886080 bytes Fixed Size 1217836 bytes Variable Size 57502420 bytes ASM Cache 25165824 bytes ASM diskgroups mounted does not throw an ERROR now, though: [SQL] SQL> drop diskgroup data; drop diskgroup data * ERROR at line 1: ORA-15039: diskgroup not dropped ORA-15001: diskgroup "DATA" does not exist or is not mounted since there is no syntax for drop diskgroup force in 10 Gb, therefore, we use the linux dd AND dbca to force the old stubborn deletion. Step: (I) through the query, we can see that raw5 hangs on data: [SQL] [root @ localhost ~] # Dd if =/dev/zero of =/dev/raw/raw5 bs = 1024 count = 5 5 + 0 records in 5 + 0 records out 5120 bytes (5.1 kB) copied, 0.011998 seconds, 427 kB/s (2) in dbca ---> show all ---> select raw5 ---> click cancel. Actually, I already have the diskgroup named "water", which is also mounted, you do not need to worry about the diskgroup of data.