4 Replies Latest reply: Jul 3, 2011 11:50 PM by 872994 RSS

    Issue for choosing disk from managed ASM

    700137
      Hello All,
      Oracle Grid Infrastructure installation(11gR2) is in progress, I am not being able to select disk from managed asm disk group, details are as listed below:
      ####################################################################
      uname -a
      Linux hostname.host.com 2.6.18-194.el5 #1 SMP Mon Mar 29 22:10:29 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux
      ####################################################################
      createdisk for ASM disk group for following disks have been completed:
      ASMDATA1
      ASMDATA21
      ASMDATA22
      OCR_VOTE01
      OCR_VOTE02
      OCR_VOTE03
      ####################################################################
      # oracleasm status
      Checking if ASM is loaded: yes
      Checking if /dev/oracleasm is mounted: yes
      ####################################################################
      # oracleasm listdisks
      ASMDATA1
      ASMDATA21
      ASMDATA22
      OCR_VOTE01
      OCR_VOTE02
      OCR_VOTE03
      ####################################################################
      $./runcluvfy.sh comp nodereach -n devrac1,devrac2 -verbose
      Pre-check for cluster services setup was successful on all the nodes.
      ####################################################################
      $./runcluvfy.sh stage -pre crsinst -n devrac1,devrac2 -verbose
      Pre-check for cluster services setup was successful.
      ####################################################################
      $./runcluvfy.sh comp nodecon -n devrac1,devrac2 -verbose
      Verification of node connectivity was successful.
      ####################################################################
      $./runcluvfy.sh comp sys -n devrac1,devrac2 -p crs -osdba crs -orainv oinstall
      Verification of system requirement was successful.
      ####################################################################
      $./runInstaller
      INSTALLATION OPTION: Install and Confgiure Grid Infrastructure for a Cluster
      INSTALLATION TYPE: Advanced Installation
      PRODUCT lANGUAGE: English
      GRID PLUG AND PLAY:
      SCAN/GNS configuration:
           cluster Name: devrac1
           SCAN Name: scan.devrac1.domain.company.net
           SCAN Port: 1521
           GNS sub Domain: devrac1.domain.company.net
           GNS VIP Address: 192.168.112.32
      CLUSTER NODE INFORMATION
           Hostname: devrac1.domain.company.net,      Hostname: devrac1.domain.company.net
           Virtual IP Name: AUTO,AUTO
           SSH Connectivity: PASS
      NETWORK INTERFACE USAGE
           Interface Name:eth0, eth1
           Subnet: 192.168.112.0,10.10.10.0
           Interface Type: Public, Private
      STORAGE OPTION: ASM
      CREATE ASM DISK GROUP
           DiskGroupname:ORCLDATA
           Redundancy: External
           If Candidate Disks is the option, does't list any disk path.
           If All Disks is the option, list all disks configured for ASM but couldn't check any disk path.
           When we click on "Next" button, following error message would be seen:
                [INS-30507] Empty ASM disk group.

      How can I select disk from managed ASM disk group here at this position? What I have missed in my installation for Oracle Grid Infrastructure?

      Thanks in advance.
      Regards,
      Suresh Gautam
        • 1. Re: Issue for choosing disk from managed ASM
          580716
          Hi suresh,

          You may want to check the discovery string on the OUI because by default OUI set discovery string to /dev/raw*. By the way you can enable the tracing for OUI to get more information on this. Also check your ASM disk scan order in the /etc/sysconfig/oracleasm file such as ORACLEASM_SCANORDER .

          It happened to me once and I had to restart oracleasm service and scan the disks again on all cluster nodes. You may want to try this.

          Regards
          Harish Kumar
          http://www.oraxperts.com
          • 2. Re: Issue for choosing disk from managed ASM
            700137
            Hello Harish,
            I don't think that there is issue of discovery string as I can see list of all disks path for ASM, but couldn't include(checked) listed disks for new ASM disk group. I couldn't see any option to trace for OUI while providing configuration for setup, it may trace the information when it starts installation. Please, correct me if I am wrong.
            Configuration of /etc/sysconfig/oracleasm is as follows:
            ORACLEASM_ENABLED=true
            ORACLEASM_UID=oracle
            ORACLEASM_GID=oinstall
            ORACLEASM_SCANBOOT=true
            ORACLEASM_SCANORDER=""
            ORACLEASM_SCANEXCLUDE=""
            How scan order can resut such a issue during installation? I couldn't understand.

            Anyway, I did modification in /etc/sysconfig/oracleasm as you have suggested, then reinitiated installation process after system reboot, modified parameters are listed below for your reference:
            ORACLEASM_SCANORDER="emcpower sd"
            ORACLEASM_SCANEXCLUDE="sda sdb sdc sdd sde sdf sdg"

            BUT COULDN'T RESOLVE THE ISSUE.

            output of "fdisk -l" is as follows, it can give you additional information:
            ========================================================================
            # fdisk -l

            Disk /dev/sda: 72.9 GB, 72999763968 bytes
            255 heads, 63 sectors/track, 8875 cylinders
            Units = cylinders of 16065 * 512 = 8225280 bytes

            Device Boot Start End Blocks Id System
            /dev/sda1 * 1 13 104391 83 Linux
            /dev/sda2 14 2053 16386300 82 Linux swap / Solaris
            /dev/sda3 2054 8875 54797715 83 Linux

            Disk /dev/sdb: 288.1 GB, 288161071104 bytes
            255 heads, 63 sectors/track, 35033 cylinders
            Units = cylinders of 16065 * 512 = 8225280 bytes

            Device Boot Start End Blocks Id System
            /dev/sdb1 1 35033 281402541 83 Linux

            Disk /dev/sdc: 287.7 GB, 287762808832 bytes
            255 heads, 63 sectors/track, 34985 cylinders
            Units = cylinders of 16065 * 512 = 8225280 bytes

            Device Boot Start End Blocks Id System
            /dev/sdc1 1 34985 281016981 83 Linux

            Disk /dev/sdd: 288.5 GB, 288559333376 bytes
            255 heads, 63 sectors/track, 35082 cylinders
            Units = cylinders of 16065 * 512 = 8225280 bytes

            Device Boot Start End Blocks Id System
            /dev/sdd1 1 1217 9775521 83 Linux
            /dev/sdd2 1218 2434 9775552+ 83 Linux
            /dev/sdd3 2435 3651 9775552+ 83 Linux
            /dev/sdd4 3652 35082 252469507+ 83 Linux

            Disk /dev/sde: 288.1 GB, 288161071104 bytes
            255 heads, 63 sectors/track, 35033 cylinders
            Units = cylinders of 16065 * 512 = 8225280 bytes

            Device Boot Start End Blocks Id System
            /dev/sde1 1 35033 281402541 83 Linux

            Disk /dev/sdf: 287.7 GB, 287762808832 bytes
            255 heads, 63 sectors/track, 34985 cylinders
            Units = cylinders of 16065 * 512 = 8225280 bytes

            Device Boot Start End Blocks Id System
            /dev/sdf1 1 34985 281016981 83 Linux

            Disk /dev/sdg: 288.5 GB, 288559333376 bytes
            255 heads, 63 sectors/track, 35082 cylinders
            Units = cylinders of 16065 * 512 = 8225280 bytes

            Device Boot Start End Blocks Id System
            /dev/sdg1 1 1217 9775521 83 Linux
            /dev/sdg2 1218 2434 9775552+ 83 Linux
            /dev/sdg3 2435 3651 9775552+ 83 Linux
            /dev/sdg4 3652 35082 252469507+ 83 Linux

            Disk /dev/emcpowera: 288.1 GB, 288161071104 bytes
            255 heads, 63 sectors/track, 35033 cylinders
            Units = cylinders of 16065 * 512 = 8225280 bytes

            Device Boot Start End Blocks Id System
            /dev/emcpowera1 1 35033 281402541 83 Linux

            Disk /dev/emcpowerb: 287.7 GB, 287762808832 bytes
            255 heads, 63 sectors/track, 34985 cylinders
            Units = cylinders of 16065 * 512 = 8225280 bytes

            Device Boot Start End Blocks Id System
            /dev/emcpowerb1 1 34985 281016981 83 Linux

            Disk /dev/emcpowerc: 288.5 GB, 288559333376 bytes
            255 heads, 63 sectors/track, 35082 cylinders
            Units = cylinders of 16065 * 512 = 8225280 bytes

            Device Boot Start End Blocks Id System
            /dev/emcpowerc1 1 1217 9775521 83 Linux
            /dev/emcpowerc2 1218 2434 9775552+ 83 Linux
            /dev/emcpowerc3 2435 3651 9775552+ 83 Linux
            /dev/emcpowerc4 3652 35082 252469507+ 83 Linux
            ========================================================================

            Any kind of follow up will be highly appriciated.

            Regards,
            Suresh Gautam
            • 3. Re: Issue for choosing disk from managed ASM
              580716
              When you enable trace for OUI, it will tell you on what basis OUI is disabling those disk in the OUI but you will need to analyze the trace to find out that. If you are still stick then try recreating the ASM disks from scratch. Alternatively check the output of the following command and set the ASM discovery string to ASM discovery string used with this command:

              /usr/sbin/oracleasm-discover <your discovery string>

              For example, if you have used ASMLIB to create ASM disks then you will be probably using ORCL:* as ASM diskcovery string. Following is output from my test lab environment:

              [grid@racnode01 ~]$ /usr/sbin/oracleasm-discover ORCL:*
              Using ASMLib from /opt/oracle/extapi/64/asm/orcl/1/libasm.so
              [ASM Library - Generic Linux, version 2.0.4 (KABI_V2)]
              Discovered disk: ORCL:ASMDATA01 [209715072 blocks (107374116864 bytes), maxio 512]
              Discovered disk: ORCL:ASMDATA02 [209715072 blocks (107374116864 bytes), maxio 512]
              Discovered disk: ORCL:ASMDATA03 [209715072 blocks (107374116864 bytes), maxio 512]
              Discovered disk: ORCL:ASMDATA04 [209715072 blocks (107374116864 bytes), maxio 512]
              Discovered disk: ORCL:ASMDATA05 [209715072 blocks (107374116864 bytes), maxio 512]
              Discovered disk: ORCL:ASMDATA06 [209715072 blocks (107374116864 bytes), maxio 512]
              Discovered disk: ORCL:ASMDATA07 [209715072 blocks (107374116864 bytes), maxio 512]
              Discovered disk: ORCL:ASMDATA08 [209715072 blocks (107374116864 bytes), maxio 512]
              Discovered disk: ORCL:ASMDATA09 [209715072 blocks (107374116864 bytes), maxio 512]
              Discovered disk: ORCL:ASMDATA10 [209715072 blocks (107374116864 bytes), maxio 512]
              Discovered disk: ORCL:ASMDATA11 [209715072 blocks (107374116864 bytes), maxio 512]
              Discovered disk: ORCL:ASMDATA12 [209715072 blocks (107374116864 bytes), maxio 512]
              Discovered disk: ORCL:OCR_VOTE1 [2097024 blocks (1073676288 bytes), maxio 512]
              Discovered disk: ORCL:OCR_VOTE2 [2097024 blocks (1073676288 bytes), maxio 512]
              Discovered disk: ORCL:OCR_VOTE3 [2097024 blocks (1073676288 bytes), maxio 512]
              Discovered disk: ORCL:OCR_VOTE4 [2097024 blocks (1073676288 bytes), maxio 512]
              Discovered disk: ORCL:OCR_VOTE5 [2097024 blocks (1073676288 bytes), maxio 512]
              [grid@racnode01 ~]$

              Oracle use oracleasm-discovery internally.

              Any correction is welcome.

              Regards
              Harish Kumar
              • 4. Re: Issue for choosing disk from managed ASM
                872994
                Hi all,

                I had this problem too.

                In "Create ASM Disk Group" page, you should pay attention to Status of disks, if this status is "Candidate" then you could select the disk, otherwise you could not select the disk. For example, status may be "MEMBER", this means that the disk is assigned already and you can't select it for new disk group.
                Your scenario may be look likes to my scenario:
                I had installed unsuccessful grid infrastructure 11g and when I want to reinstall the grid infrastructure again, I face the problem.
                So to resolve this problem you should delete the disks and recreate them.
                1-oracleasm deletedisk DISKn
                2-oracleasm createdisk DISK1 /dev/sdn1

                Bye.