Enterprise Manager 13c: What’s New in Database Lifecycle Management
A month back, we announced the
release of Enterprise Manager 13c. Enterprise Manager 13c includes several
improvements over Enterprise Manager 12c, which was itself had witnessed pretty
successful adoption over the last four years. Enterprise Manager 12c rested on the key themes of enterprise grade
management, stack management and cloud lifecycle management. The 13c version
simply bolsters those pillars.
In the area of database lifecycle
management, we have delivered some key features that span both the depth and
the width of the data center. In terms of depth, it leverages the unification
of hardware and software management to manage Exadata better. In terms of
width, it offers simpler and more scalable cloud management. Over the next few
paragraphs, I will touch upon few features that highlight the above.
patching of Exadata has been laborious process for our key customers. It
involves multiple components across multiple nodes and often multiple
administrators in the process. In Enterprise Manager 13c, some of the important
hardware management features have been assimilated into the Cloud Control
product. In course of developing the hardware aka the infrastructure management
features, we have modeled the infrastructure target types: servers, storage,
network, VMs in Enterprise Manager. This also enables us to have a more
sophisticated management of Engineered Systems. For example, Enterprise Manager
can now patch an Exadata stack- storage servers
, Infiniband drivers, compute nodes, grid infrastructure and as before, the
databases on top. The patching application offers the facility to run the
pre-flight checks and monitor the logs from a single place (imagine having to manually
monitor the patch execution logs for grid infrastructure, operating system,
storage for all the compute and storage cells in a rack).
in Database Compliance Management:
There have been some significant
enhancements in database compliance management. These include:
a) Integration of Oracheck: A long-standing
requirement that should thrill Exadata customers is the integration of Oracheck
(including Exacheck) into the Compliance framework of Enterprise Manager.
Exacheck had formerly existed as a standalone utility, but customers have asked
for at-scale execution over all the Exa’s in a data center, with the ability to
flag, suppress or escalate any violation. They can also generate reports on
overall health and share with other administrators and IT Managers.
b) Integration with corrective action: Another
much sought-after feature has been to integrate the compliance violations with
corrective action. For example, a DBA may want to lock an account with default
username and password. Enterprise Manager 13c makes this a reality.
Configuration Drift and Consistency Management:
When it comes to
managing a cloud horizontally at scale, the configuration comparison feature of
Enterprise Manager has always been a DBA’s favorite. The new configuration drift management
feature evolves the feature further by enabling administrators to proactively spot the “needle
in the haystack” among the hundreds and thousands of members that can be a part
of a cloud or even span multiple clouds (example, on-prem and Oracle Cloud). The DBA can set up a golden standard with a
selected list of configuration parameters and make sure that all the members of
a cloud or a pool of databases subscribe to that standard. In case of any
deviation, the DBA will be automatically notified. The consistency management
can be applied across the different phases of lifecycle (for example, the test
database should be the same as production) or across the different members of a
system (for example, all the nodes of an Exadata should be exactly alike).