[ID 1313657.1] 修改时间 11-AUG-2011     类型 PROBLEM     状态 MODERATED

In this Document
  Symptoms
  Cause
  Solution

---

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.

Applies to:

Oracle Server - Enterprise Edition - Version: 11.2.0.1 and later   [Release: 11.2 and later ]
Information in this document applies to any platform.
The CRS and the ASM instance can not start because the spfile is misconstrued or lost

Symptoms

The CRS and the ASM instance can not start up because the spfile is misconstrued or lost

- Start the ASM instance fail with error

SQL> startup;
ORA-00099: warning: no parameter file specified for ASM instance
ORA-00304: requested INSTANCE_NUMBER is busy

- Start up the CRS services fail with error

# crsctl start crs
CRS-4640: Oracle High Availability Services is already active
CRS-4000: Command Start failed, or completed with errors

- Checked the gpnp profile and found that it refer to spfile which is not exist in the ASM (or shared storage)

Cause

- In our case the spfile indicated in the gpnp profile was not found in the ASM diskgroup


- In general to be able to start up the CRS properly
  There should be a proper pfile or spfile to let the ASM instance startup
  and/or
  The gpnp profile should indicate to a proper spfile

Solution

1- Create a new ASM pfile
2- Start up the ASM instance

The asm instance shall start up properly

3- Check if the ASM diskgroups are mounted properly or not



4- Create the spfile


5- In the gpnp profile we shall find that the spfile information set properly there


6- We need to stop and startup the CRS to make sure that the ASM and the CRS stack startup automatically without any issues

相关的 产品 Oracle Database Products > Oracle Database > Oracle Database > Oracle Server - Enterprise Edition 关键字 ASM; CRS; CRSCTL; GRID; PFILE; PROFILE; SPFILE; STARTUP 错误 ORA-99; ORA-304; CRS-4000; CRS-4640

返回页首