On the same machine we have installed grid infrastructure of 11.2.0.2. The clusterware (owned by grid) manages all instances of 11.2..0.2 server as cluster resources in active/passive mode. It’s worth of pointing out that this problem never happens when we use local file system or clustered file system as storage in place of ASM.

Analysis

we realized that the binary file ‘oracle’ in directory $ORACLE_HOME/bin has been changed with ownership. It was changed from “oracle:oinstall” as current instances had started to ‘oracle:dba’ during creation of new instance, which made current instances crashed.

Cause

This is identified as a Bug 9786198 [http://bug.oraclecorp.com/pls/bug/webbug_edit.edit_info_top?rptno=9786198] – SRVCTL START DATABASE ORA-0178 FAILURE IN PROCESSING SYSTEM PARAMETERS

This happens when you chose “dba” for “ASM Database Administrator”,”ASM Instance Administration Operator” and “ASM Instance Administrator”
group when installing grid infrastracture.

If all other database instances are starting up on all nodes, there is no need to do any changes to setasmgid.
This change needs only to be done if you hit same issue again.