|
|
今天重启后OA的MYSQL就启动不了了，然后备份数据重装，装好后是正常的，结果数据一导入一样报错1067
试
日志错误如下
130329 20:03:20 [Note] Plugin 'FEDERATED' is disabled.
130329 20:03:20 InnoDB: The InnoDB memory heap is disabled
130329 20:03:20 InnoDB: Mutexes and rw_locks use Windows interlocked functions
130329 20:03:20 InnoDB: Compressed tables use zlib 1.2.3
130329 20:03:21 InnoDB: Initializing buffer pool, size = 1021.0M
130329 20:03:21 InnoDB: Completed initialization of buffer pool
130329 20:03:21 InnoDB: highest supported file format is Barracuda.
130329 20:03:26 InnoDB: Waiting for the background threads to start
130329 20:03:27 InnoDB: 1.1.8 started; log sequence number 11975298
130329 20:03:27 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3336
130329 20:03:27 [Note] - '0.0.0.0' resolves to '0.0.0.0';
130329 20:03:27 [Note] Server socket created on IP: '0.0.0.0'.
130329 20:03:27 [Note] Event Scheduler: Loaded 0 events
130329 20:03:27 [Note] D:\MYOA\mysql5\bin\mysqld.exe: ready for connections.
Version: '5.5.25-enterprise-commercial-advanced-log' socket: '' port: 3336 MySQL Enterprise Server - Advanced Edition (Commercial)
InnoDB: Error: tablespace id is 326 in the data dictionary
InnoDB: but in file .\td_oa\sys_para.ibd it is 353!
130329 20:03:27 InnoDB: Assertion failure in thread 3780 in file fil0fil.c line 766
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html
InnoDB: about forcing recovery.
|
|
[复制链接]
发表于 2013-3-29 20:14:17
楼主