VirtueMart Forum

VirtueMart 2 + 3 + 4 => Administration & Configuration => Topic started by: freshqa on November 01, 2012, 21:25:15 PM

Title: vmError: vmTable loadIncorrect key file for table == Need some help { thanks}
Post by: freshqa on November 01, 2012, 21:25:15 PM
After saving product i got this error popping up and all of the products are unpublished on the products page in virtuemart

vmError: vmTable loadIncorrect key file for table './g7ati_virtuemart_product_customfields.MYI'; try to repair it SQL=SELECT `g7ati_virtuemart_products_ru_ru`.* ,`g7ati_virtuemart_products`.* ,`g7ati_virtuemart_product_manufacturers`.`virtuemart_manufacturer_id` ,`g7ati_virtuemart_product_customfields`.`virtuemart_customfield_id` FROM `g7ati_virtuemart_products_ru_ru` JOIN g7ati_virtuemart_products using (`virtuemart_product_id`) LEFT JOIN `g7ati_virtuemart_product_manufacturers` on `g7ati_virtuemart_product_manufacturers`.`virtuemart_product_id`=`g7ati_virtuemart_products_ru_ru`.`virtuemart_product_id` LEFT JOIN `g7ati_virtuemart_product_customfields` on `g7ati_virtuemart_product_customfields`.`virtuemart_product_id`=`g7ati_virtuemart_products_ru_ru`.`virtuemart_product_id` WHERE g7ati_virtuemart_products_ru_ru.`virtuemart_product_id` = "578"


and virtuemart_product_id` = "578" and it goes from 460+ product up till virtuemart_product_id` = "578" with this same error

Did not change any of the config or the ftp files

Virtuemart version: 2.0.8
Joomla 2.5.6
Title: Re: vmError: vmTable loadIncorrect key file for table == Need some help { thanks}
Post by: freshqa on November 02, 2012, 15:44:19 PM
So we solved it and wasnt virtuemart fault, if anoyone gets this, you are probably run out of space @ hosting disc

just get more space, then go to mysql and fix the table (the one listed as crashed) with built in tools

Cheers
Title: Re: vmError: vmTable loadIncorrect key file for table == Need some help { thanks}
Post by: freshqa on November 09, 2012, 11:38:51 AM
The same problem occured, same table, same conditions. I can try to repair tables once again but maybe a Developer can say his oppinion on the situation to prevent this error from happening ?