Database Reference
In-Depth Information
Figure 13-1.
Enterprise Manager Cloud Control 12c architecture
Different levels of high availability can be configured for each component with varying levels of complexity and
cost. When considering your high-availability requirements, there should be minimal trade-offs in cost, complexity,
performance, and data loss. Generally, the complexity and level of high availability are proportional to each other.
The Oracle Management Agent should be configured to start on boot. This ensures that no manual intervention
will be required after a server reboots and quickly enables targets to be monitored after a service disruption. On Unix
and Linux operating systems, a script called
gcstartup
is placed in
/etc/init.d
and made to run at certain runlevels.
On Microsoft Windows, a service is created to start automatically on boot.
Oracle has defined four levels of high availability for Enterprise Manager Cloud Control. These are summarized
in Table
13-1
. Only levels 1 to 3 are covered in this chapter.
Table 13-1.
Levels of Enterprise Manager High Availability
Level
Description
Load Balancer Required
Cost
1
OMS and repository on separate hosts.
No redundancy.
No
$
2
OMS installed on shared storage with VIP used in active/passive
failover.
Repository database using local Data Guard.
No
$$
3
Multiple OMSs in active/active configuration. Repository using
RAC database with local Data Guard.
Yes, at primary site
$$$
4
Primary OMS in active/active configuration with RAC repository
database. Standby OMS at DR site in active/active configuration.
Standby RAC database at DR site.
Yes, at primary and
standby sites
$$$$
