|
|
本帖最后由 hspvm 于 2017-5-5 11:07 编辑
如图,服务器重启后服务(MySQL5_OA,Office_Task)无法启动(之前重启是正常的),如图,急救,急救
2017-05-05 09:50:29 4640 [Note] Plugin 'FEDERATED' is disabled.
2017-05-05 09:50:29 4640 [Note] InnoDB: Using atomics to ref count buffer pool pages
2017-05-05 09:50:29 4640 [Note] InnoDB: The InnoDB memory heap is disabled
2017-05-05 09:50:29 4640 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-05-05 09:50:29 4640 [Note] InnoDB: Memory barrier is not used
2017-05-05 09:50:29 4640 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-05-05 09:50:29 4640 [Note] InnoDB: Not using CPU crc32 instructions
2017-05-05 09:50:29 4640 [Note] InnoDB: Initializing buffer pool, size = 1.0G
2017-05-05 09:50:29 4640 [Note] InnoDB: Completed initialization of buffer pool
2017-05-05 09:50:29 4640 [Note] InnoDB: Highest supported file format is Barracuda.
2017-05-05 09:50:29 4640 [Note] InnoDB: The log sequence numbers 10392087739 and 10392087739 in ibdata files do not match the log sequence number 11248437810 in the ib_logfiles!
2017-05-05 09:50:29 4640 [Note] InnoDB: Database was not shutdown normally!
2017-05-05 09:50:29 4640 [Note] InnoDB: Starting crash recovery.
2017-05-05 09:50:29 4640 [Note] InnoDB: Reading tablespace information from the .ibd files...
2017-05-05 09:50:29 4640 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace crscell/crs_board uses space ID: 904 at filepath: .\crscell\crs_board.ibd. Cannot open tablespace td_oa/attendance_overtime which uses space ID: 904 at filepath: .\td_oa\attendance_overtime.ibd
InnoDB: Error: could not open single-table tablespace file .\td_oa\attendance_overtime.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.
|
-
-
|
发表于 2017-5-5 10:22:05