你的mysql 服务没有启动成功 在window下用 mysqld --console
在Linux下用 mysqld_safe
在Linux下用 mysqld_safe
解决方案 »
- 一个产品对应多个属性 一条属性一条记录 多个属性和属性值复合检索 请高人指点 在线等！
- 请教日期的mysql查询语法?
- mysql 模糊查询字母却得到汉字的问题
- 用客户端如ODBC访问远程的MySQL,每次都要set names gbk才可以
- 怎样在redhat 9里安装mysql 4.1beta
- 怎样在odbc数据源中定义mysql数据库呢？
- mysql级联查询自定义函数求指点
- 我只改了 js 文件 和jsp 为什么会出现这个错误！！！求大神
- 关于数据库名称是中文的问题
- 时间段查询语句怎么优化，内有详图，麻烦大神解答下
- 在my sql中添加一个字段，用于存放歌曲，用什么类型
- 关于排序的一段select语句，在线等，急。
什么意思啊？wamp里的mysql控制台启用不了···
2014-03-21 13:22:32 2432 [Note] Plugin 'FEDERATED' is disabled.
2014-03-21 13:22:32 2432 [Note] InnoDB: The InnoDB memory heap is disabled
2014-03-21 13:22:32 2432 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-03-21 13:22:32 2432 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-03-21 13:22:32 2432 [Note] InnoDB: Not using CPU crc32 instructions
2014-03-21 13:22:32 2432 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2014-03-21 13:22:32 2432 [Note] InnoDB: Completed initialization of buffer pool
2014-03-21 13:22:32 2432 [Note] InnoDB: Highest supported file format is Barracuda.
2014-03-21 13:22:32 2432 [Note] InnoDB: The log sequence numbers 1674880 and 1674880 in ibdata files do not match the log sequence number 1674890 in the ib_logfiles!
2014-03-21 13:22:32 2432 [Note] InnoDB: Database was not shutdown normally!
2014-03-21 13:22:32 2432 [Note] InnoDB: Starting crash recovery.
2014-03-21 13:22:32 2432 [Note] InnoDB: Reading tablespace information from the .ibd files...
2014-03-21 13:22:32 2432 [ERROR] InnoDB: checksum mismatch in tablespace .\mdsdb\mds_company.ibd (table mdsdb/mds_company)
InnoDB: Error: could not open single-table tablespace file .\mdsdb\mds_company.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.
2014-03-21 13:57:14 3680 [Note] Plugin 'FEDERATED' is disabled.
2014-03-21 13:57:14 3680 [Note] InnoDB: The InnoDB memory heap is disabled
2014-03-21 13:57:14 3680 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-03-21 13:57:14 3680 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-03-21 13:57:14 3680 [Note] InnoDB: Not using CPU crc32 instructions
2014-03-21 13:57:14 3680 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2014-03-21 13:57:14 3680 [Note] InnoDB: Completed initialization of buffer pool
2014-03-21 13:57:14 3680 [Note] InnoDB: Highest supported file format is Barracuda.
2014-03-21 13:57:14 3680 [Note] InnoDB: The log sequence numbers 1674880 and 1674880 in ibdata files do not match the log sequence number 1674890 in the ib_logfiles!
2014-03-21 13:57:14 3680 [Note] InnoDB: Database was not shutdown normally!
2014-03-21 13:57:14 3680 [Note] InnoDB: Starting crash recovery.
2014-03-21 13:57:14 3680 [Note] InnoDB: Reading tablespace information from the .ibd files...
2014-03-21 13:57:14 3680 [ERROR] InnoDB: checksum mismatch in tablespace .\mdsdb\mds_company.ibd (table mdsdb/mds_company)
InnoDB: Error: could not open single-table tablespace file .\mdsdb\mds_company.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.这是错误日志，求解，说的纤细点哈，俺是新手···