Description:
Hello folks,
In the last couple of days we came across a number of situations where data dictionary failed to complete upgrade; Examples:
1) This one gave us *some* hint (error 197)
2023-08-03T11:54:56.514052Z 1 [ERROR] [MY-011006] [Server] Got error 197 from SE while migrating tablespaces.
2023-08-03T11:54:56.519522Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed.
2023-08-03T11:54:56.519556Z 0 [ERROR] [MY-010119] [Server] Aborting
But doesn't give us a table/tablespace name or path, nor it suggests what can be done.
2) But this other one tell us nothing:
2023-07-23T20:48:07.200669-07:00 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2023-07-23T20:48:09.375511-07:00 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2023-07-23T20:48:09.391646-07:00 1 [System] [MY-011090] [Server] Data dictionary upgrading from version '80016' to '80023'.
2023-07-23T20:48:09.984293-07:00 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed.
I'm opening as S3, as lack of visibility is tremendously annoying and hinders upgrades... but of course, you might decide it's better categorized as Feature Request;
How to repeat:
Uncertain; We believe it could be due to some inconsistency (orphans?) but couldn't find any tmp table or such that was in (for example) innodb_tablespaces but not in innodb_tables or.
Suggested fix:
Increase verbosity:
- Print out to the error log current step of the DD upgrade process
- Print out file path/tablespace name and id causing an errors
- Print out possible suggestions to fix where sensible
