Introduction
Database monitoring is a critical responsibility for every database administrator (DBA). Continuous monitoring helps ensure high availability, optimal performance, proactive issue detection, and rapid troubleshooting across database environments. While administrators often rely on custom monitoring scripts or third-party monitoring tools, maintaining multiple monitoring platforms can increase operational complexity and administrative overhead.
Organizations that manage heterogeneous database environments—including Oracle and MySQL—often seek a unified monitoring solution that provides centralized visibility across their infrastructure.
Although MySQL offers its own monitoring solutions, such as MySQL Enterprise Monitor (MEM), organizations already using Oracle Enterprise Manager (OEM) Cloud Control 13c can leverage the Oracle Enterprise Manager for MySQL Plug-in to monitor MySQL databases from the same management console. This eliminates the need to maintain separate monitoring platforms while providing a consistent operational experience for database administrators.
Oracle Enterprise Manager Cloud Control 13c is Oracle’s enterprise monitoring and management platform designed to provide comprehensive visibility into databases, middleware, applications, operating systems, engineered systems, cloud resources, and other infrastructure components. Through its extensible plug-in framework, OEM can also monitor and manage various non-Oracle technologies, making it a valuable solution for enterprises operating mixed database environments.
The Oracle Enterprise Manager for MySQL Plug-in enables administrators to discover, monitor, and manage MySQL database instances directly from the OEM console. Administrators can monitor database availability, performance metrics, host resource utilization, alerts, configuration information, and other operational statistics alongside Oracle databases, providing a single pane of glass for enterprise database monitoring.
Note: The Oracle Enterprise Manager for MySQL Plug-in is a commercially licensed feature and requires the appropriate Oracle licensing before deployment in a production environment.
Why This Matters
Many enterprises today operate heterogeneous database environments consisting of Oracle, MySQL, PostgreSQL, SQL Server, and other database platforms. Managing each database using separate monitoring tools increases operational complexity, licensing costs, and administrative effort.
If Oracle Enterprise Manager is already deployed in your organization, extending it to monitor MySQL databases provides a centralized monitoring platform that reduces operational overhead while giving administrators a unified view of their database infrastructure.
What You’ll Learn
In this article, we will walk through the complete process of integrating MySQL database monitoring with Oracle Enterprise Manager (OEM) Cloud Control 13c. Starting with the prerequisite checks, we will verify software compatibility, prepare the monitoring environment, and configure the necessary MySQL monitoring user. The article then demonstrates how to download and deploy the MySQL Database Plug-in, install and validate the Oracle Management Agent, discover MySQL database targets, and promote them for monitoring. Finally, we will explore how to validate the monitored targets through the OEM console and Enterprise Manager Repository, enabling a centralized monitoring solution for both Oracle and MySQL database environments.
The following high-level tasks are covered in this article:
- Perform prerequisite checks
- Install the MySQL Database Plug-in
- Deploy and configure the Oracle Management Agent
- Discover MySQL database targets
- Promote discovered targets for monitoring
- Monitor MySQL databases using Oracle Enterprise Manager
- Validate the monitoring configuration
Environment used for this activity:
Note: OEM Cloud Control Installation / Configuration is not discussed in this chapter. Pre-existing OEM Cloud Control 13c is used for demonstration.
- Prerequisite Checks
Before installing the MySQL Database Plug-in, verify that your Oracle Enterprise Manager (OEM) Cloud Control environment meets the required software and compatibility prerequisites. This helps ensure a smooth plug-in deployment and successful monitoring of MySQL targets.
- Validate OEM Cloud Control Version
The MySQL Database Plug-in requires OEM Cloud Control 13.5 or later. Connect to the OEM Repository database and verify the installed version.
[oracle@oem-mgmt ~]$ sqlplus / as sysdba
SQL> select name, open_mode from v$database;
SQL> select version from sysman.mgmt_versions where component_name = ‘CORE’;
- Validate MySQL Version Compatibility
Before deploying the plug-in, ensure that the MySQL server version is supported by Oracle Enterprise Manager.
- MySQL 5.7 or later is supported by the MySQL Database Plug-in.
- OEM Cloud Control 13.2.4.0.0 or later supports MySQL 8.0.x.
Connect to the MySQL server and verify the installed version.
[root@mysql-serv ~]# mysql -uroot -p
mysql> select version();
- Validate Supported Platforms
The MySQL Database Plug-in can be deployed on an Oracle Management Agent running on Linux x86-64 (64-bit) or Microsoft Windows x86-64 (64-bit). Verify that the Management Agent host is running a supported operating system before proceeding.
Connect to the Management Agent host and validate the operating system and version.
[root@mysql-serv ~]# uname -a
[root@mysql-serv ~]# cat /etc/os-release
- Validate Management Agent OS User
The Oracle Management Agent should be installed using an operating system user that belongs to the MySQL user group on the monitoring server. By default, the mysql user is commonly used for installing and running the Management Agent.
Connect to the Management Agent host and verify the user and group membership.
[root@mysql-serv ~]# id mysql
- Create MySQL Monitoring User
Oracle Enterprise Manager requires a dedicated MySQL user to collect database metrics and monitor the MySQL instance. Create a user with the required monitoring privileges before promoting the MySQL target in OEM.
Connect to the MySQL server as a privileged user and create the monitoring account.
[mysql@mysql-serv ~]$ mysql -uroot -p
mysql> create user ‘myoem’@’localhost’ identified by ‘password@123’;
mysql> grant select, replication client, show databases, process, execute on *.* to ‘myoem’@’localhost’;
mysql> select user,host from mysql.user where user like ‘%oem%’;
- Configure Hostname Resolution
Ensure that the Oracle Management Server (OMS) and the Management Agent host can resolve each other’s hostnames. Update the /etc/hosts file on both servers (or configure DNS) to establish proper name resolution, which is required for successful communication between OMS and the Management Agent.
- On the Management Agent host, add the IP address and hostname of the OMS host.
- On the OMS host, add the IP address and hostname of the Management Agent host.
After updating the hosts file, verify that hostname resolution works correctly from both servers before proceeding with the plug-in deployment.
- Verify Network Connectivity
Ensure that the Oracle Management Server (OMS) and the Management Agent host can communicate over the required network ports. Proper connectivity is essential for agent communication, MySQL monitoring, and data upload to the OEM console.
- Connect to OMS host and validate the communication to Management Agent Server through ports – 3872 (OM Agent), 3306 (MySQL DB)
[oracle@oem-mgmt ~]$ curl -vvv telnet://mysql-serv:3872
[oracle@oem-mgmt ~]$ curl -vvv telnet://mysql-serv:3306
- Connect to Management Agent Server and validate the communication to OMS Host through ports – 4903 (OMS upload), 7803 (OEM console)
[mysql@mysql-serv ~]$ curl -vvv telnet://oem-mgmt:4903
[mysql@mysql-serv ~]$ curl -vvv telnet://oem-mgmt:7803
- Prepare Management Agent Installation Directory
Create a dedicated directory on the Management Agent host to install the Oracle Management Agent. Ensure the directory has the appropriate ownership and permissions before starting the installation.
[mysql@mysql-serv ~]$ mkdir -p /home/mysql/agent
[mysql@mysql-serv ~]$ ls -ld /home/mysql/agent
- Installing the MySQL Database Plug-in
- Checking the Availability of Plug-in in OEM Cloud Control 13c
- Login to OEM Cloud Control 13c
- Navigate to Setup à Extensibility à Plug-ins
- On the Plug-ins page, validate the existence of ‘MySQL Database’ plugin and the latest available version.
- Viewing Information about Plug-in
- On the Plug-ins page,
- Expand Databases and
- Click on ‘MySQL Database’ plug-in to check the details like Plug-in ID, latest available version, etc.
- Downloading Plug-ins in Online Mode
- Navigate to Setup a Extensibility a Self Update
- On the Self Update page, click on Type – Plug-in
- On the Self Update – Plug-in Updates page
- Search for ‘mysql’ in Search Description
- Select the ‘MySQL Database’ plug-in latest version available for download
- Click Download
- Check option ‘Immediately’ in the Schedule Download dialog page and click Select
- A job will be submitted by OEM Cloud Control to download the selected plug-in from the Enterprise Manager Store to the Software Library.
- A confirmation dialog appears with job successful submission.
- Click on the ‘Job Details’ from the pop-up window to monitor the job status.
Note: Once the plug-in is downloaded it must be first deployed on the OMS followed by deployment on Management Agents.
- Deploying Plug-in on OMS
- Navigate to Setup à Extensibility à Plug-Ins
- On the Plug-ins page
- Expand Databases section and Select the ‘MySQL Database’ plug-in
- Select ‘Management Servers’ from ‘Deploy On’ dropdown
- Validate the plug-in name (MySQL Database), version and click Next
- On the next page it performs the perquisite checks, validate the prerequisite status before proceeding further
- Once the pre-requisite checks are successful, click Next
- On the next page it prompts for SYS Credentials, use existing Named Credentials, if not, create new one by providing SYS user & Password and click Next
- Validate the OMS health status and continue with Deploy
- A confirmation message will be shown in the next window. Click on ‘Show Status’ to monitor the plug-in deployment progress.
- Select Job Name to monitor the progress of plug-in deployment job tasks.
- In parallel, the plug-in deployment job progress can be monitored from logs on OMS server from below directory
[oracle@oem-mgmt ~]$ cd /home/oracle/middleware/cfgtoollogs/pluginca/plugin_deployment_11/
- Finally, the plug-in deployment will be successful on OMS host
- Validate the deployed Plug-Ins on OMS from OEM Cloud Control Console
- Navigate to Setup à Extensibility à Plug-Ins
- On the Plug-ins page, we can now see that ‘MySQL Database’ plug-in is deployed on OMS
- Validate the deployed Plug-in on OMS Physical Server using EMCLI
- Enterprise Manager Command Line Interface (EMCLI) is an interface which is used from hosts running OMS and helps to perform operations at command line as an alternate to operations performed from OEM Cloud Control console. EMCLI is enabled with functionality, security, and confidentiality same as OEM Cloud Control console.
- Connect to OMS Host
- From command prompt login to sysman user using emcli
- Perform sync and
- Using emcli get the plug-in deployment status
[oracle@oem-mgmt ~]$ cd /home/oracle/middleware/bin
[oracle@oem-mgmt bin]$ ./emcli login -username=sysman
[oracle@oem-mgmt bin]$ ./emcli sync
[oracle@oem-mgmt bin]$ ./emcli get_plugin_deployment_status -plugin_id=oracle.mysql.omys
- Deploying Plug-ins on Oracle Management Agent Host
Option-1: If EM Agent already exists on Agent Server, then the plug-in which is deployed to OMS needs to be exclusively deployed on the Agent Server.
Option-2: If EM Agent not exists on Agent Server, then Management Agent needs to be installed manually using ‘Install Agent on Host’ under ‘Add Host Targets’ Wizard from OEM Cloud Control 13c Console
Option-2 automatically deploys all the plug-ins available in OMS to the Management Agent during installation.
In this example, Option-2 is shown as reference.
- On OEM Cloud Control Console
- Navigate to Setup à Add Target à Add Targets Manually
- On the Add Targets Manually page
- Select ‘Install Agent on Host’ under ‘Add Host Targets’ section
- Click on ‘+Add’, enter agent hostname / IP, select platform and click Next
- On the Next Window, add values for
> Installation Base Directory – /home/mysql/agent
> Port (agent) – 3872
> For Named Credentials – Click ‘+’ and create new credentials
> Named Credentials – username – mysql
> Password – *****
- Once done, Click Ok
- On the next page, validate the details and click Next
- On the next page, review the details and click Deploy Agent
- Agent deployment will run in 3 phases
- Initialization
- Remote Prerequisite Check
- Agent Deployment
Note: If any error is encountered in any of these phases, then the error needs to be corrected and the Agent Deployment can be re-run
- Review the warning messages (if any) and act accordingly
- Continue to monitor the agent deployment progress
- Finally, the agent gets successfully deployed on Management Agent server with a recommendation to run root.sh on agent server as root.
- Login to management agent server as root and run ‘root.sh’
[root@mysql-serv ~]# /home/mysql/agent/agent_13.5.0.0.0/root.sh
- Once root.sh execution on management agent server is successful then click on ‘Done’ in the Cloud Control page
- Validate the agent and host on EM Cloud Control Console
- Search for target ’192.168.2.1’
- Validate Agent Status on Management Agent Server
- Login to Management Agent host and check agent health
[mysql@mysql-serv ~]$ cd /home/mysql/agent/agent_13.5.0.0.0/bin
[mysql@mysql-serv ~]$ ./emctl status agent
- Adding MySQL Targets
- Adding Targets Using Autodiscovery
- Navigate to Setup à Add Target à Configure Auto Discovery
- On the Setup Discovery page, under ‘Targets on Hosts’ Table
- Select the host and click on ‘Discovery Modules’
- On the next page (Discovery Modules: )
- Check ‘Oracle MySQL Discovery’ module and click Ok
- On the Setup Discovery page
- Select the host and click on ‘Discover Now’
- A dialog page is displayed to confirm the discovery run on target, click Yes
- Discovery of targets in progress
- Upon completion of discovery, appropriate count of discovered targets will be displayed against the host
- Promote the Discovered Targets
- Navigate to Setup à Add Target à Add Discovery Results
- On the Auto Discovery Results page, under ‘Targets on Hosts’ table
- Select the target (in this case, mysql database) and click on promote
- On the next page, provide inputs for below and click Promote
- MySQL User – myoem
- MySQL Password – *****
- Confirm MySQL Password – *****
- Port (mysql DB) – 3306
- Target Promotion completed successfully
- Validate the promoted target on EM Cloud Control Console
- Search for target ‘mysql’
- Monitoring the Targets
- Monitor newly added Management Agent
- Login to OEM Cloud Control Console
- Search for target ’192.168.2.1’
- Click on agent target and monitor home page
- Monitor newly added Management Agent Host
- Login to OEM Cloud Control Console
- Search for target ’192.168.2.1’
- Click on host target and monitor home page
- Monitor newly added MySQL target
- Login to OEM Cloud Control Console
- Search for target ‘mysql’
- Click on target and monitor home page
- Validate Targets from Enterprise Repository Database
- To verify the agent, host, and other targets from Enterprise Management Repository Database
- Login to EMREP database and run the query to find the target details from sysman.em_manageable_entities
- Next Steps
Now that the MySQL Database Plug-in is configured, you can:
- Configure metric thresholds
- Enable email notifications
- Monitor MySQL performance and availability
- Create custom dashboards
- Schedule compliance and health reports
- Integrate OEM alerts with enterprise monitoring tools
Summary:
Oracle Enterprise Manager Cloud Control 13c provides a powerful centralized platform for monitoring heterogeneous database environments. By deploying the MySQL Database Plug-in, organizations can extend their existing OEM infrastructure to monitor MySQL databases without introducing another monitoring solution.
In this article, we covered the complete lifecycle—from prerequisites and plug-in deployment to target discovery and monitoring—demonstrating how OEM can serve as a single pane of glass for both Oracle and MySQL environments.
Refer to below MoS Notes for more details on OEM & MEM.
- What Is the Difference Between Using the MySQL Plugin for OEM and MySQL Enterprise Monitor (MEM) 3.0+ for Monitoring MySQL? (Doc ID 1989228.1)
Leave a Reply