Re: Need help with ASM disk/diskgroup ghost

On Oct 9, 3:32 pm, Altus <silverb..._at_photobooks.com> wrote:
> Hello,
>
> I am hoping for a quick answer to this question, as Oracle would
> (rightly so) put it as a sev 3 or 4.
>
> Our ASM disks seem to have gotten out of wack (technical term).
> We have been running with two disk groups for months. We need to add
> an additional disk to the primary disk group.
> We had our system administrator add the disk to each node and get it
> set up for ASM use.
>
> I tried to add the disk via GRID. It showd as "Member", but not a
> member of any group.
> I chose it and clicked OK and received the error:
> Failed to commit: ORA-15032: not all alterations performed ORA-15033:
> disk '/dev/raw/ASM7' belongs to diskgroup "EUDATA_01"
>
> This was news to me, as we should not have a disk group EUDATA_01.
>
> I looked in v$asm_diskgroup and found a new disk group. Further more,
> it is listed as group zero! I thought the numbers were sequential and
> climbing.
>
> The ASM alert logs don't show anything until the alter to add the disk
> to the correct disk group.
> At that point, they show my attempts to mount/drop the "new" disk
> group.
>
> At this point, I can't drop the disk or disk group. I can't add it
> where it needs to be.
>
> Questions:
> 1) How can I get rid of an un-mountable disk group?
> 2) How do I pry loose the disk I need to apply to DATA_02?
> 3) Why don't I see anything in the ASM alert logs?
>
> My versions and such:
> I am running a 2 node RAC with ASM. Everything from CRS to the
> database is 10.2.0.2. Compatibility was set by a different DBA, so I
> don't know why it isn't 10202.
> The new disk is /dev/raw/ASM7. The bad disk group is EUDATA_01.
>
> Thanks!
>
> V$ASM_DISKGROUP
> GRP NAME STATE TYPE TOTAL_MB USABLE_FILE_MB
> OFFLINE_DISKS COMPATIBIL Compatibilit
> ---- --------- ----------- ------ ---------- --------------
> ------------- ---------- ------------
> 1 DATA_02 MOUNTED EXTERN 345220
> 5840 0 10.1.0.0.0 10.1.0.0.0
> 2 FRA_01 MOUNTED EXTERN 69044
> 65565 0 10.1.0.0.0 10.1.0.0.0
> 0 EUDATA_01 DISMOUNTED 0
> 0 0 0.0.0.0.0 0.0.0.0.0
>
> V$ASM_DISK
> GRP DskNum MOUNT_S HeaderStat MODE_ST STATE REDUNDA TOT_MB FREE_MB
> NAME FAILGROUP PATH MOUNT_DAT
> --- ------ ------- ---------- ------- ------ ------- -------- -------
> ------------ ------------ ------------- ---------
> 0 1 CLOSED MEMBER ONLINE NORMAL UNKNOWN 69,044
> 0 /dev/raw/ASM7 30-MAR-06
> 1 0 CACHED MEMBER ONLINE NORMAL UNKNOWN 69,044 1,105
> DATA_02_0000 DATA_02_0000 /dev/raw/ASM1 17-JAN-06
> 1 1 CACHED MEMBER ONLINE NORMAL UNKNOWN 69,044 1,150
> DATA_02_0001 DATA_02_0001 /dev/raw/ASM2 17-JAN-06
> 1 2 CACHED MEMBER ONLINE NORMAL UNKNOWN 69,044 1,331
> DATA_02_0002 DATA_02_0002 /dev/raw/ASM3 17-JAN-06
> 1 3 CACHED MEMBER ONLINE NORMAL UNKNOWN 69,044 1,204
> DATA_02_0003 DATA_02_0003 /dev/raw/ASM4 17-JAN-06
> 1 4 CACHED MEMBER ONLINE NORMAL UNKNOWN 69,044 1,050
> DATA_02_0004 DATA_02_0004 /dev/raw/ASM5 17-JAN-06
> 2 1 CACHED MEMBER ONLINE NORMAL UNKNOWN 69,044 65,565
> FRA_01_0001 FRA_01_0001 /dev/raw/ASM6 28-JUL-05

There is a force clause for add disk...

http://download.oracle.com/docs/cd/B19306_01/server.102/b14231/storeman.htm#i1021337

"The following use of the FORCE clause enables /devices/diskc3 to be added to dgroup2, even though it is a current member of dgroup3.

ALTER DISKGROUP dgroup2 ADD DISK

     '/devices/diskc3' FORCE;"

...or you can dd into the device...

dd if=/dev/zero if=/dev/raw/ASM7 bs=1M count=100

That will strip the header out, and ASM will no longer recognize it as "one of its own".

Regards,

Steve Received on Tue Oct 09 2007 - 15:15:10 CDT