Database Reference
In-Depth Information
Why Use EM12c Jobs
The main question to be answered is why an administrator should switch from their current job management
program/scheduler to the Enterprise Manager Job System. When first introduced to an environment with EM12c,
I also wanted this question answered. I had always utilized my own suite of shell and Perl scripts that I felt quite
comfortable scheduling in the OS cron scheduler. I found the scripts/OS-level scheduler a satisfactory solution
after small adjustments to environment variables and code were put in place to take the uniqueness of the server
environment into consideration. The choice of the OS-level scheduler still appeared to be the best for ease of database
management.
As I began to manage new environments for multiple clients, multiple server platforms, and OS profile designs
and preferences, I encountered an intriguing challenge. I now was working in a large database team environment
requiring me to quickly become familiar with others' scheduling choices or a new script author's coding style, or when
investigating backup and maintenance scripts, I was even unsure of what kind of scheduler had been implemented.
When multiple job schedulers were in use, often incorrect assumptions were made about which scheduler was
executing which task in regards to monitoring, backup, and alerting.
It was immediately apparent that almost no time was required to acclimate in environments that utilized the
job system through Enterprise Manager. The interface was similar no matter whether it was in a 10g or 11g Enterprise
Manager or even the new 12c version. Maintaining, changing, “skipping,” or any other tasks regarding the job within
the Enterprise Manager Jobs interface were easy for administrators to familiarize themselves with. As all jobs were
contained within the Enterprise Manager, creating maintenance windows during blackouts was simpler to manage.
The benefits of using the EM12c Jobs interface over other schedulers are as follows:
•
Simple or advanced job search feature with wildcard functionality
•
Schedule can be viewed for any conflicts with other running jobs across the entire
environment
•
Choice to skip all jobs during a target blackout or to configure jobs to run even though the
target is in a blackout state, simplifying concerns of tasks running during maintenance
•
Ability to incorporate scripts into the EM12c Job System to perform any task, providing a
uniform scheduling, notification, and alerting system for all job tasks
Enterprise Manager Job Architecture
Three areas, shown in Figure
11-1
, are central to the EM Jobs interface for EM12c:
EM Jobs Service
: The enterprise management target service that manages all jobs in the
Enterprise Manager
Job Library
: Repository for jobs
Job Activity
: Job interface system to view, create, and manage jobs
