DB Update not Completing

Administration
1

Hi, I get the following error while upgrading the DB:

Your request failed due to a database error.

DATABASE ENGINE MIGRATION
Starting from v16, Gibbon is offering installations the option to migrate from MySQL’s MyISAM engine to InnoDB, as a way to achieve greater reliability and performance.

Your current default database engine is: InnoDB
5 of your tables are not set to InnoDB. Click “Submit” below to continue. This operation cannot be undone: backup your entire database prior to running the update!

2

Hi jmsperu,

Can you check your database to see which 5 tables didn’t update? They’ll still be listed as MyISAM and every other table will be InnoDB. Knowing which tables failed may help narrow down the issue.

Thanks!

This is odd though, I could have swore Ross already replied to this post…

3

I thought I replied too. Any chance of a duplicate post?

4
I thought I replied too. Any chance of a duplicate post?

Hi, there’s no duplicate post .

5
Hi jmsperu,

Can you check your database to see which 5 tables didn’t update? They’ll still be listed as MyISAM and every other table will be InnoDB. Knowing which tables failed may help narrow down the issue.

Thanks!

This is odd though, I could have swore Ross already replied to this post…

Do I do this via PHPMyAdmin?

6
Hi jmsperu,

Can you check your database to see which 5 tables didn’t update? They’ll still be listed as MyISAM and every other table will be InnoDB. Knowing which tables failed may help narrow down the issue.

Thanks!

This is odd though, I could have swore Ross already replied to this post…

The tables are: queryBuilderQuery Policies and Moodle tables. Well I deletd them all as I do not need the tables at the moment as am not using the related modules.

7

Ah, I suspect it might have been the Moodle tables (“views” to be precise) that interfered with the update. With this module it is best to uninstall it before the update, and then reinstall after. This is to do with some of the prep work that happens in the v16 update to get things ready for the move to InnoDB. Cheers, Ross.