Yes, I agree with the previous responder. But before you do a repair
table, you can do a "check table .... extended" to see what the problem
is with the table... just in case you want to know.
Also... it is important to note that during the repair process several
records from the problematic table may be lost. I just went through
this a few weeks ago. I had a table with about 1500 records in it. I
was getting 134 error message. After repair... about 6 records were
lost. I'm not sure how to get around this, but I thought I would call
your attention to it so that it doesn't come as a surprise.
Andy
Th************@gmail.com wrote:
IPB WARNING [2] mysql_query() [function.mysql-query]: Unable to save
result set (Line: 457 of /ips_kernel/class_db_mysql.php)
There appears to be an error with the database.
You can try to refresh the page by clicking here.
Error Returned
mySQL query error: SELECT MIN(pid) as pid FROM ib_posts WHERE queued=0
AND topic_id=85734 AND post_date 1160298086 LIMIT 0,1
SQL error: Got error 134 from storage engine
SQL error code:
Date: Wednesday 13th of October 2006 04:51:36 PM
How can I fix it?