PDA

View Full Version : Sql Prob :(


vB-Host.com
04-25-2003, 07:06 AM
Ok I just got alerted of sql errors.. so went into phpmyadmin... thread is locked up on in use...

_thread__ Browse Select Insert Properties Drop Empty in use

Erwin
04-25-2003, 07:17 AM
What exactly was the error message? Don't do anything drastic to your thread table.

vB-Host.com
04-25-2003, 07:21 AM
i tried rebooting the box... but still no change..

Database error in vBulletin 2.2.9:

Invalid SQL: SELECT count(*) AS count FROM thread WHERE dateline>='1051254000'
mysql error: Can't open file: 'thread.MYI'. (errno: 145)

mysql error number: 1016

Date: Friday 25th of April 2003 01:17:12 AM

Erwin
04-25-2003, 07:22 AM
Okay, the thread table is corrupted.

You need to "repair" it. You can do so via phpmyadmin, or by uploading and running repair.php from your uploads directory of your vB ZIP file.

Brad
04-25-2003, 07:27 AM
Today at 03:21 AM vB-Host.com said this in Post #3 (https://vborg.vbsupport.ru/showthread.php?postid=386805#post386805)
i tried rebooting the box... but still no change..

Database error in vBulletin 2.2.9:

Invalid SQL: SELECT count(*) AS count FROM thread WHERE dateline>='1051254000'
mysql error: Can't open file: 'thread.MYI'. (errno: 145)

mysql error number: 1016

Date: Friday 25th of April 2003 01:17:12 AM


Common problem, did you just upgrade to mySQL 4 be chance? :)

Refer to this thread at vB.com, its basicly repeat of erwins post, but its more of a 'step by step' post

http://www.vbulletin.com/forum/showthread.php?threadid=69171

vB-Host.com
04-25-2003, 07:35 AM
that did the trick! thanks for the fast responce

vB-Host.com
04-25-2003, 07:39 AM
Today at 12:27 AM Anime-loo said this in Post #5 (https://vborg.vbsupport.ru/showthread.php?postid=386811#post386811)
Common problem, did you just upgrade to mySQL 4 be chance? :)



yeap did the upgrade to it all Apache, PHP and SQL... now running Apache 1.3.27, PHP 4.3.1 and MySQL 4.0.12... but this customer's vB has been stable the whole while since the upgrade almost 2 weeks ago... so not sure really if SQL 4 is the problem..