HELP: error 134 from storage engine

[Macisle]

When attempting to access any kind of order history in admin or as a customer, the following error message comes up:

 

Warning: mysql_query() [function.mysql-query]: Unable to save result set in ...store/includes/functions/database.php on line 44

1030 - Got error 134 from storage engine

 

select count(*) as total from orders o, orders_total ot, orders_status s where o.customers_id = '1' and o.orders_id = ot.orders_id and ot.class = 'ot_total' and o.orders_status = s.orders_status_id and s.language_id = '4'

 

I have tried emptying the sessions table, but that didn't help. I am both a PHP and MySQL/database novice, so I need to have my hand held through any explanations if the solution is complicated.

 

We have tried a test order and it was successful. However, as stated above, attempts to access the order history receive the error.

 

There have been no recent modifications to our OSC store or to the database. It has been working fine for perhaps a year since the last OSC modification was made. The issue started in the last day or two.

 

This is a live store, so fast help replies would be wonderful. Many thanks in advance for your time and help!

 

Best regards,

 

Macisle

[Macisle]

I have been able to solve the problem.

 

Using "Check Table" in PHPMyAdmin identified a corrupt orders table in my database. Repairing that solved the problem. I checked the server info in the OSC Admin panel and the server has only been up for just over a day, so a server crash must have been the culprit.

 

So, the fix was easy and this was a good learning experience. I also learned how to identify and eliminate (through Repair Table) unwanted overhead in the database tables.

 

So, if anyone encounters the same error message, a likely solution is to go to PHPMyAdmin, select all your tables and run a Check Table command via the dropdown menu below the table list. Then, if problem tables are identified, select those tables and run a Repair Table command via the same dropdown menu. The likely cause is a server crash occuring while the database is being written to.

 

Macisle