Adding a disk to an ASM diskgroup is really simple, just an alter command. But when if you are doing this in a production database, then before adding we have to make sure that the disk is healthy.

We will follow below steps to confirm that the disk is healthy.

1.First, create the disk using ASMLIB

NOTE – If this is Solaris or HP, then the 1st step is not required, as it doesn’t need ASMLIB.

2. Check the visibility of the disks at OS level:( as grid owner from all the nodes)

3. Use kfed to read the disks:(as grid owner from all the nodes)

If you are getting an error like kfbh.type: 0 ; 0x002: KFBTYP_INVALID, then you can ignore it safely.

4. Now create a diskgroup for testing purpose:

5. Create a tablespace on this diskgroup:

As tablespace created, we can confirm that the disk is healthy. We can clean the diskgroup.

6.Let’s drop the tablespace and the diskgroup:


If you try to drop the diskgroup, without dismounting the diskgroup from all instance, except one, then you will hit the error.

ORA-15073: diskgroup TESTDG is mounted by another ASM instance


Now we have cleaned up diskgroup, after confirming that disk is perfectly healthy. So let’s proceed and add that disk to your required existing diskgroup.

7.Add the disk to existing diskgroup:


ASMCA UTILITY can also be used for adding, dropping, dismount ASM disk/disk groups.

Also Read : ASMCA Utility in  oracle