Oracle Enterprise Manager application reference

I. OEM Architecture

Currently, Oracle Enterprise Manager (EM) Version 2.2 is used to implement a three-layer structure. Its composition is as follows:

The first layer is client tools, such as EM Console, DBA Management Pack and other integrated Oracle Applications. These tools are started locally on Windows NT, Windows 95, Windows 98, or Sun Solaris machines. These tools can also be JAVA applets downloaded from a browser.

The second layer, that is, the middle layer is composed of Oracle Management server (OMS) installed on Windows NT/2000 or Sun Solaris Server. Many tools require that OMS be configured first.

OMS provides:
-Access information in the EM library Repository.
-Dispatch console requests
-Control task execution
-Monitoring event
-Prompts the task completion or event by email or Paging

Multiple OMS provides:
-Load distribution can be achieved without additional management
-Workload can be automatically shared and balanced
-Fault Tolerance: One OMS can redo the workload of another OMS.

The third layer is the Intelligent Agent), which must be installed on each server to execute tasks and monitor the software for events that occur on the Managed Objects of the server. Managed Objects include network node servers), databases, listener listeners, and other Oracle services installed on these nodes.

The layer-3 structure only distinguishes functions. It can be combined in any way during installation and configuration.

Ii. OEM component Introduction

The OEM package has a set of tools:
DataManager Data Manager): This tool enables you to execute data export/import like loading data.
SchemaManager: This tool enables you to manage objects in the database. It can be used to create, modify, and delete tables, indexes, views, snapshots, sequences, and so on.
SecurityManager Security Manager): This tool enables you to manage users, roles, permissions, and profiles.
StorageManager Storage Manager): This tool allows you to create and modify tablespaces, data files, and rollback segments.
InstanceManager instance manager): This tool allows you to disable, start an instance, and store and manage database parameters.
SQL * Worksheet: This tool enables you to run or create SQL scripts and store them on hard disks. You can use this tool to reproduce the last executed statement and check the execution results displayed on the screen.
BackupManager backup manager): This tool allows you to manage backups and restore to Oracle7 and Oracle8 databases. In Oracle7, this tool supports EnterpriseBackupUtility (EBU), and in Oracle8, this tool supports the recovery manager RecoveryManager.
SoftwareManager software manager): This allows you to install remote software on a remote server that supports this feature.

Iii. OEM installation and Setup

OEM 2.2 needs to be installed separately. It can be downloaded from the official ORACLE website. Now, the download has been canceled, so the SOURCE can only be achieved by different means.

1. Start intelligent proxy

To manage oracle services on nodes and nodes, you must configure and run an Intelligent Agent (Intelligent Agent) on the nodes ). Intelligent proxy can be installed from Oracle Server CD. Generally, you will choose to install it when installing the database. If you do not install it separately.

If the managed node is NT, It is very troublesome to set up intelligent proxy in the past. Now I think everyone is using 2 K, so you don't need to do this step, as long as you have installed it, the system automatically starts an OracleAgent service without any other settings.

If the managed node is a UNIX system, you can start, stop, and check the status through lsnrctl dbsnmp_start | dbsnmp_stop | dbsnmp_status after normal installation. If not, it may be the execution permission. Check that the $ ORACLE_HOME/bin/dbsnmp permission is-rwsr-xr-x. If not, it may be root during installation. sh is not correctly executed. this is generally not the case, so you can directly change its permissions to chmod 4755.

2. Run emca to create EM Repository

OMS requires an EM Library (Repository, not a Database). It actually requires a tablespace that contains a set of tables, views, indexes, stored procedures, and other objects required by OMS, it is mainly used to store OMS system data, application data, and the state of the managed node in the environment. Therefore, we recommend that you create the EM Repository on the DBA instead of the product database.

EmcaConfiguration Assistant is generally used to create the EM Repository tablespace on an existing database. Of course, using emca will also complete the following tasks:
-Create a repository user
-Create a mode/schema object for the repository user
-Load OMS registry data to EM repository.
-Set the configuration file to be used by OMS.
-Clear the repository from a user mode.
-Modify the repository to which the OMS connects.

3. Start OMS

In Windows, start the OracleManagementServer service to start OMS, and use oemctrl start oms & on Solaris to start OMS. Logs are stored in the $ ORACLE_HOME/sysman/log directory.

4. Start the EM Console to add managed nodes

There is a console menu in windows. The command line uses the oemapp console. The default OEM Logon Name Is sysman/oem_temp. After you enter the default logon name, you will be forced to change the initial password. It is worth noting that these users are only EM console and OMS users, not database accounts, but their information is stored in a table in EM Repository.

Then you can search for and add nodes in the graphic interface. If you cannot add nodes automatically, You can manually add them.

5. Start related tools

So far, you have completed OMS settings. You can use relevant DBA tools to complete your work. The command line is as follows: oemapp dbastudio | security | schema | instance | storage | worksheet

(