MYSQL 8.0 - unsupported redo log format

26
votes

I have recently updated mysql that was located under my xampp folder, and i've got the following errors, reporting from the log file :

2018-04-19T12:59:19.667059Z 0 [System] [MY-010116] [Server] C:\xampp\mysql\bin\mysqld.exe (mysqld 8.0.11) starting as process 9324
2018-04-19T12:59:20.025280Z 1 [ERROR] [MY-013090] [InnoDB] InnoDB: Unsupported redo log format (0). The redo log was created before MySQL 5.7.9
2018-04-19T12:59:20.026140Z 1 [ERROR] [MY-012930] [InnoDB] InnoDB: Plugin initialization aborted with error Generic error.
2018-04-19T12:59:20.229069Z 1 [ERROR] [MY-011013] [Server] Failed to initialize DD Storage Engine.
2018-04-19T12:59:20.230803Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed.
2018-04-19T12:59:20.231371Z 0 [ERROR] [MY-010119] [Server] Aborting
2018-04-19T12:59:20.233136Z 0 [System] [MY-010910] [Server] C:\xampp\mysql\bin\mysqld.exe: Shutdown complete (mysqld 8.0.11)  MySQL Community Server - GPL.

I have been told if updating your mysql, you should comment out the deprecated configs that are located in your my.ini, but i had no idea what to comment out, so i left it as it is.

Any idea what causes this?

1
phpmysqlphpmyadminxampp
dev.mysql.com/doc/mysql-installation-excerpt/5.7/en/… : To simplify InnoDB tablespace discovery during crash recovery, new redo log record types were introduced in MySQL 5.7.5. This enhancement changes the redo log format. Before performing an in-place downgrade from MySQL 5.7.5 or later, perform a clean shutdown using an innodb_fast_shutdown setting of 0 or 1. A slow shutdown using innodb_fast_shutdown=0 is a recommended step in In-Place Downgrade. – aynber
Question one why are you using a MySQL version which isn't stabile and not ready jet for production.. – Raymond Nijland
Next question to Raymond: why should MySQL 8.0.11 not be stable? It was released today as a GA version – Nico Haase
Well the main reason for using a newer version, generally, for getting better performance, getting the latest stuff etc.. But my main reason for upgrading is the usage of this command : json_objectagg so i could group rows into one json object for later usage. I couldn't find a better solution than using this function to be honest. If you have any other substitutes, they are always welcomed. – Ahmed Dolabi
I have the same issue, anyone have any ideas on how to resolve this? – xpagesbeast

1 Answers

44
votes

If you have already installed MySQL and did not perform a slow shutdown using the

innodb_fast_shutdown

Flag, simply go to your MySQL directory

/var/lib/mysql/

And remove the log files (Do not do this if you need the table data in your database until you have backed up your database):

ib_logfile0 ib_logfile1

Back them up before if you need them again.