Fix Database when Updating

[bryanharley]

I'm trying to update to the latest software version, but it keeps telling me I need to fix my database by running these queries:

UPDATE `ibf_core_output_cache` SET `cache_expire`=0 WHERE `cache_expire` IS NULL;
ALTER TABLE `ibf_core_output_cache` DROP INDEX `cache_expire`, CHANGE COLUMN `cache_expire` `cache_expire` INT NOT NULL DEFAULT 0 COMMENT 'Unix timestamp of when the cache expires', ADD KEY `cache_expire` (`cache_expire`);

I tried running the queries manually. But when I click "Check Again" it just displays the same message. I tried clicking "Fix Automatically", but that doesn't work either. Still displays that message.  How can I get past this?

Edited October 23, 2022 by bryanharley

[Randy Calvert]

How are you running those commands?  If you're just clicking "Fix this", it does not actually fix it.  It just tells you what you need to do.  Run this via phpMyAdmin, or via SSH mySQL.

[bryanharley]

I ran the queries via SSH mySQL.

[bryanharley]

Never mind, switching back to PHP 7.4 fixed it. 

[Marc Stridgen]

Please let us know if you still see issues on PHP 8 once you have upgraded to the latest release, as you shouldn't see that issue

[Istituto Beck]

Hi Marc,

I have the same issue

If You leave php 7.4 You cannot upgrade

if You switch to php 8 allways the same error message: UPDATE `core_output_cache` SET `cache_expire`=0 WHERE `cache_expire` IS NULL;
ALTER TABLE `core_output_cache` DROP INDEX `cache_expire`, CHANGE COLUMN `cache_expire` `cache_expire` INT NOT NULL DEFAULT 0 COMMENT 'Unix timestamp of when the cache expires', ADD KEY `cache_expire` (`cache_expire`);

[Marc Stridgen]

You would upload a fresh set of files from your client area, switch to PHP 8, then run the upgrader from /admin/upgrade

[eeldredge]

Hello @Marc Stridgen

I'm currently running PHP 8.0, MySQL 8.0 and when attempting to upgrade my forum to 4.7.10, I get a similar error as described above, first hitting this message:

When I click "Fix this" I get a giant list of SQL queries to run, which I did try to run in pieces manually in myPHP admin (the automatic fix didn't work).

We tried upgrading the database tables from utf8 mb3 to mb4 which seemed to remove the warnings seen when trying to the run the scripts, but coming back to the upgrader we still hit this error.

This is a self hosted forum.  URL is https://forum.nhl94.com/ and the details should be stored in my client area info. Any ideas?

Thanks,

-Evan

[Marc Stridgen]

As mentioned above, try uploading a fresh set of files, then running the upgrader from /admin/upgrade

[eeldredge]

Thanks @Marc Stridgen

I have uploaded a new set of files and ran the upgrader from /admin/upgrade and I'm stuck on a different but similar error where I run the SQL commands manually and click "I have run..." but it's stuck on this screen:

Running this as is gave me warnings about utf8 being depreciated and should use utf8mb4, so I tried changing the last statement to use uft8mb4 which then ran without warnings but still can't get past this screen.

Here's the updated statement I ran without error:

ALTER TABLE `ibf_forums_posts` CHANGE COLUMN `author_name` `author_name` VARCHAR (255) CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci NULL , DROP INDEX `ip_address`, CHANGE COLUMN `ip_address` `ip_address` VARCHAR (46) CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '' , ADD KEY `ip_address` (`ip_address`), CHANGE COLUMN `post` `post` MEDIUMTEXT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci NULL , CHANGE COLUMN `edit_name` `edit_name` VARCHAR (255) CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci NULL , DROP INDEX `post_key`, CHANGE COLUMN `post_key` `post_key` VARCHAR (32) CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '0' , ADD KEY `post_key` (`post_key`), CHANGE COLUMN `post_edit_reason` `post_edit_reason` VARCHAR (255) CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '' , CHANGE COLUMN `post_field_t1` `post_field_t1` TEXT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci NULL , CHANGE COLUMN `post_field_t2` `post_field_t2` TEXT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci NULL ;

Any other ideas?

Thanks!

-Evan

[Marc Stridgen]

What did you do after that point? Have you clicked to state you have run the command?

[eeldredge]

Hey Marc,

I just tried the "fix automatically" option and that worked - lucky break I guess!

All set now.

-Evan

[Marc Stridgen]

Glad to hear you have things sorted. Now its back online, please go to support in the admin CP and ensure you address anything that may be showing in the mysql section there

[eeldredge]

Ah good call! There was indeed a cleanup task to convert the database to utf8mb4 which just ran successfully.  Thanks for the help @Marc Stridgen!

[Marc Stridgen]

Ensure you add the line it asks you to at the end, if it does

[Percival]

Is there any other way to update in this situation other than uploading files from the client arena... ?

[Marc Stridgen]

Ensuring your database is corrected before you begin your upgrade. The point which was reached at the end, with checking and ensuring  the database is corrected by looking at the support tools (top right of the admin CP) would have likely prevented the issue

[Percival]

So it's a problem with the upgrade tool? Only manually uploading files is a fix... ?

[Jim M]

Depending on a version, there was an issue where the database check was indeed coming up false. However, keep in mind the original issue the OP had was different. 

If your queries there won't go away from the Support or upgrade screen and you're on 4.6, that is likely the error and a manual upgrade is required.