There was a problem with reindexing process – Magento

Thursday, 23. February 2012

For anyone working with Magento, I am sure you have come across There was a problem with reindexing process error at least once in your life time using Magento.

As you can tell, the error is not always very explicit on what the issues is and more than often its because MySQL database has encountered an error and could not proceed with the process.

Best way I have found to deal with this is get a bit more information is to run the PHP shell script for re-indexing the database that comes with your Magento install. This will throw detailed message to you on what went wrong!

Open your command line tool and navigate to the root of your Magento site (htdocs or publich_html etc) and type this commend.

php shell/indexer.php reindexall

Sit back and observe!

Column not found: 1054 Unknown column main_table.include_in_menu in where clause

Tuesday, 29. November 2011

Had this issue today upgrading Magento from 1.3.3.0 to 1.6.0.1 :

Column not found: 1054 Unknown column ‘main_table.include_in_menu’ in ‘where clause’

After a bit of looking around with no luck, resorted back to running a complete Index Management which solved the issue for us.

Let us know if you have any interesting observations yourself!

Magento Index Management – Cannot initialize the indexer process.

Tuesday, 9. August 2011

If you ever come across such error as “Cannot initialize the indexer process.” while running index management on Magento, the problem may probably be down to your locks folder.

To solve this problem, navigate to your locks folder:

/var/locks

Make sure the locks folder is writable. Also to make things clear, Delete all the locks files inside.

At this stage you may want to give the index manager another try!

If this didn’t help you may want to have a look at the table catalog_category_product_index and delete the contents there.

DELETE FROM catalog_category_product_index;

Magento Index Management – catalogsearch_fulltext table crashed and needs repairing

Saturday, 30. July 2011

If you have been running Magento’s index management and suddenly came across this error like I did, here is a quick and nice solution that will help you.

Use PhpMyadmin or MySql Query analyser

You will need access to your database to perform this solution. You can also use your favorite GUI DB interface if you want.

1) Connect to your database.

2) Because catalogsearch_fulltext is a MyISAM type table, you can use this query (you can change options are you see fit) and replace table_name to your table name. Then Run

-- Syntax: REPAIR TABLE table_name [,table2, table3 ...] [options]
REPAIR TABLE table_name;

Available options are

QUICK – It’s the quick way and data file is not modified.

USE_FRM – If for some reason the .MYI is missing or corapted and the plan REPAIR TABLE query fails, you can add this option so MySql can rebuild the indexes for you.

EXTENDED – I will use this as a very last resort. This option will try to repair every single row it comes across with and in the end, it may result to some Gibraltar stuff on your table!

Click this link to learn more about: REPAIR TABLE

From a command line utility

There are also commands to run on your terminal if so preferred. I will not outline exactly how to do this but there is a more useful information already on the following links.

myisamchkClick here to learn more

mysqlcheckClick here to learn more.