我有以下设置
Oracle Solaris 10 -> 5.10 Generic_147147-26 sun4v sparc
Oracle Database 11g 企业版版本 11.2.0.1.0 - 64 位生产
适用于 Solaris 10 sparc 的 Oracle Solaris Cluster 3.3u2
适用于 Solaris 10 sparc 的 Oracle Solaris Cluster Geographic Edition 3.3u2
我安装了带有 ZFS 的 Oracle Solaris 10,我有一个 /oradata 池,每当我重新启动/电源循环时,我的集群 ZFS 池就会消失,因为该集群无法启动 oracle 数据库资源/组每次我重新启动/电源循环集群后,我都必须手动执行
zpool import db
clrg online ora-rg
...
这可能是什么原因呢?
我唯一知道的是 db zpool,该池是使用 ora-has 资源导入的,我创建它如下所示(使用 Zpools 选项)
# /usr/cluster/bin/clresourcegroup create ora-rg
# /usr/cluster/bin/clresourcetype register SUNW.HAStoragePlus
# /usr/cluster/bin/clresource create -g ora-rg -t SUNW.HAStoragePlus -p Zpools=db ora-has
# zpool status db
pool: db
state: ONLINE
scan: none requested
config:
NAME STATE READ WRITE CKSUM
db ONLINE 0 0 0
mirror-0 ONLINE 0 0 0
c0t2d0 ONLINE 0 0 0
c0t3d0 ONLINE 0 0 0
errors: No known data errors
Booting in cluster mode
impdneilab1 console login: Apr 21 17:12:24 impdneilab1 cl_runtime: NOTICE: CMM: Node impdneilab1 (nodeid = 1) with votecount = 1 added.
Apr 21 17:12:24 impdneilab1 sendmail[642]: My unqualified host name (impdneilab1) unknown; sleeping for retry
Apr 21 17:12:24 impdneilab1 cl_runtime: NOTICE: CMM: Node impdneilab1: attempting to join cluster.
Apr 21 17:12:24 impdneilab1 cl_runtime: NOTICE: CMM: Cluster has reached quorum.
Apr 21 17:12:24 impdneilab1 cl_runtime: NOTICE: CMM: Node impdneilab1 (nodeid = 1) is up; new incarnation number = 1429629142.
Apr 21 17:12:24 impdneilab1 cl_runtime: NOTICE: CMM: Cluster members: impdneilab1.
Apr 21 17:12:24 impdneilab1 cl_runtime: NOTICE: CMM: node reconfiguration #1 completed.
Apr 21 17:12:24 impdneilab1 cl_runtime: NOTICE: CMM: Node impdneilab1: joined cluster.
Apr 21 17:12:24 impdneilab1 in.mpathd[262]: Successfully failed over from NIC nxge1 to NIC e1000g1
Apr 21 17:12:24 impdneilab1 in.mpathd[262]: Successfully failed over from NIC nxge0 to NIC e1000g0
obtaining access to all attached disks
答案1
亲爱的大家我找到了答案
https://community.oracle.com/thread/3714952?sr=inbox
在地理群集配置中,单节点群集预计会出现以下行为:
如果整个集群发生故障然后恢复,预期行为是地理版本在启动时停止本地集群上的保护组。这样做的原因是可能已发出接管命令,或者存储/数据可能不完整或不可用(如果主站点发生完全故障,尽管集群节点已恢复,但这并不意味着存储/数据完整并准备好承担站点在故障前的角色)。这也是我们要求在添加到保护组的应用程序 rgs 上设置 auto_start_on_new_cluster=false 的原因。集群重新启动后,用户需要进行干预并根据需要启动或执行故障回复程序。