Re: Removing a diskgroup from a corrupt ASM database

From: <>
Date: Tue, 26 May 2009 04:16:31 -0700 (PDT)
Message-ID: <>

On May 25, 9:00 pm, onedbguru <> wrote:


> > As part of DR testing and validating that we can recover from anything
> > ASM related the CREATE DISKGROUP ... FORCE has worked well for us.
> > It doesn't matter if the diskgroup is can be mounted or fails during a
> > mount attempt ... it destroys anything ASM related on the disks and re-
> > initializes them.  This may be an 11g only thing so you might need to
> > upgrade the ASM to 11g before FORCE become s a valid option in ASM
> > create diskgroup.
> Anyone using "single disks" (as opposed to SAN mirrored/RAIDed LUNS)
> without the use of failure groups is asking for trouble.  Replacing
> the failed device is futile without having thoroughly worked out the
> failover mechanisms to be able to reconstruct it without having to
> restore all of your databases.  Should you proceed with the the
> "FORCE" option, you will need to be able to restore all of your
> databases that resided in that ASM instance.

Who exactly does not know that?

Anyone who has deployed ASM without testing and documenting and recovering from all conditions including having to rebuild the ASM diskgroups from scratch just has not done their homework.

Go back and read the original post in this thread if you still are not understanding what was asked. Received on Tue May 26 2009 - 06:16:31 CDT

Original text of this message