Re: ASM disk to physical disk mapping

From: Dan <daniel.ostertag_at_visaer.com>
Date: Wed, 1 Jul 2009 10:16:51 -0700 (PDT)
Message-ID: <32e8354d-9a08-44d4-8cd6-0925d3f7bd6b_at_h18g2000yqj.googlegroups.com>



On Jul 1, 12:08 pm, John Hurley <johnbhur..._at_sbcglobal.net> wrote:
> On Jul 1, 11:55 am, Dan <daniel.oster..._at_visaer.com> wrote:
>
>
>
>
>
> > Does anyone know how to map an ASM disk that I can see in OEM to its
> > physical drive?  I have a disk that is throwing errors via my hardware
> > diagnostic (but no errors yet in Oracle).  I would like to identify it
> > in ASM, remove it and rebalance off of it.  I know and can see the
> > exact physical disk that is bad, yet I cannot definitively identify
> > what ASM disk maps to that physical disk.
>
> > Is there a tool to do this?
>
> > For example, my bad disk is disk 1:11 - on Channel 1, Target ID 11,
> > Lun 0.  I have 3 disk arrays of 14 disks each, channel 0 and 1 on one
> > controller, channel 0 on another controller.  But in my Windows
> > environment when I use Disk Management, I see two disks with Target ID
> > 11, Lun 0.  I'm not sure which is the culprit.
>
> > Thanks.
>
> > Dan
>
> Do you have your create diskgroup statements around?  You can look at
> those ... or do some querying against the ASM views.- Hide quoted text -
>
> - Show quoted text -

I checked the views and they give only what I can see in OEM. Unfortunately I don't have the create diskgroup statements because I stamped and added them to the diskgroup via asmtoolg, a gui-like tool that does all the work for you (another reason to do things yourself). I'm still researching this, I'll let you know what I find. I've seen others that lament this difficulty too, so I guess it's a known problem. Received on Wed Jul 01 2009 - 12:16:51 CDT

Original text of this message