Database Repair

It is highly recommended that you restrict access to your website while repairing the database. The following example restricts your Magento instance to your IP address exclusively. Other visitors, including search spiders, will get the HTTP “503 Service Unavailable” error.

Step 2: Create a Rewrite Rule

1. Create a file called 503.php in your Magento installation root that contains the following code:

<?php

header('HTTP/1.1 503 Service Unavailable');

header('Content-Type: text/plain; charset=UTF-8');

echo "503 Service Unavailable";

2. In .htaccess or in Apache server configuration, add the following rewrite rule. Replace the IP address xxx\.x\.x\.x (xxx.x.x.x) with your own IP address. (Be careful to preserve the backslash and dot between the numbers.

If running in a cluster environment, uncomment the FileETag line. To learn more, see: Configure ETags.

#FileETag none

RewriteEngine On

RewriteCond %(REMOTE_ADDR) !^xxx\.x\.x\.x$

RewriteRule !503.php /503.php L

3. Save the .htaccess file or reload the Apache configuration. Your site will be down until the end of the process when you restore its original state.

Step 3. Install the DB Repair Tool

1.

Download the archived Magento Database Repair tool from the Magento Community Edition download page.

Database Repair Tool Download

2.

Do either of the following:

Upload the archived file to your server, and extract it to any folder.
Extract the archive. Then, upload the file, magento-db-repair-tool-1.2.php to any folder on your server.

Step 4: Back Up and Clone Your Database

1.

Back up your existing database that has the problem, so it can be restored in the event of a problem. We’ll call it “database1.”

2.

Clone “database1” as the new “database2” on the same server.

3.

Create a new empty database, “database3.”

4.

Do one of the following:

Copy the entire Magento folder (without the cache and sessions) to a new location, and install “database3.” Then, update the local.xml file with the database credentials.
Since access to the site is restricted, you can update the database credentials to “database3” for the current Magento instance. Then, clean the cache and launch Magento. The new database will be installed automatically.

You now have “database2,” which is a clone of your original database, and a Magento installation with the empty “database3.”

Step 5: Run DB Repair

1.

Enter the following in the address bar of your browser to launch the DB Repair tool:

                                            http://[your-domain]/[path-to-folder]/magento-db-repair-tool-1.2.php

2.

Under Corrupted Database Connection, complete the following information for “database2:” This information is the same as what is entered during the Configuration step of the Magento Setup.

a.

In the Host field, enter the server's fully qualified host name or IP address. If your database server is on the same host as your web server, enter “localhost.”

b.

Enter the following credentials for the MySQL database that has the problem:

Database Name
User Name
User Password

c.

If there are multiple instances of Magento that share the same database, enter the Table Prefix.

3.

Under Reference Database Connection, enter the database credentials for the empty “database3.”

If using a Table Prefix, make sure that it is the same as the the prefix used for Database1.

4.

Click Continue to diagnose the database and display the results.

Step 6: Examine the Results

Examine the results to see the changes that were made. If nothing was changed, there is no need to fix the database.

Minor Changes

If only the table charset changed, there is usually nothing to do—especially if the table contains no text data.

Major Issues

If the table engine changed from MyIsam to InnoDb, you will need the help of a developer to investigate and resolve the problem.
If a missing foreign key, field, or table was added, you will need the help of a developer to investigate and resolve the problem.

Step 7: Perform the Repair

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

Step 8: A Little Housekeeping

1. Remove the Database Repair file, magento-db-repair-tool-1.2.php from your server.

2.

Restore access to your website.