Databases Reference
In-Depth Information
If, for whatever reason, the job cannot be completed in one go, the job reschedules
itself to run after some time. If the job still can't be completed successfully, the job
reschedules itself again but with an increasing interval. This mechanism will try to
run the job up to 16 times. If the job still can't complete, the job is marked as
Broken
.
This means that the job will not be tried again.
In the following example, there is a long running program, which can only be called
by pressing the button in the APEX application:
Calling the long_running process directly
In the preceding screenshot, a
page
process is created. This process calls the long
running program directly in an anonymous PL/SQL block. Because we want to
call this program when a button is pressed, the condition
When Button Pressed
for
the
page
process is set to the button (called
LONG_RUNNING
), as shown in the
following screenshot:
