ALL >> Computers >> View Article
Repairing Mysql Database When The Table Gets Crashed - Error 145
The MyISAM database engine is the default database engine for MySQL database. It provides a variety of indexing and field management functions. Its ability to swiftly perform the read operations on the databases is one of the biggest reasons of MySQL being so popular as a backend for Web applications. However, sometimes the MyISAM database tables do get corrupt because of several reasons. These reasons could be power surges, virus infections, abrupt system shutdown when the database is open, etc. In such cases, you should look to employ certain corrective measures to recover MySQL database. However, if you are unable to do so then you should use a third-party MySQL database recovery tool to do the needful.
Consider a scenario wherein you encounter the following error message while working on a MySQL database table:
MySQL error code 145 = Table was marked as crashed and should be repaired
Cause:
The most possible cause of this error message is that the database has corrupted due to not having enough space for the database. ...
...
Resolution:
To resolve the problem and extract the database after appearance of the aforementioned error message, you can perform the following methods:
Make a copy of the database.
Stop the mysqld server.
Run the myisamchk -r -q to repair the index file without affecting the file. It is used to perform quick recovery of the database.
If the previous step fails, then try the myisamchk --safe-recover command. It is used to perform a detailed scan and repair of the database.
If the previous step fails, then you should create a blank data and index files by using the following commands:
shell> mysql db_name
mysql> SET autocommit=1;
mysql> TRUNCATE TABLE tbl_name;
mysql> quit
Copy the old data file in the new one. This should resolve the issue.
These methods will be able to solve the problem. However, if you are unable to resolve the issue then you should use a third-party MySQL database repair tool to recover MySQL database. Such read-only tools are non-destructive in nature and do not overwrite the original data while scanning the corrupted database.
Stellar Phoenix Database Recovery for MySQL is a MySQL recovery software that enables you to repair MySQL database. It is capable of repairing the corrupted databases created in MySQL 4.x or 5.x versions. This MySQL repair tool is able to recover various database components such as tables, views, etc. It supports the recovery of various MySQL files of .myd, .myi, .frm, .ibdata, .ibd, and .frm from InnoDB and MyISAM database engines. This MySQL recovery tool is compatible with Windows 7, Vista, Server 2003, XP, and 2000.
Add Comment
Computers Articles
1. Remote Connectivity | Business Broadband Without Fibre India | Viva DigitallyAuthor: Viva
2. Spark Matrix™: Speech Analytics
Author: Umangp
3. Custom Computer Manufacturer: How To Choose The Right One For Your Needs?
Author: Jack Williams
4. Riding Up: The Surge Of Elevators And Escalators Across Asia Pacific
Author: Pujitha
5. Why Businesses In Mumbai Need Custom Software Development
Author: Aimbeat Insights
6. How A Multi-service App Can Transform Your Business Growth
Author: Swiza Joy
7. Advanced Humidity Monitor And Equipment Temperature Monitoring Solutions For Reliable Healthcare And Business Environments With Tempgenius Expertise
Author: Chris Miller
8. Why You Need Modern Telecom Sales Commission Management Systems To Boost Sales Efficiency
Author: Kevin
9. Why Access Reviews Keep Failing In Regulated, Hybrid Environments
Author: Soham Biswas
10. Building A Modern Real Estate App With Trulia Clone App Script
Author: Swiza Joy
11. Spark Matrix™: Multi-carrier Parcel Management Solutions
Author: Umangp
12. Best Odoo Erp Software Company In Dubai For Business Growth
Author: Mayur Meheshwari
13. Top Challenges Faced By Equipment Rental Companies In The Uae — And How Erp Solves Them
Author: Al murooj solutions
14. Spark Matrix™: Intelligent Virtual Assistants (iva)
Author: Umangp
15. Pos Software Designed For Retail Operations
Author: EPOS Direct






