Page History

Question: Can job dependencies be defined for the JobScheduler?

Answer:

Using job chains

Sequences of jobs can easily be configured in 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 code (for executable files), signals (for Unix only), availability of output to stderr and by errors that were raised either by API methods or by SQL exceptions (and normal SQL errors).

...

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 by pl/sql procedures.

Using successor jobs

You could configure any jobs to succeed the current job based on it's execution result:

<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>

...