Table storage engine for 'table_name' doesn't have that option

Table storage engine for 'table_name' doesn't have that option

October 20, 2026 · Illustrated author avatarBy Stefan Bogdanescu
Table storage engine for 'table_name' doesn't have that option

Solving MySQL Storage Engine Errors on Mac OSX Mavericks

Are you struggling with mysterious storage engine errors when trying to import databases into your MySQL server running on Mac OSX Mavericks? Don’t worry—you’re not alone, and there’s a straightforward solution.

Understanding the Error Message

The error message Table storage engine for 'table_name' doesn't have that option typically occurs due to compatibility issues between your database structure and the specific version of MySQL you’re running. In your case, the upgrade from MySQL 5.5.34 to 5.7.9 has likely introduced this problem.

Identifying the Root Cause

The issue lies in the fact that certain table storage engines used by your existing database may not be supported or have different options in the newer version of MySQL you’re now running (5.7). This incompatibility causes the error during the import process.

Steps to Resolve the Issue

1. Confirm the Storage Engine Type

First, let’s identify the storage engine used for your problematic table. Connect to your database using the MySQL command-line client or phpMyAdmin and execute the following query:

SHOW CREATE TABLE table_name;

Replace table_name with the name of your troubled table. This will reveal the current storage engine type being used.

2. Check Engine Support in MySQL 5.7

Next, we need to verify if the identified engine is still supported or has any option changes in MySQL 5.7. You can use the following command:

SHOW ENGINES;

Scroll down to find your specific engine (e.g., InnoDB, MyISAM, etc.) and check its current support status and available options.

3. Modify the Table Structure

If you determine that the storage engine is no longer supported or has changed significantly in MySQL 5.7, you’ll need to modify your table structure accordingly.

For example, if you’re using the InnoDB engine with MyISAM-style features in MySQL 5.5, you might need to convert the tables to use only InnoDB-compatible options in MySQL 5.7.

4. Use ALTER TABLE to Convert

To convert a table from one storage engine to another compatible type, use the ALTER TABLE command:

ALTER TABLE table_name ENGINE=InnoDB;

Replace table_name with your actual table name and InnoDB with the appropriate target engine supported by MySQL 5.7.

5. Import Your Database

After making necessary adjustments to ensure full compatibility, proceed with importing your database using the original method you were attempting before encountering the error.

Best Practices for Future Imports

To avoid such issues in the future:

  1. Always backup your databases before performing major upgrades or migrations.
  2. Thoroughly test your applications on staging environments running the new version of MySQL before deploying to production.
  3. Keep track of compatibility changes between MySQL versions that may affect your database structure.

Conclusion

In summary, resolving MySQL storage engine errors typically involves:

  • Identifying the problematic table and its current storage engine
  • Checking if the engine is supported or has option changes in the newer version
  • Modifying the table structure to match the new version’s requirements
  • Using the ALTER TABLE command to perform conversions when necessary

By following this systematic approach, you should be able to successfully import your databases into MySQL 5.7 running on Mac OSX Mavericks without encountering storage engine errors.

If you require further assistance or want to explore more advanced MySQL troubleshooting techniques, I recommend checking out the comprehensive guides available at Laravel Company.

Database PHP Deployment Import/Export

Our network