3 Replies Latest reply: Feb 19, 2014 12:36 PM by kgaur RSS

    ORA-15003 diskgroup already mounted another lock name space - 11g RAC using VMware shared disks

    kgaur

      Hi All,

       

      I am trying to install Oracle RAC 11gR2 on 2 OEL5 machines, with shared VM disks as shared storage for ASM disks.

       

      I am facing getting the following error while running root.sh on second node.

       

      DiskGroup CRS creation failed with the following message:

      ORA-15018: diskgroup cannot be created

      ORA-15017: diskgroup "CRS" cannot be mounted

      ORA-15003: diskgroup "CRS" already mounted in another lock name space

       

       

      Configuration of ASM failed, see logs for details

      Did not succssfully configure and start ASM

      CRS-2500: Cannot stop resource 'ora.crsd' as it is not running

      CRS-4000: Command Stop failed, or completed with errors.

      Command return code of 1 (256) from command: /u01/app/11.2.0/grid/bin/crsctl stop resource ora.crsd -init

      Stop of resource "ora.crsd -init" failed

      Failed to stop CRSD

       

      Here is what I found in the install log:

       

      2014-02-19 09:42:12: Querying for existing CSS voting disks

      2014-02-19 09:42:12: Performing initial configuration for cluster

      2014-02-19 09:42:13: Start of resource "ora.ctssd -init" Succeeded

      2014-02-19 09:42:13: Configuring ASM via ASMCA

      2014-02-19 09:42:14: Executing as grid: /u01/app/11.2.0/grid/bin/asmca -silent -diskGroupName CRS -diskList ORCL:CRS1,ORCL:CRS3,ORCL:CRS2 -redundancy NORMAL -configureL

      ocalASM

      2014-02-19 09:42:14: Running as user grid: /u01/app/11.2.0/grid/bin/asmca -silent -diskGroupName CRS -diskList ORCL:CRS1,ORCL:CRS3,ORCL:CRS2 -redundancy NORMAL -configu

      reLocalASM

      2014-02-19 09:42:14:   Invoking "/u01/app/11.2.0/grid/bin/asmca -silent -diskGroupName CRS -diskList ORCL:CRS1,ORCL:CRS3,ORCL:CRS2 -redundancy NORMAL -configureLocalASM

      " as user "grid"

      2014-02-19 09:42:47: Configuration of ASM failed, see logs for details

      2014-02-19 09:42:47: Did not succssfully configure and start ASM

      2014-02-19 09:42:47: Exiting exclusive mode

      2014-02-19 09:42:47: Command return code of 1 (256) from command: /u01/app/11.2.0/grid/bin/crsctl stop resource ora.crsd -init

      2014-02-19 09:42:47: Stop of resource "ora.crsd -init" failed

      2014-02-19 09:42:47: Failed to stop CRSD

      2014-02-19 09:43:34: Initial cluster configuration failed.  See /u01/app/11.2.0/grid/cfgtoollogs/crsconfig/rootcrs_rac2.log for details

       

       

      I ran root.sh on second node only after it completed on the first node.

      From the VMware configuration angle, I have marked the disk.locking= "FALSE"

       

      It is obvious that the CRS diskgroup would be mounted already by the first node. diskgroup "CRS" already mounted in another lock name space

      there is an initialization parameter LOCK_NAME_SPACE related to this, but that has to be set by the OUI itself when installing the clusterware/asm.

       

      All help welcome.

       

      Please let know what more information could help

       

      Regards

        • 1. Re: ORA-15003 diskgroup already mounted another lock name space - 11g RAC using VMware shared disks
          Baris Yildirim

          Hi,

          it seems you have mounted the disks to another server.

           

          Regards

          • 2. Re: ORA-15003 diskgroup already mounted another lock name space - 11g RAC using VMware shared disks
            kgaur

            Hi Baris,

             

            Here is the configuration scenario:

             

            nodes           non-shared_Disk     Shared_disks

            RAC1          /dev/sda

                                                              /dev/sdb1, /dev/sdc1, /dev/sdd1, /dev/sde1, /dev/sdf1     (Independent, persistent setting in vmware)                  

            RAC2           /dev/sda

             

            Installation is proceeding from RAC1 node and RAC2 is remote node.

            So .. yes, the disks are mounted in the RAC1 node too. But they have to be coz' they are shared.

             

            Please elucidate if i haven't understood what you meant correctly.

             

            Both the nodes are able to access the shared disks /dev/sd(b-f)1

             

            I stamped these logical volumes as asm disks using "oracleasm" on RAC1 as :

             

            /dev/sdb1     DATA

            /dev/sdc1     FRA

            /dev/sdd1     CRS1

            /dev/sde1     CRS2

            /dev/sdf1     CRS3

             

            "oracleasm listdisks" lists the ASM disks on both nodes. So definitely both nodes are able to access these disks.

             

            Disks CRS(1-3) were used to create the diskgroup CRS during the OUI run to install grid infra.

             

            Please let know what more information could help

             

            Regards

            • 3. Re: ORA-15003 diskgroup already mounted another lock name space - 11g RAC using VMware shared disks
              kgaur

              silly silly oversight ..

               

              had set ORACLE_SID as +ASM1 on both the nodes...

               

              set it to +ASM2 on second node and ran fresh install ..

               

              went like a breeze ..

               

              I've heard that it might also happen if the sys-network-config is not set properly ..

               

              eg. both machines using same name , say rac1 ... NOT TESTED ...

               

              It is very easy to miss one or two things with using VMware machine cloning.

               

              gotta have a checklist of such things

               

              Cheers !!