techblog 

As I use ASM more, I’m coming across interesting features. So I was trying to follow my previous and add new Diskgroups. This seemed fine on node1 then I tried the following on node2:

SQL>select name, state, type, total_mb, free_mb from v$asm_diskgroup;
NAME                  STATE       TYPE     TOTAL_MB    FREE_MB
DATA1                 MOUNTED     EXTERN     153597     153503
DATA2                 DISMOUNTED                  0          0
DATA3                 DISMOUNTED                  0          0

SQL> alter diskgroup DATA2 mount;
Error 45 initializing SQL*Plus
Internal error

This crashed me out of sqlplus, so I checked back on the node I created the diskgroup and everything still looked fine. Logging back into the node where I crashed out, the disks were still in a dismounted state. I then had a look back on the node I created them at v$asm_operation, which should show if any procedures are going on:

SQL> select * from v$asm_operation;
Error 45 initializing SQL*Plus
Internal error

So I had managed to crash out of sqlplus on both nodes. I waited. Then after a few minutes I tried to mount the diskgroup on node 2 again. It worked. V$asm_operation now returned 0 rows. Looks like you want to go make some tea, after creating a diskgroup, and v$asm_operation does not look to clever if it bombs out whenever it could show you something useful!