Updating from v4.7.15 to v4.7.16 and getting asked to do massive amount of database updates

[menscerto]

Hi - I'm updating from v4.7.15 to v4.7.16 and getting asked to do massive amount of database updates. Is this normal? I chose to do it automatically but after several seconds it just returned to previous page without doing anything. I'm reluctant to run the queries manually because there are so many of them I'm bound to make an error. What can I do? Thanks.

[teraßyte]

What kind of queries are you being asked to run exactly? There were a few changes, but not that many. 🤔

[menscerto]

Maybe hundreds - there are updates, renaming, altering, etc.

Also renaming and altering tables with "_new" at end.

Edited March 15 by menscerto

[teraßyte]

Sorry, that doesn't help. Can you post here a few of those queries?

 

That said, since you mentioned the _new suffix, I think your database might not be utf8mb4. Does the Support page in ACP list any errors for the MySQL database?

[menscerto]

 

This is what I see. Where/how do I start?

 

• Database
  Version 8.0.36

  Database problems

  Non-InnoDB tables

  Not using UTF8MB4

Edited March 15 by menscerto

[Marc Stridgen]

If its not using UTF8MB4 and its converting, then there would be a lot. It may be better to run the converter before you do the upgrade, which you can do from the admin CP in the mysql section

[menscerto]

So I should switch to UTF8MB4 first then upgrade? Stupid question, where in the ACP is the MySQL section?

[Randy Calvert]

9 minutes ago, menscerto said:

So I should switch to UTF8MB4 first then upgrade? Stupid question, where in the ACP is the MySQL section?

I believe you would find it in the Support section of the ACP.  You'll find a link in the upper right hand corner of the ACP.

There will be a section with recommended things to fix.  

If that does not work, you may have to fix it using something like phpMyAdmin. 

[Marc Stridgen]

That is correct 🙂

[menscerto]

Thanks, I am now upgraded.

For others' reference, these are the steps I took:

1. Database Backup

2. Chose "Fix This" under "Not using UTF8MB4" in Support. Complete successfully.

3. Ran version upgrade - there were no longer any extra manual queries to run. Success.

Thanks again for the quick support.
 

[Marc Stridgen]

Glad to hear things are now working for you 🙂