MySQL Lists are EOL. Please join:

List:Announcements« Previous MessageNext Message »
From:andy bang Date:October 13 2016 8:05pm
Subject:MySQL Enterprise Monitor 3.1.5 has been released
View as plain text  
We are pleased to announce that MySQL Enterprise Monitor 3.1.5 is now
available for download on the My Oracle Support (MOS) web site.

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.

IMPORTANT: MySQL Enterprise Monitor (MEM) 3.3 offers many significant
improvements over MEM 3.1 and MEM 3.2 and we highly recommend that you
consider upgrading. More information on MEM 3.3 is available here:

   What's New in MySQL Enterprise Monitor 3.2

   MySQL Enterprise Monitor

   MySQL Enterprise Monitor Frequently Asked Questions

   MySQL Enterprise Monitor Change History

Please open a bug or a ticket on My Oracle Support to report problems,
request features, or give us general feedback about how this release
meets your needs.

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

Useful URLs

* My Oracle Support -
* What's New in 3.1 -
* Change log -
* Installation documentation -
* Complete documentation -
* Product information -
* FAQs -
* Download -

Thanks and Happy Monitoring!

   - The MySQL Enterprise Tools Development Team


Changes in MySQL Enterprise Monitor 3.1.5

Functionality Added or Changed

* Important Change: The bundled sys schema is upgraded to version

   Important: If you have installed an older version of sys schema on
   your monitored instances, it is recommended to upgrade to the latest
   version. The upgrade must be performed from the command line. It is
   not currently possible to upgrade sys schema from MySQL Enterprise
   Service Manager.

* Important Change: As of this release, it is not possible to use
   MySQL Server 5.1 or 5.5 as the MySQL Enterprise Monitor repository.
   The installer displays an error and the installation process stops.

* The query collection for Query Analyzer was improved in this
   release. (Bug #22179215)

* The required privileges for configuring a non-bundled repository
   were updated in this release. (Bug #21534737)

* The Tomcat server, bundled with the MySQL Enterprise Service
   Manager, has been upgraded to 7.0.69.

* The Warnings Not Being Logged advisor text was updated.

* Events for any future-dated asset which is not an agent, OS, or
   MySQL instance, are deleted. Under certain circumstances, these
   events contained empty fields.

* The following commands are added to the MySQL Enterprise Service
   Manager configuration utility (

   o --renew: renews the existing self-signed certificate.

   o --import-certificate=<value>: imports the defined certificate

   o --import-key=<value>: imports the defined private key.

* The OpenSSL libraries used by the MySQL Enterprise Monitor
   installers and MySQL Enterprise Monitor Aggregator have been
   upgraded to 1.0.1u.

* The bundled JRE was updated to 1.8.0_102 for both the Agent and
   Service Manager.

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

Bugs Fixed

* The documentation did not specify the correct format for the ssl-ca-
   keystore-path parameter. It was listed as a file path, but is a URL.
   For example:

   (Bug #24386496)

* The InnoDB Redo Log Pending Writes graph was not displayed for MySQL
   5.7 instances. (Bug #23563358)

* The Event Handler Asset column did not display any assets for the
   eleventh handler created. That is, the Asset column correctly
   displayed assets for the first 10 event handlers, but did not for
   any other event handler. (Bug #23543149)

* The LDAP and SSL documentation did not contain information on how to
   connect to LDAP servers which implement AES256. (Bug #23507489)

* The following variables were missing from the Fulltext Search
   section of the MySQL Instance InnoDB tab:

   o innodb_ft_enable_diag_print

   o innodb_ft_result_cache_limit

   o innodb_ft_total_cache_size

   (Bug #23474063)

* LDAP configuration settings were not validated by the upgrade
   process. Some of the fields were empty.

   As of this release, default values are added to the empty fields.
   (Bug #23299301)

* LDAP configuration was not validated when saved. As a result, if the
   LDAP connection information was incorrectly configured,
   NullPointerExceptions were logged, and it was not possible to
   connect to the LDAP server. (Bug #23299288)

* Under certain circumstances, when monitoring MySQL 5.7, warnings
   were generated in Query Analyzer due to a conflict between the
   default mysql_mode and the mysql_mode set by MySQL Enterprise
   Monitor. (Bug #23033046)

* It was possible to check/uncheck the assets in the Select Instances
   field on the Edit Replication Group tab, although the selection or
   deselection had no effect on the contents of the replication group.
   Replication groups are populated dynamically, not manually. (Bug

* The certificate to keystore upgrade process attempted to use the
   system's openSSL installation instead of that delivered with the
   installer. As a result, if openSSL was not installed on the system,
   the upgrade failed. As of this release, the upgrade only uses the
   openSSL libraries delivered with the installer. (Bug #22522309)

* Under certain circumstances, deleting events resulted in a long-
   running query which generated empty events. (Bug #22247688)

* The MySQL Enterprise Service Manager utility returned a
   stack trace for unsupported commands, instead of redirecting the
   user to the help.

* Custom agent service names were not maintained by the agent upgrade
   process. The custom name was overwritten by the default agent
   service name, MySQLEnterpriseMonitorAgent.

* The advice page generated by the MySQL Enterprise Backup Health
   advisor contained broken links to the InnoDB chapters of the MySQL
   Reference Manual. It also incorrectly referred to the --start-lsn
   option as the --lsn option.

* On certain browser versions, the symbol << was transformed to Â<<.

* A message about keystore loading was logged every minute by the
   certificate loader. The log level for this message was changed to
   reduce the unnecessary log entries.
MySQL Enterprise Monitor 3.1.5 has been releasedandy bang13 Oct