[Fixed]: MySQL Error #1932: Table Doesn't Exist in Engine

You can use the tables to perform various operations in the MySQL database. For instance, for loading data into the tables or creating relationship by setting the primary and foreign keys. While performing any action on a table, if the MySQL Server fails to access the table, tablespaces, and its metadata, then you may get different errors. For example, MySQL Error #1932: Table Doesn't Exist in Engine. In this in-depth guide, we will look into this error, its occurrence in different scenarios, and how to resolve it.

About MySQL Error #1932: Table Doesn't Exist in Engine

You may encounter the MySQL error 1932: Table doesn’t exist in Engine while working on PhpMyAdmin using XAMPP server or MySQL workbench. Several MySQL users have raised a query related to this error on Stack Overflow. Some of them are:

From the above users queries, it seems that this error can arise in both web-based and standalone desktop applications. This error typically arises in the following scenarios:

• Creating backup using the mysqldump utility or the SQL Data Export and Import Wizard.
• After copying old files to newly installed XAMPP server.
• When modifying the database using the ALTER TABLE command in PhpMyAdmin.
• When trying to retrieve data from the tables in the MySQL database.

What are the Causes of Error 1932 in MySQL Server?

The storage engine may fail to read or access the tables in a database due to any of the following reasons:

• Tables in database are corrupted
• Missing table files (.frm) or InnoDB database files (.ibd files) location differs
• InnoDB tablespace might have been deleted and recreated but the corresponding .frm files of InnoDB tables from the database directory were not removed, or .frm files were moved to another database
• Incorrect permissions and ownership on table's files in MySQL/MariaDB data directory

Methods to Resolve MySQL Error #1932: Table doesn't Exist in Engine

At times, this error occurs if the table you’re trying to access or open doesn’t exist in the data directory. In this scenario, you can check the PhpMyAdmin data directory to see if it exists (see the image below).

If the concerned table is present in the data directory, then you can follow the below troubleshooting methods.

Method 1: Copy the Log Files along with the MySQL Database

You can experience the MySQL Error #1932 after copying the backup of old MySQL database to new XAMPP server. If you’re facing this situation, then a workaround is to copy the following files (starting from ib), along with the database:

Next, restart the XAMPP server.

Method 2: Check and Modify PhpMyAdmin Configuration File

At times, when this error occurs, you can see the name of the PMA table. For example, 1932 - Table 'phpmyadmin.pma__tracking' doesn't exist in engine. It ensues when the XAMPP server (PhpMyAdmin) fails to access the PMA tables where the configuration settings are stored. Incorrect configuration settings and missing or corrupted PMA tables might be reasons behind it. This would also happen if the user-configured for MySQL is password-protected or lacks the necessary permissions. To resolve the issue, follow the steps mentioned below:

• Go to the PhpMyAdmin configuration file. To find this file, open the XAMPP Control Panel. Click on Config option for Apache or MySQL. Select phpMyAdmin (config.inc.php).

• It will display the list of configuration settings.

• In the list, check for the pma-related tables. If they are missing, then recreate them by copying and replacing the following content of config.inc.php:

Also, scroll-down and check for the Authentication type and the info section. Here, check and ensure that the user has all permissions to access the MySQL database. Else, grant the desired permissions.

Method 3: Check and Repair MySQL Tables

Corruption in tables in MySQL database is also one of the major reasons for MySQL Error #1932: Table doesn't Exist in Engine. To verify this, you can run the CHECKTABLE command in the PhpMyAdmin itself. Here are the steps to follow:

• In phpMyAdmin dashboard, click the Databases tab from the main menu. This will open a list of MySQL databases.
• Click database from which you are not able to open table.
• A list of tables will appear, click on the Doctor table and select CHECK TABLE.

In workbench, run the CHECK TABLE command as shown below:

The above image shows that the table named - appointments is corrupt or its tablespace is missing. You can repair MySQL database using PhpMyAdmin. However, it has some limitations, such as:

• It has file size limitations.
• It allows repairing a single database at one time.
• It has limited functionality, such as no schema visualization and auto-compilation options.
• It does not provide a preview of the repairable data.
• Time-out problems when uploading large-sized database files.
• It may not repair InnoDB tables.

To repair InnoDB tables in MySQL, you can use Stellar Repair for MySQL. It is an easy-to-use tool that can repair corrupt MySQL database created in InnoDB and MyISAM storage engines. The tool can even repair large database files without any issues or data loss. It also allows repairing of multiple databases at once. It can help you restore severely corrupt log files, .frm files, and .ibd files. It can help you resolve MySQL Error #1932: Table doesn't Exist in Engine if it occurs due to corruption in MySQL tables.

To know how Stellar Repair for MySQL works, watch this video: