Ghost Job in DBA_SCHEDULER_RUNNING_JOBS Does Not Let AQ to Submit New PL/SQL/NTFN Job
(Doc ID 2274785.1)
Last updated on AUGUST 24, 2021
Applies to:Oracle Database Cloud Service - Version N/A and later
Oracle Database - Enterprise Edition - Version 18.104.22.168 to 22.214.171.124 [Release 12.1 to 12.2]
Oracle Database Cloud Schema Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
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.
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