Last updated on JULY 21, 2017
Applies to:Oracle Database - Enterprise Edition - Version 10.2.0.4 and later
Information in this document applies to any platform.
***Checked for relevance on 21-Jul-2017***
Scheduler job always stays in running state even though it are not really running (zombie state).
The jobs cannot be stopped or dropped and always appears in USER_SCHEDULER_RUNNING_JOBS.
Executing DBMS_SCHEDULER.STOP_JOB('<jobname>') fails with the error:
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