Bug 18884444 - JOBS STUCK IN SCHEDULED STATUS CALLING STOP_JOB WITH FORCE=TRUE
Last updated on DECEMBER 06, 2016
Applies to:Oracle Database - Enterprise Edition - Version 18.104.22.168 to 22.214.171.124 [Release 11.2]
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.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms