Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I recently upgraded MySQL server on CentOS 5 with MySQL 5.0.96 After upgrade when i am trying to import old database dump which has got both MyISAM and INNODB tables in a single database, MySQL is converting all MyISAM table to INNODB.

Am not sure why this is happening. But i certainly dont want this to happen.

Any clue why this could be happening?

share|improve this question
/etc/my.cnf? /var/log/mysqld.log? – quanta Aug 27 '12 at 7:43
Is MyISAM enabled? You can check by running SHOW ENGINES – brain99 Aug 27 '12 at 8:02
Yes the MyISAM is enabled. I have checked it. Rather MyISAM is Default engine when i issue command SHOW ENGINES... – user1627036 Aug 27 '12 at 8:34
Are you sure your database dump didn't specify the tables be created with InnoDB? – Michael Hampton Aug 27 '12 at 8:42
Of course am doing this day in and day out for past 3years without a trouble – user1627036 Aug 27 '12 at 8:53

If your dumps don't specify which engine to use for each table then the system default will be used. I suspect your system default is InnoDB.

share|improve this answer
mysqldump --opt -K --triggers -c -n -R is the command i use to create mysql dump. This does not include any options to define database table type. – user1627036 Aug 27 '12 at 10:41

Ok..well i could resolve this issue by deleting the file ib_logfile1 in /var/log/mysql and restarting mysql service.

I guess this was from the older version and was causing a problem to start the innodb engine.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.