Operations on Job Executions and Job Runs
Besides supporting the standard job operations of create, edit, create like, and delete, the Job System enables you to:
-
Suspend jobs —
You can suspend individual executions or entire jobs. For example, you may need to suspend a job if a needed resource was unavailable, or the job needs to be postponed.
If a job is scheduled to repeat but is suspended past the scheduled repeat time, or a maximum of one day, the execution of this job would be marked "Skipped." A job is also skipped when the scheduled time plus the grace period has passed.
-
Resume jobs —
After you suspend a job, any scheduled executions do not occur until you decide to resume the job.
-
Retry all failed executions in a job run —
When analyzing individual executions or entire jobs, it is useful to retry a failed execution after you determine the cause of the problem. This alleviates the need to create a new job for that failed execution. When you use the Retry operation in the Job System, Enterprise Manager provides links from the failed execution to the retried execution and vice versa, should it become useful to retroactively examine the causes of the failed executions. Only the most recent retry is shown in the Job Run page.
With regard to job runs, the Job System enables you to:
-
Delete old job runs
-
Stop job runs
-
Retry all failed executions in a job run. Successful executions are never retried.
Note:
For more information on job executions and runs, refer to Enterprise Manager online help.