Incorrect Information in File == MySQL Table Corrupted?

  • Hi Experts,

    I encountered the following problem when I'm trying to open SOME tables in MySQL database:

    "Incorrect information in file ./[database name]/


    Other tables within the same database can be opened without any issues, only some tables have this problem. And this is not just happening in one database, but the other database on the same server also has this problem (there are 2 databases AFAIK on this server). Not sure if anyone else is using this server. The database is InnoDB, running on Win2k3. Are there any other information that is required that I didn't provide?

    I have read through posts in mysql forum and it seems like none of them is able to solve my problem. The database used to work since being deployed 2 years ago and the last time the my.ini is amended is 2 years ago.

    It sounded like a data corruption issue to me and the only way is to perform data restoration from the last known working state. However, is there something wrong somewhere that I can check and fix without needing to do a restoration of the database? The users are dead against it as it would mean loss of data since the date of restoration.


  • You'll probably get a far better answer if you post this on the MySQL forums. Try This site is focused on Microsoft SQL Server and most people here will be familiar with SQL Server, not MySQL.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • Shutting Down and Restoring a Database

    mysqladmin --defaults-file=/usr/local/mysql/my.cnf --user=root --password shutdown

    mysqlbackup --defaults-file=/usr/local/mysql/my.cnf --backup-dir=/export/backups/full copy-back


    The restored data includes the backup_history table, where MySQL Enterprise Backup records details of each backup. Restoring this table to its earlier state removes information about any subsequent backups that you did. This is the correct starting point for future incremental backups, particularly those using the --incremental-base option.


    Before restoring a partial backup, you might need to delete first from the backup the .frm files associated with InnoDB tables that were not backed up.

    Read and learn following resource where the same issue was solved… Repair Toolbox for MySQL

  • It could be a problem with your .frm file

    This error is widespread but there are also many ways to repair your database.


    Follow Steps to fix.

    To fix corrupt MyISAM tables, run the following command:

    repair table tbl1 use_frm;

    Here, tbl1 is the name of the table that needs to be repaired. Replace it with the name of your table you want to fix..


Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply