Database Reference
In-Depth Information
On the next screen, titled “Add Database Instance Target: Specify Host” you need to select the host to which the
target belongs using the magnifying glass or type the name in directly. If the host you want to add your target from
does not exist in the list-of-values search you should investigate agent communication problems between the OMS
and the host. Clicking on “Next” will initiate the target discovery process.
Once that process is completed you are presented with an overview of discovered targets as shown in Figure
8-21
.
The next step is to configure them by clicking on the wrench icon in the “configure” field.
Figure 8-21.
OEM presents a list of discovered targets
The target configuration screens are usually self-explanatory. For databases all you have to add is the dbsnmp
password. Note that for newer database targets the dbsnmp is often locked and needs unlocking first. An additional
screen allows you to define the Target Global Properties such as a contact, lifecycle status, and more. After saving the
changes in the summary screen a new target becomes active after a slight delay. There is no need to panic if the target
does not appear straight away or if there is a watch depicted as the status: the agent has to gather metric information
about the target before it can be fully accessed.
If you look at Figure
8-21
closely you will notice a change from previous versions of Oracle Enterprise Manager.
Instead of only adding the database instance, Enterprise Manager 12c Cloud Control will automatically create what
it calls a
system
for a database. A system in OEM terminology is a logical group of targets that need to be up in order
to support a given service. By default, the database system created uses the suffix “SYS” to indicate its function. You
can view systems via Targets
➤
Systems. A typical system created on ASM in an Oracle Restart configuration will have
these members:
•
ASM instance
•
Listener
•
The database instance
Search WWH ::
Custom Search