Tables 5. On the source instance, use  UNLOCK TABLES  to release the locks acquired by  FLUSH TABLES ... FOR EXPORT : 6. On the destination instance, import table partitions  p2  and  p3 : mysql>  USE test; mysql>  UNLOCK TABLES; mysql>  USE test; mysql>  ALTER TABLE t1 IMPORT PARTITION p2, p3 TABLESPACE; Note When  ALTER TABLE ... IMPORT PARTITION ... TABLESPACE  is run on subpartitioned tables, both partition and subpartition table names are permitted. When a partition name is specified, subpartitions of that partition are included in the operation. Limitations •The  Transportable Tablespaces  feature is only supported for tables that reside in file-per-table tablespaces. It is not supported for the tables that reside in the system tablespace or general tablespaces. Tables in shared tablespaces cannot be quiesced. • FLUSH TABLES ... FOR EXPORT  is not supported on tables with a  FULLTEXT  index, as full-text search auxiliary tables cannot be flushed. After importing a table with a  FULLTEXT  index, run  OPTIMIZE TABLE  to rebuild the  FULLTEXT  indexes. Alternatively, drop  FULLTEXT  indexes before the export operation and recreate the indexes after importing the table on the destination instance. •Due to a  .cfg  metadata file limitation, schema mismatches are not reported for partition type or partition definition differences when importing a partitioned table. Column differences are reported. •Prior to MySQL 8.0.19, index key part sort order information is not stored to the  .cfg  metadata file used during a tablespace import operation. The index key part sort order is therefore assumed to be ascending, which is the default. As a result, records could be sorted in an unintended order if one table involved in the import operation is defined with a DESC index key part sort order and the other table is not. The workaround is to drop and recreate affected indexes. For information about index key part sort order, see Section 13.1.15, “CREATE INDEX Statement” . The  .cfg  file format was updated in MySQL 8.0.19 to include index key part sort order information. The issue described above does not affect import operations between MySQL 8.0.19 server instances or higher. Usage Notes • ALTER TABLE ... IMPORT TABLESPACE  does not require a  .cfg  metadata file to import a table. However, metadata checks are not performed when importing without a  .cfg  file, and a warning similar to the following is issued: •On Windows,  InnoDB  stores database, tablespace, and table names internally in lowercase. To avoid import problems on case-sensitive operating systems such as Linux and Unix, create all databases, Importing a table without a  .cfg  metadata file should only be considered if no schema mismatches are expected. The ability to import without a  .cfg  file could be useful in crash recovery scenarios where metadata is not accessible. Message: InnoDB: IO Read error: (2, No such file or directory) Error opening ’.\ test	.cfg’, will attempt to import without schema verification 1 row in set (0.00 sec) 3025