MySQL Lists are EOL. Please join:

List:Announcements« Previous MessageNext Message »
From:andy bang Date:April 29 2015 6:12pm
Subject:MySQL Enterprise Monitor 3.0.21 has been released
View as plain text  
We are pleased to announce that MySQL Enterprise Monitor 3.0.21 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
May update in a few weeks.  MySQL Enterprise Monitor is a
commercial extension to the MySQL family of products.

This is a maintenance release that includes a few enhancements and
fixes a number of bugs.  You can find more information on the contents
of this release in the change log:
     (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 choose the "Product or
Family (Advanced Search)" side tab in the "Patch Search" portlet.

You will also find the binaries on the Oracle Software Delivery Cloud
in a few weeks:

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

More information on MySQL Enterprise Monitor 3.0 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.21

Functionality Added or Changed

* Under certain cirumstances, such as MySQL Enterprise Service Manager
   experiencing heavy load, events could be raised for Agent host time
   out of sync relative to dashboard. These occurred even though both
   MySQL Enterprise Service Manager and the monitored host were
   synchronized with the same time server and no time-synchronization
   problems existed.

   As of this release, the Agent Health Advisor compares the time on
   the MySQL Enterprise Service Manager against the time on the
   monitored host. If no time-synchronization issues exists, these
   false positive events are auto-closed. (Bug #20519544)

* The Performance Advisor, Indexes Not Being Used Efficiently was
   improved in this release. (Bug #20020964)

* If the defined SMTP Rate Limit is exceeded, a Critical event is
   raised listing the event handler whose rate limit was exceeded and
   the rate defined on that event handler. No further notifications
   will be sent until the period ends and the new period begins
   (1 minute).

   These events are not auto-closed and are updated only for the first

   It is also possible to define an Event Handler against the Service
   Manger, to send notifications when the SMTP Rate Limit is exceeded.

* The Security advisor, UDFs Loaded From Insecure Location was removed
   because it is no longer required.

* The default value for SMTP Rate Limit is now set to 40.

* The Administration Advisors are updated in this release. The
   following changes were made:

   - Binary Logging Not Synchronized To Disk At Each Write: description

   - Default Value Being Used For max_prepared_stmt_count: removed in
     this release.

   - General Query Log Enabled: description is updated.

   - InnoDB Fast Shutdown Enabled: removed in this release.

   - InnoDB File Format Check Disabled Or Incorrect: removed in this

   - InnoDB INFORMATION_SCHEMA Plugins Missing: removed in this

   - InnoDB Tablespace Cannot Automatically Expand: renamed InnoDB
     System Tablespace Cannot Automatically Expand and the description
     is updated.

   - Key Buffer Size Greater Than 4 GB: removed in this release.

   - Next-Key Locking Disabled For InnoDB But Binary Logging Enabled:
     the underlying expression and description were updated for current
     versions. Deprecated version information removed.

     Original expression:
       (%log_bin% == "ON") && (%innodb_locks_unsafe_for_binlog% ==

     Updated expression:
       (%log_bin% == "ON") && (%binlog_format% != "ROW") &&
       ((%tx_isolation% == "READ-COMMITTED") ||
       (%innodb_locks_unsafe_for_binlog% == THRESHOLD))

   - No Value Set For MyISAM Recover Options: the expression for this
     advisor has been changed so it is triggered only if --default-
     storage-engine=MyISAM is set.

     Original expression:
       (%myisam_recover_options% == "OFF") ||
       (%myisam_recover_options% == "DEFAULT") ||
       (%myisam_recover_options% == THRESHOLD)

     Updated expression:
       (%storage_engine% == "MyISAM") &&
       ((%myisam_recover_options% == "OFF") ||
        (%myisam_recover_options% == "DEFAULT") ||
        (%myisam_recover_options% == THRESHOLD))

   - XA Distributed Transaction Support Enabled For InnoDB: removed in
     this release.

* All references to the InnoDB Plugin have been removed from the
   Advisors. The InnoDB Plugin was used in MySQL 5.1, only. MySQL 5.1
   is no longer supported.

* As of this release, the Service Manager Health advisor checks the
   timestamps of data collected by the agent to ensure the time of the
   monitored server is not set to a future time or date. Any data
   collected, with a timestamp of more than 5 minutes in the future,
   relative to the MySQL Enterprise Service Manager's system clock, is
   discarded and a critical event is generated. The critical event
   contains information on the assets whose time is incorrectly

   Important: It is strongly recommended you ensure your MySQL
   Enterprise Service Manager server and all monitored instances
   synchronize their system clocks with the same time server.

* The MySQL database, bundled with the MySQL Enterprise Service
   Manager, has been upgraded to MySQL 5.6.24.

* The Tomcat server, bundled with the MySQL Enterprise Service
   Manager, has been upgraded to 7.0.59. This enables use of TLSv1.2.

* The OpenSSL library bundled with MySQL Enterprise Monitor and the
   MySQL Enterprise Monitor Proxy and Aggregator has been upgraded to
   OpenSSL 1.0.1m.

* All mention of MySQL 4.1 was removed from Server-Enforced Data
   Integrity Checking Disabled and Server-Enforced Data Integrity
   Checking Not Strict advisors.

   The following note was added to the Tables Found With No Primary or
   Unique Keys advisor:

     Note: Tables lacking primary or unique keys can have a very
     negative impact on replication performance when using binlog-

* The following Security Advisors were updated:

   - The following advisors were renamed from Non-Authorized to Non-Root:

     Non-Authorized User Has GRANT Privileges On All Databases

     Non-Authorized User Has Server Admin Privileges

     Non-Authorized User Has DB, Table, Or Index Privileges On All

   - A link to content which explains how to migrate away from pre-4.1
     password hashing was added to the following Advisors

     Account Has Old Insecure Password Hash

     Insecure Password Authentication Option Is Enabled

     Insecure Password Generation Option Is Enabled

* The Performance Advisors are updated in this release. The following
   changes were made:

   - Data Flushed To Disk After Each SQL Statement: removed in this

   - InnoDB Not Using Newest File Format: description was updated.

   - Slow Query Log Not Enabled: removed in this release.

* The Query Cache Not Available Advisor is removed in this release.

* The following Replication Advisors were updated in this release:

   - Master Not Verifying Checksums When Reading From Binary Log: event
     text was updated with a note regarding the overhead on the master

   - Slave Master Info/Relay Log Info Not Crash Safe: event text
     updated with information on how to make the log crash safe and
     potential overhead.

   - Slave SQL Processing Not Multi-Threaded: MySQL 5.7.x-specific
     information added to Advisor text.

Bugs Fixed

* The --forceRestart and --createDataBackup options for unattended
   upgrades were not documented. (Bug #20915097)

* The documentation did not clearly state that the MySQL Enterprise
   Monitor Proxy and Aggregator is not currently available for
   Microsoft Windows platforms.

   An Important note was added at the following location: Installing
   the Proxy and Aggregator. (Bug #20889627)

* Emergency events were not displayed when the filter Worst Status was
   set to >=warning. (Bug #20866728)

* Under certain circumstances, a BadSQLGrammar error was logged if the
   agent attempted to monitor a MySQL 5.1.x instance. (Bug #20689926)

* MySQL Agent Not Reachable email notifications included the following
   text: agent_not_reachable.command=N/A. (Bug #20674778)

* Multi-byte text, such as Japanese, in NIC names was not rendered
   properly on Windows platforms. (Bug #20671527)

* The MySQL Enterprise Service Manager timed out on startup if the
   embedded agent was unable to contact one or more of the monitored
   instances or hosts. (Bug #20596111)

* The summary section of email notifications contained invalid line
   breaks. (Bug #20564920)

* Variable values were replaced with NumberFormatException in
   RadeoxFormatNumberMacro in email alerts for the RAM Usage Excessive
   advisor. (Bug #20471385)

* The Replication Status advisor raised an Slave IO Thread Not
   Running: Slave Has Problem Communicating With Master event, for
   replication or cluster installations, if the master shutdown, or
   restarted, unexpectedly. This event was not closed when the I/O
   thread restarted. (Bug #20271036)

* Under certain circumstances, when editing an Advisor, the message
   Not Suppressed was displayed. (Bug #20230532)

* The documentation implied that the auto-close policy for events was
   configurable and applied to all Advisors and the events they
   generate. It is not configurable and not all Advisors support auto-
   close for their events.

   Closing an Event contains updated information on the auto-close
   policy. (Bug #20053134)

* The Filesystem Free Space advisor raised contradictory events about
   the free space available on monitored disks.

* In previous releases, if the Data Purge Behavior period was changed
   from a large value to a smaller one, outdated event data was purged
   immediately. This could result in very large transactions on the
   MySQL Enterprise Service Manager's repository.

   As of this release, the outdated event data is purged in increments
   of one hour until the new retention policy is met, thereby reducing
   the load on the repository.
MySQL Enterprise Monitor 3.0.21 has been releasedandy bang29 Apr