This discussion is archived
5 Replies Latest reply: Jul 5, 2011 2:06 AM by 585179 RSS

ORA 15063 ASM discovered an insufficient number of disks for diskgroup

francis t Newbie
Currently Being Moderated
Hello

I'm getting this error when tying to mount the ASM

ORA-15032: not all alterations performed
ORA 15063 ASM discovered an insufficient number of disks for diskgroup
"DUARFFB"
ORA-15063: ASM discovered an insufficient number of disks for diskgroup
"DUARFDG"

Please assist

OS = Solaris 10
Database = 10.2.0.1

Any idea please, let me know.
  • 1. Re: ORA 15063 ASM discovered an insufficient number of disks for diskgroup
    Fran Guru
    Currently Being Moderated
    just add a new disk or check if your disks are mounted.
  • 2. Re: ORA 15063 ASM discovered an insufficient number of disks for diskgroup
    585179 Expert
    Currently Being Moderated
    Hi,

    Please post the ASM alertlog


    15063, 00000, "ASM discovered an insufficient number of disks for diskgroup \"%s\""
    // *Cause:  ASM was unable to find a sufficient number of disks belonging to the
    // diskgroup to continue the operation.
    // *Action: Check that the disks in the diskgroup are present and functioning,
    // that the owner of the ORACLE binary has read/write permission to
    // the disks, and that the ASM_DISKSTRING initialization parameter
    // has been set correctly. Verify that ASM discovers the appropriate
    // disks by querying V$ASM_DISK from the ASM instance.



    Cheers
  • 3. Re: ORA 15063 ASM discovered an insufficient number of disks for diskgroup
    CKPT Guru
    Currently Being Moderated
    15063, 00000, "ASM discovered an insufficient number of disks for diskgroup \"%s\""
    // *Cause:  ASM was unable to find a sufficient number of disks belonging to the
    // diskgroup to continue the operation.
    // *Action: Check that the disks in the diskgroup are present and functioning,
    // that the owner of the ORACLE binary has read/write permission to
    // the disks, and that the ASM_DISKSTRING initialization parameter
    // has been set correctly. Verify that ASM discovers the appropriate
    // disks by querying V$ASM_DISK from the ASM instance.
    //

    SQL>
  • 4. Re: ORA 15063 ASM discovered an insufficient number of disks for diskgroup
    francis t Newbie
    Currently Being Moderated
    Thanks for your reply .. I here is the extract from the log

    SQL> ALTER DISKGROUP ALL MOUNT
    Tue Jul 5 09:39:58 2011
    NOTE: cache registered group ASMDATA number=1 incarn=0x843df733
    NOTE: cache registered group BILLDATA number=2 incarn=0x846df734
    NOTE: cache registered group BILLFR number=3 incarn=0x846df735
    NOTE: cache registered group DUARFDG number=4 incarn=0x846df736
    NOTE: cache registered group DUARFFB number=5 incarn=0x846df737
    NOTE: cache registered group DWAREDG number=6 incarn=0x846df738
    NOTE: cache registered group DWAREFB number=7 incarn=0x846df739
    NOTE: cache registered group INTERDG number=8 incarn=0x846df73a
    NOTE: cache registered group INTERFB number=9 incarn=0x846df73b
    Tue Jul 5 09:40:10 2011
    NOTE: Hbeat: instance first (grp 1)
    Tue Jul 5 09:40:11 2011
    NOTE: Hbeat: instance first (grp 2)
    Tue Jul 5 09:40:11 2011
    NOTE: Hbeat: instance first (grp 3)
    ERROR: no PST quorum in group 4: required 2, found 0
    Tue Jul 5 09:40:11 2011
    NOTE: cache dismounting group 4/0x846DF736 (DUARFDG)
    NOTE: dbwr not being msg'd to dismount
    ERROR: diskgroup DUARFDG was not mounted
    Tue Jul 5 09:40:11 2011
    ERROR: no PST quorum in group 5: required 2, found 0
    Tue Jul 5 09:40:11 2011
    NOTE: cache dismounting group 5/0x846DF737 (DUARFFB)
    NOTE: dbwr not being msg'd to dismount
    ERROR: diskgroup DUARFFB was not mounted
    Tue Jul 5 09:40:11 2011
    NOTE: Hbeat: instance first (grp 6)
    Tue Jul 5 09:40:11 2011
    NOTE: Hbeat: instance first (grp 7)
    Tue Jul 5 09:40:11 2011
    NOTE: Hbeat: instance first (grp 8)
    Tue Jul 5 09:40:11 2011
    NOTE: Hbeat: instance first (grp 9)
    Tue Jul 5 09:40:15 2011
    NOTE: start heartbeating (grp 1)
    NOTE: cache opening disk 0 of grp 1: ASMDATA_0000 path:/dev/did/rdsk/d33s0
    Tue Jul 5 09:40:15 2011
    NOTE: F1X0 found on disk 0 fcn 0.0
    NOTE: cache opening disk 1 of grp 1: ASMDATA_0001 path:/dev/did/rdsk/d38s0
    NOTE: F1X0 found on disk 1 fcn 0.0
    NOTE: cache mounting (first) group 1/0x843DF733 (ASMDATA)
    * allocate domain 1, invalid = TRUE
    Tue Jul 5 09:40:15 2011
    NOTE: attached to recovery domain 1
    Tue Jul 5 09:40:15 2011
    NOTE: cache recovered group 1 to fcn 0.365
    Tue Jul 5 09:40:15 2011
    NOTE: opening chunk 1 at fcn 0.365 ABA
    NOTE: seq=92 blk=169
    Tue Jul 5 09:40:15 2011
    NOTE: cache mounting group 1/0x843DF733 (ASMDATA) succeeded
    SUCCESS: diskgroup ASMDATA was mounted
    Tue Jul 5 09:40:16 2011
    NOTE: start heartbeating (grp 2)
    Tue Jul 5 09:40:16 2011
    NOTE: erasing incomplete header on grp 2 disk BILLDATA_0004
    NOTE: cache opening disk 0 of grp 2: BILLDATA_0000 path:/dev/did/rdsk/d10s0
    NOTE: F1X0 found on disk 0 fcn 0.1674781
    NOTE: cache opening disk 1 of grp 2: BILLDATA_0001 path:/dev/did/rdsk/d7s0
    NOTE: F1X0 found on disk 1 fcn 0.1674781
    NOTE: cache opening disk 2 of grp 2: BILLDATA_0002 path:/dev/did/rdsk/d11s0
    NOTE: cache opening disk 3 of grp 2: BILLDATA_0003 path:/dev/did/rdsk/d8s0
    NOTE: F1X0 found on disk 3 fcn 0.1674781
    NOTE: cache opening disk 5 of grp 2: BILLDATA_0005 path:/dev/did/rdsk/d52s0
    NOTE: cache opening disk 6 of grp 2: BILLDATA_0006 path:/dev/did/rdsk/d47s0
    NOTE: cache opening disk 7 of grp 2: BILLDATA_0007 path:/dev/did/rdsk/d56s0
    NOTE: cache mounting (first) group 2/0x846DF734 (BILLDATA)
    Tue Jul 5 09:40:16 2011
    NOTE: recovering COD for group 1/0x843df733 (ASMDATA)
    SUCCESS: completed COD recovery for group 1/0x843df733 (ASMDATA)
    * allocate domain 2, invalid = TRUE
    Tue Jul 5 09:40:16 2011
    NOTE: attached to recovery domain 2
    Tue Jul 5 09:40:16 2011
    NOTE: cache recovered group 2 to fcn 0.2376132
    Tue Jul 5 09:40:16 2011
    NOTE: opening chunk 1 at fcn 0.2376132 ABA
    NOTE: seq=145 blk=9663
    Tue Jul 5 09:40:16 2011
    NOTE: cache mounting group 2/0x846DF734 (BILLDATA) succeeded
    SUCCESS: diskgroup BILLDATA was mounted
    Tue Jul 5 09:40:16 2011
    NOTE: start heartbeating (grp 3)
    NOTE: cache opening disk 0 of grp 3: BILLFR_0000 path:/dev/did/rdsk/d17s0
    Tue Jul 5 09:40:16 2011
    NOTE: F1X0 found on disk 0 fcn 0.0
    NOTE: cache opening disk 1 of grp 3: BILLFR_0001 path:/dev/did/rdsk/d18s0
    NOTE: F1X0 found on disk 1 fcn 0.0
    NOTE: cache mounting (first) group 3/0x846DF735 (BILLFR)
    * allocate domain 3, invalid = TRUE
    Tue Jul 5 09:40:16 2011
    NOTE: attached to recovery domain 3
    Tue Jul 5 09:40:16 2011
    NOTE: cache recovered group 3 to fcn 0.13167551
    Tue Jul 5 09:40:16 2011
    NOTE: opening chunk 1 at fcn 0.13167551 ABA
    NOTE: seq=127 blk=9647
    Tue Jul 5 09:40:16 2011
    NOTE: cache mounting group 3/0x846DF735 (BILLFR) succeeded
    SUCCESS: diskgroup BILLFR was mounted
    Tue Jul 5 09:40:16 2011
    NOTE: start heartbeating (grp 6)
    NOTE: cache opening disk 0 of grp 6: DWAREDG_0000 path:/dev/did/rdsk/d27s0
    Tue Jul 5 09:40:16 2011
    NOTE: F1X0 found on disk 0 fcn 0.0
    NOTE: cache mounting (first) group 6/0x846DF738 (DWAREDG)
    * allocate domain 6, invalid = TRUE
    Tue Jul 5 09:40:17 2011
    NOTE: attached to recovery domain 6
    Tue Jul 5 09:40:17 2011
    NOTE: cache recovered group 6 to fcn 0.198034
    Tue Jul 5 09:40:17 2011
    NOTE: opening chunk 1 at fcn 0.198034 ABA
    NOTE: seq=89 blk=1418
    Tue Jul 5 09:40:17 2011
    NOTE: cache mounting group 6/0x846DF738 (DWAREDG) succeeded
    SUCCESS: diskgroup DWAREDG was mounted
    Tue Jul 5 09:40:17 2011
    NOTE: start heartbeating (grp 7)
    NOTE: cache opening disk 0 of grp 7: DWAREFB_0000 path:/dev/did/rdsk/d28s0
    Tue Jul 5 09:40:17 2011
    NOTE: F1X0 found on disk 0 fcn 0.0
    NOTE: cache opening disk 1 of grp 7: DWAREFB_0001 path:/dev/did/rdsk/d32s0
    NOTE: F1X0 found on disk 1 fcn 0.0
    NOTE: cache mounting (first) group 7/0x846DF739 (DWAREFB)
    * allocate domain 7, invalid = TRUE
    Tue Jul 5 09:40:17 2011
    NOTE: attached to recovery domain 7
    Tue Jul 5 09:40:17 2011
    NOTE: cache recovered group 7 to fcn 0.185
    Tue Jul 5 09:40:17 2011
    NOTE: opening chunk 1 at fcn 0.185 ABA
    NOTE: seq=47 blk=79
    Tue Jul 5 09:40:17 2011
    NOTE: cache mounting group 7/0x846DF739 (DWAREFB) succeeded
    SUCCESS: diskgroup DWAREFB was mounted
    Tue Jul 5 09:40:17 2011
    NOTE: start heartbeating (grp 8)
    NOTE: cache opening disk 1 of grp 8: INTERDG_0001 path:/dev/did/rdsk/d29s6
    Tue Jul 5 09:40:17 2011
    NOTE: F1X0 found on disk 1 fcn 0.0
    NOTE: cache mounting (first) group 8/0x846DF73A (INTERDG)
    * allocate domain 8, invalid = TRUE
    Tue Jul 5 09:40:18 2011
    NOTE: attached to recovery domain 8
    Tue Jul 5 09:40:18 2011
    NOTE: cache recovered group 8 to fcn 0.903397
    Tue Jul 5 09:40:18 2011
    NOTE: opening chunk 1 at fcn 0.903397 ABA
    NOTE: seq=91 blk=5346
    Tue Jul 5 09:40:18 2011
    NOTE: cache mounting group 8/0x846DF73A (INTERDG) succeeded
    SUCCESS: diskgroup INTERDG was mounted
    Tue Jul 5 09:40:18 2011
    NOTE: start heartbeating (grp 9)
    NOTE: cache opening disk 0 of grp 9: INTERFB_0000 path:/dev/did/rdsk/d26s0
    Tue Jul 5 09:40:18 2011
    NOTE: F1X0 found on disk 0 fcn 0.0
    NOTE: cache opening disk 1 of grp 9: INTERFB_0001 path:/dev/did/rdsk/d30s0
    NOTE: F1X0 found on disk 1 fcn 0.0
    NOTE: cache mounting (first) group 9/0x846DF73B (INTERFB)
    * allocate domain 9, invalid = TRUE
    Tue Jul 5 09:40:18 2011
    NOTE: attached to recovery domain 9
    Tue Jul 5 09:40:18 2011
    NOTE: cache recovered group 9 to fcn 0.13202587
    Tue Jul 5 09:40:18 2011
    NOTE: opening chunk 1 at fcn 0.13202587 ABA
    NOTE: seq=131 blk=3060
    Tue Jul 5 09:40:18 2011
    NOTE: cache mounting group 9/0x846DF73B (INTERFB) succeeded
    SUCCESS: diskgroup INTERFB was mounted
    Tue Jul 5 09:40:19 2011
    NOTE: recovering COD for group 2/0x846df734 (BILLDATA)
    SUCCESS: completed COD recovery for group 2/0x846df734 (BILLDATA)
    NOTE: recovering COD for group 3/0x846df735 (BILLFR)
    SUCCESS: completed COD recovery for group 3/0x846df735 (BILLFR)
    NOTE: recovering COD for group 6/0x846df738 (DWAREDG)
    SUCCESS: completed COD recovery for group 6/0x846df738 (DWAREDG)
    NOTE: recovering COD for group 7/0x846df739 (DWAREFB)
    SUCCESS: completed COD recovery for group 7/0x846df739 (DWAREFB)
    NOTE: recovering COD for group 8/0x846df73a (INTERDG)
    SUCCESS: completed COD recovery for group 8/0x846df73a (INTERDG)
    NOTE: recovering COD for group 9/0x846df73b (INTERFB)
    SUCCESS: completed COD recovery for group 9/0x846df73b (INTERFB)
  • 5. Re: ORA 15063 ASM discovered an insufficient number of disks for diskgroup
    585179 Expert
    Currently Being Moderated
    Hi,


    I looks like you've lost the physical disk for diskgroup DUARFFB and DUARFDG


    Check from v$asm_disk and v$asm_diskgroup which disks are belong to both diskgroup then check physically if the disks are exist and have correct permissions


    Cheers

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points