Installing and configuring Oracle Database Control Using Emca on the command line interface

Installing and configuring Oracle Database Control Using Emca on the command line interface

As a loyal user of the command line, the O & M of the server software tends to be completed using commands or scripts, so it is annoying to use a large amount of GUI resources. As an important server software, Oracle database installation and O & M naturally fully supports the command line method, although it also provides the oui gui installer. As for Silent Installation of Oracle11g in command line, I have previously written a detailed blog post. For more information, see the blog post. The database installed in this blog post is fully available. This article is a supplement to the previous blog post, that is, to install and configure Oracle Enterprise Manager based on the database installation, so that the Administrator is tired of SQL plus, you can use a browser to manage Oracle databases.

1 Oracle Enterprise Manager and Oracle Database Control

OEMs are collectively referred to as graphical enterprise-level management tools provided by Oracle. There are three available tools:

(1) Database Control

It is used to manage a database (which can be a RAC cluster database). It has the functions of real-time management and monitoring, running and scheduling jobs, and alarming.

(2) Application Server Control

Used to manage one or more application server instances.

(3) Grid Control

Grid Control can manage multiple databases and application servers, computer nodes, and third-party products through third-party plug-ins.

Before Oracle9i and Oracle, the OEM appeared in the C/S architecture. The B/S architecture was used starting from 10 Gb, so that the administrator can directly manage it through a browser without installing the client. This article focuses on the Database Control Tool. Database Control does not need to be installed independently. It is automatically installed together when oracle is installed, but must be carefully configured before it can be used.

2 Oracle Database Control directory structure and working principle

To analyze any software, you must start from the static and dynamic aspects. The static content corresponds to the physical directory and file layout after the software is installed; it dynamically corresponds to the interaction process and memory layout between various parts during software running.

2.1 directory structure

The directory structure of Database Control in 10g and 11g is slightly different. This article describes the differences based on 11g.

After installing oracle 11g, the $ ORACLE_HOME directory contains a directory dedicated to providing services for Database Control, as shown in. In this example, the oracle oc4j iner for j2ee is abbreviated as the oracle-dedicated j2ee container, which is similar to tomcat.

-------------------------------------- Split line --------------------------------------

Oracle 11g installation manual on RedHat Linux 5.8 _ x64 Platform

Installing Oracle 12C in Linux-6-64

Install Oracle 11gR2 (x64) in CentOS 6.4)

Steps for installing Oracle 11gR2 in vmwarevm

Install Oracle 11g XE R2 In Debian

-------------------------------------- Split line --------------------------------------

2.2 Working Principle

In essence, Database Control is a j2EE application, but this application has a single function, that is, managing Oracle databases. It runs in oracle's custom j2EE container, uses its managed oracle database to store its own data, and uses a proxy process to collect system information outside the database.

From a program perspective, Database Control is actually not associated with the oracle Database managed by it (called the target Database). You can use a separate Database (such as a separate oracle Database or mysql Database) can also run in a single machine's j2EE-compliant container (such as Tomcat ). However, Oracle has customized specialized containers for the efficiency and configuration, and uses the target database to store management data, and runs on the machine where the target database instance is located.

Shows how Database Control works.

The management data used by Database Control is stored in the SYSMAN mode.

After understanding the working principle, the configuration is easy to understand. Like deploying other j2EE programs, you need to do so in terms of data and program files. In essence, all these operations can be done manually. However, whether creating a large number of configuration files or creating a large number of data tables, manual operations are inefficient and error-prone. Therefore, Oracle provides specialized tools and software for Database Control deployment.

If you use OUI to install Oracle, you can configure Database Control During the installation phase. After the installation is complete, you can also configure it through DBCA. These are easy-to-use GUI tools, however, the purpose of this article is to configure in command line only, so the above method is unavailable.

To cope with the Configuration in command line mode, ORACLE provides the Configuration Assistant emca (Enterprise manager Configuration Assistant) for Database Control ).

For more details, please continue to read the highlights on the next page:

1 2 3 Next Page