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 complete130306 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 shutdown130306 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
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.这个是另外个
除非是MYISAM的,可以直接COPY,否则用MYSQLDUMP备份再导入
我就想把这里面zly 这个数据库弄到我现在的mysql里面来。 光复制zly这个目录进来是不行的,识别不出来。
zly目录里面全是。frm文件
用mysqldump肯定比直接复制要简单啊。。
先备份:>mysqldump -uroot -ppasswd --databases zly >d:/zly.sql
然后恢复:>mysql -uroot -ppasswd < d:/zly.sql
就两个命令,很容易
你copy了mysql的数据文件目录。重新安装了mysql。所以你的数据就存在你copy出来的那个目录了。你在有mysqldump已经完了。数据库都没了。用毛啊。你现在就试着恢复。备份一定要做好。
如果不行。我在自己在我本地做一个实验看看什么文件需要改。LZ这种COPY是可以的。
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 complete130306 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 shutdown130306 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
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.这个是另外个
http://blog.csdn.net/xiangliangyu2008/article/details/8450765
之前卸载的mysql 不知道 是哪个版本了 不知道是5.5 还是5.6 现在又全部被我重新卸载了