The configured lower_case_table_names value doesn’t match the value recorded in the existing data dictionary.

Products

• VMware Tanzu Data Services

Issue/Introduction

• Mysql service instance failed with the below error message after creating the new mysql service and restoring the backup.

2025-08-22T09:28:51.696202Z 0 [Warning] [MY-010324] [Server] 'db' entry 'percona_schema mysql.pxc.sst.role@localhost' had database in mixed case that has been forced to lowercase because lower_case_table_names is set. It will not be possible to remove this privilege using REVOKE.

2025-08-25T07:00:34.231008Z 1 [ERROR] [MY-011087] [Server] Different lower_case_table_names settings for server ('1') and data dictionary ('0').
2025-08-25T07:00:34.231233Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed.
2025-08-25T07:00:34.231248Z 0 [ERROR] [MY-010119] [Server] Aborting

Cause

lower_case_table_names:

• If set to 0, table names are stored as specified and comparisons are case-sensitive.
• If set to 1, table names are stored in lowercase on disk and comparisons are not case-sensitive.

In this case, the configured lower_case_table_names value does not match the value recorded in the existing data dictionary.

With this mismatch (server = 1 vs dictionary = 0), MySQL startup aborts—causing any restore attempt to fail as well.

Resolution

The lower_case_table_names can only be configured when initializing the server. Changing the lower_case_table_names setting after the server is initialized is prohibited.

The workaround:

• Uncheck 'Enable Lower Case Table Names'
  • MySQL tile - 'Mysql Configuration' tab - 'Enable Lower Case Table Names'
• Recreate the mysql service and restore the backup