Oracle Enterprise Manager can be deployed in three different architectures:
- Database control - OEM application for managing a single Oracle Database. The binaries are always installed with the database software, and the OEM repository is optionally created and configured as part of the database creation.
- Grid control - OEM’s web-based interface for centrally managing multiple Oracle environments from a single point. It requires a separate installation and configuration.
- Cloud control - Enterprise Manager Cloud Control is a system management software that delivers centralized monitoring, administration, and lifecycle management functionality for the complete IT infrastructure, including systems running Oracle and non-Oracle technologies.
Oracle Enterprise Manager itself is part of the Oracle Database license and does not require a separate license. The OEM functionality included in the Oracle Database is, in essence, a set of basic functionalities which can be used to perform usual administrative tasks (e.g.: creating database objects [tables and indexes], managing user security, backing up and recovering the database, and importing and exporting data).
By default, during the installation process, the Oracle Management Agent (OMA) enables several so-called "Database Enterprise Edition Management Packs" including the ‘Diagnostics Pack’, ‘Tuning Pack’, ‘Database Lifecycle Management Pack’, ‘Data Masking & Subsetting Pack’, ‘Cloud Management Pack for Database’, without any connection to what a customer has licensed. As an end-user, you therefore need to proactively deselect unlicensed packs after installing the agent on a target database to avoid any unlicensed use. Doing so would, however, store a timestamp in the Database and will make the "Pack Access Agreed" marked TRUE in the underlying database schema.
Those premium functionalities contained within OEM require a separate Oracle license, the so called "Oracle Database Enterprise Edition Management Packs" or "OEM Pack”. Technically, however, such an OEM Pack does not exist – these consist of a "suite" of database features which Oracle classifies as licensable features.
In the past, OEM versions prior to Database 10g, OEM Packs were optionally installed on request of the end-user as part of OEM installation process. As of version 10g, OEM Packs are always installed with the configuration of the basic OEM functionality without the end-user having any control. As of this version, a new feature has been introduced for the end-users as well. It is called the "Management Pack Access" page and on this page, users can start enabling or disabling access to the OEM Packs functionality from that version.
When access is enabled for an OEM Pack, all the interface elements (tabs, buttons, and hyperlinks) and functionalities corresponding to the specific OEM Pack are enabled and can be accessed by the end-users.
Disabling Pack access will result in disabling or hiding all the corresponding interface elements but does not result in a deinstallation.
Starting with Database version 10g, OEM binaries, including all the packs, are always installed with the database software. The OEM Packs are installed and enabled by default with the configuration of the DB Enterprise Manager, which is part of the database creation process.