I have blogged in the past about MySQL Enterprise Monitor 3.0 and I was quite happy at the very beginning, but after a while I have to admit that I was missing many of the Oracle Enterprise Manager 12c features.
In particular, MEM 3.0 does not have a usable database. In MEM all the tables are crypted and it is not possible to list, for example, all the targets monitored, nor it is possible via API or REST web services because MEM 3.0 lacks these features.
What makes EM12c a GREAT product comparing to MEM, are many features like blackouts, a usable command line interface (emcli), integrated reporting, scheduler, automatic groups… the list would be just huge.
Luckily, Oracle has officially released a MySQL plugin for EM12c, provided that the EM is at least in version 220.127.116.11.
So I’ve upgraded (a while ago) my customer’s EM12c to 18.104.22.168. and decided to try the plugin.
The first step is to download the last version of plugin for MySQL.
I can verify that you have the last version by going to
Setup -> Extensibility -> Self-Update -> Plugins:
The agent has been downloaded, but in order to make it available on the targets, I first need to deploy it on the management servers (2 OMSes in my case):
Check the plugin name and version:
Verify the prerequisites check (here I have one column per OMS):
Now I can see that the plugin is correctly deployed on the OMSes, I can do the same for the agents:
But the discovery does not find my MySQL targets. What went wrong?
Latest posts by Ludovico (see all)
- Multitenant Pills: Partial PDB cloning (and cleanup) - May 22, 2020
- Multitenant Pills: Pushing your PDB to the Cloud in one step? - May 18, 2020
- Multitenant Pills – Change DBID for an existing PDB - May 14, 2020