Re: ASM disks with UNKNOWN header status, can't create disk group

Special thanks to Krish, who worked with me in a flurry of off-list emails.

He had me check my asm_diskstring parameter, which was empty. He suggested setting this to the actual path of the ASM disk devices, in my case this was '/dev/oracleasm/disks/VOL*'. I did this, bounced the ASM instance, and the disks now appeared in v$asm_disk as PROVISIONED and the path was now the full path under /dev/oracleasm/disks/ rather than ORCL:. I was then able to create the disk group with those disks just fine.

My only other experience with ASM was on an old desktop box with plain old IDE disks. This doesn't have the asm_diskstring parameter set and uses the partitions (just two partitions of the same hard drive) just fine by their ORCL paths.

Why does it work in one (much simpler) case, and not in the big box with the SAN? Should I just make a point to set the asm_diskstring to those paths as a best practice?

Don.

On Dec 27, 2007 8:44 AM, Don Seiler <don_at_seiler.us> wrote:
> This is not just a dbca/gui thing. I get the same error when running
> in sqlplus in the +ASM instance.
>
> SQL> CREATE DISKGROUP dgroup1
> 2 EXTERNAL REDUNDANCY
> 3 DISK 'ORCL:VOL01','ORCL:VOL02';
> CREATE DISKGROUP dgroup1
> *
> ERROR at line 1:
> ORA-15018: diskgroup cannot be created
> ORA-15072: command requires at least 1 failure groups, discovered only 0
>
> Permissions look right. They are set by /etc/init.d/oracleasm.
>
> $ ls -l /dev/oracleasm/disks/
> total 0
> brw-rw---- 1 oracle dba 8, 129 Dec 26 14:49 VOL01
> brw-rw---- 1 oracle dba 8, 113 Dec 26 14:49 VOL02
>
> Don.
>
>
> On Dec 27, 2007 8:22 AM, Finn Jorgensen <finn.oracledba_at_gmail.com> wrote:
> > Could this be just a dbca error? Have you tried creating the diskgroup by
> > hand in your ASM instance? I have encountered all kinds of permissions
> > issues and asmlib issues, but not something like this before.
> >
> > Finn
> >
> >
> >
> > On 12/26/07, Don Seiler <don_at_seiler.us> wrote:
> > >
> > >
> > >
> > > * Oracle 10.2.0.2 on RHEL4.
> > > * We have two 900gb LUNs using RAID 10.
> > > ** SysAdmin says no multipathing is involved. We do use Veritas DMP
> > > elsewhere in the SAN, fwiw.
> > >
> > > Giving this crazy ASM fad another shot.
> > >
> > > We ran through "oracleasm configure" and "oracleasm createdisk" on
> > > each of the two disks, with no problems. "oracleasm listdisks" lists
> > > the two created volumes (VOL01 and VOL02) just fine. However when I
> > > launch dbca to create the disk group, I get an ORA-15072 error.
> > > Googling around led me to some forum posts about clashes with external
> > > redundancy (which we're using) and multipathing (which we're not). I
> > > also found this query, which I ran on our ASM instance:
> > >
> > > SQL> select state,header_status,substr(name,1,12) Name,free_mb,
> > > substr(path,1,16) PATH from v$asm_disk;
> > >
> > > STATE HEADER_STATU NAME FREE_MB PATH
> > > -------- ------------ ------------ ---------- ----------------
> > > NORMAL UNKNOWN 0 ORCL:VOL02
> > > NORMAL UNKNOWN 0 ORCL:VOL01
> > >
> > > I'm open to any and all suggestions (regarding ASM, anyway).
> > >
> > > --
> > > Don Seiler
> > > http://seilerwerks.wordpress.com
> > > ultimate: http://www.mufc.us
> > >
> > > --
> > > http://www.freelists.org/webpage/oracle-l
> > >
> > >
> > >
> >
> >
>
>
>
> --
>
> Don Seiler
> http://seilerwerks.wordpress.com
> ultimate: http://www.mufc.us
>

-- 
Don Seiler
http://seilerwerks.wordpress.com
ultimate: http://www.mufc.us
--
http://www.freelists.org/webpage/oracle-l