MySQL: Database cannot be upgraded

We post answers to Frequently Asked Questions here.

Moderators: henc, Tirmellon

MySQL: Database cannot be upgraded

Postby Mikael Stalvik » Thu Oct 16, 2008 10:13 am

When starting a new version of Helium Music Manager, your current database may need to be upgraded.

The upgrading process will be performed automatically and in the most cases it will work without any hassles, but in some cases a database will not be properly upgraded. You will then see a dialog that says "Database cannot be upgraded, please contact our support".

What you can check before you contact our support, if you are using a MySQL database, is that the database is created in the InnoDB format. Some MySQL engines seems to override the creation of database and force them to use the MyISAM engine instead.

The InnoDB format is required to support proper transaction handling as well as concurrency and integrity.

You can check the format of your database by using a third party tool.

If the database is not created in the InnoDB format you can:
1) Convert it to InnoDB using a third party tool. This solution is quite quick but requires some knowledge about database management tools.
2) Export all Music Browser data such as artists, publishers, artist relations and more from the Library Management (Ctrl+D) dialog. After the data is exported, create a new MySQL database (ensure that it will use the InnoDB format) and then import the exported Music Browser data and your files again.
User avatar
Mikael Stalvik
Developer
 
Posts: 2249
Joined: Wed Dec 04, 2002 7:01 pm
Location: Gerrebacka, Göteborg, Sweden

Return to Helium Music Manager FAQ

cron