MySQL Lists are EOL. Please join:

List:Announcements« Previous MessageNext Message »
From:andy bang Date:January 6 2014 5:46pm
Subject:MySQL Enterprise Monitor 3.0.5 Is Now Available
View as plain text  
We are pleased to announce that MySQL Enterprise Monitor 3.0.5 is now
available for download on the My Oracle Support (MOS) web site.  It
will also be available via the Oracle Software Delivery Cloud with the
January update in about 1 week.

This is a maintenance release that fixes a number of bugs.  You can
find more information on the contents of this release in the change
     (also included at the end of this note for convenience)

You will find binaries for the new release on My Oracle Support:

Choose the "Patches & Updates" tab, and then use the "Product or
Family (Advanced Search)" feature.

You will also find the binaries on the Oracle Software Delivery Cloud
in approximately 1 week:

Choose "MySQL Database" as the Product Pack and you will find the
Enterprise Monitor along with other MySQL products.

Based on feedback from our customers, MySQL Enterprise Monitor (MEM)
3.0 offers many significant improvements over previous releases.
Highlights include:

o Policy-based automatic scheduling of rules and event handling
   (including email notifications) make administration of scale-out
   easier and automatic

o Enhancements such as automatic discovery of MySQL instances,
   centralized agent configuration and multi-instance monitoring
   further improve ease of configuration and management

o The new cloud and virtualization-friendly, "agent-less" design
   allows remote monitoring of MySQL databases without the need for any
   remote agents

o Trends, projections and forecasting - Graphs and Event handlers
   inform you in advance of impending file system capacity problems

o Zero Configuration Query Analyzer - Works "out of the box" with
   MySQL 5.6 Performance_Schema (supported by 5.6.14 or later)

o False positives from flapping or spikes are avoided using
   exponential moving averages and other statistical techniques

o Advisors can analyze data across an entire group; for example, the
   Replication Advisor can scan an entire topology to find common
   configuration errors like duplicate server UUIDs or a slave whose
   version is less than its master's

More information on the contents of this release is available here:

   What's new in MySQL Enterprise Monitor 3.0?

   MySQL Enterprise Edition: Demos

   MySQL Enterprise Monitor Frequently Asked Questions

   MySQL Enterprise Monitor Change History

More information on MySQL Enterprise and the Enterprise Monitor can be
found here:

If you are not a MySQL Enterprise customer and want to try the Monitor
and Query Analyzer using our 30-day free customer trial, go to, or contact Sales at

If you haven't looked at 3.0 recently, please do so now and let us
know what you think.

Thanks and Happy Monitoring!

   - The MySQL Enterprise Tools Development Team


Changes in MySQL Enterprise Monitor 3.0.5

Bugs Fixed

* With the new MySQL Enterprise Backup Advisor implementation in
   3.0.4, older Agents (3.0.3 and below) would fail to report data with
   MySQL Enterprise Service Manager 3.0.4 when the MySQL Enterprise
   Backup Advisor was enabled. MySQL Enterprise Backup users must
   upgrade each Agent to 3.0.4+. (Bug #17938176)

* It was possible to see a NULL pointer exception on the MySQL
   Instances Dashboard if no InnoDB assets were collected for a MySQL
   instance. For example, on a MySQL Server 5.1.x installation without
   the I_S InnoDB plugins installed. (Bug #17912048)

* The Object Changed Detected Advisor now includes information about
   events and procedures, namely COM_ALTER_EVENT, COM_ALTER_PROCEDURE,
   COM_DROP_PROCEDURE. (Bug #17918387)

* The libaio detection routine of the MySQL Enterprise Service Manager
   Installer was updated to compare 32-bit and 64-bit versions of
   libaio in relation to the Installer. (Bug #17897905)

* The uptime reported from the "MySQL Server Has Been Restarted"
   Advisor would sometimes report a value of 0. (Bug #17830530)

* Sometimes the Agent would not attempt to reconnect to a MySQL Server
   after a long (5+ minutes) timeout. (Bug #17830547)

* When using a non-bundled MySQL server for the MySQL Enterprise
   Service Manager Repository, the "#" character was not allowed in the
   associated MySQL server password. (Bug #17812516)

* MySQL Enterprise Service Manager now also (first) checks the MySQL
   server 5.6+ master-info-repository variable to obtain the master's
   information. If set to table, then master information is read from
   the mysql.slave_master_info table. (Bug #17829049)

* When executing the MySQL Enterprise Service Manager Installer from
   the command line, defining "localhost" as the hostname for a non-
   bundled Repository database would only attempt to connect via a
   socket, and not TCP. (Bug #17798799)

* Rule expression text was updated, and is now easier to read. (Bug

* With the latest version of Google Chrome, the vertical toolbar in
   the MySQL Enterprise Monitor User Interface was not displayed
   properly. (Bug #17744006)

* The Ignore MySQL Instances functionality was removed from MySQL
   Enterprise Service Manager. (Bug #17751514)

* The Edit Instances option no longer validates connection setting
   changes with bulk editing of MySQL instances (multiple connections)
   unless their values were changed. (Bug #17788818)

* Some default collection precondition statements were updated to
   better function with MySQL server 5.0.x, which generated too many
   Agent log messages about non-existent information_schema tables.
   (Bug #17582225)

* The --mysqlconnectiongroup Agent Installer option now allows an
   Agent to be assigned to multiple groups, by passing in a comma-
   separated list of group names. For example, '--mysqlconnectiongroup
   "a,b,c"' will assign the Agent to groups "a", "b", and "c". (Bug
   #17559349, Bug #70497)

* On Mac OS X, the option to "Install as a Service" was added to the
   MySQL Enterprise Monitor Installer. (Bug #17550529)

* Log entries for failed Agent login attempts were clarified in the
   log files, as it now reports the user for the attempted login. (Bug
   #17564469, Bug #70530)

* The MEB Provider continued to log errors after an associated MySQL
   instance was deleted.

* The bundled MySQL Server was upgraded to 5.6.15. The previous
   version was 5.6.14.
MySQL Enterprise Monitor 3.0.5 Is Now Availableandy bang6 Jan