blocks|key|1554970|text|如果这些是MyISAM表，那么将.FRM、.MYD和.MYI文件放入数据库目录(例如，/var/lib/mysql/dbname)将使该表可用。它不必与它们来自同一数据库、同一服务器、同一MySQL版本或同一体系结构。您可能还需要更改文件夹的所有权(例如，chown+-R+mysql:mysql+/var/lib/mysql/dbname)|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1554971|请注意，权限(GRANT等)是mysql数据库的一部分。因此，它们不会与表一起还原；您可能需要运行适当的GRANT语句来创建用户、授予访问权限等(可以还原mysql数据库，但您需要小心MySQL版本和任何需要的mysql_upgrade实用程序运行)。|1554972|实际上，您可能只需要.FRM+(表结构)和.MYD+(表数据)，但是您必须修复表来重建.MYI+(索引)。|1554973|唯一的限制是，如果你正在降级，你最好检查一下发行说明(可能还会运行repair+table)。当然，较新的MySQL版本增加了一些功能。|1554974|尽管很明显，如果您混合并匹配表，那么这些表之间关系的完整性就是您的问题；MySQL不会关心，但是您的应用程序和用户可能会关心。此外，这种方法对InnoDB表根本不起作用。只有MyISAM，但是考虑到您拥有的文件，您就有了MyISAM|1554975|entityMap^0|17|L|3K|16|0|7|5|F|5|1G|5|25|5|2X|D|0|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@$9|Q|A|R|B|C]|$9|S|A|T|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|U|8|@$9|V|A|W|B|C]|$9|X|A|Y|B|C]|$9|Z|A|10|B|C]|$9|11|A|12|B|C]|$9|13|A|14|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|15|8|@]|D|@]|E|$]]|$1|J|3|K|5|6|7|16|8|@]|D|@]|E|$]]|$1|L|3|M|5|6|7|17|8|@]|D|@]|E|$]]|$1|N|3|-4|5|6|7|18|8|@]|D|@]|E|$]]]|O|$]]

If these are MyISAM tables, then plopping the .FRM, .MYD, and .MYI files into a database directory (e.g., <code>/var/lib/mysql/dbname</code>) will make that table available. It doesn't have to be the same database as they came from, the same server, the same MySQL version, or the same architecture. You may also need to change ownership for the folder (e.g., <code>chown -R mysql:mysql /var/lib/mysql/dbname</code>)

Note that permissions (<code>GRANT</code>, etc.) are part of the <code>mysql</code> database. So they won't be restored along with the tables; you may need to run the appropriate <code>GRANT</code> statements to create users, give access, etc. (Restoring the <code>mysql</code> database is possible, but you need to be careful with MySQL versions and any needed runs of the <code>mysql_upgrade</code> utility.)

Actually, you probably just need the .FRM (table structure) and .MYD (table data), but you'll have to repair table to rebuild the .MYI (indexes).

The only constraint is that if you're downgrading, you'd best check the release notes (and probably run repair table). Newer MySQL versions add features, of course.

[Although it should be obvious, if you mix and match tables, the integrity of relationships between those tables is your problem; MySQL won't care, but your application and your users may. Also, this method does not work at all for InnoDB tables. Only MyISAM, but considering the files you have, you have MyISAM]

blocks|key|1339487|text|请注意，如果您想要重建MYI文件，那么正确使用修复表是：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1339488|修复表可调USE_FRM；|1339489|否则，您可能会得到另一个错误。|1339490|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

Note that if you want to rebuild the MYI file then the correct use of REPAIR TABLE is:

REPAIR TABLE sometable USE_FRM;

Otherwise you will probably just get another error.

blocks|key|1339604|text|很简单！创建一个虚拟数据库(比如abc)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1339605|将所有这些.myd、.myi、.frm文件复制到mysql\data\abc，其中mysql\data\是存储所有数据库的.myd、.myi、.frm的位置。|1339606|然后转到phpMyadmin，转到db+abc，您就可以找到您的数据库。|1339607|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

Simple! Create a dummy database (say abc)

Copy all these .myd, .myi, .frm files to mysql\data\abc wherein mysql\data\ is the place where .myd, .myi, .frm for all databases are stored.

Then go to phpMyadmin, go to db abc and you find your database.

blocks|key|1555081|text|有一件事需要注意：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1555082|特定于您的MySQL版本的.FRM文件中包含您的表结构。|1555083|.MYD文件不是特定于版本的，至少不是次要版本。|1555084|.MYI文件是特定的，但可以省略并使用REPAIR+TABLE重新生成，就像其他答案所说的那样。|offset|length|style|CODE|1555085|这个答案的目的是让您知道，如果您有一个表的模式转储，那么您可以使用它来生成表结构，然后用您的备份替换这些.MYD文件，删除MYI文件，并修复它们。这样，您可以将备份恢复到另一个MySQL版本，或者在不使用mysqldump的情况下完全移动数据库。我发现这在移动大型数据库时非常有用。|1555086|entityMap^0|0|0|0|J|C|0|2U|9|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|S|8|@$H|T|I|U|J|K]]|9|@]|A|$]]|$1|L|3|M|5|6|7|V|8|@$H|W|I|X|J|K]]|9|@]|A|$]]|$1|N|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|O|$]]

One thing to note:

The .FRM file has your table structure in it, and is specific to your MySQL version.

The .MYD file is NOT specific to version, at least not minor versions.

The .MYI file is specific, but can be left out and regenerated with <code>REPAIR TABLE</code> like the other answers say.

The point of this answer is to let you know that if you have a schema dump of your tables, then you can use that to generate the table structure, then replace those .MYD files with your backups, delete the MYI files, and repair them all. This way you can restore your backups to another MySQL version, or move your database altogether without using <code>mysqldump</code>. I've found this super helpful when moving large databases.

blocks|key|1339367|text|我认为.myi你可以从mysql内部修复。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1339368|如果您在MySQL中看到以下类型的错误消息:数据库无法执行查询(查询)+1016:无法打开文件：'sometable.MYI‘。(errno:+145)错误消息:+1034:表'sometable‘的密钥文件不正确。试着修复它，然后你可能有一个崩溃或损坏的表。|1339369|您可以从mysql提示符中检查和修复该表，如下所示：|1339370|check+table+sometable;
%2B------------------%2B-------%2B----------%2B----------------------------%2B
%7C+Table+%7C+Op+%7C+Msg_type+%7C+Msg_text+%7C+
%2B------------------%2B-------%2B----------%2B----------------------------%2B+
%7C+yourdb.sometable+%7C+check+%7C+warning+%7C+Table+is+marked+as+crashed+%7C+
%7C+yourdb.sometable+%7C+check+%7C+status+%7C+OK+%7C+
%2B------------------%2B-------%2B----------%2B----------------------------%2B+

repair+table+sometable;
%2B------------------%2B--------%2B----------%2B----------%2B+
%7C+Table+%7C+Op+%7C+Msg_type+%7C+Msg_text+%7C+
%2B------------------%2B--------%2B----------%2B----------%2B+
%7C+yourdb.sometable+%7C+repair+%7C+status+%7C+OK+%7C+
%2B------------------%2B--------%2B----------%2B----------%2B|code-block|syntax|javascript|1339371|现在你的表应该没问题了：|1339372|check+table+sometable;
%2B------------------%2B-------%2B----------%2B----------%2B+
%7C+Table+%7C+Op+%7C+Msg_type+%7C+Msg_text+%7C
%2B------------------%2B-------%2B----------%2B----------%2B+
%7C+yourdb.sometable+%7C+check+%7C+status+%7C+OK+%7C
%2B------------------%2B-------%2B----------%2B----------%2B|1339373|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|S|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|T|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|U|8|@]|9|@]|A|$]]|$1|M|3|N|5|H|7|V|8|@]|9|@]|A|$I|J]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

blocks|key|1339251|text|只要data文件夹的mySQL版本完全相同，并且保留了该目录中的所有关联文件，您就可以将文件复制到data文件夹的适当命名的子目录目录中。如果你没有所有的文件，我很确定你会有问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1339252|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

You can copy the files into an appropriately named subdirectory directory of the data folder as long as it is the EXACT same version of mySQL and you have retained all of the associated files in that directory. If you don't have all the files, I'm pretty sure you're going to have issues.

blocks|key|1555172|text|http://forums.devshed.com/mysql-help-4/mysql-installation-problems-197509.html|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1555173|上面说要重命名ib_*文件。我做到了，它还给了我db。|1555174|entityMap|0|LINK|mutability|MUTABLE|url^0|0|26|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@$A|N|B|O|1|P]]|C|$]]|$1|D|3|E|5|6|7|Q|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|R|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|4]]]]

<a href="http://forums.devshed.com/mysql-help-4/mysql-installation-problems-197509.html" rel="nofollow noreferrer">http://forums.devshed.com/mysql-help-4/mysql-installation-problems-197509.html</a>

It says to rename the ib_* files. I have done it and it gave me back the db.

blocks|key|1339757|text|上面的描述不足以让我的工作(可能是密集的或懒惰的)，所以我创建了这个脚本，一旦我找到了答案，在未来帮助我。希望它能帮助其他人|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1339758|vim+fixperms.sh+

#!/bin/sh
for+D+in+`find+.+-type+d`
do
++++++++echo+$D;
++++++++chown+-R+mysql:mysql+$D;
++++++++chmod+-R+660+$D;
++++++++chown+mysql:mysql+$D;
++++++++chmod+700+$D;
done
echo+Dont+forget+to+restart+mysql:+/etc/init.d/mysqld+restart;|code-block|syntax|javascript|1339759|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

The above description wasn't sufficient to get things working for me (probably dense or lazy) so I created this script once I found the answer to help me in the future. Hope it helps others

<pre><code>vim fixperms.sh 

#!/bin/sh
for D in `find . -type d`
do
 echo $D;
 chown -R mysql:mysql $D;
 chmod -R 660 $D;
 chown mysql:mysql $D;
 chmod 700 $D;
done
echo Dont forget to restart mysql: /etc/init.d/mysqld restart;
</code></pre>

blocks|key|1339680|text|对于那些安装了Windows+XP并安装了MySQL+server+5.5的用户，数据库的位置是C:\Documents+and+Settings\All+Users\Application+Data\+MySql+\MySQL+Server+5.5\data，除非您在MySql工作台安装图形用户界面中更改了该位置。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1339681|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

For those that have Windows XP and have MySQL server 5.5 installed - the location for the database is C:\Documents and Settings\All Users\Application Data\MySQL\MySQL Server 5.5\data, unless you changed the location within the MySql Workbench installation GUI.

How to restore one of my MySQL databases from <code>.myd</code>, <code>.myi</code>, <code>.frm</code> files?

How to recover MySQL database from .myd, .myi, .frm files

SQL数据库

SQL Server

数据库

服务器

Windows

MySQL

如何从.myd、.myi、.frm文件恢复我的MySQL数据库？

问如何从.myd、.myi、.frm文件恢复MySQL数据库
EN

回答 9

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何从.myd、.myi、.frm文件恢复MySQL数据库EN

回答 9

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何从.myd、.myi、.frm文件恢复MySQL数据库
EN