The Complete Setup button was missing from the Setup page you were taken to after the current subscription expired. (Bug#41685)

If the host-id of the monitored instance and the host-id of the current agent did not match, the agent generated the following error message:

Please TRUNCATE TABLE mysql.inventory on this mysql-instance and restart the agent.

However, it did not suggest using sql_log_bin = 0. This is used for all other actions against this table so that they are not replicated to slaves, each of which has their own copy of this table. (Bug#41673)

The Agent did not start up when the monitored server had many databases and tables, and was under heavy load. This was because the trigger_schema query was taking too long on agent start up. (Bug#41555)

The Monitor Agent failed to install on Solaris 10 x86. The following error was generated:

Installing
0% ______________ 50% ______________ 100%
########################################
Warning: Problem running post-install step.
Installation may not complete correctly
Error running /usr/local/mysqlagent/bin/mysql-monitor-agent
--defaults-file=/usr/local/mysqlagent/etc/mysql-monitor-agent.ini
--plugins=agent --agent-generate-uuid=true : 2008-12-12 13:06:02: (critical)
Conversion from character set '646' to 'UTF-8' is not supported
2008-12-12 13:06:02: (message) shutting down normally

(Bug#41445)

The console/stdout appender remained in the log4j configuration, which meant that all the MySQL Enterprise Monitor server logs were duplicated to Catalina's stdout, and thus catalina.out, which was wasteful, especially as that file was not rotated or managed. (Bug#41439)

When creating new multiple user accounts, the first attempt worked fine. However, following attempts to create new users did not show the Query Analyzer Options in the Create User popup until the role field was changed. (Bug#41430)

When login privileges were required the Service Manager did not redirect the user to the login page. This resulted in error messages being displayed rather than simply redirecting the user to the login page. This problem typically occurred if it was necessary to restart Tomcat. (Bug#41320)

The monitor 2.0.0.7105 and 2.0.0.7122 Solaris Intel update installer quits unexpectedly. The installer exits from the GUI in the Backup of Previous Installation screen, when OpenSolaris is running on top of Sun xVM.

The console output for both installer versions is given below:

shell> ./mysqlmonitor-2.0.0.7105-solaris-intel-update-installer.bin
X Error of failed request:  BadMatch (invalid parameter attributes)
  Major opcode of failed request:  73 (X_GetImage)
  Serial number of failed request:  21161
  Current serial number in output stream:  21161

shell> ./mysqlmonitor-2.0.0.7122-solaris-intel-update-installer.bin
X Error of failed request:  BadMatch (invalid parameter attributes)
  Major opcode of failed request:  73 (X_GetImage)
  Serial number of failed request:  21148
  Current serial number in output stream:  21148

(Bug#41315)

The Rename Group function failed if the new group name was different to the current one only in the case used; for example, if “Merlin” was changed to “MERLIN”.

The error generated was:

U0105 This group name is already in use. Enter a different name.

(Bug#41266)

The Agent returned an inventory list of all databases and tables. This information was not used by MySQL Enterprise Monitor, other than to populate the inv_databases and inv_tables tables. For large-scale deployments, where there were many databases and tables, this resulted in redundant XML messages being sent from the Agent to the Service Manager. (Bug#33150)