<p>The tablespace for the referenced table has been discarded, making the table inaccessible until it is re-imported.</p>
<p>MySQL Error 1814 ER_TABLESPACE_DISCARDED occurs when a table’s tablespace was removed with ALTER TABLE ... DISCARD TABLESPACE, leaving no .ibd file. Re-enable the table by running ALTER TABLE your_table IMPORT TABLESPACE or recreating the table.</p>
Tablespace has been discarded for table '%s'
The server is telling you that the .ibd file holding the table’s data and indexes has been deliberately removed by executing ALTER TABLE ... DISCARD TABLESPACE. Because the file no longer exists, InnoDB cannot open the table, and any read or write statement fails with this error.
The error appears immediately after the discard operation or later if another session tries to access the table before the tablespace is re-imported. Until the file is restored, the table is logically present in the data dictionary but physically missing on disk.
The error shows up during SELECT, INSERT, UPDATE, DELETE, ALTER TABLE, or any DDL that touches the affected table. It is most common in transportable tablespace workflows, backup-restore pipelines, and mis-configured replication setups where the DISCARD phase ran but IMPORT never followed.
While a tablespace is discarded, the table is completely unusable, breaking application features, ETL jobs, and foreign-key relationships. Leaving the table in this state risks data inconsistency, replication lag, and operational outages. Prompt resolution restores data availability and prevents cascading errors.
An administrator or script issued the DISCARD command to detach the .ibd file for backup, compression, or migration and forgot to import it back.
The server crashed, the session timed out, or permissions blocked the IMPORT step, leaving the table half-migrated and inaccessible.
In replication, the DISCARD event reached the replica but the matching IMPORT event was filtered out, so replicas report the error while the source works fine.
InnoDB cannot open the tablespace file because it is missing or corrupted, similar to but not triggered by DISCARD.
Generic InnoDB storage engine error often returned when file permissions or disk issues block tablespace access.
The table definition itself is missing, unlike 1814 where the definition exists but the storage does not.
No. Until the tablespace is imported or the table is recreated, any query will fail with error 1814.
No. It moves or deletes only the .ibd file. If you still have that file, you can import it and recover all data.
No. The feature is specific to InnoDB. MyISAM and other engines have different transport mechanisms.
Galaxy’s editor logs every DDL statement and flags tables left in a discarded state, helping teams notice and fix the issue quickly.
.avif)
.avif){kind=logo}
