How to start up the ASM instance when the spfile is misconstrued or lost.ORA-00099: warning: no parameter file specified for ASM instance ORA-00304: requested INSTANCE_NUMBER is busy
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.
1. Create a new ASM pfile.
2. Start up the ASM instance on the first node:
3. Check if the ASM diskgroups are mounted properly or not.
4. Create the spfile:
6. We need to stop and startup the CRS to make sure that the ASM and the CRS stack startup automatically without any issues.