...
Using job chains
Sequences of jobs Jobs can easily be configured in job chains Job Chains that guarantee that a successor job is not invoked if a previous job provokes an error. Job errors can be configured to be detected by execution return code (for executable files), signals (for Unix only), availability of output to stderr and by errors that were are raised either by API methods or by SQL exceptions (and normal SQL errors).
Job chains are nodes of jobs that are organized in a sequence, every node is given a distinct state. An order Order proceeds along the jobs job nodes in a job chain one after the other. Should a processing error occur, then the order is stopped and can be configured to stop, to repeat (setback) or to be removed from the job chain.
See the samples in What is the concept of "job chains and order processing"?
In addition to this you could use monitor Monitor scripts to implement more complex conditions for job starts in any of the languages Java , and Javascript, Perl and VBscript. The Job Scheduler API provides a method scheduler_job.start() methods that can be used in scripts that implement their own business logic for conditional job starts.
Moreover this API method can be exposed to Oracle pl/sql procedures or functions (by Java classes in the database) that enable jobs to be launched in a transactional environment (e.g. start a job exlusively after commit has been invoked) either by triggers or e.g. by plPL/sql SQL procedures.
Using successor jobs
...
| Code Block |
|---|
<job>
<process file="..."> or <script language="...">
<commands on_exit_code="success">
<start_job job="ftp_get_files"><params/></start_job>
</commands>
<commands on_exit_code="error">...</commands>
<commands on_exit_code="1 2 4 8">...</commands>
</process>
</job>
|
See also
You could configure any job to start arbitrary successor jobs and orders from Job Scheduler release 1.2.7 onwards.