Dead Job Still In DBA_SCHEDULER_RUNNING_JOBS
Last updated on DECEMBER 06, 2016
Applies to:Oracle Database - Enterprise Edition - Version 10.2.0.1 and later
Information in this document applies to any platform.
While querying DBA_SCHEDULER_RUNNING_JOBS and V$SCHEDULER_RUNNING_JOBS, there is a job with no session ID and no process ID running with a large elapsed time.
Actually this job is not really running. The problem is that , it can't be stopped using DBMS_SCHEDULER.STOP_JOB. It throws below error :
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