How to start up the ASM instance when the spfile is misconstrued or lost ?
(Doc ID 1313657.1)
Last updated on MAY 05, 2020
Applies to:Oracle Database - Enterprise Edition - Version 188.8.131.52 to 184.108.40.206 [Release 11.2]
Information in this document applies to any platform.
The CRS and the ASM instance can not start because the spfile is misconstrued or lost
CRS and the ASM instance can not start up because the spfile is misconstrued or lost
- Starting ASM instance fails with error:
ORA-00099: warning: no parameter file specified for ASM instance
ORA-00304: requested INSTANCE_NUMBER is busy
- Starting up the CRS services fails 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 referred to an spfile which did not exist in the ASM (or shared storage)
$ cat /u01/app/11.2.0/grid/gpnp/<HOSTNAME>/profiles/peer/profile.xml
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document