"Translated from MoS article" CRS shows that the running DB instance is offline state

CRS shows that the running DB instance is offline status
Turn from:
CRS shows Running Instance Status as OFFLINE (Doc ID 1673397.1)

Suitable for:
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.

Symptoms:
In the Crsctl stat res-t output, the status of the DB instance is displayed offline, but the DB instance is running

$ <grid_home>/bin/crsctl Stat Res ora.racdb.db- T--------------------------------------------------------------------------------NAME TARGET State SERVE R state_details--------------------------------------------------------------------------------Cl Uster Resources--------------------------------------------------------------------------------ora.racdb.db 1 O Ffline OFFLINE corrupted Controlfile---> show ' corrupted Controlfile ' 2 ONLINE on Line Rachost2 Open 3 online online rachost3 open$ <grid_home&gt ;/bin/srvctl status database-d racdbinstance racdb1 is isn't running on node rachost1instance RACDB2 are running on node RAC Host2instance RACDB3 is running on node Rachost3 $ sqlplus/as sysdba ...               Sql> Select instance_name, status from Gv$instance;instance_name status----------------------------racdb1 OpenraCDB2 OPENracdb3 OPEN 

The alert log for the instance may display the following information:

Based on this result, the database service is not running on offline instance.

Reason:

Due to unpublished Bug 13257122 CRSD Agent report DB Controlfile corrupted but IT still ONLINE, CRSD AGENT reports corrupt Ed control file for read error during fixed table query which was not a real corruption and caused by concurrent control fi Le write.

Solution Solutions
Bug 13257122 have 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

"Translated from MoS article" CRS shows that the running DB instance is offline state