分类： Oracle
2009-07-13 13:20:31
| Subject: | Diagnosing CRS-215 Error When Starting Clusterware Resources | |||
| Doc ID: | 781632.1 | Type: | BULLETIN | |
| Modified Date: | 16-JUN-2009 | Status: | PUBLISHED | |
In this Document
The purpose of this document is to assist in diagnosing the CRS-215 error.
The error is reported when
there is a problem starting a clusterware
resource.
It is intended for DBAs.
Conventions used :
| Software Home | Contents |
|---|---|
| RDBMS_HOME | The RDBMS software home or ORACLE_HOME |
| ASM_HOME | The home used to install ASM if separate from above |
| CRS_HOME | The Oracle Clusterware home |
The error CRS-215 indicates there was a problem starting a clusterware
resource. The CRS-215 error is a general one
and does not give specific
details by itself of why the resource failed to start.
Further diagnosis
is required to determine the cause. Sometimes additional errors are displayed
on-screen along with the CRS-215 which help determine the cause. If this is not
the case then you need to refer to the specific log file for that resource or
the Instance Monitor log file ( imon) which is also created for DB
instances.
The resource specific log files are stored in either CRS_HOME
or RDBMS_HOME depending on the resource type and use a naming convention
depending on the resource type ( This shows UNIX format, but the same path
applies on Windows) . The 'imon' log files are under
RDBMS_HOME.
Where the resource log files and imon logs are
stored :
( For readability assume a node name of 'mynode1' a database called 'mydb'
and an instance called 'mydb1')
1) CRS_HOME/log/mynode1/racg
- Contains VIP and ONS resource logs.
(As the VIP is relocatable
it's possible to find the vip log from other nodes.
ora.mynode1.vip.log
ora.mynode2.vip.log ( for example)
ora.mynode1.ons.log
ora.mydb.mydb1.inst.log
- In addition to the resource log files RDBMS instances also report
errors to a file called imon
imon
3) ASM_HOME/log/mynode1/racg
( Only if ASM home is
separate from RDBMS; else these logs are stored under RDBMS_HOME.)
-
Contains ASM and LSNR resource logs:
ora.mynode1.ASM1.asm.log
ora.mynode1.LISTENER_mynode1.lsnr.log
The action to take depends on the type of resource which failed (VIP,
instance, ASM) and the error specific to that resource.
Note: In 11g the errors are written to the screen, in 10g you need to check
the resource logs and if it's an instance resource, the relevant
imon*.log.
Here are some examples of CRS-215 followed by a list
of articles documenting specific cases of CRS-215.
o
Example #1 (11g)
- CRS-215 while starting an ASM instance:
$ srvctl start asm -n
mynode1
- Displayed on the screen is the error:
mynode1:ora.mynode1.ASM1.asm:SQL> ORA-01078: failure in processing
system parameters
mynode1:ora.mynode1.ASM1.asm:LRM-00109: could not open
parameter file '/u01/app/oracle/product/11.1.0/asm/dbs/init+ASM1.ora'
...
CRS-0215: Could not start resource 'ora.mynode1.ASM1.asm'
- In this case the reason is that the init+ASM1.ora file does not exist.
- No entries are written to ora.mynode1.ASM1.asm.log.
o Example
#2 (11g)
- CRS-215 trying to start an RDBMS instance (where the
init.ora parameter REMOTE_LISTENERS was deliberately appended with _XX to cause
an error )
$ srvctl
start instance -i mydb1 -d mydb mynode1:ora.mydb.mydb2.inst:SQL> ORA-00119: invalid specification
for system parameter REMOTE_LISTENER
mynode1:ora.mydb.mydb2.inst:ORA-00132:
syntax error or unresolved network name 'LISTENERS_MYDB_XX'
mynode1:ora.mydb.mydb2.inst:ORA-01078: failure in processing system
parameters
...
CRS-0215: Could not start resource
'ora.mydb.mydb2.inst
- No entries are written to ora.mynode1.mydb1.inst.log but the
imonmydb.log will have :
SQL> ORA-00119: invalid specification for system parameter REMOTE_LISTENER
ORA-00132: syntax error or unresolved network name 'LISTENERS_RAC11G'
ORA-01078: failure in processing system parameters
SQL>
Disconnected
o Example #3 (10g)
$ srvctl start database
-d rac10g
PRKP-1001 : Error starting instance rac10g1 on node mynode1
CRS-0215: Could not start resource 'ora.rac10g.rac10g1.inst'.- No message written to the screen, so check the instance resource log to find the reason :
$ tail $ORACLE_HOME/log/node1/racg/ora.rac10g.rac10g1.inst.log
SQL*Plus: Release 10.2.0.4.0 - Production on Tue Mar 3 12:18:55 2009
Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
Enter user-name:
Connected to an idle instance.
SQL> ORA-00119: invalid specification for
system parameter REMOTE_LISTENER
- Also check the imonrac10g.log
$ tail $ORACLE_HOME/log/jcrac1/racg/imonrac10g.log
SQL> ORA-00119:
invalid specification for system parameter REMOTE_LISTENER
ORA-00132: syntax
error or unresolved network name 'LISTENERS_RAC10G'
ORA-01078: failure in
processing system parameters
SQL> Disconnected
Here is a list of notes which address specific occurances of CRS-215,
grouped by resource type:
= Database / Instances
- Srvctl Cannot Start database
- PRKP-1001 and ORA-00119 when trying to startup instance using
srvctl or sqlplus
- Cannot Start Instance with Srvctl but Can With SQL*Plus
- VRTSodm : ORA-29702 Instance Hang On Startup
- SRVCTL FAILS TO START DATABASE WHILE SQLPLUS WORKS
- Cannot start instance using srvctl but sqlplus can
=
VIP
- How to Configure Virtual IPs for 10g RAC
- CRS-0215: Could not start resource 'ora..vip'
= ASM
- Unable To Start Asm Instance After Adding Node To Rac Cluster
- Ora-15160: Rolling Migration Internal Fatal Error During Upgrade
of ASM To 11.1.0.7.0
= Listener
- NETCA Fails To Create Listener.ora On Remote Cluster Node,
Resulting In CRS-0215
= Other
- 'Srvctl Start Service' Fails With PRKP-1030, CRS-0215 And
ORA-1003, CLSR-0002
- SRVCTL: PRKP-1001 : CRS-0215: Could not start resource, racgimon
killed by NS
- %ORA_CRS_HOME% NOT REPLACED IN IN USRVIP SCRIPT INSTALLING
10.2.0.3
- Srvctl Can Not Start/Stop Resource For Remote Node
ORA-216/ORA-215
- CRS-0215 / ONS Failed to Start. Pingwait Exited With Exit Status
2