Last updated on JUNE 15, 2017
Applies to:Oracle Database - Enterprise Edition - Version 184.108.40.206 to 220.127.116.11 [Release 12.1 to 12.2]
Information in this document applies to any platform.
Scheduler job does not work as expected when ORA-4031 is reported due to lack of memory.
In such case a running scheduler job dies suddenly, however its entry is still shown in DBA_SCHEDULER_RUNNING_JOBS. This is like a GHOST entry.
The presence of ghost job in DBA_SCHEDULER_RUNNING_JOBS does not let AQ to submit any new plsql ntfn job, as a result messages remains in ready state and notifications are not sent.
But there is no session ID and no process ID associated with the job.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms