Database Reference
In-Depth Information
Some administrators choose to be notified of job run successes (Succeeded). Based on my professional
experience, I recommend not configuring jobs to perform this notification. The largest amount of time spent by an
administrator on alerts is caused not by too little monitoring, but too much. If Enterprise Manager is configured to
include emailed “success” notifications, you become accustomed to receiving them, knowing that they do not require
response, and this may result in critical issue notifications missed.
For those administrators who want to shut off individual success messages and simply report these andjob
failures once a day, a secondary job can be set up to report and eliminate unnecessary inividual notifications.
select mj.job_id, mj.job_name, mjes.start_time, mjes.end_time,
mjes.status_detail, mjes.retried
from sysman.mgmt_job mj, sysman.mgmt_job_exec_summary mjes
where mj.job_id=mjes.job_id
and mjes.start_time >= sysdate-1
and mj.job_status!=0
and mj.expired=0;
JOB_ID
--------------------------------
JOB_NAME START_TIM
---------------------------------------------------------------- ---------
END_TIME STATUS_DETAIL RETRIED
--------- ------------- ----------
285DCE9F51ED4E6D843974116963EDC3
DPEXP_ORCL_1230 31-DEC-12
31-DEC-12 0
The preceding output shows a job that failed, was not expired, and was never retried. The query reequested any
job that was run in the last day, had not failed (
successful=0
), and was not expired (
0
is actively scheduled jobs).
This information can be used instead of reporting on each individual job. The choice is up to the administrator,
but knowing how to find information about a job is essential when default options are not to the administrator's
preference.
Permissions
Many times I've experienced conflicts in scheduled jobs that have occurred, for example, between one task that was
scheduled through a shell script via cron, another in theDBMS_SCHEDULER, and a third in the EM Job scheduler.
The EM12c Jobs Service provides a job scheduler that can handle numerous task script formats and job types, and has
a single job interface to manage the jobs. The security for job management is part of the administrator creation steps,
securing the users who can create, manage, and remove jobs.
There are many ways to view who can create and manage jobs in the EM12c environment. Because the
administrator may not always be aware of who is creating jobs, how many, and how often in the environment, it is
essential to ensure that EM job demands are not impairing the performance of the system.
The following query provides a clear view, shown in Figure
11-26
, of who has been granted the rights to create
and schedule jobs.
SELECT grantee from SYSMAN.MGMT_PRIV_GRANTS
WHERE PRIV_NAME='SUPER_USER';
