Lesson 1

Oracle database administration can be performed through several different interfaces. Earlier lessons in this course emphasized command-driven interaction with Oracle, especially through tools such as SQL*Plus. That approach remains important because a database administrator must understand SQL, PL/SQL, privileges, roles, users, storage, sessions, and database behavior at the command level. A graphical tool can make administration easier, but it cannot replace the knowledge required to understand what the database is doing.

Oracle Enterprise Manager, commonly abbreviated as OEM, provides a centralized web-based management environment for Oracle databases and related infrastructure. In a modern Oracle Database 23ai environment, Enterprise Manager is best understood as an operational control plane. It helps administrators monitor databases, review alerts, inspect performance, manage targets, schedule jobs, view configuration information, and maintain visibility across many systems from a single administrative console.

This lesson introduces Oracle Enterprise Manager as a major interface used by Oracle DBAs. The goal is not to suggest that Enterprise Manager replaces SQL*Plus, SQLcl, RMAN, listener utilities, shell scripts, or direct SQL commands. Instead, Enterprise Manager should be viewed as a complementary platform. Command-line tools provide precision and scriptability. Enterprise Manager provides centralized visibility, monitoring, reporting, alerting, and operational coordination.

A single Oracle database can be administered with command-line tools, SQL scripts, and manual inspection. That approach becomes harder as the environment grows. A production organization may have development, test, staging, reporting, and production databases. It may also have multiple hosts, listeners, storage systems, application servers, engineered systems, cloud resources, and different administrative teams. When the number of systems grows, the DBA needs a way to see the health of the environment as a whole.

Enterprise Manager helps solve that problem by collecting information from managed systems and presenting it through a browser-based console. Instead of connecting to each database separately to determine whether it is available, overloaded, misconfigured, or generating alerts, the administrator can review a centralized view of monitored targets. This does not eliminate the need for deeper command-line investigation, but it gives the DBA a strong starting point.

For example, if a database target crosses a warning threshold for tablespace usage, Enterprise Manager can raise an event or incident. If a host target shows abnormal CPU utilization, the monitoring view can help the administrator identify the affected system. If a database is unavailable, the console can show that status without requiring the DBA to discover the failure manually. This kind of unattended monitoring is one of the strongest reasons to use Enterprise Manager in a modern Oracle environment.

A modern Oracle DBA should be comfortable with both command-line administration and web-based administration. Each approach has a different strength.

Command-line administration is direct, precise, and scriptable. SQL*Plus and SQLcl allow the DBA to connect to the database, run SQL statements, execute PL/SQL blocks, create users, grant privileges, revoke privileges, query data dictionary views, and perform many other administrative tasks. RMAN is used for backup and recovery operations. Listener and network utilities help diagnose connectivity problems. Shell scripts and scheduled jobs can automate recurring work.

Enterprise Manager adds a different layer. It provides dashboards, target pages, monitoring templates, alerts, incidents, job scheduling, configuration information, and historical visibility. It is especially useful when a DBA is responsible for more than one database or when several administrators need a shared view of the environment.

Certification exams and serious administration work still require command knowledge. A DBA should understand what Enterprise Manager is doing behind the interface. For example, if Enterprise Manager shows a problem with a user account, tablespace, listener, or performance metric, the DBA should know how to investigate the condition with SQL, data dictionary views, operating system tools, or Oracle diagnostic utilities. Enterprise Manager improves visibility, but the administrator still needs database knowledge.

Oracle Enterprise Manager is Oracle's centralized management platform for monitoring and administering Oracle databases, hosts, and related infrastructure. In current Oracle environments, Enterprise Manager Cloud Control is the web-based platform used to manage many Oracle targets from a central console.

The term target is important. In Enterprise Manager, a target is a managed object. A target can be an Oracle database, a host, a listener, an application server, a storage component, an engineered system, or another monitored resource. By treating each managed component as a target, Enterprise Manager can organize administration around the actual systems that matter to the business.

For Oracle Database 23ai administration, a database target may expose information about availability, performance, storage usage, sessions, configuration, alerts, incidents, and other operational details. A host target may expose operating system information such as CPU, memory, disk, and process behavior. A listener target may help the DBA understand whether database connectivity infrastructure is functioning correctly.

Enterprise Manager is therefore more than a graphical replacement for SQL*Plus. It is a management platform that connects monitoring, configuration, alerting, job execution, and administration into one operational framework.

Older Oracle training material often described Enterprise Manager in terms of two-tier and three-tier GUI configurations. That historical model is no longer the best way to introduce the product. A modern explanation should focus on the major Enterprise Manager components used in Cloud Control architecture.

The first major component is the Enterprise Manager Console. This is the browser-based interface used by DBAs and system administrators. Through the console, administrators can view targets, review alerts, inspect database health, manage jobs, examine configuration information, and move through different administrative workflows.

The second major component is Oracle Management Service, or OMS. The OMS is the middle-tier service that coordinates the Enterprise Manager environment. It communicates with Management Agents, processes information from monitored targets, works with plug-ins, stores collected information in the Management Repository, and renders the web interface used by administrators.

The third major component is the Management Repository. This repository is a database used by Enterprise Manager to store collected monitoring information, configuration data, job history, incident information, and other management data. The repository is important because Enterprise Manager is not only showing current status. It also retains historical information that can be used for review, reporting, trend analysis, and troubleshooting.

The fourth major component is the Management Agent. A Management Agent is installed to collect information from managed hosts and targets. The agent monitors target status, collects metrics, communicates with the OMS, and helps Enterprise Manager maintain an accurate view of the managed environment.

Enterprise Manager 24ai also introduces modern Remote Agent capabilities. A Remote Agent can monitor and manage remote targets without requiring a traditional local agent installation on every host. This can reduce agent lifecycle overhead in large environments. The DBA should understand the basic distinction: a local agent monitors targets on or near its host, while a remote agent can monitor supported remote targets through remote protocols and managed connectivity.

Enterprise Manager monitoring is built around targets and metrics. A target is the object being monitored. A metric is a measurement collected about that object. For a database target, metrics may describe availability, tablespace usage, active sessions, workload behavior, memory pressure, wait activity, backup status, or other operational conditions. For a host target, metrics may describe CPU utilization, memory usage, filesystem consumption, or operating system status.

A threshold defines a condition that should be considered abnormal or worth attention. Thresholds are usually classified into warning and critical levels. A warning threshold indicates that a condition should be reviewed before it becomes serious. A critical threshold indicates that the condition may already be affecting availability, performance, capacity, or service quality.

When a target goes down or a metric crosses a threshold, Enterprise Manager can generate an event or incident. An event records that something significant occurred. An incident groups related events or conditions into a form that can be tracked, assigned, reviewed, and resolved. This model helps DBAs move from passive observation to active operational response.

Notifications extend that model. Instead of requiring administrators to stare at a console all day, Enterprise Manager can notify interested parties when important conditions occur. A production DBA team can configure notification rules so that the right people are alerted when database availability, storage, performance, or infrastructure conditions require attention.

Enterprise Manager Cloud Control supports unattended monitoring of an Oracle environment. The word unattended is important because production systems must be watched even when a DBA is not actively connected to them. Enterprise Manager collects metrics, evaluates thresholds, records events, raises incidents, and supports notification workflows.

The monitoring process begins when targets are added to Enterprise Manager. Targets can be added manually, or Enterprise Manager can discover them. Discovery is especially useful in larger environments because it helps identify hosts, databases, listeners, and related components that should be monitored. After targets are discovered and promoted, Enterprise Manager can begin collecting metrics from them.

Monitoring settings can be standardized so that similar targets are managed consistently. For example, a company may want all production databases to use one monitoring standard, all test databases to use another standard, and all development databases to use a less aggressive notification policy. Administration groups and monitoring templates help DBAs apply consistent settings across many targets.

Enterprise Manager also supports metric extensions. A metric extension allows administrators to monitor a condition that is specific to their environment. This is useful when a company has a custom application, a special operational rule, or a site-specific query that should be included in monitoring. Instead of relying only on built-in metrics, the DBA can extend monitoring to include local business or technical requirements.

Oracle Database 23ai continues the long Oracle tradition of requiring administrators to understand users, privileges, roles, profiles, storage, backup, recovery, security, performance, and connectivity. Enterprise Manager does not remove these responsibilities. Instead, it provides a centralized environment for observing and managing them.

In a user management module, Enterprise Manager is especially relevant because database security is not only a matter of issuing individual commands. A DBA must understand who can connect, what privileges have been granted, which roles exist, how profiles affect account behavior, and how security activity is monitored. SQL statements such as CREATE USER, GRANT, and REVOKE remain fundamental. Enterprise Manager can help the DBA view and manage related administrative information through a web interface.

Enterprise Manager also helps administrators see the broader operational context around users and security. For example, a locked account, failed login behavior, configuration issue, or availability problem may appear as part of a larger monitoring picture. In a production environment, user management is connected to application availability, audit expectations, compliance requirements, and change control.

Oracle Unified Auditing, privilege management, role design, and account security remain command-level and policy-level topics. Enterprise Manager can support administration and visibility, but the DBA still needs to understand the underlying database concepts. This is why the best learning path combines SQL-based administration with Enterprise Manager awareness.

Oracle Enterprise Manager

A centralized Oracle management platform used to monitor, administer, and manage Oracle databases, hosts, and related infrastructure.

OEM

A common abbreviation for Oracle Enterprise Manager.

Enterprise Manager Cloud Control

The web-based Enterprise Manager platform used for centralized monitoring and management of Oracle environments.

Enterprise Manager Console

The browser-based interface used by administrators to view targets, alerts, incidents, jobs, configuration information, and monitoring data.

Oracle Management Service

The middle-tier component that coordinates communication between the console, agents, plug-ins, and repository.

Management Repository

The database repository where Enterprise Manager stores monitoring data, configuration data, job information, incident history, and other management information.

Management Agent

Software that collects monitoring and configuration information from managed hosts and targets and communicates with the Oracle Management Service.

Remote Agent

A modern agent model that can monitor supported remote targets and reduce the need to install a separate agent on every monitored host.

Target

A managed object in Enterprise Manager, such as a database, host, listener, application server, storage component, or cloud-related resource.

Metric

A measured value collected about a target, such as availability, storage usage, CPU utilization, session activity, or response time.

Threshold

A configured warning or critical boundary that determines when a metric should raise attention.

Incident

A managed operational condition that can be reviewed, assigned, tracked, and resolved by administrators.

A DBA may use Enterprise Manager at the beginning of the workday to check database availability, review open incidents, inspect recent alerts, and determine whether any targets require immediate attention. This provides a structured way to move from environment-wide status to individual problem investigation.

Enterprise Manager can also be used during performance review. If users report that an application is slow, the DBA may begin by checking the affected database target, reviewing workload indicators, looking for resource pressure, and identifying unusual activity. The DBA may then move into SQL tuning, operating system analysis, application review, or command-line diagnostics depending on what Enterprise Manager reveals.

Job scheduling is another common use case. Enterprise Manager can help administrators define and monitor administrative jobs. In large environments, centralized job management can be easier to review than isolated scripts scattered across individual hosts. However, the DBA should still understand the commands and scripts that the jobs execute.

Configuration management is also important. Enterprise Manager can help compare and review configuration information across targets. When many databases exist, even small differences in configuration can affect performance, security, backup behavior, or availability. Centralized configuration visibility helps the DBA detect inconsistency before it becomes an operational problem.

It is tempting to think of Enterprise Manager as a tool that makes Oracle administration easy. That is only partly true. Enterprise Manager makes many administrative conditions easier to see, but it does not eliminate the need to understand Oracle architecture.

If Enterprise Manager reports that a database is unavailable, the DBA still needs to know how database instances, listeners, services, network configuration, operating system resources, and storage interact. If Enterprise Manager reports a performance condition, the DBA still needs to understand SQL execution, wait events, indexing, memory, I/O, and workload patterns. If Enterprise Manager exposes a user or security issue, the DBA still needs to understand users, privileges, roles, profiles, authentication, and auditing.

The best way to use Enterprise Manager is to treat it as a high-value operational interface. It helps the DBA observe, organize, and respond. The underlying expertise still comes from knowing the database.

Oracle Enterprise Manager is a central part of modern Oracle Database administration. It provides a browser-based administrative console for monitoring targets, reviewing metrics, responding to incidents, managing jobs, viewing configuration information, and maintaining operational visibility across Oracle environments.

For Oracle Database 23ai, Enterprise Manager should be understood alongside SQL*Plus, SQLcl, RMAN, listener utilities, shell scripts, and direct SQL administration. Command-line tools remain essential because they provide precision, automation, and certification-relevant knowledge. Enterprise Manager adds centralized monitoring, alerting, dashboards, historical visibility, and management workflows.

This lesson introduces Enterprise Manager as the starting point for the module. The remaining lessons can build on this foundation by showing how Oracle administration tasks relate to users, privileges, roles, security, monitoring, and database management in a modern Oracle environment.