cluster.framework 求教 stderr metaset there are no existing database

xxxx321

Solaris Cluster issue, Log as following:

root@sunha02 # scswitch -z -g oracle-rg -h sunha01  
scswitch: Resource group oracle-rg failed to start on chosen node and may fail over to other node(s)


syslog 如下
Sep 19 14:50:25 sunha01 Cluster.RGM.rgmd: [ID 707948 daemon.notice] launching method <hafoip_prenet_start> for resource <plmmcsg>, resource group <oracle-rg>, timeout <300> seconds
Sep 19 14:50:26 sunha01 Cluster.RGM.rgmd: [ID 736390 daemon.notice] method <hafoip_prenet_start> completed successfully for resource <plmmcsg>, resource group <oracle-rg>, time used: 0% of timeout <300 seconds>
Sep 19 14:50:26 sunha01 Cluster.RGM.rgmd: [ID 707948 daemon.notice] launching method <hastorageplus_prenet_start> for resource <oracle-ha>, resource group <oracle-rg>, timeout <1800> seconds
Sep 19 14:50:28 sunha01 Cluster.Framework: [ID 801593 daemon.notice] stdout: becoming primary for plmds
Sep 19 14:50:29 sunha01 Cluster.Framework: [ID 801593 daemon.error] stderr: metaset: sunha01: plmds: there are no existing databases
Sep 19 14:50:29 sunha01 Cluster.Framework: [ID 801593 daemon.error] stderr: metaset: sunha01: plmds: must be owner of the set for this command
Sep 19 14:51:04 sunha01 Cluster.Framework: [ID 801593 daemon.notice] stdout: becoming primary for plmds
Sep 19 14:51:05 sunha01 Cluster.Framework: [ID 801593 daemon.error] stderr: metaset: sunha01: plmds: there are no existing databases
Sep 19 14:51:05 sunha01 Cluster.Framework: [ID 801593 daemon.error] stderr: metaset: sunha01: plmds: must be owner of the set for this command
Sep 19 14:51:08 sunha01 SC[SUNW.HAStoragePlus:2,oracle-rg,oracle-ha,hastorageplus_prenet_start_private]: [ID 500133 daemon.warning] Device switchover of global service plmds associated with path /u02 to this node failed: Node failed to become the primary.
Sep 19 14:51:08 sunha01 SC[SUNW.HAStoragePlus:2,oracle-rg,oracle-ha,hastorageplus_prenet_start_private]: [ID 500133 daemon.warning] Device switchover of global service plmds associated with path /u03 to this node failed: Node failed to become the primary.
Sep 19 14:51:08 sunha01 SC[SUNW.HAStoragePlus:2,oracle-rg,oracle-ha,hastorageplus_prenet_start_private]: [ID 790080 daemon.error] Global service plmds associated with path /u02 is unable to become a primary on node 1.
Sep 19 14:51:08 sunha01 Cluster.RGM.rgmd: [ID 938318 daemon.error] Method <hastorageplus_prenet_start> failed on resource <oracle-ha> in resource group <oracle-rg> [exit code <1>, time used: 2% of timeout <1800 seconds>]
Sep 19 14:51:08 sunha01 Cluster.RGM.rgmd: [ID 707948 daemon.notice] launching method <hastorageplus_stop> for resource <oracle-ha>, resource group <oracle-rg>, timeout <1800> seconds
Sep 19 14:51:08 sunha01 Cluster.RGM.rgmd: [ID 736390 daemon.notice] method <hastorageplus_stop> completed successfully for resource <oracle-ha>, resource group <oracle-rg>, time used: 0% of timeout <1800 seconds>
Sep 19 14:51:08 sunha01 Cluster.RGM.rgmd: [ID 707948 daemon.notice] launching method <hafoip_stop> for resource <plmmcsg>, resource group <oracle-rg>, timeout <300> seconds
Sep 19 14:51:08 sunha01 ip: [ID 347787 kern.notice] TCP_IOC_ABORT_CONN: local = 192.168.099.070:0, remote = 000.000.000.000:0, start = -2, end = 6
Sep 19 14:51:08 sunha01 ip: [ID 440816 kern.notice] TCP_IOC_ABORT_CONN: aborted 0 connection
Sep 19 14:51:08 sunha01 Cluster.RGM.rgmd: [ID 736390 daemon.notice] method <hafoip_stop> completed successfully for resource <plmmcsg>, resource group <oracle-rg>, time used: 0% of timeout <300 seconds>
Sep 19 14:51:08 sunha01 Cluster.RGM.rgmd: [ID 707948 daemon.notice] launching method <hastorageplus_postnet_stop> for resource <oracle-ha>, resource group <oracle-rg>, timeout <1800> seconds
Sep 19 14:51:09 sunha01 Cluster.RGM.rgmd: [ID 736390 daemon.notice] method <hastorageplus_postnet_stop> completed successfully for resource <oracle-ha>, resource group <oracle-rg>, time used: 0% of timeout <1800 seconds>


求教原因, 请各位大侠赐教

doging

metadb检查本地metadb是否正常
format检查共享硬盘是否正常，如果正常，检查分区表s７是否存在

xxxx321

多谢楼上  

if it maybe caused by bug 6426463?

xxxx321

不好意思，我是菜鸟， 各位大侠 ，发现如下问题，不知如何修复？

节点1 的metadb 比节点2 要少，不知道是否存在问题？
sunha01>#metadb
        flags           first blk       block count
     a m  p  luo        16              8192            /dev/dsk/c0t0d0s7
     a    p  luo        8208            8192            /dev/dsk/c0t0d0s7
     a    p  luo        16400           8192            /dev/dsk/c0t0d0s7
     a    p  luo        16              8192            /dev/dsk/c0t1d0s7
     a    p  luo        8208            8192            /dev/dsk/c0t1d0s7
     a    p  luo        16400           8192            /dev/dsk/c0t1d0s7

root@sunha02 # metadb
        flags           first blk       block count
     a m  p  luo        16              8192            /dev/dsk/c1t0d0s7
     a    p  luo        8208            8192            /dev/dsk/c1t0d0s7
     a    p  luo        16400           8192            /dev/dsk/c1t0d0s7
     a    p  luo        16              8192            /dev/dsk/c1t1d0s7
     a    p  luo        8208            8192            /dev/dsk/c1t1d0s7
     a    p  luo        16400           8192            /dev/dsk/c1t1d0s7
     a    p  luo        16              8192            /dev/dsk/c1t2d0s7
     a    p  luo        8208            8192            /dev/dsk/c1t2d0s7
     a    p  luo        16400           8192            /dev/dsk/c1t2d0s7
     a    p  luo        16              8192            /dev/dsk/c1t3d0s7
     a    p  luo        8208            8192            /dev/dsk/c1t3d0s7
     a    p  luo        16400           8192            /dev/dsk/c1t3d0s7
     a    p  luo        16              8192            /dev/dsk/c1t4d0s7
     a    p  luo        8208            8192            /dev/dsk/c1t4d0s7
     a    p  luo        16400           8192            /dev/dsk/c1t4d0s7
     a    p  luo        16              8192            /dev/dsk/c1t5d0s7
     a    p  luo        8208            8192            /dev/dsk/c1t5d0s7
     a    p  luo        16400           8192            /dev/dsk/c1t5d0s7
root@sunha02 #

xxxx321

metadb  -d/a