Warning! Before running repair tool on a production environment, make sure you have tested it before on a backup.

Also, it is highly encouraged to restrict access to your website while repairing database. Here is an example of restricting your Magento instance to your IP address exclusively. Other visitors, including search spiders, will get the HTTP 503 Service Unavailable error.

Enter access credentials to “database2” as “corrupted” database and to “database3” as “reference” database

Set table prefixes, if applicable

Press “Continue” and you’ll see result screen where you’ll see what was done to “corrupted” database.

What does the report mean:

if nothing was changed, then there is no need to fix your database

only table charset was changed — usually no need to worry about it, especially if these tables don’t tave text data

table engine was changed from MyIsam to InnoDb — major issue. Needs developer for investigation

added missing foreign key or field (or even a table!) — major/fatal issue. Ask a developer for help.

Eventually, if you are satisified with database repair report and need to fix your live database, you can either switch your installation to the “database2” (because it was repaired), or to perform repair directly on live database.

Don’t forget to remove the tools/db/Repairdb.php and restore access to website when you finish.