如何解决MySQL启动时InnoDB引擎被禁用的问题

这篇文章主要介绍如何解决MySQL启动时InnoDB引擎被禁用的问题，文中介绍的非常详细，具有一定的参考价值，感兴趣的小伙伴们一定要看完！

发现问题

今天在工作中，从本地数据库复制表数据到虚拟机 CentOS 6.6 上的数据库时，得到提示：

Unknown table engine 'InnoDB'

于是在服务器 MySQL 中查看了引擎：

mysql> show engines\G

得到：

*************************** 1. row ***************************
  Engine: MyISAM
  Support: DEFAULT
  Comment: MyISAM storage engine
Transactions: NO
   XA: NO
 Savepoints: NO
*************************** 2. row ***************************
  Engine: CSV
  Support: YES
  Comment: CSV storage engine
Transactions: NO
   XA: NO
 Savepoints: NO
*************************** 3. row ***************************
  Engine: MEMORY
  Support: YES
  Comment: Hash based, stored in memory, useful for temporary tables
Transactions: NO
   XA: NO
 Savepoints: NO
*************************** 4. row ***************************
  Engine: BLACKHOLE
  Support: YES
  Comment: /dev/null storage engine (anything you write to it disappears)
Transactions: NO
   XA: NO
 Savepoints: NO
*************************** 5. row ***************************
  Engine: MRG_MYISAM
  Support: YES
  Comment: Collection of identical MyISAM tables
Transactions: NO
   XA: NO
 Savepoints: NO
*************************** 6. row ***************************
  Engine: PERFORMANCE_SCHEMA
  Support: YES
  Comment: Performance Schema
Transactions: NO
   XA: NO
 Savepoints: NO
*************************** 7. row ***************************
  Engine: ARCHIVE
  Support: YES
  Comment: Archive storage engine
Transactions: NO
   XA: NO
 Savepoints: NO
*************************** 8. row ***************************
  Engine: FEDERATED
  Support: NO
  Comment: Federated MySQL storage engine
Transactions: NULL
   XA: NULL
 Savepoints: NULL
*************************** 9. row ***************************
  Engine: InnoDB
  Support: NO
  Comment: Supports transactions, row-level locking, and foreign keys
Transactions: NULL
   XA: NULL
 Savepoints: NULL
rows in set (0.00 sec)

在 InnoDB 的 Supports 为 NO

解决方法

编辑 my.cnf

[root@localhost mysql]# vim /etc/my.cnf

把其中 innodb = OFF 改为 innodb = ON

同时把 skip-innodb 注释掉即可。

以上是如何解决MySQL启动时InnoDB引擎被禁用的问题的所有内容，感谢各位的阅读！希望分享的内容对大家有帮助，更多相关知识，欢迎关注行业资讯频道！

如何解决MySQL启动时InnoDB引擎被禁用的问题

相关推荐