ALERT.LOG for ASM Shows "WARNING: failed to online diskgroup resource ora.GI.dg (unable to communica

APPLIES TO:

OracleDatabase - Enterprise Edition - Version 11.2.0.1 to 12.1.0.1 [Release 11.2 to12.1]

Informationin this document applies to any platform.

***Checked for relevance on 03-Jul-2013*** 

SYMPTOMS

If OCR is located on ASM diskgroup, following shows inASM alert log ($ORACLE_BASE/diag/asm/+asm/+ASMn/trace/alert_+ASMn.log)
after ASM mounted all diskgroup successfully whilestarting up Grid Infrastructure(CRS):

 

 

SQL>ALTER DISKGROUP ALL MOUNT /* asm agent */

..

SUCCESS:diskgroup GI was mounted

SUCCESS:ALTER DISKGROUP ALL MOUNT /* asm agent */

..

WARNING:failed to online diskgroup resource ora.GI.dg (unable to communicate withCRSD/OHASD)

 

 

Or after ASM dismounted all diskgroup successfullywhile shutting down clusterware:

 

..

SUCCESS:ALTER DISKGROUP ALL DISMOUNT /* asm agent */

Sun Feb07 11:11:13 2010

WARNING:failed to offline diskgroup resource ora.GI.dg (unable to communicate withCRSD/OHASD)

..

freeingrdom 0

 

 

 

CAUSE

In contrast to previous version of CRS, 11gR2 ASM doesnot depend on CRSD anymore; rather if OCR is located on ASM, ASM will startbefore CRSD while clusterware is coming up, and stops
after CRSD whileclusterware is going down. Due to the new startup sequence, ASM can not updatediskgroup resource status in CRSD either during clusterware startup orshutdown, thus above message is logged.

SOLUTION

The message can be ignored, the status of diskgroupand diskgroup resource will be synchronize by oraagent once clusterware isfully up.

 

To find out diskgroup resource status:

 

$GRID_HOME/bin/srvctl status diskgroup -gdiskgroupname -a

 

To start or sync diskgroup resource:

 

$GRID_HOME/bin/srvctl start diskgroup -g diskgroupname

时间: 2015-01-04
Tags: LOG, agent

ALERT.LOG for ASM Shows "WARNING: failed to online diskgroup resource ora.GI.dg (unable to communica的相关文章

【RAC】failed to online diskgroup resource ora.GI.dg

ALERT.LOG for ASM Shows "WARNING: failed to online diskgroup resource ora.GI.dg (unable to communicate with CRSD/OHASD)" [ID 1060920.1] 现象: If OCR is located on ASM diskgroup, following shows in ASM alert log ($ORACLE_BASE/diag/asm/+asm/+ASMn/tr

Alert Log中“Fatal NI connect error 12170”错误

Alert Log中"Fatal NI connect error 12170"错误 Fatal NI connect error 12170.     VERSION INFORMATION:         TNS for Linux: Version 11.2.0.4.0 - Production         Oracle Bequeath NT Protocol Adapter for Linux: Version 11.2.0.4.0 - Production      

【DataGuard】ORA-16014 and ORA-00312 Messages in Alert.log of Physical Standby

安装完成dg后,发现alert 之中的有如下错误 ORA-16014: log 4 sequence# 44 not archived, no available destinations ORA-00312: online log 4 thread 1: '/opt/oracle/oradata/orclpdg/redo04.log' Wed Aug 24 22:55:45 2011 Errors in file /opt/oracle/admin/orcl/bdump/orclpdg_arc

[20141027]通过视图查看alert.log的问题

[20141027]通过视图查看alert.log的问题.txt --曾经写过一篇通过X$DBGALERTEXT查看alert*.log的文章,实际上在11G,定义了许多v$diag的视图,通过这些视图就可以获得许多信息. --甚至不需要直接查看相关文件X$DBGALERTEXT. http://blog.itpub.net/267265/viewspace-775126/ [email protected]> @ver1 PORT_STRING                    VERSION     

[20111221]快速定位浏览alert log文件.txt

作为数据库管理员经常要查看alert log文件,每次查找都要打入很长的路径,才能访问alert log文件,我以前的做法是建立一个别名,写死整个路径.例子: alias vialert='view /u01/app/oracle/diag/rdbms/test/test/trace/alert_test.log' 这样每次输入vialert就可以访问alert log文件. 今天看一个网站http://halisway.blogspot.com/2006/11/oracle-alert-log

ORA-00824: cannot set sga_target due to existing internal settings, see alert log for more information

    这篇文章是上篇文章"Expdp 导数错误 ORA-00832"的延续,前几天工作比较忙.累,直到今天才整理发出来.这个数据库实例的参数设置比较诡异其实是有原因的,由于这台数据库服务器系统是32位,数据库也是32位的.对于绝大部分32位系统上的32位数据库,SGA 最大的设置都不能超过2G,有的系统最大值甚至不能超过1.7G左右.DBA为了让内存充分利用,不至于浪费内存资源,于是想让SGA_MAX_SIZE 最大化,对数据库相关参数做了调整,设置参数USE_INDIRECT_DA

提取oralce当天的alert log的shell脚本代码_linux shell

提取oralce当天的alert log的shell脚本 复制代码 代码如下: #/bin/sh#get alert of everyday#then name of file is everyday_alert.shdir="/oracle/admin/bbdz/bdump"num=$(cat -n ${dir}/alert_bbdz.log | grep "`date|cut -c 1-10`"|head -n 1 |awk '{print $1}') tail

oracle提示Alert Log Errors: 12170 TNS-12535/TNS-00505: Operation Timed Out

客户反馈系统经常报会话超时,导致应用测试无法正常进行,经检查alert日志发现 Fatal NI connect error 12170.     VERSION INFORMATION:         TNS for HPUX: Version 11.2.0.4.0 - Production         Oracle Bequeath NT Protocol Adapter for HPUX: Version 11.2.0.4.0 - Production         TCP/IP

ORA-00205: error in identifying control file, check alert log for more info

境:oracle10gR2   solaris10 操作:在没有创建pfile的情况下,直接执行了以下命令 1 SQL>create pfile from spfile; 2 SQL>shutdown immediate 3 SQL>startup 4 ORA-00205: error in identifying control file, check alert log for more info 查看alter_TEST.log文件 Tue Jul 03 13:37:49 CST