Solution to the problem that the InnoDB engine is disabled when MySQL is started

Find the problem

Today at work, when copying table data from a local database to a database on a virtual machine CentOS 6.6, I got the prompt:

Unknown table engine 'InnoDB'

So I checked the engine in the server MySQL:

mysql> show engines\G

get:

*************************** 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)

When InnoDB Support is set to NO

Workaround

Edit my.cnf

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

Change innodb = OFF to innodb = ON

At the same time, just comment out skip-innodb .

Summarize

The above is the full content of this article. I hope that the content of this article can bring some help to your study or work. If you have any questions, you can leave a message to communicate. Thank you for your support of 123WORDPRESS.COM.

You may also be interested in:

InnoDB type MySql restore table structure and data
mysql executes sql file and reports error Error: Unknown storage engine'InnoDB' solution
Sharing of experience on repairing MySQL innodb exceptions
MySQL InnoDB monitoring (system layer, database layer)
Summary of the operation records of changing MyISAM storage engine to Innodb in MySQL
About MySQL innodb_autoinc_lock_mode
MySQL Optimization: InnoDB Optimization
Detailed explanation of the difference between MyISAM and InnoDB in MySQL storage engine
MySQL prompts that the InnoDB feature is disabled and needs to enable InnoDB. Solution
Tutorial on the relationship between Innodb transaction isolation level and lock in MySQL
Detailed explanation of InnoDB storage files in MySQL

<<: JavaScript implements circular carousel

>>: How to Set Shortcut Icons in Linux