ORA-27300: OS system dependent operation:fork failed with status: 2

This error normally would appear in alert logs in the following way: ORA-27300: OS system dependent operation:fork failed with status: 2 ORA-27301: OS failure message: No such file or directory ORA-27302: failure occurred at: skgpspawn5 Process J001 died, see its trace file kkjcre1p: unable to spawn jobq slave process Errors in file /oracle_home/oracle/myserver/diag/rdbms/myservertest/myserverTEST/trace/myserverTEST_cjq0_18153518.trc: When you try to connect to sqlplus, you may get the following error: $ sqlplus / as sysdba SQL*Plus: Release 11.2.0.3.0 Production on Tue Mar 31 11:09:58 2015 Copyright (c) 1982, 2011, Oracle. All rights reserved. ERROR: ORA-12536: TNS:operation would block This is caused by the inability of the Oracle software owner to get the OS to spurn more processes. In other words, the user (Oracle software owner) has reached it's maximum number of processes it is allowed to spurn. A check on the server resources will usually show that utilization is no where near maximum. Solution: Check current "maxuproc" for the user # lsattr -E -l sys0 | grep -i maxuproc maxuproc 128 Maximum number of PROCESSES allowed per user True Increase this value to a higher one # chdev -l sys0 -a maxuproc=NewValue Additionally, we can increase number of processes at the database level SQL> show parameter processes SQL> alter system set processes=NewValue scope=spfile;