Quiet Release MySQL Plugin 12.1.0.1.2 — bug fixes
Dec 11, 2012 / By Alex Gorbachev
This is just a small bug fix release of the plugin. It was actually quietly released for a while now of if you have downloaded the plugin recently, you have the latest version. To be sure — check the version in the Console or you will see it in the file name.
There are two bugs fixed:
1. Deployment on an OMS hosted on Solaris didn’t work (and suspect could be the same for Agents on Solaris).
2. Changing thresholds on the metrics caused an error “Modification of Target Monitoring Settings has Failed”. Also applying monitoring template was failing for the same reason.
If you did’t know that you can setup threshold and customized the thresholds that are set out of the box with the plugin then you are not using full capabilities of the Enterprise Manager. You can do that in the MySQL target menu — Monitoring -> Metric and Collection Settings. When alert or warning conditions are met, Oracle EM can raise incidents and send notification according to your settings. As I stated above, 12.1.0.1.0 had a bug that prevented users from changing the thresholds.
Same known issues exist as for 12.1.0.1.0 release.
Useful links:
Follow the same deployment procedure for upgrade — (1) import into EM12c using EMCLI, (2) upgrade on OMS by deploying on OMS, (3) upgrade on Agents byt deploying on agents.
Happy monitoring!
6 comments on “Quiet Release MySQL Plugin 12.1.0.1.2 — bug fixes”
Leave a Reply
You must be logged in to post a comment.

Is is “Quite release” or “Quiet release”?
Or maybe it was not really quite a quiet release? :-)
Hehe… just checking if anybody is paying attention. :)
This is excellent, Alex. Fixed the metric and template issues I has having with the previous version. And works with both OEM 12.1.0.1 and 12.1.0.2. Nice job!
Hi Alex,
we are using your MySQL-Plugin 12.1.0.1.2 with Cloud Control 12.1.0.2. and are really excited.
Sadly, there is one problem. The monitored MySQL databases logs a warning in the error log every five minutes:
[Warning] Aborted connection 7011 to db: ‘unconnected’ user: ‘our_user’ host: ‘our_host’ (Got an error reading communication packets)
Perhaps, is there a missing close_mysql_connection or something else?
Regards,
Spiker
Hi Alex,
solved it. I omitted the REPLICATION CLIENT right. We doesn’t use replication, so i thought this user right isn’t necessary.
Regards,
Spiker
Interesting… Thanks for reporting. I’ll check to see if there is a better way to handle it in the plugin than leaving unfinished connection.