数据库的导入问题

2013-03-26 12:46:05 517 阅读 AI 写同款 · GEO 优化AI 选题数据监测一键分发 ›

【C++】C++异常语法、使用、规范、异常安全及异常的优缺点实际中我们可以可以去继承exception类实现自己的异常类。但是实际中很多公司像上面一样自己定义一套异常继承体系。因为C++标准库设计的不够好用。如果有一个块抛出一个异常，捕获异常的方法会使用 try 和 catch 关键字。try 块中放置可能抛出异常的代码，try 块中的代码被称为保护代码。C++ 提供了一系列标准的异常，定义在中，我们可以在程序中使用这些标准的异常。异常是一种处理错误的方式，阅读详情

我是复制的方式把数据库复制出来的（里面的表是.frm格式文件），然后重新安装了mysql，我想把数据库导入到现在的mysql里面，粘贴好像不行，听别人说，可能是版本不同的原因，识别不出来（有人说要修改某些配置才行）我应该怎么弄才能让现在的mysql识别出来呢，

真的很急~~谢谢指点！

...全文

C#调用Bartender打印标签，除了打印还能一键导出图片和PDF（附完整代码）本文详细介绍了如何使用C#集成Bartender实现标签的多格式输出，包括打印、图片和PDF导出。通过完整的代码示例和实战技巧，帮助开发者解决分辨率适配、纸张尺寸控制等核心问题，提升工业自动化和物流管理中的标签处理效率。阅读详情

zly361814478

MySQL 57,062 成员 56,759 内容

+ 关注 + 加入社区

切换为时间正序

zly361814478 2013-04-12

打赏
举报

感谢大神们的分享。我理解很多

zly361814478 2013-04-08

打赏
举报

引用 21 楼 k_scott 的回复:

你之前卸载的mysql版本是几。现在重新安装的是几。 http://blog.csdn.net/xiangliangyu2008/article/details/8450765

之前卸载的mysql 不知道是哪个版本了不知道是5.5 还是5.6 现在又全部被我重新卸载了

zly361814478 2013-04-07

打赏
举报

130403 10:53:11 [ERROR] Cannot find or open table zly/connect from the internal data dictionary of InnoDB though the .frm file for the table exists. Maybe you have deleted and recreated InnoDB data files but have forgotten to delete the corresponding .frm files of InnoDB tables, or you have moved .frm files to another database? or, the table contains indexes that this version of the engine doesn't support. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html how you can resolve the problem. 130403 10:53:11 [ERROR] Cannot find or open table zly/content from the internal data dictionary of InnoDB though the .frm file for the table exists. Maybe you have deleted and recreated InnoDB data files but have forgotten to delete the corresponding .frm files of InnoDB tables, or you have moved .frm files to another database? or, the table contains indexes that this version of the engine doesn't support. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html how you can resolve the problem. 130403 10:53:11 [ERROR] Cannot find or open table zly/login from the internal data dictionary of InnoDB though the .frm file for the table exists. Maybe you have deleted and recreated InnoDB data files but have forgotten to delete the corresponding .frm files of InnoDB tables, or you have moved .frm files to another database? or, the table contains indexes that this version of the engine doesn't support. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html how you can resolve the problem. 130403 10:53:11 [ERROR] Cannot find or open table zly/person from the internal data dictionary of InnoDB though the .frm file for the table exists. Maybe you have deleted and recreated InnoDB data files but have forgotten to delete the corresponding .frm files of InnoDB tables, or you have moved .frm files to another database? or, the table contains indexes that this version of the engine doesn't support. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html how you can resolve the problem. 130403 10:53:11 [ERROR] Cannot find or open table zly/photo from the internal data dictionary of InnoDB though the .frm file for the table exists. Maybe you have deleted and recreated InnoDB data files but have forgotten to delete the corresponding .frm files of InnoDB tables, or you have moved .frm files to another database? or, the table contains indexes that this version of the engine doesn't support. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html how you can resolve the problem. 130403 10:53:11 [ERROR] Cannot find or open table zly/photo_block from the internal data dictionary of InnoDB though the .frm file for the table exists. Maybe you have deleted and recreated InnoDB data files but have forgotten to delete the corresponding .frm files of InnoDB tables, or you have moved .frm files to another database? or, the table contains indexes that this version of the engine doesn't support. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html how you can resolve the problem. 130403 10:53:11 [ERROR] Cannot find or open table zly/photoreview from the internal data dictionary of InnoDB though the .frm file for the table exists. Maybe you have deleted and recreated InnoDB data files but have forgotten to delete the corresponding .frm files of InnoDB tables, or you have moved .frm files to another database? or, the table contains indexes that this version of the engine doesn't support. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html how you can resolve the problem. 130403 10:53:11 [ERROR] Cannot find or open table zly/review from the internal data dictionary of InnoDB though the .frm file for the table exists. Maybe you have deleted and recreated InnoDB data files but have forgotten to delete the corresponding .frm files of InnoDB tables, or you have moved .frm files to another database? or, the table contains indexes that this version of the engine doesn't support. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html how you can resolve the problem. 130403 10:53:12 [ERROR] Cannot find or open table zly/content from the internal data dictionary of InnoDB though the .frm file for the table exists. Maybe you have deleted and recreated InnoDB data files but have forgotten to delete the corresponding .frm files of InnoDB tables, or you have moved .frm files to another database? or, the table contains indexes that this version of the engine doesn't support. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html how you can resolve the problem. 130403 10:53:14 [ERROR] Cannot find or open table zly/login from the internal data dictionary of InnoDB though the .frm file for the table exists. Maybe you have deleted and recreated InnoDB data files but have forgotten to delete the corresponding .frm files of InnoDB tables, or you have moved .frm files to another database? or, the table contains indexes that this version of the engine doesn't support. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html how you can resolve the problem. 这个是另外个

zly361814478 2013-04-07

打赏
举报

130306 18:08:23 [Note] Giving client threads a chance to die gracefully 130306 18:08:23 [Note] Event Scheduler: Purging the queue. 0 events 130306 18:08:23 [Note] Shutting down slave threads 130306 18:08:23 [Note] Forcefully disconnecting remaining clients 130306 18:08:23 [Note] Binlog end 130306 18:08:23 [Note] Shutting down plugin 'partition' 130306 18:08:23 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA' 130306 18:08:23 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS' 130306 18:08:23 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN' 130306 18:08:23 [Note] Shutting down plugin 'INNODB_SYS_FIELDS' 130306 18:08:23 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS' 130306 18:08:23 [Note] Shutting down plugin 'INNODB_SYS_INDEXES' 130306 18:08:23 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS' 130306 18:08:23 [Note] Shutting down plugin 'INNODB_SYS_TABLES' 130306 18:08:23 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE' 130306 18:08:23 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE' 130306 18:08:23 [Note] Shutting down plugin 'INNODB_FT_CONFIG' 130306 18:08:23 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED' 130306 18:08:23 [Note] Shutting down plugin 'INNODB_FT_DELETED' 130306 18:08:23 [Note] Shutting down plugin 'INNODB_FT_INSERTED' 130306 18:08:23 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD' 130306 18:08:23 [Note] Shutting down plugin 'INNODB_METRICS' 130306 18:08:23 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS' 130306 18:08:23 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU' 130306 18:08:23 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE' 130306 18:08:23 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET' 130306 18:08:23 [Note] Shutting down plugin 'INNODB_CMPMEM' 130306 18:08:23 [Note] Shutting down plugin 'INNODB_CMP_RESET' 130306 18:08:23 [Note] Shutting down plugin 'INNODB_CMP' 130306 18:08:23 [Note] Shutting down plugin 'INNODB_LOCK_WAITS' 130306 18:08:23 [Note] Shutting down plugin 'INNODB_LOCKS' 130306 18:08:23 [Note] Shutting down plugin 'INNODB_TRX' 130306 18:08:23 [Note] Shutting down plugin 'InnoDB' 130306 18:08:23 InnoDB: FTS optimize thread exiting. 130306 18:08:23 InnoDB: Starting shutdown... 130306 18:08:23 InnoDB: Shutdown completed; log sequence number 2483746 130306 18:08:23 [Note] Shutting down plugin 'BLACKHOLE' 130306 18:08:23 [Note] Shutting down plugin 'ARCHIVE' 130306 18:08:23 [Note] Shutting down plugin 'MRG_MYISAM' 130306 18:08:23 [Note] Shutting down plugin 'MyISAM' 130306 18:08:23 [Note] Shutting down plugin 'MEMORY' 130306 18:08:23 [Note] Shutting down plugin 'CSV' 130306 18:08:23 [Note] Shutting down plugin 'mysql_old_password' 130306 18:08:23 [Note] Shutting down plugin 'mysql_native_password' 130306 18:08:23 [Note] Shutting down plugin 'binlog' 130306 18:08:23 [Note] C:\mysql\Sql1\bin\mysqld: Shutdown complete 130306 19:07:29 [Note] Plugin 'FEDERATED' is disabled. 130306 19:07:32 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator. 130306 19:07:32 InnoDB: The InnoDB memory heap is disabled 130306 19:07:32 InnoDB: Mutexes and rw_locks use Windows interlocked functions 130306 19:07:32 InnoDB: Compressed tables use zlib 1.2.3 130306 19:07:32 InnoDB: CPU does not support crc32 instructions 130306 19:07:32 InnoDB: Initializing buffer pool, size = 107.0M 130306 19:07:32 InnoDB: Completed initialization of buffer pool 130306 19:07:32 InnoDB: highest supported file format is Barracuda. 130306 19:07:32 InnoDB: 128 rollback segment(s) are active. 130306 19:07:32 InnoDB: Waiting for the background threads to start 130306 19:07:32 InnoDB: 1.2.5 started; log sequence number 2483746 130306 19:07:32 [Note] Event Scheduler: Loaded 0 events 130306 19:07:32 [Note] C:\mysql\Sql1\bin\mysqld: ready for connections. Version: '5.6.5-m8' socket: '' port: 3306 MySQL Community Server (GPL) 130306 22:36:02 [Note] C:\mysql\Sql1\bin\mysqld: Normal shutdown 130306 22:36:02 [Note] Giving client threads a chance to die gracefully 130306 22:36:02 [Note] Event Scheduler: Purging the queue. 0 events 130306 22:36:02 [Note] Shutting down slave threads 130306 22:36:02 [Note] Forcefully disconnecting remaining clients 130306 22:36:02 [Note] Binlog end 130306 22:36:02 [Note] Shutting down plugin 'partition' 130306 22:36:02 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA' 130306 22:36:02 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS' 130306 22:36:02 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN' 130306 22:36:02 [Note] Shutting down plugin 'INNODB_SYS_FIELDS' 130306 22:36:02 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS' 130306 22:36:02 [Note] Shutting down plugin 'INNODB_SYS_INDEXES' 130306 22:36:02 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS' 130306 22:36:02 [Note] Shutting down plugin 'INNODB_SYS_TABLES' 130306 22:36:02 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE' 130306 22:36:02 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE' 130306 22:36:02 [Note] Shutting down plugin 'INNODB_FT_CONFIG' 130306 22:36:02 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED' 130306 22:36:02 [Note] Shutting down plugin 'INNODB_FT_DELETED' 130306 22:36:02 [Note] Shutting down plugin 'INNODB_FT_INSERTED' 130306 22:36:02 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD' 130306 22:36:02 [Note] Shutting down plugin 'INNODB_METRICS' 130306 22:36:02 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS' 130306 22:36:02 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU' 130306 22:36:02 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE' 130306 22:36:02 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET' 130306 22:36:02 [Note] Shutting down plugin 'INNODB_CMPMEM' 130306 22:36:02 [Note] Shutting down plugin 'INNODB_CMP_RESET' 130306 22:36:02 [Note] Shutting down plugin 'INNODB_CMP' 130306 22:36:02 [Note] Shutting down plugin 'INNODB_LOCK_WAITS' 130306 22:36:02 [Note] Shutting down plugin 'INNODB_LOCKS' 130306 22:36:02 [Note] Shutting down plugin 'INNODB_TRX' 130306 22:36:02 [Note] Shutting down plugin 'InnoDB' 130306 22:36:02 InnoDB: FTS optimize thread exiting. 130306 22:36:02 InnoDB: Starting shutdown... 130306 22:36:03 InnoDB: Shutdown completed; log sequence number 2483756 130306 22:36:03 [Note] Shutting down plugin 'BLACKHOLE' 130306 22:36:03 [Note] Shutting down plugin 'ARCHIVE' 130306 22:36:03 [Note] Shutting down plugin 'MRG_MYISAM' 130306 22:36:03 [Note] Shutting down plugin 'MyISAM' 130306 22:36:03 [Note] Shutting down plugin 'MEMORY' 130306 22:36:03 [Note] Shutting down plugin 'CSV' 130306 22:36:03 [Note] Shutting down plugin 'mysql_old_password' 130306 22:36:03 [Note] Shutting down plugin 'mysql_native_password' 130306 22:36:03 [Note] Shutting down plugin 'binlog' 130306 22:36:03 [Note] C:\mysql\Sql1\bin\mysqld: Shutdown complete

WWWWA 2013-04-07

打赏
举报

把pc_zly.err 文件的内容贴出来看看

zly361814478 2013-04-07

打赏
举报

引用 16 楼 k_scott 的回复:

删除前，先备份。你试试，如果不行。你看看PC_ZLY.err中的错误日志是什么。贴出来。你目前的问题是这样吧：你copy了mysql的数据文件目录。重新安装了mysql。所以你的数据就存在你copy出来的那个目录了。你在有mysqldump已经完了。数据库都没了。用毛啊。你现在就试着恢复。备份一定要做好。如果不行。我在自己在我本地做一个实验……

差不多就你说的这个问题，这个pc_zly.err 文件也不太懂~~ ，急需解决，十分感谢！

十年彩虹 2013-04-07

打赏
举报

你之前卸载的mysql版本是几。现在重新安装的是几。 http://blog.csdn.net/xiangliangyu2008/article/details/8450765

十年彩虹 2013-04-06

打赏
举报

删除前，先备份。你试试，如果不行。你看看PC_ZLY.err中的错误日志是什么。贴出来。你目前的问题是这样吧：你copy了mysql的数据文件目录。重新安装了mysql。所以你的数据就存在你copy出来的那个目录了。你在有mysqldump已经完了。数据库都没了。用毛啊。你现在就试着恢复。备份一定要做好。如果不行。我在自己在我本地做一个实验看看什么文件需要改。 LZ这种COPY是可以的。

十年彩虹 2013-04-06

打赏
举报

用mysqldump导出来多好啊。

你把innodb的那个log删除后试试。

WWWWA 2013-04-03

打赏
举报

问题是我复制的时候没有停掉mysql呢。数据有可能出问题

zly361814478 2013-04-03

打赏
举报

引用 5 楼 rucypli 的回复:

复制出来data目录是可以的但是必须先停止数据库服务

问题是我复制的时候没有停掉mysql呢。

zly361814478 2013-04-03

打赏
举报

引用 12 楼 WWWWA 的回复:

问题是我复制的时候没有停掉mysql呢。数据有可能出问题

是啊，所以现在不知道如何弄，这是我毕业设计的数据库啊~~ 里面好多张表的结构我都忘记了·

kk_lucky 2013-03-29

打赏
举报

用navicat客户端就可以，试过很多次

Neptune_yin 2013-03-29

打赏
举报

mysqldump -uroot -proot --databases design >d:/design.sql

引用 8 楼 zly361814478 的回复:

引用 1 楼 wwwwb 的回复:是表中的数据？除非是MYISAM的，可以直接COPY，否则用MYSQLDUMP备份再导入有没简单的方法呢，我也不知道我是什么结构

用mysqldump肯定比直接复制要简单啊。。先备份：>mysqldump -uroot -ppasswd --databases zly >d:/zly.sql 然后恢复：>mysql -uroot -ppasswd < d:/zly.sql 就两个命令，很容易

rucypli 2013-03-26

打赏
举报

复制出来data目录是可以的但是必须先停止数据库服务

Rotel-刘志东 2013-03-26

打赏
举报

myisam可以直接的复制就可以了。否则mysqldump备份。

Neptune_yin 2013-03-26

打赏
举报

如果表不多且复制的表是MyISAM表的话，那么在数据库中建立同名的同引擎的表，在关闭服务器，把你之前复制的.frm文件复制进去，覆盖掉你刚刚建。如果是InnoDB表的话，除了复制了.frm文件还要把InnoDB的各种表空间文件复制进去，

ACMAIN_CHM 2013-03-26

打赏
举报

表中的结构定义是存放在FRM文件，而数据如果你不骨看MYD文件则是存放在上层目录的ibdata1中。

wwwwb 2013-03-26

打赏
举报

是表中的数据？除非是MYISAM的，可以直接COPY，否则用MYSQLDUMP备份再导入

zly361814478 2013-03-26

打赏
举报

引用 1 楼 wwwwb 的回复:

是表中的数据？除非是MYISAM的，可以直接COPY，否则用MYSQLDUMP备份再导入

有没简单的方法呢，我也不知道我是什么结构

加载更多回复（2）

数据库的导入问题

相关推荐