PL/SQL API jcs.delete_job
Summary
Delete the repository information and the output and log files of a job.
When the job has subjobs that haven't finished yet, or the job's process server is not running, the job will get the DELETING status. It will be deleted once the situation changes.
warning
The override and async parameters are meant mainly for internal use. Customers that need to delete specific jobs should not need to change these two parameters from their default value.
Privileges
To delete your own job you need the DELETE_JOB privilege. To delete someone else's job, you need the DELETE_ANY_JOB privilege and DELETE privilege on the queue that the job ran in.
Specification
procedure delete_job(job_id in number,
override in varchar2 default const.jcs_yes,
async in varchar2 default const.jcs_no,
recgroup in varchar2 default const.jcs_no,
force in varchar2 default const.jcs_no)
Parameters
- job_id - the ID obj the job
- override - N = just check whether the job has expired its keep clause; Y = the job is removed
- async - N = wait until the delete is finished; Y = do not wait for the delete to finish
- recgroup - N = delete just this one job; Y = delete the entire recurrence group
- force - This parameter is obsolete
Transaction keyword
The transaction keyword defines how and/or when the changes are committed to the database. A definition of the various transaction keywords can be found on the jcs package summary page.
blocks
See Also
jcs_jobs (not implemented).
jcs_job_statuses (not implemented).
plsqlTopic
onsiteTopic