Functionality Added or Changed
A new blog at http://blogs.oracle.com/mysqlenterprise/ displays announcements, current news, and tips and tutorials about the MySQL Enterprise Monitor product. You can subscribe to RSS or Atom feeds, linked from this page, to be notified when software updates are ready.
Last Full MySQL Enterprise Backup Too
Old was not evaluated correctly. The corresponding
event could return a status of
Failure, and sometimes an incorrect
After an upgrade, certain rule evaluations cause errors with
messages such as
variable was not found in the symbol
not evaluate . If you encounter
such errors after an upgrade to MySQL Enterprise Monitor 2.3.4,
upgrade to the latest 2.3.5 to fix them.
variable: the variable
was not found in the symbol table
The disk space usage graph was not available on Red Hat
Enterprise Linux 5 or 6. If you encountered this issue, use the
refresh inventory feature in the
Manage Servers tab on affected servers, after
upgrading, to restore the graphs.
The format of the file name when a graph is exported as a
.png file was made consistent with the file
name for the
Added the following new InnoDB-related items to graphs:
Old series to the
InnoDB Buffer Pool graph.
Redo Log series to the
InnoDB OS File Access graph.
InnoDB Buffer Pool Page
InnoDB Buffer Pool Pending
InnoDB Change Buffer Usage.
InnoDB Change Buffer Activity (two
graphs, pre and post 5.5 versions).
InnoDB Doublewrite Buffer
InnoDB Redo Log Pending Writes.
(Bug #12589662, Bug #61277)
An error could occur during expression evaluation, of the form
> not defined for object of type java.lang.String
and java.lang.String. This error could result in some
graphs not being displayed, such as the Replication
(Bug #12589645, Bug #61242)
An unnecessary message about username and password prompts was displayed during unattended installation. This message is now suppressed. (Bug #12584441)
uninstall file was missing from the
backup directory created by the upgrade installer.
Auto-close notes can now be changed on a scheduled rule at any time, not just if the rule or schedule is enabled for auto-close. (Bug #12564331)
On Windows systems, running the command
mysqlmonitorctl.bat install, for example to
reinstall the Windows services after a problem with an upgrade
install, would change the
DISPLAY_NAME to be
the same as the
SERVICE_NAME, removing the
spaces in the name.
A rule was added to check if the MySQL instance contains time
zone data required for the
function to work properly. See
MySQL Server Time Zone Support for background information
about time zone support, and
mysql_tzinfo_to_sql — Load the Time Zone Tables for the utility to load
time zone data into MySQL.
(Bug #11933240, Bug #60676)