ORA-01078 ORA-29701 11g单机asm系统启动后不能启动asm
NAME=ora.cssd
TYPE=ora.cssd.type
ACTION_SCRIPT=
ACTIVE_PLACEMENT=0
-bash-3.2$ crs_stat -p ora.diskmon
--再次手动启动asm
--成功,之后启动数据库顺利
--其他相关服务
--设置自动启动css后资源状态
-bash-3.2$ crsctl modify resource "ora.cssd" -attr "AUTO_START=1"
-bash-3.2$ crs_stat -p ora.cssd
NAME=ora.cssd
TYPE=ora.cssd.type
ACTION_SCRIPT=
ACTIVE_PLACEMENT=0
由于在之前的版本中ora.diskmon和ora.cssd服务是互相依赖的,及这两个服务中随便停止那个两个都会停止,同样的随便启动那个两个都会启动。
[root@osdbso ~]# crs_stat -p ora.cssd
NAME=ora.cssd
TYPE=ora.cssd.type
ACTION_SCRIPT=
ACTIVE_PLACEMENT=0
AUTO_START=never
CHECK_INTERVAL=30
DESCRIPTION="Resource type for CSSD"
FAILOVER_DELAY=0
FAILURE_INTERVAL=3
FAILURE_THRESHOLD=5
HOSTING_MEMBERS=
PLACEMENT=balanced
RESTART_ATTEMPTS=5
SCRIPT_TIMEOUT=600
START_TIMEOUT=600
STOP_TIMEOUT=900
UPTIME_THRESHOLD=1m
发现两者的随has自动启动属性都是never,以为和这个有关,然后都修改为随has自动启动:
crsctl modify resource "ora.cssd^C-attr "AUTO_START=1"
然后从其cssd或者diskmon的服务:
启动的时候也提示diskmon服务成功启动,但是查依然是offline状态,并且cssd服务的日志里面存着如下信息:
修改时间 26-SEP-2011 类型 ANNOUNCEMENT 状态 PUBLISHED
In this Document
Prior to 11.2.0.3:
ps -ef| grep diskmon.bin
grid 3361 3166 0 22:57 ? 00:00:00 /ocw/grid/bin/diskmon.bin -d -f
On 11.2.0.3:
ps -ef| grep diskmon.bin
===========================
--昨天搭的11g单机asm
--os 关闭之后重新启动后启动asm报错
--如下:
--os 关闭之后重新启动后启动asm报错
--如下:
[root@localhost init.d]# su - grid
-bash-3.2$ sqlplus / as sysasm
SQL*Plus: Release 11.2.0.1.0 Production on Thu Jan 5 10:44:42 2012
Copyright (c) 1982, 2009, Oracle. All rights reserved.
Connected to an idle instance.
SQL> startup
ORA-01078: failure in processing system parameters
ORA-29701: unable to connect to Cluster Synchronization Service
SQL>
ORA-29701: unable to connect to Cluster Synchronization Service
SQL>
--报错css没有启动
--使用crs_stat命令查看css状态
--发现AUTO_START=never
--也就是说其实css还没有设定为自动启动
--又查看了diskmon,也同样是不自动启动
--使用crs_stat命令查看css状态
--发现AUTO_START=never
--也就是说其实css还没有设定为自动启动
--又查看了diskmon,也同样是不自动启动
-bash-3.2$ crs_stat -p ora.cssd
NAME=ora.cssd
TYPE=ora.cssd.type
ACTION_SCRIPT=
ACTIVE_PLACEMENT=0
AUTO_START=never
CHECK_INTERVAL=30
DESCRIPTION="Resource type for CSSD"
FAILOVER_DELAY=0
FAILURE_INTERVAL=3
FAILURE_THRESHOLD=5
HOSTING_MEMBERS=
PLACEMENT=balanced
RESTART_ATTEMPTS=5
SCRIPT_TIMEOUT=600
START_TIMEOUT=600
STOP_TIMEOUT=900
UPTIME_THRESHOLD=1m
DESCRIPTION="Resource type for CSSD"
FAILOVER_DELAY=0
FAILURE_INTERVAL=3
FAILURE_THRESHOLD=5
HOSTING_MEMBERS=
PLACEMENT=balanced
RESTART_ATTEMPTS=5
SCRIPT_TIMEOUT=600
START_TIMEOUT=600
STOP_TIMEOUT=900
UPTIME_THRESHOLD=1m
-bash-3.2$ crs_stat -p ora.diskmon
NAME=ora.diskmon
TYPE=ora.diskmon.type
ACTION_SCRIPT=
ACTIVE_PLACEMENT=0
TYPE=ora.diskmon.type
ACTION_SCRIPT=
ACTIVE_PLACEMENT=0
AUTO_START=never
CHECK_INTERVAL=20
DESCRIPTION="Resource type for Diskmon"
FAILOVER_DELAY=0
FAILURE_INTERVAL=3
FAILURE_THRESHOLD=5
HOSTING_MEMBERS=
PLACEMENT=balanced
RESTART_ATTEMPTS=10
SCRIPT_TIMEOUT=60
START_TIMEOUT=60
STOP_TIMEOUT=60
UPTIME_THRESHOLD=5s
DESCRIPTION="Resource type for Diskmon"
FAILOVER_DELAY=0
FAILURE_INTERVAL=3
FAILURE_THRESHOLD=5
HOSTING_MEMBERS=
PLACEMENT=balanced
RESTART_ATTEMPTS=10
SCRIPT_TIMEOUT=60
START_TIMEOUT=60
STOP_TIMEOUT=60
UPTIME_THRESHOLD=5s
--手动启动css
--启动过程中diskmon被一起拉起来
--启动后查询集群资源状况如下:
--启动过程中diskmon被一起拉起来
--启动后查询集群资源状况如下:
-bash-3.2$ crsctl start resource ora.cssd
CRS-2672: Attempting to start 'ora.cssd' on 'localhost'
CRS-2679: Attempting to clean 'ora.diskmon' on 'localhost'
CRS-2681: Clean of 'ora.diskmon' on 'localhost' succeeded
CRS-2672: Attempting to start 'ora.diskmon' on 'localhost'
CRS-2676: Start of 'ora.diskmon' on 'localhost' succeeded
CRS-2676: Start of 'ora.cssd' on 'localhost' succeeded
CRS-2679: Attempting to clean 'ora.diskmon' on 'localhost'
CRS-2681: Clean of 'ora.diskmon' on 'localhost' succeeded
CRS-2672: Attempting to start 'ora.diskmon' on 'localhost'
CRS-2676: Start of 'ora.diskmon' on 'localhost' succeeded
CRS-2676: Start of 'ora.cssd' on 'localhost' succeeded
-bash-3.2$ crs_stat -t
Name Type Target State Host
------------------------------------------------------------
ora.DATA.dg ora....up.type OFFLINE OFFLINE
ora....ER.lsnr ora....er.type ONLINE ONLINE localhost
ora.asm ora.asm.type OFFLINE OFFLINE
ora.cssd ora.cssd.type ONLINE ONLINE localhost
ora.db11.db ora....se.type OFFLINE OFFLINE
ora.diskmon ora....on.type ONLINE ONLINE localhost
------------------------------------------------------------
ora.DATA.dg ora....up.type OFFLINE OFFLINE
ora....ER.lsnr ora....er.type ONLINE ONLINE localhost
ora.asm ora.asm.type OFFLINE OFFLINE
ora.cssd ora.cssd.type ONLINE ONLINE localhost
ora.db11.db ora....se.type OFFLINE OFFLINE
ora.diskmon ora....on.type ONLINE ONLINE localhost
--再次手动启动asm
--成功,之后启动数据库顺利
-bash-3.2$ sqlplus / as sysasm
SQL*Plus: Release 11.2.0.1.0 Production on Thu Jan 5 10:48:16 2012
Copyright (c) 1982, 2009, Oracle. All rights reserved.
Connected to an idle instance.
SQL*Plus: Release 11.2.0.1.0 Production on Thu Jan 5 10:48:16 2012
Copyright (c) 1982, 2009, Oracle. All rights reserved.
Connected to an idle instance.
SQL> startup
ASM instance started
Total System Global Area 284565504 bytes
Fixed Size 1336036 bytes
Variable Size 258063644 bytes
ASM Cache 25165824 bytes
ASM diskgroups mounted
SQL>
Fixed Size 1336036 bytes
Variable Size 258063644 bytes
ASM Cache 25165824 bytes
ASM diskgroups mounted
SQL>
--其他相关服务
--has默认是自动启动的
--手动启停命令如下
--手动启停命令如下
--查看状态
crsctl check has
crsctl check has
--关启自动启停
crsctl disable has
crsctl enable has
crsctl disable has
crsctl enable has
--手动启停
crsctl start has
crsctl stop has
crsctl start has
crsctl stop has
--css和diskmon可以设置为自动启动
--开启css和diskmon自动启动
crsctl modify resource "ora.cssd" -attr "AUTO_START=1"
crsctl modify resource "ora.diskmon" -attr "AUTO_START=1"
--开启css和diskmon自动启动
crsctl modify resource "ora.cssd" -attr "AUTO_START=1"
crsctl modify resource "ora.diskmon" -attr "AUTO_START=1"
--关闭css和diskmon自动启动
crsctl modify resource "ora.cssd" -attr "AUTO_START=never"
crsctl modify resource "ora.diskmon" -attr "AUTO_START=never"
crsctl modify resource "ora.cssd" -attr "AUTO_START=never"
crsctl modify resource "ora.diskmon" -attr "AUTO_START=never"
--设置自动启动css后资源状态
-bash-3.2$ crsctl modify resource "ora.cssd" -attr "AUTO_START=1"
-bash-3.2$ crs_stat -p ora.cssd
NAME=ora.cssd
TYPE=ora.cssd.type
ACTION_SCRIPT=
ACTIVE_PLACEMENT=0
AUTO_START=1
CHECK_INTERVAL=30
DESCRIPTION="Resource type for CSSD"
FAILOVER_DELAY=0
FAILURE_INTERVAL=3
FAILURE_THRESHOLD=5
HOSTING_MEMBERS=
PLACEMENT=balanced
RESTART_ATTEMPTS=5
SCRIPT_TIMEOUT=600
START_TIMEOUT=600
STOP_TIMEOUT=900
UPTIME_THRESHOLD=1m
DESCRIPTION="Resource type for CSSD"
FAILOVER_DELAY=0
FAILURE_INTERVAL=3
FAILURE_THRESHOLD=5
HOSTING_MEMBERS=
PLACEMENT=balanced
RESTART_ATTEMPTS=5
SCRIPT_TIMEOUT=600
START_TIMEOUT=600
STOP_TIMEOUT=900
UPTIME_THRESHOLD=1m
今天装了个Oracle 11.2.0.3的环境,结果发现diskmon总是处于offline状态:
[root@osdbso ~]# crs_stat -t
Name Type Target State Host
------------------------------------------------------------
ora.DATA.dg ora....up.type ONLINE ONLINE osdbso
ora....ER.lsnr ora....er.type ONLINE ONLINE osdbso
ora.asm ora.asm.type ONLINE ONLINE osdbso
ora.cssd ora.cssd.type ONLINE ONLINE osdbso
ora.diskmon ora....on.type OFFLINE OFFLINE
ora.evmd ora.evm.type ONLINE ONLINE osdbso
ora.oemrep.db ora....se.type ONLINE ONLINE osdbso
ora.ons ora.ons.type OFFLINE OFFLINE
Name Type Target State Host
------------------------------------------------------------
ora.DATA.dg ora....up.type ONLINE ONLINE osdbso
ora....ER.lsnr ora....er.type ONLINE ONLINE osdbso
ora.asm ora.asm.type ONLINE ONLINE osdbso
ora.cssd ora.cssd.type ONLINE ONLINE osdbso
ora.diskmon ora....on.type OFFLINE OFFLINE
ora.evmd ora.evm.type ONLINE ONLINE osdbso
ora.oemrep.db ora....se.type ONLINE ONLINE osdbso
ora.ons ora.ons.type OFFLINE OFFLINE
由于在之前的版本中ora.diskmon和ora.cssd服务是互相依赖的,及这两个服务中随便停止那个两个都会停止,同样的随便启动那个两个都会启动。
可是在上面的案例中,我发现cssd服务是起来的。查看一下这两个服务的属性
[root@osdbso ~]# crs_stat -p ora.diskmon
NAME=ora.diskmon
TYPE=ora.diskmon.type
ACTION_SCRIPT=
ACTIVE_PLACEMENT=0
AUTO_START=never
CHECK_INTERVAL=3
DESCRIPTION="Resource type for Diskmon"
FAILOVER_DELAY=0
FAILURE_INTERVAL=3
FAILURE_THRESHOLD=5
HOSTING_MEMBERS=
PLACEMENT=balanced
RESTART_ATTEMPTS=10
SCRIPT_TIMEOUT=60
START_TIMEOUT=600
STOP_TIMEOUT=60
UPTIME_THRESHOLD=5s
NAME=ora.diskmon
TYPE=ora.diskmon.type
ACTION_SCRIPT=
ACTIVE_PLACEMENT=0
AUTO_START=never
CHECK_INTERVAL=3
DESCRIPTION="Resource type for Diskmon"
FAILOVER_DELAY=0
FAILURE_INTERVAL=3
FAILURE_THRESHOLD=5
HOSTING_MEMBERS=
PLACEMENT=balanced
RESTART_ATTEMPTS=10
SCRIPT_TIMEOUT=60
START_TIMEOUT=600
STOP_TIMEOUT=60
UPTIME_THRESHOLD=5s
[root@osdbso ~]# crs_stat -p ora.cssd
NAME=ora.cssd
TYPE=ora.cssd.type
ACTION_SCRIPT=
ACTIVE_PLACEMENT=0
AUTO_START=never
CHECK_INTERVAL=30
DESCRIPTION="Resource type for CSSD"
FAILOVER_DELAY=0
FAILURE_INTERVAL=3
FAILURE_THRESHOLD=5
HOSTING_MEMBERS=
PLACEMENT=balanced
RESTART_ATTEMPTS=5
SCRIPT_TIMEOUT=600
START_TIMEOUT=600
STOP_TIMEOUT=900
UPTIME_THRESHOLD=1m
发现两者的随has自动启动属性都是never,以为和这个有关,然后都修改为随has自动启动:
crsctl modify resource "ora.diskmon" -attr "AUTO_START=1"
crsctl modify resource "ora.cssd^C-attr "AUTO_START=1"
然后从其cssd或者diskmon的服务:
[root@osdbso ~]# crsctl stop resource ora.cssd
CRS-2673: Attempting to stop 'ora.cssd' on 'osdbso'
CRS-2677: Stop of 'ora.cssd' on 'osdbso' succeeded
[root@osdbso ~]# crsctl start resource ora.diskmon
CRS-2672: Attempting to start 'ora.diskmon' on 'osdbso'
CRS-2672: Attempting to start 'ora.cssd' on 'osdbso'
CRS-2676: Start of 'ora.diskmon' on 'osdbso' succeeded
CRS-2676: Start of 'ora.cssd' on 'osdbso' succeeded
CRS-2673: Attempting to stop 'ora.cssd' on 'osdbso'
CRS-2677: Stop of 'ora.cssd' on 'osdbso' succeeded
[root@osdbso ~]# crsctl start resource ora.diskmon
CRS-2672: Attempting to start 'ora.diskmon' on 'osdbso'
CRS-2672: Attempting to start 'ora.cssd' on 'osdbso'
CRS-2676: Start of 'ora.diskmon' on 'osdbso' succeeded
CRS-2676: Start of 'ora.cssd' on 'osdbso' succeeded
启动的时候也提示diskmon服务成功启动,但是查依然是offline状态,并且cssd服务的日志里面存着如下信息:
2012-05-01 10:46:43.735: [ default][3976595200]CELL communication is configured to use 0 interface(s):
2012-05-01 10:46:43.735: [ default][3976595200]Kgzf_ini_begin: diskmon is disabled
2012-05-01 10:46:43.735: [ CSSD][3976595200]clssscSAGEInitFencing: kgzf fence initialization successfully started
直接就误解了,没办法还是上MOS把,结果不查不知道一查吓一跳,原来在11.2.0.3版本的非Exadata数据库上,diskmon的服务是被disable掉的。
直接就误解了,没办法还是上MOS把,结果不查不知道一查吓一跳,原来在11.2.0.3版本的非Exadata数据库上,diskmon的服务是被disable掉的。
请看官文:
11.2.0.3 Grid Infrastructure diskmon Will be Offline by Default in Non-Exadata Environment [ID 1346881.1]
修改时间 26-SEP-2011 类型 ANNOUNCEMENT 状态 PUBLISHED
In this Document
What is being announced?
As Grid Infrastructure daemon diskmon.bin is used for Exadata fencing, started from 11.2.0.3, resource ora.diskmon will be offline in non-Exadata environment. This is expected behaviour change.
As Grid Infrastructure daemon diskmon.bin is used for Exadata fencing, started from 11.2.0.3, resource ora.diskmon will be offline in non-Exadata environment. This is expected behaviour change.
Prior to 11.2.0.3:
ps -ef| grep diskmon.bin
grid 3361 3166 0 22:57 ? 00:00:00 /ocw/grid/bin/diskmon.bin -d -f
On 11.2.0.3:
ps -ef| grep diskmon.bin
>> no more diskmon.bin
来自 “ ITPUB博客 ” ,链接:http://blog.itpub.net/29313086/viewspace-1482572/,如需转载,请注明出处,否则将追究法律责任。
转载于:http://blog.itpub.net/29313086/viewspace-1482572/