How to start up the ASM instance when the spfile is misconstrued or lost

1

Posted on 2013 年 4 月 23 日 by

在11g中,asm的spfile都存放在asm磁盘组中,所以当ASM的spfile被消失了或删除了,需要自己手动写个pfile 临时把磁盘组mount,然后create spfile到原来的磁盘组上。

错误:

- 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 found that it referred  
to an spfile which did not exist in the ASM (or shared storage) 

 

处理过程:

1.查看asm的spfile的位置
[grid@oradbca1 ~]$ cat /u01/app/11.2/grid/gpnp/profiles/peer/profile.xml

 

2.Create a new ASM pfile

 

+ASM1.asm_diskgroups='DATA'#Manual Mount
+ASM2.asm_diskgroups='DATA'#Manual Mount
*.asm_diskstring='/dev/asm-disk*'
*.asm_power_limit=1
*.diagnostic_dest='/u01/app/oracle'
*.instance_type='asm'
*.large_pool_size=12M
*.remote_login_passwordfile='EXCLUSIVE'

 

3. Start up the ASM instance

$ sqlplus / as sysasm

sql> startup pfile=<the full pathname of ora_+ASM1.ora>

 

4.Check if the ASM diskgroups are mounted properly or not

sql> select name , state from v$asm_diskgroup

 

5.Create the spfile

sql> create spfile='+DATA/../spfileasm.ora' from pfile='<the full path name of ora_+ASM1.ora>

 

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

 

 

Response to How to start up the ASM instance when the spfile is misconstrued or lost

发表评论