TheSQL 5.1 changed innodb_log_file_size getting error on restart

innodbMySQL

In order to optimise my MySQL 5.1 (running on Window 2008 WebServer). I changed a few InnoDB options in my.ini namely the innodb_buffer_pool_size and innodb_log_file_size. But now when I am trying to restart the service it won't start. In the event viewer I can see the following errors:

Unknown/unsupported table type: INNODB

I have read about deleting log files and then starting the service but I have no clue where those log files are on windows machine. Also what is the best way to recover from this trauma without loosing any table data ?

Best Answer

Yup, you'll need to remove the log files to change their sizes. They're in where ever your DATADIR is. Just make sure you remove them when the server is shutdown. Then restart and you'll be fine (it will recreate them).

DO NOT remove any ibdata files, though. That has your actual persistent data.

Related Solutions

Mysql – Changing InnoDB data directory prevents MySQL service from starting

You mention that you are running on Windows. The path to Windows directories are not the same as UNIX ( you cannot just use /ibdata). Instead try setting it like:

innodb_data_home_dir="C:\path\to\ibdata"

Mysql – How to add databases from a crashed MySQL 5.1 server to a new MySQL 5.6 server

I have resolved this issue using the instructions posted here: http://dev.mysql.com/doc/refman/5.6/en/innodb-backup.html

I was unaware that by default all data in InnoDB tables across all databases on the server are stored in one single file at the root of the data directory: ibdata1. That file, and I believe the log files, must also be copied along with the folders containing the FRM files (which apparently just store the table structure). The side effect of this, of course, is that any InnoDB tables already defined on your new server will be rendered unusable.

Best Answer

Related Solutions

Mysql – Changing InnoDB data directory prevents MySQL service from starting

Mysql – How to add databases from a crashed MySQL 5.1 server to a new MySQL 5.6 server

Related Question