My Oracle Support Banner

-Bash: Fork: Resource Temporarily Unavailable (Doc ID 1279664.1)

Last updated on MARCH 31, 2020

Applies to:

Oracle Exadata Hardware - Version and later
Information in this document applies to any platform.


1) You encounter many of the following message in the DB alert log on an Exadata compute node:

Process startup failed, error stack:
Errors in file <PATH>/trace/<SID>_psp0_9150.trc:
ORA-27300: OS system dependent operation:fork failed with status: 11
ORA-27301: OS failure message: Resource temporarily unavailable
ORA-27302: failure occurred at: skgpspawn3

2) You will also see messages similar to these in the /var/log/messages file on the Exadata compute node:

Dec 17 21:37:51 exad05 init: cannot fork, retry..
Dec 17 21:38:26 exad05 last message repeated 7 times
Dec 17 21:39:31 exad05 last message repeated 13 times
Dec 17 21:40:36 exad05 last message repeated 13 times
Dec 17 21:40:41 exad05 init: cannot execute "/opt/oracle.cellos/compmon/"
Dec 17 21:40:41 exad05 last message repeated 10 times
Dec 17 21:40:41 exad05 init: Id "emh1" respawning too fast: disabled for 5 minutes

Warning: If these messages go unnoticed, the node may become unresponsive and you will need to perform a reboot in order to recover.


Applied the DB host convenience pack for <patch:10248893>


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.