應該是ASM的SPFILE有問題了，重建一下SPFILE應該就會沒問題了，可參考METALINK上的如下方法：
1) Please create a temporary pfile (on node #1 (+ASM1), with the next values on the /dbs/init+ASM1.ora:
asm_diskgroups='GRROUP_NAME'
asm_diskstring='ORCL:*'
asm_power_limit=1
instance_type='asm'
large_pool_size=12M
remote_login_passwordfile='EXCLUSIVE'
2) Then startup the +ASM1 instance:
$> cd < Grid Infrastructure Oracle Home>/dbs/
$> export ORACLE_SID=+ASM1
$> sqlplus “/as sysasm”
SQL> STARTUP pfile=init+ASM1.ora
3) Recreate the spfile
SQL> create spfile='+YONG' from pfile='/opt/grid/product/11.2.0/grid_1/dbs/init+ASM1.ora';
File created.
4) Restarted the OHAS/CRS stack on both nodes:
4.1) Please shutdown all the services on both nodes as follow:
Node #1:
Connect as root user:
# /opt/grid/product/11.2.0/grid_1/bin/crsctl stop crs
Node #2:
Connect as root user:
# /opt/grid/product/11.2.0/grid_1/bin/crsctl stop crs
4.2) Verify that the Grid Infrastructure stack has shutdown successfully on both nodes. The following command should show no output if the GI stack has shutdown:
# ps -ef | grep diskmo[n]
4.3) Start the Grid Infrastructure stack on the first node:
# /opt/grid/product/11.2.0/grid_1/bin/crsctl start crs
4.4) Wait until the Grid Infrastructure stack has started successfully on the first node. To check the status of the Grid Infrastructure stack, run the following command and verify that the "ora.asm" instance is started. Note that the command below will continue to report that it is unable to communicate with the Grid Infrastructure software for several minutes after issuing the "crsctl start crs" command above:
# /opt/grid/product/11.2.0/grid_1/bin/crsctl status resource -t
4.5) Start the Grid Infrastructure stack on the remaining node:
# /opt/grid/product/11.2.0/grid_1/bin/crsctl start crs
4.6) Monitor the startup progress (this could take several minutes):
# /opt/grid/product/11.2.0/grid_1/bin/crsctl status resource -t
4.7) Verify OHAS, CRS & CSS are running on each node:
$> crsctl check has
$> crsctl check crs
$> crsctl check css