Summary Of OEM Features

Oracle Enterprise Manager (OEM) V2.0.4:

- The OEM must be installed in an Oracle Home that is different than the one used for

Oracle 8i.

- In the new OEM, the Backup Manager and the Data Manager are integrated into the Storage Manager. The Data Manager can also be found in the Schema Manager!

- Most of the console and the DBA Management Pack tools are rewritten from C++ to Java.

- The Communication Daemon is not used anymore.

Oracle Management Server "OMS":

- Only one OMS per machine.

- An OMS can manage only one repository.

- Handles connections to the repository. OEM consoles connect to the OMS in order to gain access to the repository.

- Jobs and events are managed by the OMS. In the old OEM, they were managed by the console. This feature enables the events and jobs to function even when the OEM console is not started.

- The OMS can reside on a machine by its own. For example, you can have the

OMS in one machine, the OEM Console in other machine, and the database containing the repository in another machine. (3-Tier Architecture.)

- Must be started before starting the OEM console. In NT, the OMS exist as a NT service.

- The OMS is created when a new repository is created.

- Different OMSs can access one repository. This feature enables load balancing and fault-tolerance.

- Before running the OMS, the following services must be up and running:

- The database containing the repository.

- The Listener.

- The IA.

Repository:

- A repository can be shared now by more than one DBA. In the old OEM this wasn't possible.

- The repository can be placed in a schema by its own. In the old OEM, the repository exists in a user's schema.

- The repository can be located in any database accessible to the OMS.

- A repository can be accessed by more than one OMS.

Intelligent Agent (IA):

- The IA used in OEM V2 is same as the one shipped with OEM version 1.X.

- The IA must be started before starting the OMS.

- Only one IA per machine.