Database Reference
In-Depth Information
As you can see from the previous sections it is vital to get the sizing of the hardware for the OMS servers and
repository database right. Also don't forget that you might need the same infrastructure in a disaster recovery
environment. If OEM really becomes the consolidated monitoring platform then you simply cannot afford if the lights
go out and you are not proactively informed about problems with your managed targets. Therefore, before rolling out
such a crucial piece of infrastructure the golden rule of IT applies again: test it under production conditions before
you rely on it!
More detailed information about sizing considerations than we could cram into this section can be found in the
Oracle
®
Enterprise Manager Cloud Control Advanced Installation and Configuration Guide, Chapter 11: “Sizing Your
Enterprise Manager Deployment”.
Installing Cloud Control
Oracle Enterprise Manager is installed in two steps. The first step involves the creation of the repository database.
Depending on the number of targets and the amount of history to preserve you should allocate sufficient disk space
for the management data. If you are planning a large number of targets to be monitored, you should also ensure that
the management repository database is hosted on sufficiently powerful hardware.
If resilience to database instance failure is a strict requirement you should consider the Real Application Clusters
option for the repository database. Organizations experimenting with the consolidation of monitoring solutions
should put special emphasis on the availability of the repository. Consider a high-availability solution for the
database. If there are multiple essentially stateless OMSs for resilience, but only a single instance Oracle database
you might still be in trouble if that goes down! Losing the repository database means losing availability of the directly
attached OMSs, resulting in the undesirable situation of flying blindly. One of the biggest threats to successful
database management is not being able to receive alerts proactively.
Choosing the Operating System for the Management Host
The Management host and repository database do not need to have the same operating system, although you cannot
really make a mistake using x86-64 Linux. At the time of writing Linux was the development platform for Enterprise
Manager, and problem fixing is expected to be quickest and most efficient on the Linux platform. Additionally, as laid
out in the chapter about hardware, the performance of the current x86 processors is more than adequate to display
the Enterprise Manager console. The Enterprise Manager OMS is certified for Oracle Linux 5 update 2 and later. The
OMS is also certified on Oracle Linux 6 after the application of a mandatory patch.
■
Due to the constraints in regards to addressing raM you should not use a 32-bit operating system for the
management host! This recommendation should actually be extended in most situations to: “you should not use 32-bit
operating systems for production.”
Note
As with any planned deployment of Oracle products on a specific combination of hardware and software
you should check the certification matrix first. Enter the following after logging into My Oracle Support's
“Certifications” tab:
•
“Enterprise Manager Base Platform - OMS” in the Product field.
•
“12.1.0.x.0” as the Release.
•
Your target platform in the Platform field.
Search WWH ::
Custom Search