Re: Removing a diskgroup from a corrupt ASM database

From: <johnbhurley_at_sbcglobal.net>
Date: Wed, 27 May 2009 08:12:22 -0700 (PDT)
Message-ID: <a05915e7-41fa-4900-86f4-8430182e9d28_at_z7g2000vbh.googlegroups.com>



On May 27, 10:50 am, daniel.oster..._at_visaer.com wrote:

snip

> John,
> No problems, appreciate your help.
>
> Per your advice I pursued the recreating of the diskgroup.  Nothing
> worked, I kept getting various errors including ORA-15106, which said
> my disk paths were wrong.  As I knew they were right, I researched
> further.  Finally I found a deeply buried post in MetaLink saying to
> remove the commas from disk listing in the 'CREATE DISKGROUP'
> statement.  This goes against all the official Oracle doc, but it
> worked!  And without the FORCE option (not sure why).  When I did all
> this from scratch, I created the ASM database and did everything via
> DBCA.  But now, since I had to fix the ASM database, I had to do the
> create diskgroup manually.  I'm able to bounce the ASM database and
> the diskgroup is mounted and appears healthy.
>
> Here's my create diskgroup statement that worked.  I use a fail group
> for each disk. There's only 13 disks as one slot is empty.
> CREATE DISKGROUP DATA NORMAL REDUNDANCY
>   FAILGROUP DATA_0000 DISK '\\.\ORCLDISKDATA0'
>   FAILGROUP DATA_0001 DISK '\\.\ORCLDISKDATA1’
>   FAILGROUP DATA_0002 DISK '\\.\ORCLDISKDATA2'
>   FAILGROUP DATA_0003 DISK '\\.\ORCLDISKDATA3'
>   FAILGROUP DATA_0004 DISK '\\.\ORCLDISKDATA4'
>   FAILGROUP DATA_0005 DISK '\\.\ORCLDISKDATA5'
>   FAILGROUP DATA_0006 DISK '\\.\ORCLDISKDATA6'
>   FAILGROUP DATA_0007 DISK '\\.\ORCLDISKDATA7'
>   FAILGROUP DATA_0008 DISK '\\.\ORCLDISKDATA8'
>   FAILGROUP DATA_0009 DISK '\\.\ORCLDISKDATA9'
>   FAILGROUP DATA_0010 DISK '\\.\ORCLDISKDATA10'
>   FAILGROUP DATA_0011 DISK '\\.\ORCLDISKDATA11'
>   FAILGROUP DATA_0012 DISK '\\.\ORCLDISKDATA12';
>
> My next task is to build the non-ASM database.  Hopefully that will go
> smoothly and I can get everything back good as new.  I'll let you know
> how I make out.
>
> Again, thanks for the help.
> Dan

Well I am glad you are back operating now ...

The ASM syntax is a little peculiar no doubt. I am using external redundancy letting my storage arrays do the mirroring ... ( lots of varied opinions here on how to use ASM on one side and the other ). No FAILGROUPs.

You certainly need ( as far as I know ) commas between multiple disks in the straight up case ... ( like ):

CREATE DISKGROUP some_name EXTERNAL REDUNDANCY DISK '/some_path/disk1' FORCE,'/some_path/disk2' FORCE;

If you haven't already trashed it you should have something left over from the original create via dbca that would have had the syntax used the first time around by the GUI ... for whatever that's worth.

Have fun! Received on Wed May 27 2009 - 10:12:22 CDT

Original text of this message