> For the complete documentation index, see [llms.txt](https://mariadb.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mariadb.com/docs/server/reference/error-codes/mariadb-error-codes-1900-to-1999/e1932.md).

# Error 1932: Table doesn't exist in engine

| Error Code | SQLSTATE | Error                           | Description                                     |
| ---------- | -------- | ------------------------------- | ----------------------------------------------- |
| 1932       | 42S02    | ER\_NO\_SUCH\_TABLE\_IN\_ENGINE | Table '%-.192s.%-.192s' doesn't exist in engine |

## Possible Causes and Solutions

The server has a definition of the table, in the table's `.frm` file, but the storage engine doesn't know the table. The table is listed by `SHOW TABLES`, but every statement that opens it fails:

```
SELECT * FROM ghost;
ERROR 1932 (42S02): Table 'shop.ghost' doesn't exist in engine
```

With InnoDB, this usually means that the `.frm` file, or the `.frm` and `.ibd` files, were copied into the data directory by hand, for example from another server or from a backup. InnoDB knows only the tables in its data dictionary, so it can't use copied files without an import.

To solve the error:

* If the table isn't needed, remove it with [DROP TABLE](/docs/server/server-usage/tables/drop-table.md). This removes the leftover `.frm` file.
* If you have the table's `.frm`, `.ibd` and `.cfg` files from [FLUSH TABLES … FOR EXPORT](/docs/server/reference/sql-statements/administrative-sql-statements/flush-commands/flush-tables-for-export.md), import the table with `ALTER TABLE … IMPORT TABLESPACE`. From MariaDB 11.2, this works directly on the copied files. In older versions, first create an empty table with the same definition and run `ALTER TABLE … DISCARD TABLESPACE`, then copy the `.ibd` and `.cfg` files and import them. See [Copying Transportable Tablespaces](/docs/server/server-usage/storage-engines/innodb/innodb-tablespaces/innodb-file-per-table-tablespaces.md#copying-transportable-tablespaces).
* If you copied a whole data directory, copy it again with the server stopped, including the InnoDB system tablespace and log files, or restore it from a backup made with [mariadb-backup](/docs/server/server-usage/backup-and-restore/mariadb-backup.md).

A table whose `.ibd` file is missing gives a different error: [error 1030](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1030.md) with `Got error 194 "Tablespace is missing for a table" from storage engine InnoDB`. A table without a `.frm` file gives [error 1146](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1146.md). See also [InnoDB Data Dictionary Troubleshooting](/docs/server/server-usage/storage-engines/innodb/innodb-troubleshooting/innodb-data-dictionary-troubleshooting.md).

<sub>*This page is licensed: CC BY-SA / Gnu FDL*</sub>

{% @marketo/form formId="4316" %}