Database repair is not a general fix for connection errors or slow queries. Start with the exact database error and identify the affected table and storage engine.
Before doing anything
- Download a current backup if the database is readable.
- Keep any known-good backup separate from the damaged data.
- Record the error and table name. Contact ArkHost if corruption is suspected and you are unsure how to proceed.
Repair only supported tables
DirectAdmin or phpMyAdmin may offer a repair operation. Its behavior depends on the database engine. MySQL's REPAIR TABLE supports engines such as MyISAM, but it does not repair InnoDB tables.
For a supported table, use the repair option only after taking a backup and confirming that it is appropriate. Read the full result and test the application afterward.
If repair fails
Stop and contact support with the exact result. Do not drop and recreate the table as a troubleshooting step: that deletes its data. OPTIMIZE TABLE is not a substitute for a recovery plan. InnoDB corruption needs a different investigation and may require restoring a known-good backup.
