Details
-
Bug
-
Status: Closed (View Workflow)
-
Blocker
-
Resolution: Fixed
-
10.2.6, 10.2(EOL)
-
None
-
centos 7.3
Description
2 types of errors on mysql_upgrade from 10.1.23 to 10.2.6
1/
jbm.conf_client_settings
Error : Function or expression 'AUTO_INCREMENT' cannot be used in the UNTYPED clause of `pk`
error : Corrupt
2/
jbm_adobe_campaign.bl_kpi_demo
Error : Table 'jbm_adobe_campaign.bl_kpi_demo' doesn't exist in engine
status : Operation failed
tail -100 /var/log/mysql_errors.log 2017-05-27 20:51:04 139656884177152 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2017-05-27 20:51:04 139656884177152 [Note] Plugin 'FEEDBACK' is disabled.
2017-05-27 20:51:04 139656884177152 [ERROR] Unknown/unsupported storage engine: InnoDB
2017-05-27 20:51:04 139656884177152 [ERROR] Aborting
Attachments
Issue Links
- causes
-
MDEV-29203 Incorrect information in file: ... #sql-alter ... .frm on ALTER when adding unique hash index, ERROR 1901
- Closed
- relates to
-
MDEV-13320 virtual columns fail when expression references auto increment column
- Closed
-
MDEV-17199 Assertion `pos < table->n_v_def' failed in dict_table_get_nth_v_col after upgrade from 10.1/10.0 to 10.2
- Closed
-
MDEV-22759 Failing assertion: !cursor->index->is_committed() upon update on table with HASH index
- Closed