在今年的OOW上，oracle发布了最新12c，不过不是database而是 Enterprise Manager Control。
名字叫 Enterprise Manager Cloud Control 12c，很时髦的云控制。
我在MOS上搜索了一下，目前还没有提供下载，如下：

虽然说还没提供下载，但是相关的文档却已经出来或更新了，如下是几篇不错的文档：
FAQ: Enterprise Manager Cloud Control 12c Install / Upgrade Frequently Asked Questions [ID 1363863.1]

Applies to:

Enterprise Manager Grid Control – Version:
12.1.0.1.0 and later   [Release: 12.1 and later ]
Information
in this document applies to any platform.

Purpose

This FAQ includes frequently asked
question about Enterprise Manger Cloud Control 12c (12.1.0.1) Install and
Upgrade.

Questions and Answers

1.) What is new with the install process in
Enterprise Manager Cloud Control 12c?

a.) Enterprise Manager Cloud Control is configured on top of 10.3.5
Oracle Weblogic Server.
b.) The installer (OUI) can install Weblogic Server
(10.3.5) which means there is no need for you to have an existing Oracle
WebLogic Server instance as was the case with Enterprise Manager 11g.
c.) The
installer (OUI) provides an option to have a Simple or Advanced
Installation.
d.) The installer (OUI) provides an option to install only the
software binaries of Enterprise Manager Cloud Control at one point, and
configure it at a later point.

2.) What is the difference between Simple and
Advanced Installation ?

Simple Install uses typical, default configuration.
It is simple and quick, requires less input parameters and uses default settings
and preferences. This option is meant for administrators who do not worry about
the granular control of the installer and wants to install Enterprise Manager
system quickly. Uses common password for SYSMAN, Weblogic user account, node
manager user account and Agent Registration.

Advanced
Install uses custom or advanced configuration, is more flexible. Allows
you to customize different passwords for each user account, OMS Instance base
location, plugins to be installed and configured, data file locations for
tablespaces and customize ports.

3.) What are Oracle Management Plug-ins?

Plug-Ins are pluggable entities that offer special management
capabilities customized to suit specific target types. Unlike the earlier
releases of Enterprise manager, in Enterprise Manager Cloud Control, the
plug-ins work in conjunction with the OMS and the Management Agent to monitor
every target in your environment. Plug-ins are deployed to the OMS as well as
the Management Agent. In the earlier releases, plug-ins enabled you to monitor
only third-party targets, but in Enterprise Manager Cloud Control, plug-ins
enable you to monitor all types of targets in your environment.

Plug-ins
have independent release cycles, so every time you have a new version of an
Oracle product released, you will have a new version of the plug-in released to
support monitoring of that new product version in Enterprise Manager Cloud
Control. This simplifies things as you no longer have to wait to upgrade your
Enterprise Manager system to support a new product version.

4.) What are the Default Plug-ins that get
installed with a new Enterprise Manager system?

Below are the mandatory plug-ins that are installed by default with
a new Enterprise Manager system:

Component	Description
Oracle Database	Enables you to monitor and manage Oracle Database and related targets such as Oracle Real Application Clusters (RAC), Oracle Automatic Storage Management (ASM), and so on.
Oracle Fusion Middleware	Enables you to monitor and manage Oracle Fusion Middleware products such as Oracle WebLogic Domain, Oracle WebLogic AdminServer, Oracle WebLogic Server, Oracle SOA Suite, Oracle Web Tier, and so on.
Oracle My Oracle Support	Enables you to log in to My Oracle Support from within the Cloud Control console, search the knowledge library for notes and documents, raise service requests, and create patch plans and templates for patching monitored targets.
Oracle Exadata	Enables you to monitor and manage Oracle Exadata targets.

5.) Can Enterprise Manager Cloud Control
communicate with earlier release of Management Agents?

Enterprise Manager Cloud Control can communicate only with Oracle
Management Agent 12c and not with any earlier release of the Management
Agent.

6.) How to download 12c Management Agent software
binaries?

The Management Agent software for the same platform and version as
OMS is always present under the OMS Home. If you want to install a Management
Agent for a platform that is different from the one on which the OMS is running,
then ensure that you download that software using the Self Update console, which
is built into the Cloud Control console. For information on Self Update and how
you can use it to download the software, see the chapter on Self Update in the
Oracle Enterprise Manager Cloud Control Administrator’s
Guide.

7.) What Is Add Host Target Wizard?

The Add Host Targets Wizard is a GUI-rich application accessible
from within the Cloud Control console, and used for installing Management Agents
on unmanaged hosts and converting them to managed hosts in the Enterprise
Manager system.
Using the Add Host Targets Wizard, you can do the
following:
Install a fresh Management Agent
Clone an existing well-tested,
pre-patched, and running Management Agent
Install a Management Agent from an
existing, centrally shared Management Agent

8.) What Is Add Management Service Deployment
Procedure?

A deployment procedure is a procedure that contains a hierarchal
sequence of provisioning or patching steps, where each step may contain a
sequence of other steps. In other words, the workflow of all tasks that need to
be performed for a particular life cycle management activity is encapsulated in
a deployment procedure.

Enterprise Manager Cloud Control offers multiple
deployment procedures, one of them which falls within the context of Enterprise
Manager Cloud Control installation is the Add Management Service deployment
procedure. The Add Management Service deployment procedure helps you meet
high-availability requirements by enabling you to install an additional OMS
using an existing OMS that is running on an AdminServer host. The deployment
procedure clones an existing OMS and replicates its configuration to the
destination host. The earlier releases of Enterprise Manager offered this
installation type from the Enterprise Manager Installation Wizard. However, for
the Enterprise Manager Cloud Control release, this installation type is offered
as a deployment procedure. For more information about the deployment procedure,
see the chapter on adding additional management service in the Oracle Enterprise
Manager Cloud Control Basic Installation Guide.

9.) What are the Supported Upgrade Paths?

The following upgrade paths are supported:

• You can upgrade from Enterprise Manager 10g Grid Control Release 5
  (10.2.0.5.0) directly to Enterprise Manager Cloud Control
• You can upgrade from Enterprise Manager 11g Grid Control Release 1
  (11.1.0.1.0) directly to Enterprise Manager Cloud Control.
• You can upgrade from Enterprise Manager 10g Grid Control Release 5
  (10.2.0.5.0) to Enterprise Manager 11g Grid Control Release 1 (11.1.0.1.0), and
  then upgrade to Enterprise Manager Cloud Control.

10.) What are the available Upgrade
Approaches?

Oracle offers the following upgrade approaches to upgrade your
existing Enterprise Manager system:

• 1-System Upgrade Approach: This approach enables you to
  upgrade to Enterprise Manager Cloud Control on the same host where your earlier
  release of Enterprise Manager is running. This approach also upgrades the Oracle
  Management Repository (Management Repository) in the existing database. Since
  the upgrade happens on the same host, there is a reasonable downtime involved.
  This approach does not refer to upgrading of an Enterprise Manager system in an
  environment with one Oracle Management Service (OMS). It refers to upgrading of
  an Enterprise Manager system on the same host as the old one, and having only
  one Enterprise Manager system existing at any point.

• 2-System Upgrade Approach: This approach enables you to
  install Enterprise Manager Cloud Control on a host that is different from the
  host where your existing Enterprise Manager system is running.This approach does
  not upgrade the Management Repository in the existing database, but upgrades the
  one in the backed up database, thus enabling two Enterprise Manager systems to
  exist. Since a new Enterprise Manager system coexists with the old one, there is
  no or near zero downtime involved.

• 1-System Upgrade Approach on a Different Host: This
  approach enables you to install Enterprise Manager Cloud Control on a host
  different from where the existing Enterprise Manager is running. This approach
  is similar to the 2-system upgrade approach, but unlike the 2-system upgrade
  approach, this approach upgrades the Management Repository in the existing
  database itself. Since only one Enterprise Manager system exists at any point,
  there is a reasonable downtime involved.

11.) Provide a Comparison between the available
Upgrade Approaches?

另外还有两篇相关的文章，大家也可以参考参考，如下：

How to Configure Logging for EM 12c Management Agent [ID 1363757.1]
FAQ On Best Practices for Preparing Your Fusion Applications Instance for Troubleshooting [ID 1353907.1]