How to Repair Joomla Database Tables

Create a database backup before attempting a repair

Before changing table structures or using database repair tools, create a current database backup. If the site is still accessible, also create a full site backup so the database and filesystem can be recovered together.

Do not continue with destructive repair work if the only copy of important data is the live database. A failed repair, incorrect SQL statement, or storage-engine problem can make recovery harder.

First check whether this is a Joomla schema problem

Joomla includes a database schema check for Joomla core tables. In the Administrator, go to System → Maintenance → Database. Joomla compares the installed schema with the schema expected by the installed Joomla version.

1. Review the database status shown by Joomla.
2. If Joomla reports that the database structure is out of date, use the available Update Structure or repair action.
3. Allow the process to finish, then reload the database screen and confirm that the schema reports as current.
4. Clear Joomla's cache and retest the feature that originally failed.

This process repairs missing Joomla core schema changes. It is not a general corruption-repair tool for arbitrary extension tables or damaged database files.

Check the affected table and its storage engine

If an error names a specific table, inspect that table in your database management tool, such as phpMyAdmin. Confirm the exact table name and storage engine before choosing a repair method.

Modern Joomla installations normally use InnoDB. The SQL command REPAIR TABLE is intended for storage engines that support it, such as MyISAM; it is not a general repair method for InnoDB tables.

You can safely begin with a check:

CHECK TABLE `yourprefix_example_table`;

Replace the example name with the exact affected table. Read the returned status before taking further action.

Repair a MyISAM table only when the table actually uses MyISAM

If the affected table uses MyISAM and the database reports that it is crashed or requires repair, phpMyAdmin's Repair table action or the SQL command below can be appropriate:

REPAIR TABLE `yourprefix_example_table`;

Run the repair only against the confirmed affected table. When it finishes, run CHECK TABLE again and retest Joomla.

If the table is InnoDB, do not convert it to MyISAM simply so that REPAIR TABLE can be used. InnoDB recovery is handled differently and may require restoring the table/database, correcting server storage problems, or working with the hosting provider/database administrator.

If the problem belongs to an extension table

Joomla's core database repair screen does not know the intended schema of every third-party extension. If an extension table is missing or has the wrong columns, compare the installed extension version with its installation/update SQL or reinstall/update the extension using the developer's supported procedure.

• Do not copy a table structure from a different extension version without confirming compatibility.
• Do not delete and reinstall an extension if uninstalling it would remove data you need.
• Check the extension's own database migration or repair tools when available.

If the error began immediately after a failed extension update, the most useful evidence is often the exact SQL/database error and the extension's current version.

Verify the repair and investigate the cause

After the repair, repeat the action that previously failed and review Joomla, PHP, and database logs. A table that becomes corrupt again can indicate a server, filesystem, storage, memory, or database-service problem rather than a Joomla problem.

For repeated InnoDB corruption, database service crashes, failed recovery, or multiple damaged tables, stop making ad-hoc changes and involve the hosting provider or database administrator. Restore from a known-good backup if that is safer than attempting further repair.