以前一直没问题..突然提示:
Can't connect to MySQL server on 'localhost' (10061)
服务再也启动不了了
把my.ini里的datadir换了一个地址可用....但是怎么把以前位置的数据库转移过来?
貌似问题在ibdeta1这个文件上。。一指向原来的就不行....
Can't connect to MySQL server on 'localhost' (10061)
服务再也启动不了了
把my.ini里的datadir换了一个地址可用....但是怎么把以前位置的数据库转移过来?
貌似问题在ibdeta1这个文件上。。一指向原来的就不行....
解决方案 »
- Mysql导入sql文件,out of memory问题
- 有谁知道mysql的jdbc源代码研究社区?
- MySQL的MySQL Administrator是如何实现备份、恢复的?
- mysql 无法启动 启动服务报错
- 靠!中招了,EMS PgManager只能自动生成select语句,现在老板要我找个可以像access那样,支持拖放,不但可以是select,还可以生成insert,d
- 100分解决一个网站移植的问题(来者有分)
- 多对多关系中间表问题
- 请教一个SQL查询语句。
- mysql数据表优化问题
- MYSQL按时间排序分页问题,求解决!
- 看一下这段SQL哪儿错了?
- MySQL提示1135-Can't create a new thread (errno12)
InnoDB: Error: trying to access tablespace 3085274529 page no. 3837493288,
InnoDB: but the tablespace does not exist or is just being dropped.
120409 23:53:22 InnoDB: The InnoDB memory heap is disabled
120409 23:53:22 InnoDB: Mutexes and rw_locks use Windows interlocked functions
120409 23:53:22 InnoDB: Compressed tables use zlib 1.2.3
120409 23:53:22 InnoDB: Initializing buffer pool, size = 47.0M
120409 23:53:22 InnoDB: Completed initialization of buffer pool
120409 23:53:23 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
120409 23:53:23 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
120409 23:53:24 InnoDB: Error: page 7 log sequence number 2599620
InnoDB: is in the future! Current system log sequence number 2587660.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
120409 23:53:24 InnoDB: Error: page 1 log sequence number 2599809
InnoDB: is in the future! Current system log sequence number 2587660.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
120409 23:53:24 InnoDB: Error: page 11 log sequence number 2606126
InnoDB: is in the future! Current system log sequence number 2587660.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
120409 23:53:24 InnoDB: Error: page 46 log sequence number 2595814
InnoDB: is in the future! Current system log sequence number 2587660.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
120409 23:53:24 InnoDB: Error: page 459 log sequence number 2595814
InnoDB: is in the future! Current system log sequence number 2587660.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
120409 23:53:25 InnoDB: Error: page 194 log sequence number 2587708
InnoDB: is in the future! Current system log sequence number 2587660.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
120409 23:53:25 InnoDB: Error: page 457 log sequence number 2587708
InnoDB: is in the future! Current system log sequence number 2587660.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
120409 23:53:25 InnoDB: Error: page 197 log sequence number 2588333
InnoDB: is in the future! Current system log sequence number 2587660.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
120409 23:53:25 InnoDB: Error: page 425 log sequence number 2588333
InnoDB: is in the future! Current system log sequence number 2587660.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
120409 23:53:25 InnoDB: Error: page 454 log sequence number 2588333
InnoDB: is in the future! Current system log sequence number 2587660.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
120409 23:53:25 InnoDB: Error: page 337 log sequence number 2588751
InnoDB: is in the future! Current system log sequence number 2587660.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
120409 23:53:25 InnoDB: Error: page 334 log sequence number 2589063
InnoDB: is in the future! Current system log sequence number 2587660.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
120409 23:53:25 InnoDB: Error: page 413 log sequence number 2589297
InnoDB: is in the future! Current system log sequence number 2587660.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
120409 23:53:25 InnoDB: Error: page 467 log sequence number 2589515
InnoDB: is in the future! Current system log sequence number 2587660.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
120409 23:53:25 InnoDB: Error: page 507 log sequence number 2589753
InnoDB: is in the future! Current system log sequence number 2587660.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
120409 23:53:25 InnoDB: Error: page 341 log sequence number 2589992
InnoDB: is in the future! Current system log sequence number 2587660.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
120409 23:53:25 InnoDB: Error: page 470 log sequence number 2590246
InnoDB: is in the future! Current system log sequence number 2587660.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
120409 23:53:26 InnoDB: Error: page 416 log sequence number 2590572
InnoDB: is in the future! Current system log sequence number 2587660.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
120409 23:53:26 InnoDB: Error: page 222 log sequence number 2591182
InnoDB: is in the future! Current system log sequence number 2587660.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
120409 23:53:26 InnoDB: Error: page 418 log sequence number 2591182
InnoDB: is in the future! Current system log sequence number 2587660.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
120409 23:53:26 InnoDB: Error: page 508 log sequence number 2591182
InnoDB: is in the future! Current system log sequence number 2587660.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
120409 23:53:26 InnoDB: Error: page 471 log sequence number 2591582
InnoDB: is in the future! Current system log sequence number 2587660.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
120409 23:53:26 InnoDB: Error: page 226 log sequence number 2592176
InnoDB: is in the future! Current system log sequence number 2587660.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
120409 23:53:26 InnoDB: Error: page 422 log sequence number 2592176
InnoDB: is in the future! Current system log sequence number 2587660.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
120409 23:53:26 InnoDB: Error: page 426 log sequence number 2592176
InnoDB: is in the future! Current system log sequence number 2587660.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
120409 23:53:26 InnoDB: Error: page 399 log sequence number 2601032
InnoDB: is in the future! Current system log sequence number 2587660.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
120409 23:53:26 InnoDB: Error: page 344 log sequence number 2602932
InnoDB: is in the future! Current system log sequence number 2587660.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
120409 23:53:26 InnoDB: Error: page 235 log sequence number 2603379
InnoDB: is in the future! Current system log sequence number 2587660.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
120409 23:53:26 InnoDB: Error: page 434 log sequence number 2603379
InnoDB: is in the future! Current system log sequence number 2587660.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
120409 23:53:26 InnoDB: Error: page 493 log sequence number 2603379
InnoDB: is in the future! Current system log sequence number 2587660.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
120409 23:53:26 InnoDB: Error: page 236 log sequence number 2604504
InnoDB: is in the future! Current system log sequence number 2587660.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
120409 23:53:26 InnoDB: Error: page 592 log sequence number 2604504
InnoDB: is in the future! Current system log sequence number 2587660.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
120409 23:53:26 InnoDB: Error: page 237 log sequence number 2606065
InnoDB: is in the future! Current system log sequence number 2587660.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
120409 23:53:26 InnoDB: Error: page 435 log sequence number 2606065
InnoDB: is in the future! Current system log sequence number 2587660.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
120409 23:53:26 InnoDB: Error: page 239 log sequence number 2607999
InnoDB: is in the future! Current system log sequence number 2587660.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
120409 23:53:26 InnoDB: Error: page 367 log sequence number 2607999
InnoDB: is in the future! Current system log sequence number 2587660.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
120409 23:53:27 InnoDB: Error: page 249 log sequence number 2610459
InnoDB: is in the future! Current system log sequence number 2587660.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
120409 23:53:27 InnoDB: Error: page 466 log sequence number 2610459
InnoDB: is in the future! Current system log sequence number 2587660.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
120409 23:53:27 InnoDB: Error: page 272 log sequence number 2612054
InnoDB: is in the future! Current system log sequence number 2587660.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
120409 23:53:27 InnoDB: Error: page 318 log sequence number 2612054
InnoDB: is in the future! Current system log sequence number 2587660.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
120409 23:53:27 InnoDB: Error: page 274 log sequence number 2613709
InnoDB: is in the future! Current system log sequence number 2587660.
[mysqld]
innodb_force_recovery = 4(1-6都试试)
Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files.
看看这个。