ORA-27300, ORA-27301, ORA-27302,ORA-27303:
$ sqlplus / as sysdba
SQL*Plus: Release 12.1.0.2.0 Production on Wed Apr 30 12:35:25 2018
Copyright (c) 1982, 2014, Oracle. All rights reserved.
Connected.
SQL> startup;
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 = 1001 (dba)
SQL> shut immediate;
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 = 1001 (dba)
Alert Log file last content below:-
At alert log 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 = 1001 (dba)
2018-04-30T12:40:21.796988-04:00
Process J000 died, see its trace file
2018-04-30T12:40:21.797204-04:00
kkjcre1p: unable to spawn jobq slave process
2018-04-30T12:40:21.797384-04:00
Solution:-
Before we go on and involve clusterware, let’s replay the scenario (changing the group of the oracle executable) manually outside of clusterware to see if we can get the same behaviour
Solution for this problem is quite simple, go view this file
-rwxr-x--x 1 oracle asmadmin 232473728 Apr 30 12:59 /u01/app/oracle/product/12.1.0.2/db_1/bin/oracle
Change file group ownership back to oinstall and restart the database/ASM instance.
-rwxr-x--x 1 oracle oinstall 232473728 Apr 30 12:59 /u01/app/oracle/product/12.1.0.2/db_1/bin/oracle
