程序師世界是廣大編程愛好者互助、分享、學習的平台,程序師世界有你更精彩!
首頁
編程語言
C語言|JAVA編程
Python編程
網頁編程
ASP編程|PHP編程
JSP編程
數據庫知識
MYSQL數據庫|SqlServer數據庫
Oracle數據庫|DB2數據庫
 程式師世界 >> 數據庫知識 >> Oracle數據庫 >> Oracle教程 >> CRS顯示正在運行的dbinstance是offline狀態

CRS顯示正在運行的dbinstance是offline狀態

編輯:Oracle教程

CRS顯示正在運行的dbinstance是offline狀態


CRS顯示 正在運行的db instance 是offline狀態
轉自:
CRS shows Running Instance Status as OFFLINE (Doc ID 1673397.1)

適用於:
Oracle Database - Enterprise Edition - Version 11.2.0.2 to 11.2.0.3 [Release 11.2]
Information in this document applies to any platform.

症狀:
在crsctl stat res -t 輸出裡,數據庫實例的status顯示offline,但是數據庫實例是正在運行的

$ /bin/crsctl stat res ora.racdb.db -t

--------------------------------------------------------------------------------
NAME           TARGET  STATE        SERVER                   STATE_DETAILS       
--------------------------------------------------------------------------------
Cluster Resources
--------------------------------------------------------------------------------
ora.racdb.db
     1        OFFLINE OFFLINE                               Corrupted Controlfile--->顯示'Corrupted Controlfile'
     2        ONLINE  ONLINE       rachost2                 Open
     3        ONLINE  ONLINE       rachost3                 Open


$ /bin/srvctl status database -d racdb
Instance racdb1 is not running on node rachost1
Instance racdb2 is running on node rachost2
Instance racdb3 is running on node rachost3

 
$ sqlplus / as sysdba
...
SQL> select INSTANCE_NAME, STATUS from gv$instance;

INSTANCE_NAME        STATUS
----------------     ------------
racdb1               OPEN
racdb2               OPEN
racdb3               OPEN

 

實例的alert日志可能會顯示如下的信息:

基於此結果,數據庫服務不在 offline的instance 上運行。

 

原因:

Due to unpublished Bug 13257122 CRSD AGENT REPORT DB CONTROLFILE CORRUPTED BUT IT STILL ONLINE, CRSD agent reports corrupted control file for read error during fixed table query which is not a real corruption and caused by concurrent control file write.

解決方案
Bug 13257122 has been fixed in 11.2.0.4 and 12.1. Apply the patchset 11.2.0.4 should avoid the problem.

To workaround the issue, please try to re-start the instance via srvctl:

$ srvctl start instance -d racdb -i racdb1

 

  1. 上一頁:
  2. 下一頁:
Copyright © 程式師世界 All Rights Reserved