Comments - InnoDB: Upgrade after a crash is not supported…

1 year, 1 month ago Daniel Black

When you have 10.4.24 started up on your mysql datadir. Stop by issuing a sql "SHUTDOWN". Examine your logs to ensure that "Shutdown complete" is the last thing in the log.

Then swap back to running MariaDB 10.11.2 on that directory contents.

 
1 year, 1 month ago Klaus Normal

Okay, how I am doing in the XAMPP Control Panel a sql "SHUTDOWN"?

MySQL->Admin->SQL

SHUTDOWN WAIT FOR ALL SLAVES;

 
1 year, 1 month ago Daniel Black

Sure, ensure XAMPP doesn't impose some very short timeout and kill it off, that would have the same effect as a crash.

 
1 year, 1 month ago Klaus Normal

Unfortunately, it does not work with the Shut Down of old MariaDB.

Neither with „SHUTDOWN WAIT FOR ALL SLAVES;“ nor with „SHUTDOWN;“. I obtained in both cases the message: unrecognized statement type. (near Shutdown). After the shutdown the following messages: 1 errors were found during analysis. Unrecognized keyword. (near "ON" at position 25) SQL query: Edit Edit SET FOREIGN_KEY_CHECKS = ON; MySQL said: Documentation

  1. 2006 - MySQL server has gone away

When I switched to the new Maria DB, I got again the message: Upgrade after a crash is not supported… What I did wrong?

 
Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.