Re: Major MySQL problems
Posted by:
Rick James
Date: February 12, 2010 11:04AM
Stay away from the underlying files until you understand the ramifications of what you are doing.
The size of the innodb logs is controlled by one of the my.cnf settings. However, if they do not match, InnoDB cannot come up (as you discovered). If MySQL is gracefully shutdown, the logs can be removed, and will be created upon restart. (That is how to change the size of the logs.) If it was an ungraceful shutdown, those logs are necessary for the integrity of InnoDB -- changing/deleting/etc the files would cause trouble.
A .frm file contains the schema for one table. Moving/removing it will cause trouble. It can possibly be recreated by CREATE TABLE, but probably should be done in another database, then moved to the right database (directory). I do not know if this will work.
Read the docs about --force-recovery.
Subject
Views
Written By
Posted
5098
February 10, 2010 04:26AM
2624
February 11, 2010 10:45PM
2442
February 12, 2010 07:17AM
Re: Major MySQL problems
1960
February 12, 2010 11:04AM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.