Briefly. When we create table it's dictionary contains the description of indexes in the certain order. In the case if we import tablespace for the table without cfg file(which contains metadata for indexes as well), there can be the case when the order of indexes in innodb dictionary (in .frm file as well) is not the same as the order of root pages for the indexes in tablespace file what cause the error during tablespace import or when the indexes are used.
Briefly. When we create table it's dictionary contains the description of indexes in the certain order. In the case if we import tablespace for the table without cfg file(which contains metadata for indexes as well), there can be the case when the order of indexes in innodb dictionary (in .frm file as well) is not the same as the order of root pages for the indexes in tablespace file what cause the error during tablespace import or when the indexes are used.
The detailed description is here https:/ /percona. zendesk. com/attachments /token/ EzERiNDmk8a1gJj tQMhPfA7Dv/ ?name=descr. txt .