Introduction to Oracle enterprise manager OEM 13c and its history
Oracle Enterprise Manager is Oracle’s solution to manage/monitor various database/applications which may be running on Cloud infrastructure or on-premise. OEM 13c is the latest version.
Oracle Enterprise Manager (OEM) has built-in management capabilities that enable DBAs and Apps DBAs to monitor and manage the complete Oracle IT infrastructure including the Databases and Applications on Cloud as well as On-Premise from a single console.
The Management Agent on each monitored host monitors the status, health, and
performance of all managed components (targets) on that host. If a target goes down, or if a performance metric crosses a warning or critical threshold, an event is triggered and sent to Enterprise Manager. Administrators or any interested party can be notified of the triggered event through the Enterprise Manager notification system.
Oracle Enterprise Manager 13c is a comprehensive management solution provided by Oracle Corporation for managing Oracle software and hardware environments. It is designed to simplify the administration and monitoring of Oracle infrastructure, including databases, middleware, applications, and engineered systems.
Oracle Enterprise Manager 13c offers a centralized and unified management console that enables administrators to monitor, manage, and diagnose the entire Oracle ecosystem from a single interface.
Oracle enterprise manager OEM 13c and its history
Oracle Enterprise Manager is a management solution by Oracle Corporation. Its history includes the initial version in 1998, expansion in 2000, improvements in 9i (2001) and 10g (2004) with grid control, 11g (2007) with cloud features, 12c (2011) with cloud computing focus, and 13c (2015) with advanced capabilities for cloud, application performance, and security management. Oracle continues to release new versions to meet evolving customer needs.
Architecture/components of OEM
1) AGENTS
Agent or management agent is a piece of software that runs on every host that you want to monitor. Management agent work in conjunction with plug-ins to monitor the target server. All hosts where you install the agents are then termed as “Managed Hosts”.
Agents can be of two types:
CENTRAL AGENT : When you first install Oracle Management Service (OMS), by default you receive a Management Agent called the Central Agent. It is used for monitoring the OMS host, the OMS, and the other targets running on this OMS.
host.
STANDALONE TARGET AGENT : To monitor other hosts and the targets running on those hosts, you must install a separate Standalone Management Agent on each of those hosts
2) ORACLE MANAGEMENT SERVICE
OMS is the actual brain of OEM. OMS is deployed over Weblogic 13c. It is a web-based application and perform below broad level activities:
Works with the Management Agents and the plug-ins to discover targets.
Monitor and manage the agents
Store the collected information in a repository for future reference and analysis
Renders the user interface for Enterprise Manager Cloud Control.
3) ORACLE MANAGEMENT REPOSITORY
Oracle Management Repository is simply a database/database schema where all the information collected by the Management Agent gets stored. The Management Repository then organizes the data so that it can be retrieved by the OMS and displayed in the Enterprise Manager Cloud Control console.
4) PLUG-INS
Plug-ins as name suggest are pluggable entities that offer special management capabilities customized to suit specific target types. Example if your target type is Oracle EBS, you will need specific plug-ins to monitor the Oracle EBS. Plug-ins are deployed to the OMS as well as the Management Agent in OEM 13c.
Good thing about Plug-ins is that they have independent release cycles, so every time you have a new version of an Oracle product released, you will have a new version of the plug-in released to support monitoring of that new product version in Enterprise Manager Cloud Control.
Default Plugins that OEM 13c will install are:
Oracle Database
Oracle Fusion Middleware
Oracle Exadata
Oracle Cloud Framework
Oracle System Infrastructure
In addition to these plug-ins, you can optionally install other plug-ins available in the software kit.
5) BI PUBLISHER
Oracle Business Intelligence (BI) Publisher is Oracle’s primary reporting tool for authoring, managing, and delivering all your highly formatted documents. Starting with Oracle Enterprise Manager 13c, Oracle BI Publisher is installed and configured by default on the OMS.
6) CONSOLE
Console is the GUI Front end of the OEM application. With the help of the console, you can monitor and administer your entire computing environment from one location. All the systems and services including enterprise application systems, databases, hosts, middleware application servers, listeners etc will be visible through Console
7) EM CLI
The Enterprise Manager Command Line Interface (EM CLI) is a command-line too that is accessible through classic programming language constructs, enabling tasks t be created and run either from the command-line or programatically.
8) TARGETS
A target, or more specifically, a target instance, can be defined as any entity that can be monitored within an enterprise. Managed targets are the entities that Enterprise Manager can monitor and manage. Examples of targets include hosts, databases, application servers, applications, and listeners. As your environment changes, you can add and remove targets from Enterprise Manager as required.
9) CONNECTORS
Connector is a very specialized piece of software whose work is to be act like an intermediary between OEM and third party application like BMC Remedy Ticket generation system. Connectors make your life easier in the sense that they give you ready-made solution to connect your OEM system to other famous third party applications.
10) JVMD ENGINE
Java Virtual Machine Diagnostics (JVMD) Engine enables you to diagnose performance problems in Java applications. Starting with Oracle Enterprise Manager 13c , as part of the Oracle Fusion Middleware Plug-in deployment, one JVMD Engine is installed and configured by default on the
OMS. You will also need JVMD Agents to be manually deployed on the targeted JVMs.
Benefits of OEM
1.System Monitoring and Management: Monitor and manage databases, middleware, operating systems, virtualization, and hardware from a centralized console.
2.Database Management: Administer, tune performance, backup and recover, and manage security for Oracle databases.
3.Middleware Management: Monitor and manage Oracle Fusion Middleware components like WebLogic Server, SOA Suite, Service Bus, and Identity Management.
4.Application Performance Management: Trace and diagnose performance issues in Oracle-based applications for optimization.
5.Cloud Management: Manage and monitor Oracle Cloud Infrastructure resources, provision services, and monitor cloud-based applications.
6.Lifecycle Management: Automate software deployment, patch management, and configuration management across the environment.
7.Security Management: Enforce security policies, manage user access and privileges, and monitor user activities for security.
8.Reporting and Analytics: Generate custom reports, charts, and dashboards, track KPIs, and gain insights into system health and performance.
Drawbacks of OEM13C:
While Oracle Enterprise Manager 13c provides numerous benefits for managing Oracle environments, there are also some potential drawbacks to consider. Here are a few drawbacks associated with Oracle Enterprise Manager 13c:
Complexity: Oracle Enterprise Manager 13c is a feature-rich and comprehensive management solution, which can lead to a complex and steep learning curve for administrators. The extensive set of functionalities and configuration options may require significant time and effort to understand and effectively utilize.
Resource Consumption: Oracle Enterprise Manager 13c itself can be resource-intensive, requiring dedicated hardware and computing resources to run efficiently. Depending on the size and complexity of the managed environment, the tool may consume significant system resources, potentially impacting the overall performance of the management system itself.
Licensing Costs: Oracle Enterprise Manager 13c is a licensed product, and its deployment and usage may incur additional costs. The licensing model can be complex, especially if you have a large and diverse Oracle environment with various components and options. It's essential to carefully consider the licensing requirements and associated costs before implementing the solution.
Dependency on Oracle Infrastructure: Oracle Enterprise Manager 13c is designed specifically for managing Oracle software and hardware environments. While it provides excellent support for Oracle products, it may have limited or no support for managing non-Oracle systems or heterogeneous environments. This can be a limitation if your organization utilizes a mix of Oracle and non-Oracle technologies.
Version Compatibility: Oracle Enterprise Manager 13c is typically compatible with specific versions of Oracle software products. Upgrading or patching Oracle software components in your environment may require corresponding updates or patches to Oracle Enterprise Manager itself. Ensuring compatibility and managing the upgrade process can sometimes be challenging and time-consuming.
Reliance on Oracle Support: If you encounter issues or require assistance with Oracle Enterprise Manager 13c, you may need to rely on Oracle Support for resolution. Depending on your support contract and response times, this can impact the speed and effectiveness of issue resolution.
It's important to carefully evaluate these drawbacks against the specific needs and requirements of your organization before implementing Oracle Enterprise Manager 13c. Considerations such as the size of your environment, available resources, and the extent of your Oracle infrastructure will help determine whether the benefits outweigh the potential drawbacks.
Basic commands to work on OEM server
After you have installed OEM Cloud Control 13c, you should know how to start and stop the OEM components.
Here I will explain the sequence of starting and stopping OEM 13c components and same steps could be used for starting and stopping OEM
cloud control 12c. For this example, my $ORACLE_HOME (OEM repository database home) is /u01/app/oracle/product/12.1.0/db, $OMS_HOME is /u01/software/em/middleware, and $AGENT_HOME is
/u01/software/em/agent/agent_13.1.0.0.0
Starting OEM 13c Components
1)Start the listener.
[oracle@proddb~]$ $ORACLE_HOME/bin/lsnrctl start
2)Start the repository database.
[oracle@proddb~]$ $ORACLE_HOME/bin/sqlplus /nolog
SQL*Plus: Release 12.1.0.2.0 Production on Thu Jun 2 16:48:18 2016
Copyright (c) 1982, 2014, Oracle. All rights reserved.
SQL> conn sys as sysdba
Enter password:
Connected to an idle instance.
SQL>startup
3) Start the OMS
To check the status of OMS, we can login to OEM server.
[oracle@em13c ~]$emctl status oms
Oracle Enterprise Manager Cloud Control 13c Release 2
Copyright (c) 1996, 2016 Oracle Corporation. All rights reserved.
WebTier is Up
Oracle Management Server is Up
JVMD Engine is Up
BI Publisher Server is Down………………
[oracle@proddb~] $OMS_HOME/bin/emctl start oms
Oracle Enterprise Manager Cloud Control 13c Release 1
Copyright (c) 1996, 2015 Oracle Corporation. All rights reserved.
Starting Oracle Management Server...
WebTier Successfully Started
Oracle Management Server Successfully Started
Oracle Management Server is Up
JVMD Engine is Up
Starting BI Publisher Server ...
BI Publisher Server Successfully Started………….
BI Publisher Server is Up
[oracle@proddb~]$ $OMS_HOME/bin/emctl stop oms -all
How to check the status of Agent in Em13c
[oracle@em13c ~]$emctl status agent
Oracle Enterprise Manager Cloud Control 13c Release 2
Copyright (c) 1996, 2016 Oracle Corporation. All rights reserved.
---------------------------------------------------------------
---------------------------------------------------------------
Agent is Running and Ready
4) Start the agent
[oracle@proddb~]$ $AGENT_HOME/bin/emctl start agent
Oracle Enterprise Manager Cloud Control 13c Release 1
Copyright (c) 1996, 2015 Oracle Corporation. All rights reserved.
Starting agent .................................................started.
5) Stop the agent.
[oracle@proddb~]$ $AGENT_HOME/bin/emctl stop agent
Oracle Enterprise Manager Cloud Control 13c Release 1
Copyright (c) 1996, 2015 Oracle Corporation. All rights reserved.
Stopping agent ... stopped.
Agent Version
$AGENT_HOME/bin/emctl getversion agent
Agent Home
$AGENT_HOME/bin/emctl getemhome
Reload Agent
To reload the agent (restart with an updated configuration) use:
$AGENT_HOME/bin/emctl reload agent
Upload Data
To upload collected metric data from the agent to the OMS use:
$AGENT_HOME/bin/emctl upload agent
Plug-Ins
To list plug-ins excluding discovery plug-ins:
[oracle@server1]$ $AGENT_HOME/bin/emctl listplugins agent
emctl status agent jobs
$AGENT_HOME/bin/emctl status agent jobs
For more information
Please visit to this link
Enjoy the work and do like me if you like this article!!!
