When upgrading to MySQL Enterprise Monitor 2.2, be aware of the following issues:
If you are upgrading to MySQL Enterprise Monitor 2.2, upgrade from MySQL Enterprise Monitor 2.0 or higher. If you are using MySQL Enterprise Monitor 1.3 or lower, upgrade to MySQL Enterprise Monitor 2.0 first before upgrading to MySQL Enterprise Monitor 2.2.
Rules and advisors in MySQL Enterprise Monitor 2.2 now support auto-close functionality if the issue that raised the notification is no longer causing a problem. Review all your existing rules schedules and confirm whether the auto-close feature is useful in each case.
The MySQL Enterprise Service Manager supports the use of a separate, self-managed, MySQL server in place of the MySQL server bundled with the MySQL Enterprise Service Manager installation for storing repository data. For more information, see Section 5.2.1, “Service Manager Installation Common Parameters”.
If you are upgrading a MySQL Enterprise Service Manager that uses a remote, self-managed MySQL database to store the MySQL Enterprise Monitor repository data, then perform the installation as follows:
Shut down MySQL Enterprise Service Manager.
Shut down the MySQL instance supporting your MySQL Enterprise Monitor repository.
Upgrade the MySQL server as you would any other MySQL server instance. See Upgrading MySQL.
Ensure when performing the upgrade that the MySQL server instance is configured with support for InnoDB and that the InnoDB storage engine is enabled. Also ensure that support for partitioning is available within the server.
Run the mysql_upgrade to ensure that the system tables have been correctly updated.
Restart the MySQL repository instance.
Restart MySQL Enterprise Service Manager and confirm that it was able to connect to the MySQL server.
When upgrading MySQL Enterprise Service Manager, the installer tries to determine if you are using a local MySQL server (as bundled with the MySQL Enterprise Service Manager) or a remote and self-managed MySQL server instance to store your repository data.
To determine whether the existing installation is using a
local MySQL server, the installer examines the existing
MySQL Enterprise Service Manager configuration file. If the value of the
mysql.server configuration parameter is
localhost, the installer assumes the
MySQL server is local. If any value is identified, the
installer assumes that the server is remote/self-managed and
it does not upgrade the MySQL server component.
If the correct MySQL server version and supported functionality (partitioning) are not supported by the MySQL server you are using, the installer stops.
The storage tables used for storing MySQL Enterprise Service Manager data, and the rules and methods required for purging old information, have changed in MySQL Enterprise Service Manager 2.2. You can improve the purging and disk space usage for these data tables by using the techniques shown in Section B.7, “Improving Disk Space Usage with Purge in 2.1 and 2.2”.
For MySQL Enterprise Agent installations, the installer can now create a user on your MySQL server with suitable credentials. To perform this operation, the installer requests the root login and password for your MySQL server so that the user and other details can be updated.