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

Just one FYI is that this is for a single instance, not RAC. A search on Metalink turned up Note 396015.1, which describes the symptoms I'm seeing (including alert log output) to a tee, except we aren't using NetApp, fstab checks out fine, and we aren't using multipath at all, Veritas or Linux native. *sigh*

Don.

On Dec 26, 2007 2:32 PM, 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