Functionality Added or Changed
A new graph is available, displaying the average size of queries in the query cache. See Query Cache Average Query Size graph for details. (Bug #12825244)
A new graph is available, displaying query cache fragmentation. See Query Cache Fragmentation graph for details. (Bug #12825023)
On the Global Settings tab, you can now customize how server names are displayed, to remove repetitive information. You can omit standard port numbers, omit the domain portion of the host names, or even set up abbreviations and nicknames based on substitution patterns. (Bug #11750223, Bug #40658)
The rules that check for accounts with no passwords were
enhanced to avoid false positive warnings for accounts that
authenticate using the new MySQL 5.5 authentication plugins.
Such accounts have no passwords listed in the
mysql.user table. The rules now also check
the plugin column of that table. This change applies to the rule
Server Has Accounts Without A Password and
mysql:no_password data collection item.
libmysqlclient library linked with the
Agent has been upgraded to the MySQL 5.5 level. This change is
necessary for compatibility with the new MySQL authentication
plugins in MySQL 5.5.
The Service Manager could fail to parse certain service request items retrieved from the My Oracle Support web site. (Bug #12861143)
A new graph is available, displaying information about slow
queries, corresponding to the
section of the
SHOW GLOBAL STATUS output. See
graph for details.
MySQL Agent Not Reachable could
errors depending on network-related factors. The fix turns off
the auto-close property for this advisor. The auto-close
property for this advisor will also be turned off if necessary
at other checkpoints, such as importing a new advisor bundle.
If you change the
data-dir parameter of the
MySQL Enterprise Monitor repository database, to store the table
data outside the
subdirectory of the MEM installation directory, the upgrade
process is more complex than usual. The fix for this bug
corrects a misleading error message that was issued when such a
MEM instance was upgraded:
Warning: We have detected that you are using your own remote instance of the MySQL server... It appears that the MySQL Server data directory has been moved from its standard location. Automatic upgrades of such a configuration are not supported.
Update Advisors button on the
Global Settings tab would incorrectly
downgrade the Advisors JAR file to 2.3.4.
Corrected the recommended action for the rules
Cache Not Optimal and
Table Cache Set Too Low
For Startup so that the commands worked when pasted to
a mysql command prompt.
The advice for the
No Value Set For
myisam-recover rule was changed to reflect the new
myisam-recover-options, which applies to
MySQL 5.5.3 and higher.
(Bug #12660628, Bug #61522)
A stored procedure call to a MySQL 5.5 server could hang (never return) when the connection went through the MySQL Enterprise Monitor Agent proxy. (Bug #12567070)
GRANT statement used a SQL-style
_) in the
database name, the rule
User Has Rights To Database
That Does Not Exist could produce an incorrect alert.
For example, this statement could cause a false positive when
evaluating the rule expression:
GRANT SELECT ON `test_%`.* TO 'testuser'@'localhost';
(Bug #12368217, Bug #60677)
Key Buffer Size May Not Be Optimal For System
RAM was updated to also check whether the buffer usage
has been greater than 75% of system RAM.
(Bug #11897242, Bug #60586)
The upgrade installer could incorrectly report that settings for the repository database differed from the recommended settings. The configuration values are now checked using a case-insensitive comparison. (Bug #11764095, Bug #56891)
Clarified the action for the message
An item was
expired by the cache while it was locked (increase your cache
timeout). Edit the
file, increasing the value for
maxElementsInMemory so that it is greater
than the number of rows in the MySQL Enterprise Monitor
(Bug #11756695, Bug #11748818, Bug #48642, Bug #37435)