Database Reference
In-Depth Information
In this example, we will add a usage metric to monitor for mapping errors on an unmonitored NFS server
(see Figure
11-30
).
Set the Target Type option to Host and the Metric option to Unmonitored NFS Server Mapping Errors. Then
you choose the host target you wish to base ithe metric on and choose whether to allow EM12c to monitor each disk
separately or by the average of total storage free on the specific disk (see Figure
11-31
).
Next, you click Continue and proceed to name your usage metric and set warning and critical thresholds
(see Figure
11-32
). Then click OK to save the new usage metric.
Figure 11-32.
After giving the usage metric a descriptive title, set reasonable thresholds
This metric is now available for use and can be accessed from the All Metrics section of the EM console.
Migrating Scripts to the EM Job System
It is a simple process to migrate existing scripted jobs that may be currently using cron or another scheduler to the EM
Job System.
These changes to the preexisting scripts must be considered:
•
No longer will many environment variables be required as they once were. The EM Job System
will already know what the
ORACLE_HOME
, the
ORACLE_SID
(target), and others will be through
the EM and the target properties.
•
Submitting a job against multiple targets is easy, whereas before, complex, cross-server
authentication may have been required.
•
Maintenance and other jobs can be submitted against target groups in EM, allowing for ease
of database management. If the group is updated, the job will then address the changes to the
group as well.
•
Jobs can be attributed to multiple types of targets, including hosts, clusters, and directories.
EM Job privileges are very granular, allowing the creator/administrator to share the job with other administrators.
These privileges include the following:
•
Full access to edit, delete, or manage the job.
•
Viewing the results of the job
