The BROKEN procedure sets the state of a job to either
broken or not broken.
A broken job cannot be executed except by using the RUN
procedure.
Syntax
>>-DBMS_JOB.BROKEN--(--job--,--broken--+--------------+--)-----><
'-,--next_date-'
Parameters
- job
- An input argument of type DECIMAL(20) that specifies the identifier
of the job to be set as broken or not broken.
Note: The
expected value for job identifier is not the value of TASKID in the
SYSTOOLS.ADMIN_TASK_LIST view. For example, you have the following
job list:
NAME TASKID
--------------- ------
DBMS_JOB_TASK_2 3
DBMS_JOB_TASK_3 4
If you want to modify DBMS_JOB_TASK_2,
you must pass 2 as the job identifier.
- broken
- An input argument of type BOOLEAN that specifies the job status.
If set to "true", the job state is set to broken.
If set to "false", the job state is set to not broken.
Broken jobs cannot be run except through the RUN procedure.
- next_date
- An optional input argument of type DATE that specifies the date
and time when the job runs. The default is SYSDATE.
Authorization
EXECUTE privilege on the DBMS_JOB
module.
Examples
Example 1: Set the state
of a job with job identifier 104 to broken:
CALL DBMS_JOB.BROKEN(104,true);
Example 2: Change the state back to not
broken:
CALL DBMS_JOB.BROKEN(104,false);