(unable to communicate with CRSD/OHASD
ASM例項的alert檔案出現大量
WARNING: failed to online diskgroup resource ora.DG_DATA.dg (unable to communicate with CRSD/OHASD)
WARNING: failed to online diskgroup resource ora.DG_OCR.dg (unable to communicate with CRSD/OHASD)
Applies to:
Oracle Database - Enterprise Edition - Version 11.2.0.1 to 12.1.0.1 [Release 11.2 to 12.1]Information in this document applies to any platform.
***Checked for relevance on 03-Jul-2013***
Symptoms
If OCR is located on ASM diskgroup, following shows in ASM alert log ($ORACLE_BASE/diag/asm/+asm/+ASMn/trace/alert_+ASMn.log) after ASM mounted all diskgroup successfully while starting up Grid Infrastructure(CRS):
..
SUCCESS: diskgroup GI was mounted
SUCCESS: ALTER DISKGROUP ALL MOUNT /* asm agent */
..
WARNING: failed to online diskgroup resource ora.GI.dg (unable to communicate with CRSD/OHASD)
Or after ASM dismounted all diskgroup successfully while shutting down clusterware:
SUCCESS: ALTER DISKGROUP ALL DISMOUNT /* asm agent */
Sun Feb 07 11:11:13 2010
WARNING: failed to offline diskgroup resource ora.GI.dg (unable to communicate with CRSD/OHASD)
..
freeing rdom 0
Cause
In contrast to previous version of CRS, 11gR2 ASM does not depend on CRSD anymore; rather if OCR is located on ASM, ASM will start before CRSD while clusterware is coming up, and stops after CRSD while clusterware is going down. Due to the new startup sequence, ASM can not update diskgroup resource status in CRSD either during clusterware startup or shutdown, thus above message is logged.
Solution
The message can be ignored, the status of diskgroup and diskgroup
resource will be synchronize by oraagent once clusterware is fully up.
To find out diskgroup resource status:
To start or sync diskgroup resource:
To find out diskgroup resource status:
$ORACLE_HOME/bin/srvctl status diskgroup -g DG_ARCH -a
$ORACLE_HOME/bin/srvctl status diskgroup -g DG_DATA -a
To start or sync diskgroup resource:
$ORACLE_HOME/bin/srvctl start diskgroup -g DG_ARCH
$ORACLE_HOME/bin/srvctl start diskgroup -g DG_DATA
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/21754115/viewspace-1761462/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- crsd.bin Fail With Error CRS-1019 When ohasd Restarted (文件 ID 2291799.1)AIErrorREST
- RAC一個節點OHASD啟動不了waiting for init.ohasd to be startedAI
- Angular 2 Components CommunicateAngular
- Fails to Join the Cluster as CRSD and EVMD are in INTERMEDIATE StateAI
- crsd.bin程式狂吃CPU
- CRS-4534: Cannot communicate with Event Manager
- has、ohasd、crs、cluster區別和聯絡
- CRS-0184 Cannot communicate with the CRS daemon
- OHASD not Starting After Reboot on SLES (Doc ID 1325718.1)boot
- CRS-0184: Cannot communicate with the CRS daemon
- CRS-2765: Resource 'ora.crsd' has failed on serverAIServer
- 11.2RAC環境中的CRSD程式
- 【Oracle】RAC 11.2.0.4.0 OHASD服務無法啟動Oracle
- 11g的ohasd無法隨機啟動隨機
- CRS-0184: Cannot communicate with the CRS daemon.
- CRS-4535: Cannot communicate with Cluster Ready Services
- 【轉】ohasd不能正常啟動:ioctl操作:npohasd的問題
- Oracle 11gR2 RAC ohasd failed to start 解決方法OracleAI
- 神奇的CRS-0184: Cannot communicate with the CRS daemon
- unable to get oracle owner forOracle
- CRS-0184: Cannot communicate with the CRS daemo的診斷
- 解決:CRS-0184: Cannot communicate with the CRS daemon.
- Unable to locate factory with name [default]
- unable to get file lock, will retry ...
- Unable to create git index lockGitIndex
- crs_stat -t CRS-0184: Cannot communicate with the CRS daemon
- ORA-7445(ACCESS_VIOLATION)(unable_to_trans_pc)(UNABLE_TO_WRITE)錯誤
- CRSD自動重啟和產生CORE DUMP的故障處理
- CRS-0184: Cannot communicate with the CRS daemon. 問題處理
- OUTLOOK - Unable to Delete Meetingsdelete
- Unable to connect to SQL Server ExpressSQLServerExpress
- Unable to load SELinux PolicyLinux
- Unable to start HTTP server after restoreHTTPServerREST
- 11.2.0.4單例項ASM安裝報錯ohasd failed to ... line 73.單例ASMAI
- 轉:Oracle叢集重要程式evmd、cssd和crsd發源地及跟蹤探索OracleCSS
- 【RAC】Oracle叢集重要程式evmd、cssd和crsd發源地及跟蹤探索OracleCSS
- How to Diagnose and Resolve UNABLE TO EXTEND ErrorsError
- Unable to Find Sources for Current Linux KernelLinux