Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Damaged Database

Status
Not open for further replies.

robhob

Programmer
Dec 1, 2008
22
ZA
G'day!

I've got an unusual situation. We backup our MySQL databases every night. The backup is done by copying the folders containing the database files (MyISAM on a Windows 2000 server) to a temp folder. They are then zipped and FTP'd to a server at our offices. If I then unzip the database they is always one table that needs to be repaired. I've check the table on the live server using CHECK TABLE table_name and it comes up clean. I've even tried the extended CHECK TABLE and it also comes up clean. If I copy just that table from the live server to my local installation and run the CHECK TABLE table name EXTENDED I then get a size difference warning for the indexfile and the datafile as well as a error "Record at: 2874384 Can't find key for index: 6" and then another error that simply says Corrupt. The table is then marked as crashed. If I run REPAIR TABLE table_name EXTENDED I get a message stating that the number of rows changed from 217393 to 230912.

I hope I'm making sense. Any help would be appreciated.

Many thanks

robhob
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top