The reason for this issue is a change in MySQL 5.6.20 as one could read in the change log:
As a result of the redo log BLOB write limit introduced for MySQL 5.6, the innodb_log_file_size setting should be 10 times larger than the largest BLOB data size found in the rows of your tables plus the length of other variable length fields (VARCHAR, VARBINARY, and TEXT type fields). No action is required if your innodb_log_file_size setting is already sufficiently large or your tables contain no BLOB data.
Set or increase the value of the innodb_log_file_size option in
my.ini below the
[mysqld] section. Its default value is
48M. Setting it to
Be careful when changing the value of
innodb_log_file_size. Follow these steps to do this safely:
- Shut the server down cleanly and normally.
- Shutting down MySQL may not be as simple as just
service mysql stop!
- Following things should be done to shut down mysql server normally and cleanly:
- Double check the instance you are going to shutdown!!
- Stop Replication
- Flush the dirty pages
- Check the long running transactions
- Dump and reload the buffer pool
- Move away (don’t delete) the log files, which are named ib_logfile0, ib_logfile1, and so on.
- Check the error log to ensure there was no problem shutting down.
- Then restart the server and watch the error log output carefully.
- There should see InnoDB print messages saying that the log files don’t exist. It will create new ones and then start.
- Verify that InnoDB is working. If it’s working, then the old log files can be deleted.