Database Reference
In-Depth Information
In Figure
7-21
, in the Synchronization Status box in the middle of the page, you can see the number of targets
with statuses of Synchronized, Pending, Failed, Excluded, and N/A for monitoring templates, compliance standards,
and cloud policies. Follow the recommendations in Table
7-1
for targets in Pending, Failed, or N/A status.
Table 7-1.
Recommendations for Action Based on Synchronization Status
Synchronization Status
What to Do
Pending Targets
Ensure that you have a global synchronization schedule defined. The presence of a Next
Synchronization date indicates that one is defined. If you see N/A instead, define
a schedule.
Failed Targets
Drill down to get details of the specific failures. Fix them where possible. Then either
resync manually, or allow the next scheduled synchronization to take place.
N/A Targets
Targets have no associated monitoring template. Drill down to get the target type,
and add monitoring templates to the template collection.
Incident Management Recommendations
Monitoring the database environment also means making sure that if any of your targets encounter any issues, you
are made aware of them quickly—ideally before any of your clients become aware. It also means that if any operations
occur that are of interest (normal or otherwise), that they will be addressed as needed.
What about impending problems? We need to be made aware of these too, and resolve them before they become
disasters. EM12c provides the tools for the solution in the form of events, incidents, rules, and rule sets. In this section,
you will see how to effectively employ these features to simplify and automate the monitoring requirements.
Events, Incidents, and Problems
An
event
is a discrete occurrence that affects a single monitored target in Enterprise Manager—for example, when
a listener goes down or a filesystem fills up or an archiver hangs. Other occurrences such as job operation status
changes (completed, failed, stopped, suspended) also fall under the category of events.
An
incident
can be thought of as a set of one of more correlated events. An incident typically represents
the occurrence of a significant disruption of service requiring specific actions—including tracking, assignment,
escalation, and resolution. Management of significant occurrences as a single unit is done via incidents and not
events. A host target may generate high CPU (%) and memory utilization events (see Figure
7-22
). A single event
occurrence by itself may not indicate an incident, but a collection of related events may point to an incident that
describes a resource problem.
