Oracle Server – Enterprise Edition – Version: 126.96.36.199 and later [Release: 11.1 and later ]
Information in this document applies to any platform.
When running a job from the scheduler on a very heavily loaded database you could receive an ora-610 error. The job slave process creation takes a long time and raises a reported error as a fatal error in the background process.
The resulting trace file will have this information listed in it:
New process timed out
error 610 in job queue process
ORA-00610: Internal error code
Died during process startup with error 447 (seq=109)
OPIRIP: Uncaught error 447. Error stack:
ORA-00447: fatal error in background process
This is caused by lack of resources on the server. If the system is extremely loaded, the timeout could be hit and the spawning error will occur. You will see this problem where a job slave process is not started is if the system is running out of resources (e.g. no memory left, max number of processes hit, etc.)
Ensure that there are enough resources on the server to satisfy all the scheduler/job queue requests.