Bug 18884444 - JOBS STUCK IN SCHEDULED STATUS CALLING STOP_JOB WITH FORCE=TRUE
(Doc ID 1903551.1)
Last updated on FEBRUARY 26, 2019
Applies to:Oracle Database - Enterprise Edition - Version 126.96.36.199 to 188.8.131.52 [Release 11.2]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Exadata 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.
Calling DBMS_SCHEDULER.STOP_JOB with force=TRUE parameter seems not to release job_queue_processes count, as new jobs remain in SCHEDULED status. After about 5 minutes, jobs are RUNNING again.
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