MySQL error Incorrect file format Solution

The following articles mainly introduce the MySQL error, that is, the Incorrect file format/data table "in use" solution. The following describes the specific content of the article, I hope it will help you in this regard. I hope you will play a role in your future study.

Hard Disk error. The disk is automatically checked when windows is started. When you start working, the web program runs abnormally and has the following information:

130: Incorrect file format xx_messages'

It seems that the MySQL table is corrupted. in phpmyadmin, the table is displayed as "in use", and in "operations" in the toolbar, find "repair table ", however, it is strange that this item does not exist. Only "Force update table (" FLUSH ")" seems to be a serious problem). The MySQL error is prompted as follows: incorrect file format 'xx _ messages'

Google, many people have encountered such problems. The solution is to fix tables and the like. Then run the SQL command directly. Run in phpmyadmin:

 
 

  
  
check table xx_messages;  
  
  
analyze table xx_messages;  
  
  
repair table xx_messages; 
 
 

The result is useless, as shown in the following figure: "Incorrect file format 'xx _ messages '"

It seems that the online saying does not necessarily solve my problem. It is better to seek help and solve it by yourself.

When you go to the mysql database directory, check whether the file is normal. Otherwise, import the previous backup.

The file size of xx_messages.MYI is 0. It seems that the index is broken and copied from the previous backup file, the other two files in the 0-size file are not replaced.) phpmyadmin prompts a MySQL error.

 
 

  
  
#1194 – Table ‘bne9pb_messages’ is marked as crashed and should be repaired 
 
 

It must be an index problem. I modified the table structure yesterday and used the old index file to fix the table:

 
 

  
  
repair table bne9pb_messages; 
 
 

Solve the problem. However, it doesn't matter if all the data is lost and it becomes an empty table. It is used for local development. If it is a table on the server, it must be backed up in advance. Otherwise, it is really tearful.

This is only because the index file is broken. If all the data files are broken, you can only rechange them based on the old data backup.

Only the index breaks down and actually runs

 
 

  
  
REPAIR TABLE xx_messages USE_FRM; 
 
 

This should solve the problem. In this way, the original data can be retained without being lost, but no attempt has been made. This time, no backup of bad files can be made, and no further competition can be made.

The above content is an introduction to the MySQL error: Incorrect file format/"in use" of the data table to solve the manual. I hope you will get something.