减小字体
增大字体- ·上一篇文章：详解MySQL字符集的使用方法
- ·下一篇文章：MySQL中查询当前正在运行的SQL语句
mysql数据库恢复损坏数据的方法
o;t mark table as checkedRepair options (When using ‘-r’ or ‘-o’)-B, –backup Make a backup of the .MYD file as ‘filename-time.BAK’–correct-checksum Correct checksum information for table.-D, –data-file-length=# Max length of data file (when recreating datafile when it’s full)-e, –extend-check Try to recover every possible row from the data fileNormally this will also find a lot of garbage rows;Don’t use this option if you are not totally desperate.-f, –force Overwrite old temporary files.-k, –keys-used=# Tell MyISAM to update only some specific keys. # is abit mask of which keys to use. This can be used toget faster inserts!-r, –recover Can fix almost anything except unique keys that aren’tunique.-n, –sort-recover Forces recovering with sorting even if the temporaryfile would be very big.-p, –parallel-recoverUses the same technique as ‘-r’ and ‘-n’, but createsall the keys in parallel, in different threads.THIS IS ALPHA CODE. USE AT YOUR OWN RISK!-o, –safe-recover Uses old recovery method; Slower than ‘-r’ but canhandle a couple of cases where ‘-r’ reports that itcan’t fix the data file.–character-sets-dir=…Directory where character sets are–set-character-set=nameChange the character set used by the index-q, –quick Faster repair by not modifying the data file.One can give a second ‘-q’ to force myisamchk tomodify the original datafile in case of duplicate keys-u, –unpack Unpack file packed with myisampack.Other actions:-a, –analyze Analyze distribution of keys. Will make some joins inMySQL faster. You can check the calculated distributionby using ‘–description –verbose table_name’.-d, –description Prints some information about table.-A, –set-auto-increment[=value]Force auto_increment to start at this or higher valueIf no value is given, then sets the next auto_incrementvalue to the highest used value for the auto key + 1.-S, –sort-index Sort index blocks. This speeds up ‘read-next’ inapplications-R, –sort-records=#Sort records according to an index. This makes yourdata much more localized and may speed up thingsC:\mysql\bin>myisamchk c:\mysql\data\hw_enterprice\function_products.frmmyisamchk: error: ‘c:\mysql\data\hw_enterprice\function_products.frm’ is not a MyISAM-tableC:\mysql\bin>myisamchk c:\mysql\data\hw_enterprice\function_products.myiChecking MyISAM file: c:\mysql\data\hw_enterprice\function_products.myiData records: 85207 Deleted blocks: 39myisamchk: warning: Table is marked as crashedmyisamchk: warning: 1 clients is using or hasn’t closed the table properly- check file-size- check key delete-chain- check record delete-chainmyisamchk: error: record delete-link-chain corrupted- check index reference- check data record references index: 1- check data record references index: 2- check data record references index: 3- check record linksmyisamchk: error: Wrong bytesec: 0-195-171 at linkstart: 841908MyISAM-table ‘c:\mysql\data\hw_enterprice\function_products.myi’ is corruptedFix it using switch “-r” or “-o”继续进行操作：C:\mysql\bin>myisamchk –recover –quick c:\mysql\data\hw_enterprice\function_products.myi- check key delete-chain- check record delete-chainmyisamchk: error: record delete-link-chain corruptedmyisamchk: error: Quick-recover aborted; Run recovery without switch ‘q’Updating MyISAM file: c:\mysql\data\hw_enterprice\function_products.myiMyISAM-table ‘c:\mysql\data\hw_enterprice\function_products.myi’ is not fixed because of errorsTry fixing it by using the –safe-recover (-o) or the –force (-f) option系统提示我使用–safe-recover (-o) or the –force (-f) option进行修复操作，于是C:\mysql\bin>myisamchk –safe-recover c:\mysql\data\hw_enterprice\function_products.myi- recovering (with keycache) MyISAM-table ‘c:\mysql\data\hw_enterprice\function_products.myi’Data records: 85207Wrong bytesec: 0-195-171 at 841908; SkippedData records: 85215
将修复后的物理文件复制到MySQL\data下之后，通过PHPMyAdmin进行访问，OK正常!
本次数据恢复操作成功，数据已被正常恢复，总计85215条记录，其中数据恢复共计85207条。
总结本次经验及查找资料，如下：
当你试图修复一个被破坏的表的问题时，有三种修复类型。如果你得到一个错误信息指出一个临时文件不能建立，删除信息所指出的文件并再试一次–这通常是上一次修复操作遗留下来的。
这三种修复方法如下所示：
% myisamchk –recover –quick /path/to/tblName
% myisamchk –recover /path/to/tblName
% myisamchk –safe-recover /path/to/tblName
第一种是最快的，用来修复最普通的问题;而最后一种是最慢的，用来修复一些其它方法所不能修复的问题。
检查和修复MySQL数据文件
如果上面的方法无法修复一个被损坏的表，在你放弃之前，你还可以试试下面这两个技巧：
如果你怀疑表乃饕募?*.MYI)发生了不可修复的错误，甚至是丢
mysql数据库恢复损坏数据的方法
