Bug #90467 Case sensitive may cause error 1067
Submitted: 17 Apr 2018 8:00 Modified: 2 May 2018 13:10
Reporter: Andrej Thomsen Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: DML Severity:S1 (Critical)
Version:8.0.3 OS:Microsoft Windows (10)
Assigned to: CPU Architecture:Any
Tags: 1067, case, lower_case_table_names, MySQL 8, windows

[17 Apr 2018 8:00] Andrej Thomsen
Description:
When the server crashed during a transaction, the server may not be started again if "lower_case_table_names" was set to "2". If it throws an error 1067 when trying to start the service and fails even with "innodb_force_recovery" set to "3", simply remove the setting "lower_case_table_names". It should start up normally again, then you can add the setting and restart the service again.

How to repeat:
Cause a server-crash during a transaction.

Suggested fix:
It seems like camelcase table names cause a lot of trouble on windows-machines in general.
[17 Apr 2018 12:11] Miguel Solorzano
Please open a command prompt and issue:

mysqld --defaults-file=path_for_my.ini --standalone --console

and print here the error printed by the server to check the reason for the service got 1067 error message. Thanks.
[2 May 2018 13:10] Andrej Thomsen
Deprecated because GA was released