ORACLE CRS 狀態 UNKNOWN 變為offline

 

In this Document
  
  

---

Applies to:

Oracle Server - Enterprise Edition - Version: 10.2.0.1 to 11.1.0.7 - Release: 10.2 to 11.1
Information in this document applies to any platform.

Goal

A resource status is showing as UNKNOWN in crs_stat -t output :


When the resource state is UNKNOWN, srvctl cannot start or stop the resource.  It fails with the following errors:


After the failed srvctl command, the crsd.log will show an error:


Even running srvctl status on the resource can error:


These errors are all due to the resource state of UNKNOWN.

Solution

The UNKNOWN state can often be resolved by bringing the resource offline using crs_stop.


Any CRS resource can be in an UNKNOWN state, including vip, gsd, database, or instances.  The following uses an instance resource as an example.

1. Find the proper name for your instance resource.  To find it, do "crs_stat -u | grep inst", this will give the names of all instance resources in the OCR.


Pick the instance associated with the node and database in question.
For example, for a database named prod and instance named prod1, the resource name will be "ora.prod.prod1.inst".


2.  Before you go any further, make sure that you have a recent backup of your OCR.
You can check on your OCR automatic backups with the command "ocrconfig -showbackup":


If no backup exists, then create one using ocrconfig -export, following the instructions in the documentation:




3. Restore the instance resource to OFFLINE with this command:

crs_stop [instance resource name]

eg:




4. Check that instance status is now OFFLINE instead of UNKNOWN



5. If the instance status is OFFLINE, then you can try again to start it with srvctl.

6. If the startup fails again, then open a SR and provide Oracle Support with the following information:

a) Gather a trace by using the following script.


(Replace "ora.prod.prod1.inst" with the name of your actual instance resource; replace prod with the name of your database and prod1 with the name of your instance).

The trace log will be found in /tmp/trace1.out.

b) latest crsd.log from this node

c) the resource log for this instance from $CRS_HOME/log/<>/racg

d) ls -l of $ORACLE_HOME/log/<>/racg