Wednesday, March 31, 2010

Repairing corrupt MySQL tables

MySQL table corruption can be easily identified. Few symptoms that allow you to identify table corruption are - queries stop fetching records, display of an error message, and display of incorrect records. The above symptoms primarily results in inaccessibility of records stored in MySQL tables. In such situations, a complete database backup allows you to overcome the problem by restoring all the required data. However, there is a possibility that the data backup is corrupted or does not restore the required information. For absolute repair of corrupted tables under such situations, you will need to opt for advanced MySQL Repair software.

Consider a practical example, where you encounter the below error message when you attempt to access the records saved in Employee table:

"Unexpected end of File"

The above error message makes the data stored in the Employee database records inaccessible. In addition, the same error message re-appears each time you attempt to access the records saved in the Employee table.

Cause:

The root cause for the occurrence of the above error message is the corruption of Employee table. Few main reasons for table corruption can be unexpected system shut down, improper locking of tables, header corruption, virus attack, and human errors.

Resolution:

To resolve the above error and access the records saved in Employee table, you will need to follow the below measures:

Check the Employee table for the extent of corruption using the below command: CHECK TABLE Employee

If the above command reports corruption, then you will need to repair the table by using the below command:

REPAIR TABLE Employee

In most cases, table corruption gets resolved by using the above command. However, if the problem persists and the same error message appears again while accessing the records, then you will need to use advanced MySQL Database Repair software. Such read only MySQL Recovery utilities employ powerful procedures to to systematically scan and repair the corrupted tables. These repair tools are built with highly interactive user-interface and can be used by both technical and non-technical users.

Wednesday, March 24, 2010

Resolving Error Codes 126, 127, 144, and 145 in MySQL database

Sometimes, when you attempt to access the records saved in MySQL database table, there is a possibility of getting an error message. The error message primarily occurs due to MySQL database corruption. Few main causes of MySQL database corruption are server crash, MySQL bug, damaged table handler, and many more similar reasons. In such situation, the records stored in your MySQL database components become inaccessible. For complete access of records in such scenarios, an ideal way is to restore the data from an updated and valid backup. However, if no backup is available or backup falls short to restore the correct records, then you will need to opt for advanced third party MySQL Repair application.

Consider a practical scenario, where you attempt to mount your MySQL database (Employee) and receive any of the below error messages:

“Got error 126 from table handler”

Or

“Got error 127 from table handler”

Or

“Got error 144 from table handler”

Or

“Got error 145 from table handler”

Data stored in the Employee database becomes inaccessible after any of the above error message appears. In addition, the same error messages appear each time you attempt to mount your Employee database.

Cause:

The root cause for the occurrence of the above error message is corruption of Employee database after damage in table handler.

Resolution:

To resolve the above error message and access the records stored in the Employee database, you will need to run the below command to analyze the below command to check the extent of Employee database corruption:

“Check Table tablename”

After analyzing the extent of Access database corruption, you will need to use the below repair command:

“Repair Table tablename”

In most cases, the above resolution resolves your issue and the database becomes inaccessible. However, if the database remains inaccessible and you still encounter the above error message, then you will need to use advanced MySQL Database Recovery software. These MySQL Recovery utilities provide secure, comprehensive, and fast database repair by maintaining the intactness of data.

Saturday, March 20, 2010

Resolving Error 29 in MySQL Database

Mysqldump is a backup program that allows you to dump MySQL database(s) or transfer the records to another SQL Server. The dump contains SQL statements that can either populate the table or create the table. While the backup program creates backup in most cases, the program gets halted when your database gets corrupted or damaged. In most of these situations, you encounter an error message that does not allow you to create a backup. To overcome these situations, you will need to use an advanced MySQL Repair tool to repair the corrupted or damaged MySQL database.

Consider a practical scenario, where you try and do a mysqldump, and encounter the below error message:

[root@www diaendomet]# mysqldump -ucojjohealth -p --all-databases >
alldatabases.sql
Enter password:
mysqldump: Got error: 29: File '../diaendomet/users.MYD' not found
(Errcode: 2) when using LOCK TABLES

The same error message appears each time you attempt to run mysqldump. In addition, the mysqldump halts every time it encounters the above error.

Cause:

The fundamental cause for the occurrence of the above error message is corruption of MySQL database. Few main reasons for MySQL database corruption are improper system shutdown, virus attack, and application malfunction.

Resolution:

To resolve the above error message, you will need to run the below command:

“mysqlcheck --all-databases --auto-repair -ucojjohealth -p”

While the above command repairs corrupted databases in most cases, there is a possibility of getting a new error message after this command:

“error: File '../diaendomet/users.MYD' not found (Errcode: 2)”

If you encounter the above error message, then your database has been corrupted badly. To repair your database in such situations, you will need to use third-party MySQL Database Recovery tools. MySQL Recovery utilities provide advanced, complete, and risk-free database repair applications that repair damaged MySQL database while maintaining the intactness of data. These tools employ high-end scanning mechanisms to comprehensively repair the corrupted MySQL databases. With to-the-point documentation, the tools serve as self-explanatory and repair-centric tools.

Thursday, March 18, 2010

Resolving “Database page corruption” Error in MySQL

MySQL database uses two storage engines- InnoDB and ISAM. InnoDB is the standard element of all current MySQL libraries. It supports several feature, which make it better than other storage engines. The features include foreign key support and storing data in primary key order. The InnoDB also features ACID properties- compliant transaction support, which allows it to recover from unforeseen crashes. In some situations, the InnoDB database may corrupt if you kill Mysqlid process, virus infection, improper system shutdown, application malfunction and many others. In such cases, you need to restore your database from most recent backup. If the backup is not available or up to date, you will require MySQL Repair solutions to retrieve data from damaged database.

In a practical scenario, you might come across below error message while trying to access data from an InnoDB database:

“Database page corruption on disk or a failed file read”

When this error message occurs, the MySQL application and database crashes down and renders all your critical data inaccessible. In order to gain access of your valuable data in such situations, you need to find out the cause of this behavior and go for MySQL Recovery by resolving it.

Root of the problem

As stated in the above error message, this problem occur due to corruption to the database pages or entire database. When database corruption occurs, MySQL can not read information from database and returns the error. However, other reasons of above problem can be improperly configured or damaged libraries.

Resolution

To sort out above problem, go through underwritten steps:

Check that all the linked libraries are correct and properly configured.
If the MySQL database is corrupted, use following steps to recover:
Analyze MySQL table corruption by this command:
Check Table tablename
Run following command to repair the damaged table:
Repair Table tablename
If the error message still occurs, repair and restore the damaged database using MySQL Repair software.

These are effective applications, which let you carry out absolute MySQL Database Recovery in most of the corruption scenarios. They are completely easy to use as they have interactive and simple graphical user interface. The software do not alter original contents of the database due to read-only behavior.

Database Recovery for MySQL is a powerful utility to handle all types of Repair MySQL Database corruption issues. It supports recovery from MySQL 5.x and 4.x. The software is compatible with Microsoft Windows Vista, 2003, XP and 2000 and all major Linux distributions.

Tuesday, March 16, 2010

How to Resolve “Record-file is crashed” Error in MySQL

MySQL database is made up of several tables, which store data in the form of rows and columns. A MySQL database table is the collection of several interrelated data records. The MySQL database tables are identified with different and unique names. You can easily and quickly identify table corruption when they produce incorrect result or retrieve irrelevant data.MySQL database corruption generally caused by improper system shutdown or application shutdown, application bug in MyISAM or MySQL code, user of third party application (such as myisamchk) on like table, virus infection, faulty memory and so forth. In these critical situations, if you do not have complete backup of your database, you are required to go for effective MySQL Repair using advanced tools.

In a practical scenario, where you use the Select statement to show all records of the Employee table. For this purpose you write below command:

Select * from employee;

When you execute this MySQL command, you come across below given error message and you does not get any record as output:

“Record-file is crashed”

The same problem might occur with any of the database table. Above error message indicates that the database table is damaged. Furthermore, you come across same error message and face same behavior every time when you run Select statement on MySQL table. Subsequent to the above error, all of the data stored in particular database table become inaccessible and you come across data loss situations. At this point, you are required to find out the cause of this problem and go for MySQL Recovery by resolving it.

Solution

In order to work around this issue and gain access of your mission critical data, first of all check the database table for corruption and integrity using underwritten command:

CHECK TABLE ;

After completion of this process, repair damaged database table using following command:
REPAIR TABLE
;
However, when the repair command can not fix the above issue, data may still remain inaccessible and you face same problem. In such cases, you should go for third party SQL Database Recovery software for assured and complete recovery.

These tools use high-end scanning techniques for in-depth scanning of affected database and retrieve all of its objects. These MySQL Repair applications have self-descriptive and interactive graphical user interface to offer ease of use. Due to read-only and non-destructive conduct, these tools are completely safe to use.

Stellar Phoenix Database Recovery for MySQL is the most trustworthy application to handle all cases of Repair MySQL database corruption. This tool supports both (MyISAM and InnoDB) MySQL database storage engines. It is designed to recover data from MySQL database installed on Windows Vista, 2003, XP, 2000 and Linux (all major distributions) operating systems.

Sunday, March 14, 2010

Table Crash Might Cause Database Corruption in MySQL

Each MySQL database is an organized group of table, which store data and information in form of rows and columns. Tables could be added or deleted as per your requirement. But in some situations, the database tables might get damaged and the stored data become inaccessible. Generally the MySQL tables are damaged due to improper system shutdown, using external application (such as myisamchk) on like table, insufficient disk space, virus infection, faulty memory and many alike. Corruption to database table cause serious data loss situations. In these cases, for absolute recovery, restore data from most recent backup. But if the backup is not available, you need to go for MySQL Repair solutions to get your critical data back.

In a practical scenario, when you try to access the MyISAM (account) table in MySQL database, you might come across below given error message and the process might get terminated:

“MySQL error: 145
Table './rootforu_forum/Accounts' is marked as crashed and should be repaired
Query: SELECT * FROM Accounts WHERE sid='73bc9dbecbab357dc2ca7a54fb410f09' AND ip='XX.XX.X.XXX' LIMIT 1”

The above error message indicates that corruption has occurred in the Accounts table of MyISAM database and thus you can not get into account.

Root of the problem

The major cause of this problem is corruption to the MyISAM table or entire database. The corruption could be due to insufficient memory space. In above scenario, the Accounts table needs to be repaired and restores for further accessing of the database.

Resolution

In order to sort out above issue and carry out MySQL Repair, check database corruption using below command:

“CHECK TABLE Accounts;
(If the Accounts table is stored on server, make sure that the server is currently running)
Next, repair Accounts table by using any of the following commands:

% mysqlcheck -uuser -ppass Accounts fixtures;
(When you run this command, make sure that the server is currently running)
Or
% myisamchk fixtures Accounts.MYI
(The server must be down and the Accounts table must be inactive when you run this command)

When all else fails to sort out your problem, go for MySQL Recovery using third party software. These software are particularly designed to effectively scan the damaged database and retrieve all of the data from it. The MySQL Recovery software are completely easy and safe to use.

Stellar Phoenix Database Recovery for MySQL is the most popular and widely used software to ensure perfect recovery. This read only application works well with MySQL 5.x and 4.x. This software is designed for Microsoft Windows Vista, 2003, XP, 2000 and Linux distributions.

Article Source :- http://articlenexus.com/Article/Table-Crash-Might-Cause-Database-Corruption-in-MySQL/271704

Thursday, March 11, 2010

MySQL Database Corruption Due to Damaged Table Handler


MySQL is a powerful and widely used Relational Database Management System (RDBMS), which provides multi-user access to different databases. This works on various operating system platforms including Microsoft Windows and Linux. The MySQL databases could involve several powerful feature such as triggers, stored procedures, cursors, query caching and views. In some situations, the reliable database gets damaged. In these cases, you are required to restore the database from backup to get your mission critical data back. In case if the backup is unavailable, it becomes essential to go for MySQL Recovery using proper tools.

In a practical scenario of MySQL database corruption, you might come across the below given error message when you attempt to access the database:

"Got error ### from table handler"

Where, ### refers to the MySQL error codes like 126, 127, 144, 145 etc.

After this behavior, the database could not be accessed and you come across data loss. At this point, you are required to find out the cause of this problem and go for MySQL Recovery by sorting it out.

Root of the issue

The above problem might take place because of the database corruption that might occur due to any of the below reasons:

Mysqld process has killed while writing data in the database. Hardware problems such as CPU and memory related. Improper system shutdown. Use of third party utilities for database operations. Software error in MyISAM or MySQL code. Resolution

In order to sort out this problem of MySQL Database, you need to go through below steps: Analyze the extent of database corruption. Use below command for the same: Check Table tablename If the database is damaged, you need to run the underwritten command for repairing it: Repair Table tablename

Scan whole database with the Check Table command again to verify if the database is free from corruption. If the problem persists, run mysqldump command to backup the database. Then create a new empty MySQL database and import the information from damaged database. After that, edit /admin/config.php point of newly created database. When all else fails, go for MySQL Database Recovery using third party tools.

These applications employ high-end scanning algorithms for efficient scanning of corrupted MySQL database and retrieve all of the data from it. They come equipped with interactive user interface and thus allows you to carry out easy and safe MySQL Repair.

Stellar Phoenix Database Recovery for MySQL is the absolute solution for all MySQL database corruption scenarios. It works well with MySQL 5.x and 4.x. This software recovers all MySQL database objects and compatible with Microsoft Windows Vista, XP, 2003 and 2000.

Article Source :- http://www.goarticles.com/cgi-bin/showa.cgi?C=1968809

Tuesday, March 9, 2010

Rectifying “Database page corruption” Error in MySQL


MySQL database use two different data storage engines and InnoDB is one among them. The InnoDB is a standard component of all the current MySQL libraries. It supports different features, which make is superior than other data storage engines. These storage engines are the foreign key support, for storing data rows in the primary key order. The InnoDB also features the ACID compliant transaction support, which enables the database to recover from unanticipated system crashes. Along with the unanticipated system crashes, the InnoDB database may also get damaged when you accidentally kill the Mysqlid process. In these circumstances, the database become inaccessible and you need to restore it from most recent backup. But in case if the backup is not available, you come across data loss situations and require MySQL Repair to sort them out.

In a practical scenario, while trying to access data from a InnoDB storage engine, you might encounter the below given error message:

"Database page corruption on disk or a failed file read"

When this error message occurs, the MySQL gets crashed down. This behavior of MySQL makes the database inaccessible. To gain access of your data in such situations, you are required to find out the cause of this issue and go for MySQL Recovery by sorting it out.

Root of the issue

As stated in the above error message, this behavior of InnoDB database occurs due to corruption. In case of corruption, MySQL can not recognize the data on hard drive and thus can not read it. Nevertheless the cause of this problem, ultimate result would be the loss of your valuable data.

Resolution

In order to sort out the above problem, try following methods:

Verify that all of the linked libraries are right and properly configured. Identify and resolve the hardware problems, if any. If the problem is due to database corruption, repair and restore it using MySQL Repair software.

These are powerful and advanced third party applications, which are capable of handling most of the InnoDB database corruption scenarios. These Repair MySQL Database applications use high-end scanning methods to ensure absolute and effective recovery. They have simple and interactive graphical user interface to let you carry out recovery, without demanding sound and prior technical skills. With read only conduct, these applications are quite safe to use.

Stellar Phoenix Database Recovery for MySQL is a powerful and effective repair software for corrupted MySQL databases. This software supports recovery for both MyISAM and InnoDB. This non-destructive application is compatible with Microsoft Windows Vista, 2003, XP, 2000 and Linux operating systems.

Article Source :- http://www.goarticles.com/cgi-bin/showa.cgi?C=1948123

Monday, March 8, 2010

Incorrect Key Files in Table Cause Corruption in MySQL Database

In MySQL database, the tables that are created by end user, that allows the users to store various kinds of data. These database tables are actually store all of your data and create the database. But in some cases, the database tables could get damaged due to interruption in mysqld (MySQL Server) procedures, virus infection, application bug, improper system shutdown, but in MySQL or MyISAM code and many alike. In these circumstances, the stored data become inaccessible and you come across data loss situations. In order to access data in these cases, you are required to go for data restoration from backup. In case if the restore process fails or you do not have backup, then you need to repair and restore the database using MySQL Recovery solutions.

In a practical scenario, when you try to open a MySQL database table, you might come across the below given error message and the table remains inaccessible:

"Incorrect key file for table: 'Users'. Try to repair it"

Subsequent to the above error message, the database queries don't find the rows in database table and thus you get incomplete results. Major reason behind the occurrence of the above error message is damage to the database table because of improper system shutdown.

Resolution

In order to sort out this problem and gain access of your valuable data, you need to repair and restore the damaged database tables. For this, you need to run the following command from MySQL prompt:

REPAIR TABLE ;

However, if you are not able to access MySQL prompt, then you need to access shell and then run myisamck tool. For checking the database table, you are required to run underwritten command on shell:

myisamchk /path/to/the/table

For repairing the table, write underwritten command on shell:

myisamchk -r /path/to/the/table

When all else fails, it becomes essential for you to go for third party applications to repair and restore the database. These applications are known MySQL Recovery software. They use efficient scanning algorithms to effectively scan the damaged database and retrieve all of the data from them.

These MySQL Repair applications do not demand sound and prior technical skills to repair the database as they have interactive user interface. The MySQL Database Recovery tools are complete safe to use with read only conduct.

Stellar Phoenix Database Recovery for MySQL is the most excellent solution for MySQL database corruption situations. This software supports recovery from InnoDB and MyISAM database engines of MySQL. It is compatible with Microsoft Windows Vista, 2003, XP and 2000 and on the Linux platform.

Article Source :- http://quizilla.teennick.com/stories/13932714/incorrect-key-files-in-table-cause-corruption-in-mysql-database

Friday, March 5, 2010

Heavy Load Might Corrupt InnoDB Database

Storing MySQL database with InnoDB storage engine gives enhancements of ACID-compliant transaction support and foreign key support, as compared to other storage engines. But database thus stored can also become corrupt and inaccessible due to several issues. Using MySQL Server in heavy load environment might corrupt the database. In such cases, it is recommended to dump the database tables if a valid backup is available. But if no clean backup is present, use powerful MySQL Recovery software to repair and restore the database.

Following is the example of a MySQL Server database stored using InnoDB storage engine that processes large amount of data and performs multiple tasks at a time:

A large database with thousands GB of data Multiple threads are running that write data to the server Several complex are running Multiple threads are running that query data from the server Different operations are performing to manipulate data from several tables

If you use a MySQL Server database in such an environment, the Server might crash and result into a corrupt database. You might observe that the InnoDB engine hangs when you to try to access the database.

Solution

If there are one or more database tables that are preventing the MySQL Server to start, you can dump those tables provided you have a valid backup available. To do so, follow these steps:

Before trying to start MySQL Server, add the following line to /etc/my.cnf configuration file:

[mysqld] innodb_force_recovery=4

This allows starting the server while preventing background operations.

Restart MySQL Server Dump all the database tables and shutdown the database You next need to delete the data dictionary and execute mysql_install_db in order to create the default tables that MySQL requires You should then remove the innodb_force_recovery line from the file Restore from backup

In case, no valid backup is available, you are suggested to use third-party MySQL Database Recovery tools. MySQL Recovery utilities are powerful, comprehensive and safe database repair applications that repair damaged MySQL database while maintaining the intactness of data.

Database Recovery For MySQL is an advanced and powerful MySQL Database Recovery utility that supports both MySQL database storage engines - MyISAM and InnoDB. It can completely repair and restore MySQL objects such as tables, primary key(s) and relations. It is compatible with Windows Vista, XP, 2003 and 2000. It supports MySQL 5.x. It also supports Windows based recovery from MySQL database installed on Linux platform.

Article Source :- http://www.goarticles.com/cgi-bin/showa.cgi?C=1931742

Thursday, March 4, 2010

Killing INSERT … SELECT Can Corrupt MySQL Table on MyISAM

The MySQL INSERT ... SELECT command allows you to insert several rows into a table from various tables. But at times, when you kill the command on MyISAM, you observe that the table gets corrupt. Such type of errors usually occur with large data sets. When you run CHECK TABLE command to check the table for consistency, it reports that the table is unusable as it is corrupt. The table thus corrupted should be restored from backup or you can alternatively use MySQL Repair tools that are competent products to allow safe repair of database and its objects.

To illustrate the same, consider that you use a table with name 'a' on MyISAM storage engine'. You execute INSERT ... SELECT command and kill it while it is running. After this, you use CHECK TABLE command to perform the sanity check of the table and come across errros similar to:

Table Op Msg_type Msg_text test.a check warning Table is marked as crashed and last repair failed test.a check warning Size of indexfile is: 1337344 Should be: 1024 test.a check error Record-count is not ok; is 92522 Should be: 0 test.a check warning Found 92522 key parts. Should be: 0 test.a check error Partition pMin returned error test.a check error Corrupt

Cause

The error indicates that the table has got corrupt. When you kill the INSERT ... SELECT statement, which is being applied on the table with indexes and contains large amount of data, it might get corrupt. This occurs when we disable the indexes for the purpose of fast insert. After the bulk_insert operation is completed, indexes are tried to be re-enabled. While MySQL is re-enabling the indexes, killing the query results into aborting the repair table operation and hence the table gets corrupt.

Solution

Use any of these methods to repair the corrupted MyISAM table:

You can use the following command to repair:

REPAIR TABLE table_name

Where, table_name is the name of corrupted table

Use MySQL Recovery tools for achieving best and safe repair results. MySQL Repair tools are fully-competent database recovery utilities built with powerful scanning technology and easy to use interface.

Stellar Phoenix Database Recovery For MySQL is the most powerful and advanced MySQL Recovery utility. It supports both Repair MySQL Database storage engines - MyISAM and InnoDB and is competent to completely repair and restore MySQL objects such as tables, primary key(s) and relations. It is compatible with Windows Vista, XP, 2003 and 2000. It supports MySQL 5.x. It also supports Windows based recovery from MySQL database installed on Linux platform.

Article Source :- http://www.goarticles.com/cgi-bin/showa.cgi?C=1909241

Wednesday, March 3, 2010

MySQL Fails to Start After Upgrading Fedora

MySQL is a multi-threaded and multi-user database server that allows implementing client/server architecture. It is consisted of different client libraries and programs and a server daemon called mysqld. MySQL can work on various system platforms including Linux. At times, you observe that after you upgrade the system, MySQL fails to start. It could occur if the database has become inconsistent due to errors while upgrading the system. In such situations, you need to use your backup or MySQL Repair tools to restore the corrupted database and its components.

For an instance, you are using MySQL on a Fedora Core 10 installed system. You upgrade the system to Fedora Core 11 and after this, when you attempt to start MySQL, it fails. Viewing the /var/log/mysql error log gives you errors such as:

"Fatal error: Can't open and lock privilege tables: Incorrect key file for table 'table_name; try to repair it"

The error log also describes to run mysql_upgrade and further errors such as:

"Incorrect key file for table 'table_name'; try to repair it"

As suggested, you cannot run mysql_upgrade as MySQL is failing to start.

Cause

One of the prominent reasons for such errors to occur is that MySQL tables have got corrupted due to version incompatibilities issues.

Solution

To reconcile the issue, you can try applying these methods of recovery:

If a clean database backup is available, use it to restore You need to run mysql_upgrade that is competent to check all database tables for incompatibility issues with the existing version of MySQL Server. After any error is found, the tool attempts to repair the table. You can also downgrade your MySQL installation to MySQL 5.0.67 and repair the table by running the below command:

REPAIR TABLE table_name

You can then upgrade MySQL to the current version. If above measures prove to be useless, you need to use MySQL Repair software. MySQL Recovery applications are competent products built with powerful database repair technology that restore corrupted database safely and provide interactive interface.

MySQL is a powerful Repair MySQL Database utility that supports both MySQL database storage engines - MyISAM and InnoDB. It can completely repair and restore MySQL objects such as tables, primary key(s) and relations. It is compatible with Windows Vista, XP, 2003 and 2000. It supports MySQL 5.x. It also supports Windows based recovery from MySQL database installed on Linux platform.

Tuesday, March 2, 2010

Resolving MySQL Error: 'Found wrong record at 0'

MySQL database tables can become inconsistent when a write operation to a data file doesn't accomplish successfully. This could occur due to several reasons like non-graceful shutdown of the server or power failure. Another reasons include application bugs, storage engine issues and more. The application provides myisamchk and mysqlcheck as two tools that can detect and repair such corruption errors in MySQL tables. If they fail to do so, you will require a valid backup to restore the lost information. However, if backup too fails to give the required results, you need to use MySQL Database Recovery application to repair the corrupted database.


For an instance, when you run myisamchk to check the consistency of a MySQL database table, it might report you errors as below:

“myisamchk: error: Found wrong record at 0
MyISAM-table 'table_name.MYI' is corrupted”

Where, table_name.MYI refers to the name of the table. MySQL uses .MYI files to use index information of the database table.

Cause

The above error is generally encountered when the .MYI file is inconsistent due to corruption.

Solution

To troubleshoot the database table corruption errors and to restore the information, you should apply these methods:

If you suspect that database table is corrupted, execute myisamchk command. Before running the command, you need to ensure that your MySQL server is not running. Follow this syntax to repair:

myisamchk --recover table_name.MYI

If the issue persists, try restoring from your backup. In order for backup to give complete results, it should exist in clean and completely updated state.
If none of the above measures help or is feasible, delete the damaged database table and create a new one.

To prevent data loss, you can alternatively repair your database using MySQL Recovery tools. Such MySQL Database Recovery utilies employ effective scanning algorithms to repair and restore the data stored in MyISAM tables. With exceptionally realistic user interface, this repair utility is easily usable without sound technical understanding. The repair tools should also set a secure link with MySQL Server while repairing the corrupted MyISAM table.

Stellar Phoenix Database Recovery for MySQL is the most used MySQL Repair software. This non-destructive repair utility is compatible with both (MyISAM and InnoDB) MySQL database storage engines. It can completely restore and Repair MySQL components like tables, primary key(s) and relations. It supports MySQL Recovery from MySQL database installed Windows (Vista, XP, 2003 and 2000) and on Linux platform.

Article Source :- http://www.articledashboard.com/Article/Resolving-MySQL-Error---Found-wrong-record-at-0-/1054308

Table Error After Upgrading MySQL Server

With the release of each new version of MySQL, the application goes advanced and safer. If you are upgrading your MySQL Server from an earlier version to later, it is highly recommended that you backup all the data first. Any errors while the upgrade process might result into database or table corruption errors, thereby making the data inaccessible. Thus, to restore such lost information, you will need to use your recent data backup or scan your damaged MySQL database using MySQL Database Recovery applications. These tools are repair utilities to restore damaged MySQL databases.

For an instance, after you upgrade MySQL 4.0 to MySQL 5.0.67, you might receive the following error message with one or more of the database tables:

"Incorrect key file for table 'filename.MYI'; try to repair it"

This error indicates corruption of .MYI file that is the index file of database.

Cause

The above error results if .MYI file gets corrupted due to errors while upgrading or table incompatibilities issue with MySQL 5.0.67.

Solution

To check the database table for incompatibilities with the present version of MySQL, it is recommended to use mysql_upgrade. Besides checking the tables, the tool also upgrades the tables so that to make them compatible according to new features of MySQL.

However, to repair such damaged tables, you should perform these steps:

Run the below command to check table for inconsistencies:

Check Table tablename

Upon finding errors, execute the following command:

Repair Table tablename

If issue remains the same, restore from backup, if is available and valid
If you don't have any valid data backup, you should use commercial MySQL Recovery to effectively repair and restore the database and its components.

MySQL Database Recovery tools are special-purposed utilities designed to scan the damaged MySQL database using powerful scanning algorithms. Such tools benefit you graphically rich use interface, complete documentation, safe database repair results and realistically unique set of features. These products are built with premier technology to examine the corrupted database. You can use these tools in any case of logical database corruption.

Stellar Phoenix Database Recovery for MySQL is the comprehensive and the most trusted MySQL Recovery tool. This read-only database repair application supports both (MyISAM and InnoDB) MySQL database storage engines. The software supports MySQL 4.x and 5.x. It can completely restore and Repair MySQL components like tables, primary key(s) and relations. It is compatible with recovery from MySQL database installed Windows (Vista, XP, 2003 and 2000) and on Linux platform.

Naveen Kadian is a self employed Internet entrepreneur and product reviewer Stellar Phoenix Database Recovery For MySQL is the premier MySQL Repair tool that can instantly repair and restore corrupt MySQL databases. It supports InnoDB (.ibdata, .ibd and .frm) and MyISAM (.myd, .myi and .frm) files.

Source Taken From :- http://ezinearticles.com/?Table-Error-After-Upgrading-MySQL-Server&id=2722933