4 Replies Latest reply: Oct 25, 2012 9:50 AM by user1760184 RSS

    Oracle restart starts disabled ASM diskgroup?

    user1760184
      I'm confused. I've read the documentation which hasn't helped me. I've scoured the forums and can't find a similar problem, so thought I'd open my question to this forum.

      I may have misunderstood, but my understanding is that should a service, instance or diskgroup be disabled on a node, then it should not be started on restart. However upon restart I find a diskgroup which is disabled on a node is started on that node. For info I am running 11gR2 11.2.0.3 x86-64 clusterware on RHEL5.

      I have a new installation of RAC and I've been doing some testing. I created several diskgroups including DATA and FRA after creating my ASM instance. I have separate diskgroups to hold the ASM spfile, vote and ocr, so currently DATA and FRA are not being used at all.

      I created DATA and FRA on node1. This started them on node1. I then started FRA on node2. So initial state of DATA and FRA:
      ora.DATA.dg
                     ONLINE  ONLINE       node1
                     OFFLINE OFFLINE      node2
      ora.FRA.dg
                     ONLINE  ONLINE       node1
                     ONLINE  ONLINE       node2
      I then issued the following:
      node1> srvctl stop diskgroup -g FRA -n node1
      node1> srvctl disable diskgroup -g FRA -n node1
      Both completed successfully. New status:
      ora.DATA.dg
                     ONLINE  ONLINE       node1
                     OFFLINE OFFLINE      node2
      ora.FRA.dg
                     OFFLINE OFFLINE      node1
                     ONLINE  ONLINE       node2
      
      node1> srvctl status diskgroup -g FRA
      Disk Group FRA is running on node2
      I've performed two separate tests with the same results. test 1 - bounce node1, test 2 - stopped the whole cluster and restarted:
      node1> crsctl stop cluster -all
      node1> crsctl start cluster -all
      The status after restart:
      ora.DATA.dg
                     ONLINE  ONLINE       node1
                     OFFLINE OFFLINE      node2
      ora.FRA.dg
                     ONLINE  ONLINE       node1
                     ONLINE  ONLINE       node2
      To me the FRA being ONLINE on node1 is totally unexpected, I would expect that since FRA is disabled on node1, it should not be started. Interestingly DATA which has not yet been started on node2 does not start on node2.

      Did the disable command work? I tried it again:
      node1> srvctl disable  diskgroup -g FRA -n node1
      PRCC-1013 : FRA was already disabled on node1
      PRCR-1003 : Resource ora.FRA.dg is already disabled
      Does this seem wrong to anyone else?
      Can anyone explain the restart behaviour?

      Thanks for reading,
      Andy