Database Reference
In-Depth Information
Second, the other management tools are scaled-down tools that generally connect to only a single environment
at a time, rather than giving you the much broader data center-wide vision of your environment. As an example, DB
Control can connect to only a single Oracle database at a time. If you want to use DB Control to manage or monitor
another Oracle database, you have to first disconnect from the original database before connecting to the new one.
In fact, if you don't do that, Oracle will do it for you automatically.
Finally, there are some incompatibilities between the different tools. For example, when you create an Oracle
database by using the Database Configuration Assistant (DBCA), you will be asked whether you want the database
to be managed centrally (via EM12c) or locally (via DB Control). It's an either/or decision; you can't choose both.
This incompatibility reaches its zenith with the OMR. When you install EM12c, you are prompted for the location
of the repository. (The installer does not create the database for you; it simply prompts you to point to the location
of an existing Oracle database somewhere in your environment.) If the database you point the installer to has been
configured by DBCA to be locally managed by DB Control, you will in fact get an error from the installer indicating
that the database is already locally managed. (The installer does give you the command to remove the DB Control
configuration if you so choose, but won't actually execute the command for you.)
On a final note, at the time of writing this chapter, Oracle has announced that DB Control will be desupported in
database releases after 11.2. Although we don't know yet what the new product will be called, Oracle notes, “In future
Oracle Database releases, basic database management will be available through a streamlined management tool,
while extensive management capabilities will exist through the latest Oracle Database plug-in deployed from Oracle
Enterprise Manager Cloud Control” (see Note 1484775.1 on My Oracle Support for details).
Command-Line Tools
In addition to the GUI that most users of EM12c will use for their day-to-day work, Oracle provides two command-line
tools that you need to become familiar with:
Enterprise Manager Command Line Interface (EMCLI)
: This tool is largely used for scripting
operations that might need to be repeated. It is a tool often used by consulting companies
that make a business out of configuring EM12c, who thus have a need to execute the same
operations repeatedly across different customers. EMCLI can be installed on any computer
(not necessarily the OMS or OMR) simply by downloading the tool via the Cloud Control
Setup menu and then following the installation instructions. Not all operations that can be
performed through the GUI can be performed with EMCLI, however.
Enterprise Manager Control (EMCTL)
: This utility is used for a variety of tasks, the most
important of which are starting, stopping, and checking the status of the OMS, agent, and
Cloud Control itself. It is also used to secure/unsecure agents and the OMS, starting and
stopping blackouts and other operations.
Repository Users
In terms of database users, the most important user in an EM12c installation is the
SYSMAN
user. The
SYSMAN
user has
been around for a number of releases now. It is basically the owner of the database schema containing the repository.
In many ways, it is akin to the
SYS
user in an Oracle database, and as such, should not be used apart from the first time
you create another Super Administrator account (see Chapter 4 for more details on Super Administrator accounts).
Apart from the
SYSMAN
account, other database users are created in the repository during repository creation or
upgrade. These include the following:
•
CLOUD_ENGINE_USER
and
CLOUD_SWLIB_USER
are used to perform cloud operations.
•
MGMT_VIEW
is used for report generation.
