[23-Mar-2024 11:34:42 UTC] PHP Fatal error: Trait 'AAM_Core_Contract_RequestTrait' not found in /home/xhtmljunkies/public_html/wp-content/plugins/advanced-access-manager/application/Service/Uri.php on line 24 [23-Mar-2024 17:22:13 UTC] PHP Fatal error: Trait 'AAM_Core_Contract_RequestTrait' not found in /home/xhtmljunkies/public_html/wp-content/plugins/advanced-access-manager/application/Service/Toolbar.php on line 22 [26-Mar-2024 13:29:00 UTC] PHP Fatal error: Trait 'AAM_Core_Contract_ServiceTrait' not found in /home/xhtmljunkies/public_html/wp-content/plugins/advanced-access-manager/application/Service/Shortcode.php on line 19 [07-Apr-2024 20:50:03 UTC] PHP Fatal error: Trait 'AAM_Core_Contract_SingletonTrait' not found in /home/xhtmljunkies/public_html/wp-content/plugins/advanced-access-manager/application/Service/Compatibility.php on line 21 [22-Apr-2024 01:11:01 UTC] PHP Fatal error: Trait 'AAM_Core_Contract_ServiceTrait' not found in /home/xhtmljunkies/public_html/wp-content/plugins/advanced-access-manager/application/Service/LoginRedirect.php on line 23 [27-Apr-2024 12:01:47 UTC] PHP Fatal error: Trait 'AAM_Core_Contract_SingletonTrait' not found in /home/xhtmljunkies/public_html/wp-content/plugins/advanced-access-manager/application/Service/Core.php on line 29 [29-Apr-2024 08:46:14 UTC] PHP Fatal error: Trait 'AAM_Core_Contract_ServiceTrait' not found in /home/xhtmljunkies/public_html/wp-content/plugins/advanced-access-manager/application/Service/Capability.php on line 16 [20-May-2024 23:30:31 UTC] PHP Fatal error: Trait 'AAM_Core_Contract_ServiceTrait' not found in /home/xhtmljunkies/public_html/wp-content/plugins/advanced-access-manager/application/Service/Capability.php on line 16 [14-Jun-2024 03:19:07 UTC] PHP Fatal error: Trait 'AAM_Core_Contract_ServiceTrait' not found in /home/xhtmljunkies/public_html/wp-content/plugins/advanced-access-manager/application/Service/Capability.php on line 16 [15-Jun-2024 11:51:01 UTC] PHP Fatal error: Trait 'AAM_Core_Contract_RequestTrait' not found in /home/xhtmljunkies/public_html/wp-content/plugins/advanced-access-manager/application/Service/Uri.php on line 24 [21-Jun-2024 22:54:39 UTC] PHP Fatal error: Trait 'AAM_Core_Contract_SingletonTrait' not found in /home/xhtmljunkies/public_html/wp-content/plugins/advanced-access-manager/application/Service/Compatibility.php on line 21 [25-Jul-2024 17:18:44 UTC] PHP Warning: Module 'sodium' already loaded in Unknown on line 0 [25-Jul-2024 17:18:44 UTC] PHP Fatal error: Trait 'AAM_Core_Contract_RequestTrait' not found in /home/xhtmljunkies/public_html/wp-content/plugins/advanced-access-manager/application/Service/Toolbar.php on line 22 [15-Aug-2024 09:41:56 UTC] PHP Warning: Module 'sodium' already loaded in Unknown on line 0 [15-Aug-2024 09:41:56 UTC] PHP Warning: Version warning: Imagick was compiled against ImageMagick version 1692 but version 1693 is loaded. Imagick will run but may behave surprisingly in Unknown on line 0 [15-Aug-2024 09:41:56 UTC] PHP Fatal error: Trait 'AAM_Core_Contract_ServiceTrait' not found in /home/xhtmljunkies/public_html/wp-content/plugins/advanced-access-manager/application/Service/Capability.php on line 16 [26-Aug-2024 09:54:58 UTC] PHP Warning: Module 'sodium' already loaded in Unknown on line 0 [26-Aug-2024 09:54:58 UTC] PHP Warning: Version warning: Imagick was compiled against ImageMagick version 1692 but version 1693 is loaded. Imagick will run but may behave surprisingly in Unknown on line 0 [26-Aug-2024 09:54:58 UTC] PHP Fatal error: Trait 'AAM_Core_Contract_ServiceTrait' not found in /home/xhtmljunkies/public_html/wp-content/plugins/advanced-access-manager/application/Service/Capability.php on line 16 [28-Aug-2024 00:16:58 UTC] PHP Warning: Module 'sodium' already loaded in Unknown on line 0 [28-Aug-2024 00:16:58 UTC] PHP Warning: Version warning: Imagick was compiled against ImageMagick version 1692 but version 1693 is loaded. Imagick will run but may behave surprisingly in Unknown on line 0 [28-Aug-2024 00:16:58 UTC] PHP Fatal error: Trait 'AAM_Core_Contract_ServiceTrait' not found in /home/xhtmljunkies/public_html/wp-content/plugins/advanced-access-manager/application/Service/Shortcode.php on line 19 [06-Sep-2024 22:28:06 UTC] PHP Warning: Module 'sodium' already loaded in Unknown on line 0 [06-Sep-2024 22:28:06 UTC] PHP Warning: Version warning: Imagick was compiled against ImageMagick version 1692 but version 1693 is loaded. Imagick will run but may behave surprisingly in Unknown on line 0 [06-Sep-2024 22:28:06 UTC] PHP Fatal error: Trait 'AAM_Core_Contract_SingletonTrait' not found in /home/xhtmljunkies/public_html/wp-content/plugins/advanced-access-manager/application/Service/Core.php on line 29 [11-Sep-2024 15:48:15 UTC] PHP Warning: Module 'sodium' already loaded in Unknown on line 0 [11-Sep-2024 15:48:15 UTC] PHP Warning: Version warning: Imagick was compiled against ImageMagick version 1692 but version 1693 is loaded. Imagick will run but may behave surprisingly in Unknown on line 0 [11-Sep-2024 15:48:15 UTC] PHP Fatal error: Trait 'AAM_Core_Contract_RequestTrait' not found in /home/xhtmljunkies/public_html/wp-content/plugins/advanced-access-manager/application/Service/SecureLogin.php on line 32 [13-Sep-2024 13:54:30 UTC] PHP Warning: Module 'sodium' already loaded in Unknown on line 0 [13-Sep-2024 13:54:30 UTC] PHP Warning: Version warning: Imagick was compiled against ImageMagick version 1692 but version 1693 is loaded. Imagick will run but may behave surprisingly in Unknown on line 0 [13-Sep-2024 13:54:30 UTC] PHP Fatal error: Trait 'AAM_Core_Contract_ServiceTrait' not found in /home/xhtmljunkies/public_html/wp-content/plugins/advanced-access-manager/application/Service/DeniedRedirect.php on line 21 [24-Sep-2024 18:09:42 UTC] PHP Warning: Module 'sodium' already loaded in Unknown on line 0 [24-Sep-2024 18:09:42 UTC] PHP Warning: Version warning: Imagick was compiled against ImageMagick version 1692 but version 1693 is loaded. Imagick will run but may behave surprisingly in Unknown on line 0 [24-Sep-2024 18:09:42 UTC] PHP Fatal error: Trait 'AAM_Core_Contract_RequestTrait' not found in /home/xhtmljunkies/public_html/wp-content/plugins/advanced-access-manager/application/Service/Toolbar.php on line 22 [24-Oct-2024 10:28:10 UTC] PHP Warning: Module 'sodium' already loaded in Unknown on line 0 [24-Oct-2024 10:28:10 UTC] PHP Warning: Version warning: Imagick was compiled against ImageMagick version 1692 but version 1693 is loaded. Imagick will run but may behave surprisingly in Unknown on line 0 [24-Oct-2024 10:28:10 UTC] PHP Fatal error: Trait 'AAM_Core_Contract_ServiceTrait' not found in /home/xhtmljunkies/public_html/wp-content/plugins/advanced-access-manager/application/Service/DeniedRedirect.php on line 21 How to Use Magento Database Repair Tool | Xhtmljunkies
Check out our newest developed Magento 2 Customer Discount More Info

How to Use Magento Database Repair Tool

Time and again there may be the chances, where your Magento database can get distorted and you will be facing lots of errors while installing your Magento. Instead of wasting your time in fixing the database, which may wind up with an absolutely broken website, you should use the Magento Database Repair Tool, created by Magento core Team, which will surely help you in big time.

The Magento Database Repair Tool evaluates two databases i.e. reference and target. After comparing these two databases, this tool updates the target database so as to keep its structure same as the structure of reference database. This is done by performing the following methods:

  1. Adding up missing tables or restoring them to get the identical engine type and char set.
  2. Adding Missing fields or repairing them.
  3. Taking out incompatible data from tables that have broken foreign key references.
  4. Adding up missing foreign keys and indexes.

The Database Repair Tool is applied to fix the database of an existing Magento installation that contains any of the errors which are stated above. You just have to install the same version of Magento that you are using into a clean database. Use the new database as “reference” and existing database as “corrupted”.

The most important thing which you should always keep in your mind, make sure that you have tested the database repair tool on development environment before actually running it on production environment. Also, don’t forget to keep a backup of your original database prior to running database repair tool.

While the repairing process is going on, it is highly advisable to restrict the access to your website. By restricting your Magento instance to your IP address, the visitors including search spiders, will get the HTTP503 Service Unavailable error.

You have to generate a 503.php file in your Magento installation root as:

  1. <?php
  2. header(‘HTTP/1.1 503 Service Unavailable’);
  3. header(‘Content-Type: text/plain; charset=UTF-8’);
  4. echo “503 Service Unavailable”;

After doing this, you have to add the rewrite rule in .htaccess or in Apache server configuration as follows:

RewriteEngine On

RewriteCond %{REMOTE_ADDR} !^127.0.0.1$

RewriteRule  ! 503.PHP$ /503.PHP [L]

Where, 127.0.0.1 (backslashes ahead of dots) should be reinstated with your IP-address. As you save this .htaccess file or restore the Apache configuration, your site will be down until you bring back to original status.

Here are the Steps:

  1. Download Magento database repair tool archive from the download page
  2. Uncompress the archive
  3. Locate the magento-db-repair-tool-1.0.php into any folder on your server
  4. Take Backup of your present database so that you can restore it if anything goes wrong
  5. Duplicate it as new database on the same server. Say, “database2”
  6. Create an empty database, ”database3”
  7. Copy your whole Magento folder into a new one and install it into “database3”
  8. If you have by now constrained the access to your Magento instance, change your database records into “database3”, remove all the cache and start on Magento once: it will get installed automatically.

Currently, You have the duplicate copy of your original database in “database2” and empty Magento installed in”database3”

Now,

Run http://url-of-your-server/path-to-folder/magento-db-repair-tool-1.0.php

  1. Enter access credentials to “database2” as “corrupted” database and to “database3” as “reference” database
  2. Set table prefixes, if pertinent
  3. Press “Continue” and you will see result screen where you will see what was done to the “corrupted” database.

Don’t forget to remove the magento-db-repair-tool-1.0.php. Now, you can Access your website on browser and you are done.

Author: Harshal Shah

Harshal Shah is CEO & Founder of Xhtmljunkies, Located in Gujarat, India, XHTML Junkies is one of the best companies that offer unique eCommerce solutions by the virtue of its dedicated professionals. Our professionals are extremely proficient in offering development services pertaining to eCommerce. You can find Harshal on and Twitter.

The following two tabs change content below.

Harshal Shah

Harshal Shah is CEO & Founder of Xhtmljunkies, Located in Gujarat, India, XHTML Junkies is one of the best companies that offer unique eCommerce solutions by the virtue of its dedicated professionals. Our professionals are extremely proficient in offering development services pertaining to eCommerce. You can find Harshal on and Twitter.