STOP_JOB

The STOP_JOB procedure is used to terminate a running job.

Privilege requirements

The sys tenant can terminate jobs running for other users. Other users can only terminate their own running jobs.

Syntax

DBMS_SCHEDULER.STOP_JOB (
job_name              IN VARCHAR2,
force                 IN BOOLEAN DEFAULT FALSE);

Parameters

Considerations

• Terminating multiple job runs: When the STOP_JOB statement is executed, all jobs and their corresponding sessions that were started before the execution time will be terminated.
• Impact on future scheduling: The STOP_JOB statement only terminates the currently running job instance and does not affect any future scheduled executions of the job. The job will continue to run as planned.
• Failure count statistics for terminated jobs: Jobs terminated by STOP_JOB or kill session will be counted as one failure. If a job fails consecutively a certain number of times (such as 16 times), it may be marked as corrupted by the system.
• Impact on job execution when queues are backed up: If the system tenant queue or Oracle tenant queue is backed up, it may affect the execution of the STOP_JOB statement. Queue backup can lead to resource shortages, which may delay or block the execution of the STOP_JOB statement.

Examples

Immediately terminate the job MYJOB.

BEGIN
  DBMS_SCHEDULER.STOP_JOB(
    JOB_NAME            => 'MYJOB,
    force               => FALSE);
END;