返回信息流2013-11-26 10:19:51 - Workbench will use cmd shell commands to start/stop this instance
2013-11-26 10:19:51 - Status check of service 'MySQL57' returned stopped
2013-11-26 10:20:01 - Status check of service 'MySQL57' returned stopped
2013-11-26 10:20:01 - Starting server...
2013-11-26 10:20:09 - Status check of service 'MySQL57' returned stopped
FROM LENOVO-PC.err:
2013-11-26T02:20:08.015174Z 0 [Note] Plugin 'FEDERATED' is disabled.
2013-11-26T02:20:08.015174Z 0 [Warning] option 'innodb-autoextend-increment': unsigned value 67108864 adjusted to 1000
2013-11-26T02:20:08.015174Z 0 [Warning] InnoDB: 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.
2013-11-26T02:20:08.015174Z 0 [Note] InnoDB: The InnoDB memory heap is disabled
2013-11-26T02:20:08.030774Z 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-11-26T02:20:08.030774Z 0 [Note] InnoDB: Uses system mutexes
2013-11-26T02:20:08.030774Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-11-26T02:20:08.030774Z 0 [Warning] InnoDB: Adjusting innodb_buffer_pool_instances from 8 to 1 since innodb_buffer_pool_size is less than 1024 MiB
2013-11-26T02:20:08.030774Z 0 [Note] InnoDB: Number of pools: 1
2013-11-26T02:20:08.030774Z 0 [Note] InnoDB: Not using CPU crc32 instructions
2013-11-26T02:20:08.030774Z 0 [Note] InnoDB: Initializing buffer pool, total size = 77.0M, instances = 1
2013-11-26T02:20:08.030774Z 0 [Note] InnoDB: Completed initialization of buffer pool
2013-11-26T02:20:08.061974Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2013-11-26T02:20:08.077574Z 0 [Note] InnoDB: The log sequence numbers 12783917 and 12783917 in ibdata files do not match the log sequence number 14169296 in the ib_logfiles!
2013-11-26T02:20:08.077574Z 0 [Note] InnoDB: Database was not shutdown normally!
2013-11-26T02:20:08.077574Z 0 [Note] InnoDB: Starting crash recovery.
2013-11-26T02:20:08.077574Z 0 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-11-26T02:20:08.077574Z 0 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace secpcy/crntpcy uses space ID: 37 at filepath: .\secpcy\crntpcy.ibd. Cannot open tablespace spdb1/orders which uses space ID: 37 at filepath: [truncated, 275 bytes total]
InnoDB: Error: could not open single-table tablespace file .\spdb1\orders.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
2013-11-26 10:20:09 - Server start done.
2013-11-26 10:20:09 - Status check of service 'MySQL57' returned stopped
这是一条镜像帖。来源：北邮人论坛 / database / #7885同步于 2013/11/26
Database机器人发帖
Mysql 数据库启动不了了 求大神帮助啊？提示信息如下
z1002574903
2013/11/26镜像同步0 回复
订阅后，新回复会通过你的通知中心匿名送达。
0 条回复
暂无回复 · 你可以订阅本帖等待新回复。