MySQL plug-in 1.1 for Oracle 10g Grid Control
It’s been a while since the MySQL Management Plug-in 0.42 was released. Since then, I quietly updated it to version 1.0. The changes were very few; the biggest news was that the plug-in was certified by Oracle and added to OTN Oracle 10g Grid Control Extensions Exchange (see at the bottom).
I think the next version is due, as a few people have come back to me with some issues. The biggest was compatibility with Windows. Since I used the command line MySQL client, *nix and Windows shell incompatibilities were a major headache to solve, and I still couldn’t make it work reliably. I wanted to use DBI and DBD:MySQL, but it required installing and compiling Perl packages, which makes the deployment process very inconvenient.
Finally, I found a solution — Net::MySQL is a native Perl implementation of the MySQL client. I had to fix some bugs and add a few improvements to it, and I hope to get the author to re-introduce them back to the new CPAN distribution. Net::MySQL is dependent on IO::Socket, which is a core module that comes with the standard Perl distributed with the Oracle Management Agent.
Version 1.1 turned out to be a major rewrite for the Perl collection scripts and the net result is that compatibility across platforms is greatly improved. I have successfully tested the new version on Linux and Windows Agent hosts.
So what’s new in version 1.1 compared to 0.42?
- certified by Oracle; see OTN Extensions Exchange
- no MySQL client is required on Agent hosts. The Perl Net::MySQL package is distributed with the plug-in
- fully compatible with Windows
- MySQL client path property removed
- added support for local connection using Unix sockets
- added connection error message when target is down — can be seen in Availability History
- commands statistics skips collection for never-executed commands so less data is collected; thus, I could safely increased default collection frequency; command names are formated better
- changed default collection frequency for network, joins and sort statistics
- % command executions are collected right now — the “Questions” statistic didn’t match the total of all Com_ statistics.
- metric “Processes by Action” now excludes the plug-in’s own connection which was always adding one to “Query”
- a few minor typos fixed
Downloads, requirements, and installation instructions — as well as the datasheet — are available at the MySQL Plug-in for Oracle Grid Control home page.
You can also go directly to the plug-in download page by clicking here:
June 16th, 2008 at 1:32 pm
That’s cool stuff, Alex. I downloaded it the other week and hopefully we can try it in the next week or two. I’ll let you know how it goes.
June 16th, 2008 at 1:57 pm
Thanks Doug. Let me know the results. I’ve got few confirmations by email already.
June 17th, 2008 at 2:00 am
[…] now an official plug-in is available, created by Alex Gorbachev (Pythian Group). It can be downloaded from the “Oracle […]
June 20th, 2008 at 2:59 am
Cool Plug-in, deployment easy, reports very nice.
All is running well. (Only an little error in Executions history graph, perhaps it’s my confirguration…)
June 20th, 2008 at 8:23 am
Pascal,
Thanks for the feedback. There was an issue with this graph in case you are upgrading from previous version because execution names changed (I replaced “_” with ” ” for readability). However, I fixed that by introducing REPLACE in the SQL statement for the report.
Could you give me the error you see in the graph and also the errors in emoms.log from $OMS_HOME/sysman/logs.
Thanks,
Alex
June 20th, 2008 at 11:38 am
[…] the worlds of MySQL and Oracle was Alex Gorbachev, who released the MySQL plug-in 1.1 for Oracle 10g Grid Control, with a bunch of new features, and good reviews […]
June 25th, 2008 at 3:52 am
Dear Alex,
I have downloaded the pluggin and I have installed it on a Solaris 10 Sparc plataform.
The problems is that I only can modify the “collection schedule” on the metrics “response time” and “status”. The other metrics have the “collection schedule” value set “Real-time Only”.
It is correct? Do you think that it is a mistake of configuration?
Thank you very much in advance.
June 26th, 2008 at 7:36 am
Tòfol,
Thanks for you feedback.
What you see is wrong — you should be able to modify collection schedule easily. Can you give me a bit more info?
- How do you chance collection schedule? Give me detailed instructions please so I can try to reproduce.
- Have you upgraded from a previous version of plug-in?
Please check whether you have in the following file:
$OMS_HOME/system/admin/default_collection/mysql.xmlIs there only “Response” metric or are there other metrics as well?
Alex
July 11th, 2008 at 8:38 am
Thank you for attending to myself and you forgive for the delay,
it’s the first time that I install the plug-in. I have searched in the directory $OMS_HOME/sysman/admin/default_collection and I don’t find the file mysql.xml.
I have tried to change the collection schedule, but I can’t.
Thank you very much.
Tòfol.
July 11th, 2008 at 8:47 am
Tòfol,
There should be nothing in $OMS_HOME.
When you install the plug-in and *deploy* it to the agent, the files are deployed on the agent side in $OMS_HOME/sysman/admin/… ($OMS_HOME/{hostname}/sysman/admin/default_collection if it’s cluster agent).
To change the collection frequency, you should not touch default collection XML file. Instead, you can use Grid Control GUI for the target to change collection frequency there.
Hope this helps,
Alex