Enterprise Manager Jobs - Expert Oracle Enterprise Manager 12c - page 416

There are two considerations when making the choice:

• If you allow jobs to continue to run during the blackout and the target becomes unavailable at

the very end of the job, when the target agent would send a successful execution code back to
the Jobs Service, the job will continue to show as running, and any subsequent runs of the job
will be skipped.

• If you stop jobs from running during the entire blackout, jobs will be skipped during that

blackout. If the job is set to notify on Action Required, notifications will be sent for every
scheduled job that is skipped.

As blackouts are also issued as jobs, but run in the background, you can view these by querying tables in the
database as well. The following query examples show how first, a join between the three tables of MGMT_JOB , MGMT_
JOB_EXEC_SUMMARY , and MGMT_BLACKOUTS results in information regarding any existing blackout scheduled.

SELECT mj.job_name, mj.job_id, mje.status, mje.scheduled_time
FROM MGMT_JOB mj, MGMT_JOB_EXEC_SUMMARY mje, MGMT_BLACKOUTS mb
WHERE mb.start_job_id=mj.job_id
AND mj.job_id=mje.job_id;

Figure 11-50. Output from querying a blackout in EM12c

The next query then offers us details on the blackout scheduled, including the individual steps as seen by the EM
Jobs Service.

SELECT mje.step_id, mje. step_name, mje .step_type, mje. step_status,
mje .start_time, mje .output_id, mje .error_id
FROM MGMT_JOB_EXECUTION mje, MGMT_BLACKOUTS mb
WHERE mje.job_id=mb.start_job_id
ORDER BY mje.step_id;