MySQL - решение ошибки после обновления 5.1 до 5.6 версии - InnoDB: auto-extending data file ./ibdata1 is of a different size 640 pages (rounded down to MB)

Материал из Wiki - Iphoster - the best ever hosting and support. 2005 - 2023
Версия от 11:37, 30 марта 2020; Admin iph (обсуждение | вклад)
(разн.) ← Предыдущая | Текущая версия (разн.) | Следующая → (разн.)
Перейти к:навигация, поиск

Доступная цена


MySQL - решение ошибки после обновления 5.1 до 5.6 версии - InnoDB: auto-extending data file ./ibdata1 is of a different size 640 pages (rounded down to MB)

После обновления версии mysql с 5.1 до 5.6 - вылезла ошибка вида:

2017-09-30 11:13:54 23818 [ERROR] InnoDB: auto-extending data file ./ibdata1 is of a different size 640 pages (rounded down to MB) than specified in the .cnf file: initial 768 pages, max 0 (relevant if non-zero) pages!
2017-09-30 11:13:54 23818 [ERROR] InnoDB: Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data!
2017-09-30 11:13:54 23818 [ERROR] Plugin 'InnoDB' init function returned error.
2017-09-30 11:13:54 23818 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2017-09-30 11:13:54 23818 [ERROR] Unknown/unsupported storage engine: InnoDB
2017-09-30 11:13:54 23818 [ERROR] Aborting


решение:

# vi /etc/my.cnf
[mysqld]
innodb_data_file_path = ibdata1:10M:autoextend

Перезапускаем mysql сервер:

# /etc/init.d/mysqld restart