DG cannot automatically mount causes the database to fail to start properly: ORA-01157, ORA-01110, ORA-17503, ORA-150

DG cannot automatically mount causes the database to fail to start properly: ORA-01157, ORA-01110, ORA-17503, ORA-15001, ORA-15001 phenomenon: after each restart of the entire CRS, D

DG cannot automatically mount causes the database to fail to start properly: ORA-01157, ORA-01110, ORA-17503, ORA-15001, ORA-15001 phenomenon: after each restart of the entire CRS, D

DG cannot automatically mount causes the database to fail to start properly: ORA-01157, ORA-01110, ORA-17503, ORA-15001, ORA-15001
Symptom:
After the whole CRS is restarted, the database cannot be automatically enabled to the OPEN state. An error is returned when you view the alert Log:
SUCCESS: diskgroup UNID was mounted
Thu Nov 14 21:46:01 2013
Create Relation SWEEPERR
Setting recovery target incarnation to 1
Successful mount of redo thread 1, with mount id 2364838615
Database mounted in Exclusive Mode
Lost write protection disabled
Completed: ALTER DATABASE MOUNT
Thu Nov 14 21:46:05 2013
ALTER DATABASE OPEN MIGRATE
Errors in file/opt/app/diag/rdbms/nc/nc1/trace/nc1_dbw0_8399.trc:
ORA-01157: cannot identify/lock data file 21-see DBWR trace file
ORA-01110: data file 21: '+ INDX/nc/datafile/INDX.256.820323481'
ORA-17503: ksfdopn: 2 Failed to open file + INDX/nc/datafile/INDX.256.820323481
ORA-15001: diskgroup "INDX" does not exist or is not mounted.
ORA-15001: diskgroup "INDX" does not exist or is not mounted.
Errors in file/opt/app/diag/rdbms/nc/nc1/trace/nc1_dbw0_8399.trc:
ORA-01157: cannot identify/lock data file 22-see DBWR trace file
ORA-01110: data file 22: '+ INDX/nc/datafile/INDX.257.820323659'
ORA-17503: ksfdopn: 2 Failed to open file + INDX/nc/datafile/INDX.257.820323659
ORA-15001: diskgroup "INDX" does not exist or is not mounted.
The alert log shows that indx dg files cannot be read,
Check that indx dg is in DISMOUNT state.

Analysis:
In ASM, two DG: UNID and INDX are created. Only UNID is automatically mounted at a time, and INDX cannot be automatically mounted.
Check the asm_diskgroups parameter and find that only the UNID is set. This is why INDX is not automatically mounted each time.
SQL>
SQL> show parameter asm

NAME TYPE VALUE
-----------------------------------------------------------------------------
Asm_diskgroups string UNID
SQL> show parameter pfile

NAME TYPE VALUE
-----------------------------------------------------------------------------
Spfile string

Solution:
Add indx to the asm_diskgroups parameter.
Spfile: alter system set asm_diskgroups = 'unid', 'indx 'scope = both;
Pfile: Modify the asm_diskgroups parameter in pfile.

Related reading:

ORA-01172, ORA-01151 error handling

ORA-00600 [2662] troubleshooting

Troubleshooting for ORA-01078 and LRM-00109

Notes on ORA-00471 Processing Methods

ORA-00314, redolog corruption, or missing Handling Methods

Solution to ORA-00257 archive logs being too large to store