Hi,

I have a problem with our self-hosted Invision Community Version 4.7.18. I cannot upgrade to the latest V4.7.20.

On first glance the forum works correctly for users.

"Database Check
There are some problems with your database which need to be fixed before you can start the upgrade."

On Get Support page of Admin CP I see the following issues:

"Database problems
Non-InnoDB tables
Not using UTF8MB4"

When I tried to fix Database problems issue, I get the following error:

"Incorrect key file for table 'club_core_admin_logs'; try to repair it"

After this, the forum gets completely broken and it doesn't opens anymore, any page.

I've recoverd a SQL database from a backup and I tried to fix manually this issue manually and I see 738 SQL commands suggested by Invision to fix this database problem - it fails on 4nd command.

Then I tried to fix UTF8MB4 issue firstly (it was done successfully). And then I tried to fix the database issue - the same result - the community becomes broken.

My SQL database is about 48 MB.

We have 2 Invision Communities since 2002 and 2014 and it's the first time when database crashed.

PHP: Version 8.1.29
MYSQL v.8.0
Shared web hosting, OVH France.

There isnt really a "crash the table" command, so that can only really be being caused by your hosting. However from what you have said, I would do it in this order

You mention UTF8MB4 conversion is working. Get that done first, then backup the site entirely. Ensure you are updating the conf_global.php file as it mentions

Update all tables to INNODB on your server. If you are unsure on how to do this, you should contact your host for their assistance with this.

At that point check what SQL commands you have. To be honest, if you have done the above and still have 738 items, then you likely havent done the above correctly. Dont continue at that point if you have that many. Update your access details and that point and I can take a look to see what is there.

Hi Marc,

Thank you for the quick reply! I'll do that you suggested.

Marc,

1. Earlier I didn't complete UTF8MB4 conversion correctly, I forgot to modify global_conf.php file.
   Now I did this.
   

2. Then I exported SQL database to a .sql file and using Notepad++ text editor replaced quotes ENGINE=MyISAM to ENGINE=InnoDB in all tables by using Ctrl+H (replace all the text). Because there were 134 old tables.
   I hope that this method is safe for this conversion.

   
   

3. I saw another Database problems issue report. Now it contains only several SQL instructions. And Invision AdminCP applied the suggested fixes automatically.
   

   Then I checked again - no new errors.

4. And finally I successfully performed the upgrade to V4.7.20 security patch. All is OK now.

   Thank you very much for your help.

P.S. I have another Invision Community installation. And it also has 2 warnings - for UTF8MB4 and old MyISAM tables. And the commuity works correctly - no database errors. Should I do the same for its database, too? It much larger - about 300 MB.

Edited February 4Feb 4 by Igor Kokarev_61905

If the method you have just used has worked, then yes of course. I have never done the conversion to INNODB in the way you described, but if its worked for you, all good.

Marc, thanks again! You can set this topic as solved.

Edited February 4Feb 4 by Igor Kokarev_61905

Marc,

I forgot to ask.

After conversion of all MyISAM tables to InnoDB mode should I modify the following option in config_global.php

$INFO['mysql_tbl_type'] = 'MyISAM';

My SQL server is MariaDB.

Yes, you can change that to INNODB