Resolving "MySQL Error Code 135=No More Room In Record File" Article

	1888 Articles Home \| Computer Articles \| Data Recovery Articles	Data Recovery RSS
Resolving "MySQL error code 135=No more room in record file"

If the commands fail to resolve the error and the table data remains inaccessible, then the user needs to opt for an effective MySQL database repair application.

Author: Gaurav Kumar

Article Tools:

Records saved in MyISAM tables have to be changed due to many reasons like, optimizing and updating the database. For any modifications in MyISAM tables, the administrator executes ALTER TABLE TABLENAME command. While in most cases, all the changes are performed soon after the administrator executes the command, there might be few situations where the command might fail to execute. One of the common reasons why the command fails to execute is corruption of MyISAM table.

In most of these situations, the SELECT command also fails to execute, resulting into inaccessibility of all the database table records. To detect and fix such MyISAM table corruption scenarios, the administrator needs to execute myisamchk *.MYI (for checking the table) and then myisamchk –r –q tablename (for repairing the table). In case the above commands work and repair the table, then the user can view all the records. However, if the above commands fail to resolve the error and the table data remains inaccessible, then the user needs to opt for an effective MySQL database repair application.

Consider the below error message that a MySQL database administrator encountered while executing the ALTER TABLE command:

"MySQL error code 135 = No more room in record file"

After the above error appeared on the screen, none of the commands worked on that table.

Cause:

The root cause for the above error message is corruption in MyISAM table. Corruption usually occurs due to unexpected end of the file, record file crash, and application malfunction.

Resolution:

To get pass the above error message, the administrator needs to follow the below steps:
1. Check and repair the table by running below commands:
a. myisamchk *.MYI
b. myisamchk –r –q tablename
2. In case the above commands fail to execute, restore the data from an updated backup.
3. In case of no backup availability, use an effective third-party MySQL database repair application.

MySQL database repair tool information:

A MySQL database repair software is an easy solution to repair any corrupted MySQL database table. Be it an MyISAM or InnoDB database table, such MySQL database repair applications repair the tables and recover all the records. These MySQL repair tools are easy to understand and implement.

Applied for:
MySQL 5.x

About Author

Gaurav work as a freelancer and researcher for Data Recovery & MySQL Database Recovery Software.
For more information visit: http://www.datarecovery-info.com/database-recovery/mysql-recovery.html

Article Source: http://www.1888articles.com/author-gaurav-kumar-36016.html

Resolving "MySQL error code 135=No more room in record file"