are you using asmlib or Udev ?
do you have physical objects inside this diskgroup ?
- You only Drop the disks from the disk Group.
- Wait the rebalance process to finish
- Drop the Diskgroup with the last disk
- Then you can use again those disk on another diskGroup
Or Drop the DiskGroup
DISKGROUPstatement lets you drop an Automatic Storage Management disk group along with all the files in the disk group. Automatic Storage Management first ensures that no files in the disk group are open. It then drops the disk group and all its member disks and clears the disk header.
I hope this help you
lets say this is a 10TB diskgroup
dropping all the disks, waiting for rebalance and then dropping diskgrop would take a lot longer to complete wouldn't it? - more to the point in this scenario how does the rebalance actually work if there are no other disks to rebalance onto?
Regarding drop diskgroup, the link you have provided relates to 11.1 docs. this is an 11.2 system..... this is the point im making about the 11.2 docs and how I am unclear from them that 'DROP Diskgroup data1' or example would clear the header status on all disks within the diskgroup unless INCLUDING CONTENTS is specified.
I send you the information for 11.2:
DISKGROUPstatement lets you drop an Oracle ASM disk group along with all the files in the disk group. Oracle ASM first ensures that no files in the disk group are open. It then drops the disk group and all its member disks and clears the disk header.
CONTENTSto confirm that Oracle ASM should drop all the files in the disk group. You must specify this clause if the disk group contains any files.
CONTENTSto ensure that Oracle ASM drops the disk group only when the disk group is empty. This is the default. If the disk group is not empty, then an error will be returned.
- If you want to drop this DiskGroup then use Including content and all the disks again will be available for the ASM.
- Or, Drop all the physical files by yourself with asmcmd and then Drop the DiskGroup without "INCLUDING CONTENTS" (default)
If you choose method 1 or 2, the result will be the same for the disks and the disks will be available for ASM.
There is a point here:
Both ASM command DROP DISKGROUP (no matter if INCLUDING/EXCLUDING CONTENTS) and ALTER DISKGROUP <DG_NAME> DROP DISK, Oracle DOESN'T format(erasing data) ASMDISK dropped it only destroy metadata on Header marking as FORMER.
Using ALTER DISKGROUP <DG_NAME> DROP DISK it first move data from ASMDISK being dropped to MEMBER ASMDISK and after rebalance only destroy metadata on Header of that ASMDISK marking as FORMER.
All Operation System do that, only destroy header of Disk Device when drop a Disk Device from a Volume Group or anything else.
INCLUDING CONTENTS option is only a security to make sure which User is aware that executing this command he is "excluding data" not only a empty diskgroup.