In this case MySQL will not start if InnoDB failed to start:

If using innodb plugin and mysql 5.1 add this to my.cnf: innodb=FORCE.UPDATE: To prevent this in the future you can do 2 things (thanks Shantanu for pointing this out): The fix was easy: restart mysql using this instructions () and upload the dump again (or convert myisam to innodb manually). That was happened: mysql used MyISAM instead of InnoDB, produced warnings, but they are usually ignored. | Warning | 1266 | Using storage engine MyISAM for table 'aaa' | | Warning | 1286 | Unknown table engine 'non_existing_engine' |

Query OK, 0 rows affected, 2 warnings (0.16 sec) Mysql> create table aaa(i int) engine=non_existing_engine For example if we create a table with non-existing storage engine, MySQL will use MyISAM instead: In this case mysql restored the tables, but the storage engine was substituted from InnoDB to MyISAM. Although, mysql server was started, but without InnoDB. So, InnoDB was not stared as the size of log files was changed in the my.cnf and the old log files were not moved. Version: '5.1.51-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Server (GPL) usr/sbin/mysqld: ready for connections. Plugin 'InnoDB' registration as a STORAGE ENGINE failed. Plugin 'InnoDB' init function returned error. ib_logfile0 is of different size 0 5242880 bytes Next we look into the error log to find out, why InnoDB was not started. | ARCHIVE | YES | Archive storage engine | NO | NO | NO |Īs we see, there is no InnoDB in the list. | FEDERATED | NO | Federated MySQL storage engine | NULL | NULL | NULL | | MEMORY | YES | Hash based, stored in memory, useful for temporary tables | NO | NO | NO | | CSV | YES | CSV storage engine | NO | NO | NO | | BLACKHOLE | YES | /dev/null storage engine (anything you write to it disappears) | NO | NO | NO | | MRG_MYISAM | YES | Collection of identical MyISAM tables | NO | NO | NO | | MyISAM | DEFAULT | Default engine as of MySQL 3.23 with great performance | NO | NO | NO | | Engine | Support | Comment | Transactions | XA | Savepoints | Second we run “show engines” on the new server: “Why mysqldump is converting my tables from InnoDB to MyISAM?”įirst of all we made sure that the tables are InnoDB on the old server.

When finished, all the tables became MyISAM on the new server. One of my clients had a case when they were migrating to a new mysql server: they used mysqldump to export data from the old server (all InnoDB) and imported it to the new server. First of all: mysqldump is not converting tables.

Mysqldump zero byte file