Details
-
New Feature
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
None
Description
MariaDB does not support migration from MySQL-generated physical database tables containing virtual columns, and produces column mismatch errors, failures in mysql_upgrade, and InnoDB data dictionary inconsistencies where the tablename appears in "show tables;" but when selected produces error 1932.
2021-01-04 12:00:30 6 [Warning] InnoDB: Table test/REDACTED contains 11 user defined columns in InnoDB, but 10 columns in MariaDB. Please check INFORMATION_SCHEMA.INNODB_SYS_COLUMNS and https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue.
|
2021-01-04 12:00:30 6 [ERROR] mariadbd: Table 'REDACTED' is marked as crashed and should be repaired
|
2021-01-04 12:00:30 6 [ERROR] InnoDB: Table `test`.`REDACTED` is corrupted. Please drop the table and recreate.
|
mysql_upgrade:
test.REDACTED
|
Error : Table 'REDACTED' is marked as crashed and should be repaired
|
error : Corrupt
|
MariaDB [test]> show tables;
|
+----------------+
|
| Tables_in_test |
|
+----------------+
|
| Customers |
|
| REDACTED |
|
| simple |
|
| vw_simple |
|
+----------------+
|
4 rows in set (0.000 sec)
|
 |
MariaDB [test]> select * from REDACTED;
|
ERROR 1932 (42S02): Table 'test.REDACTED' doesn't exist in engine
|
It would be very helpful for administrators if they could see a message when these errors happen letting them know that InnoDB has encountered an incompatible and unsupported table type, and recommend starting over with the corrupted tabled dumped logically and then dropped from the source.