DOYENSYS Knowledge Portal

We Welcome you to visit our DOYENSYS KNOWLEDGE PORTAL : Doyensys Knowledge Portal

Friday, March 3, 2017

Creation database on ASM using dbca causes crash of existing instances

During creation of new instance of version with ASM on Oracle, some existing instances of the same ORACLE_HOME suddently crashes! I’ve got such error message in alert.log.
Whilr running DBCA creation,We got this error:
Unexpected error 27140 in job slave process
ORA-27140: attach to post/wait facility failed
ORA-27300: OS system dependent operation:invalid_egid failed with status: 1
ORA-27301: OS failure message: Operation not permitted
ORA-27302: failure occurred at: skgpwinit6
ORA-27303: additional information: startup egid = 1000 (oinstall), current egid = 1200 (dba)
On the same machine we have installed grid infrastructure of 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.
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.
cd $GRID_HOME/bin
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.
-rwsr-s--x 1 oracle dba 19872189 Feb 28  2017 oracle
chown -R oracle:oinstall oracle
-rwsr-s--x 1 oracle oinstall 19872189 Feb 28  2017 oracle

No comments: