All apps dba Blog is the blog contributed by Doyensys Employees, With the view to share the knowledge out of their experience.
Doyensys Is a Fast Growing Oracle Technology Based Solutions Company Located in the US And Offshore Delivery Centers in India. With rich experience In Oracle E-Business, Oracle Database, Oracle Application Express (APEX), Oracle J Developer, Oracle OBIEE and E-Business Suite
On the same machine we have installed grid infrastructure of 220.127.116.11. The clusterware (owned by oracle) manages all instances of 11.2..0.2 server as cluster resources in active/passive mode. It’s happens while we are using storage as ASM.
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.
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.
check setasmgidwrap script under grid home.
It should contain entry as below.
vi setasmgid script:
Check if setasmgid exists under SETASMGID_LOC. rename $SETASMGID_LOC/setasmgid to $SETASMGID_LOC/setasmgid.orig.
restore the permission of oracle binary to oinstall.