MySQL Bugs: #113359: Unable to import table from .ibd files in mysql database

Bug #113359	Unable to import table from .ibd files in mysql database
Submitted:	7 Dec 2023 7:22	Modified:	12 Dec 2023 4:54
Reporter:	Saroj Mahanta	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	MySQL Enterprise Backup	Severity:	S3 (Non-critical)
Version:	8.0.34 MySQL Community Server - GPL	OS:	Red Hat (EL8)
Assigned to:		CPU Architecture:	x86 (64)

Description:
I am trying to restore/import database from the backups. I have .ibd and .frm files. And also the .sql file with all the table creation script inside it. 
Method followed :
A. Installed a new mysql database. 
B. Created a database with same name as it was there in the source database.
C. From the .sql file i picked one table creation script, run it in the new mysql database. 
D. alter table <tablename> discard tablespace;
E. went to the server and copied the tablename.ibd from the backedup directory to the current mysql data directory , ie /var/lib/mysql/confluence/
F. chown mysql:mysql <tablename>.ibd
G. Went to the mysql prompt and run Alter table <tablename> import tablespace.
H. I get and error, message as below.
ERROR 1808 (HY000): Schema mismatch (Clustered index validation failed. Because the .cfg file is missing, table definition of the IBD file could be different. Or the data file itself is already corrupted.)

i manage to restore some of the ibd files, but some parent tables with more number of columns, unable to restore them. 

Kindly advise.

How to repeat:
We can reproduce by following the above steps in the description section.

Suggested fix:
No idea. Need help.

Please note, the backups are from Mysql community server 5.0.7 version. 
And now i am trying to restore/import the ibd files in the newly installed mysql database version 8.0.34. 

I am able to login to the mysql and manage to import 23+ tables, out of 70 tables in the database, by following the steps mentioned in the description section.

Hi Mr. Mahanta,

Thank you for your bug report.

However, you are mentioning release 5.0.7, which was deprecated 15 (fifteen) years ago.

I guess that you meant 5.7. Importing from 5.7 to 8.0 is not done in the way that you described. That import is done differently and it is fully described in our Reference Manual for 8.0, found on dev.mysql.com.

Last, but not least, you have set that you are using MySQL Enterprise Backup, or MEB. MEB is available only to customer, so if you are a paying customer, you can go to our Support Portal and ask questions.

If you have the output from 5.7 mysqldump, it should be possible to be imported to 8.0, but it might requrie some changes. The necessary changes are also described in our Reference Manual and you should search for the instructions in the Manual.

This forum is intended only for true bugs, with fully repeatable test cases.

Unsupported.

My apology.

The correct mysql version is 5.7

Can you please share the manual reference link here ? 
I am looking for the exact link in the dev.mysql.com website.

Hi Mr. Mahanta,

We would like to inform you that reading our Reference Manual is a pre-requisition for filing the bug reports.

You should read at least the following entire chapters fully, with all sub-chapters:

* https://dev.mysql.com/doc/refman/8.0/en/introduction.html

* https://dev.mysql.com/doc/refman/8.0/en/installing.html

* https://dev.mysql.com/doc/refman/8.0/en/data-dictionary.html

* https://dev.mysql.com/doc/refman/8.0/en/innodb-storage-engine.html

You should also read all the chapters that are mentioned and referenced in the above links.