MySQL啟動時InnoDB引擎被禁用了的解決方法

2024-07-24 13:14:10

字體：大中小

來源：轉載

供稿：網友

發現問題

今天在工作中，從本地數據庫復制表數據到虛擬機 CentOS 6.6 上的數據庫時，得到提示：

Unknown table engine 'InnoDB'

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

mysql/1437.html">mysql> show engines/G

得到：

*************************** 1. row ***************************  Engine: MyISAM  Support: DEFAULT  Comment: MyISAM storage engineTransactions: NO   XA: NO Savepoints: NO*************************** 2. row ***************************  Engine: CSV  Support: YES  Comment: CSV storage engineTransactions: NO   XA: NO Savepoints: NO*************************** 3. row ***************************  Engine: MEMORY  Support: YES  Comment: Hash based, stored in memory, useful for temporary tablesTransactions: 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 tablesTransactions: NO   XA: NO Savepoints: NO*************************** 6. row ***************************  Engine: PERFORMANCE_SCHEMA  Support: YES  Comment: Performance SchemaTransactions: NO   XA: NO Savepoints: NO*************************** 7. row ***************************  Engine: ARCHIVE  Support: YES  Comment: Archive storage engineTransactions: NO   XA: NO Savepoints: NO*************************** 8. row ***************************  Engine: FEDERATED  Support: NO  Comment: Federated MySQL storage engineTransactions: NULL   XA: NULL Savepoints: NULL*************************** 9. row ***************************  Engine: InnoDB  Support: NO  Comment: Supports transactions, row-level locking, and foreign keysTransactions: NULL   XA: NULL Savepoints: NULLrows in set (0.00 sec)

在 InnoDB 的 Supports 為 NO

解決方法

編輯 my.cnf