SQL error:#0, #1016, #1064 help needed

[izan]

I'm having problems with my database and am stuck. This happened after their upgrade (and as a result of it) since I changed nothing. It's explained below. The email errors depend on who's trying to login but the database error is always there. The database backups from the 10th and 11th are 2.9 kb and stop at the table just prior to the affected one. The tables that are in the backup look normal. The database backups after the 12th are 0.3kb. I've included what it shows at the bottom of this message, if needed. These are the backups from the OPS SQL page, not after trying to run it through phpAdmin (which will not work because of the error).
Can anybody help, please!

Here's an email I sent to powweb's tech support and their useless 'copy and paste from the announcment page' reply that follows (yes, I did check the notes page before contacting them):

My forum was working fine but as of Tuesday, January 11, 2005 9:41 AM I
have been receiving numerous emails with the following message:
"Database error in vBulletin : Link-ID == false, connect failed mysql
error: mysql error number: 0"

I logged into OPS (phpAdmin) and ran a database backup which resulted in the
following: error: #1016 - Can't open file: 'xxxx_iponline.MYI' (errno: 145)

I tried repairing the table by typing REPAIR TABLE <xxxx_iponline.MYI>
under the SQL tab in the RUN SQL box. That returns this message:

MySQL returned: #1064 - You have an error in your SQL syntax; check the manual that
corresponds to your MySQL server version for the right syntax to use
near '<xxxx_iponline.MYI>' at line 1
Now I'm lost. How did this happen and how do I fix this?
--------------------------------------------------------------
Hello,
Thank you for contacting Powweb support.
Please read the following:
http://dev.mysql.com/doc/mysql/en/U...g-from-4.0.html

Several visible behaviors have changed between MySQL 4.0 and MySQL 4.1 to
fix some critical bugs and make MySQL more compatible with standard SQL. These
changes may affect your applications.

If you're experiencing problem since the upgrade - notably with timestamp
formatting or character sets - you should check the notes at the above link
for more information and make the appropriate changes in order for your
database to run properly.

Also, try to do a "repair table" from the PHPMyADMIN interface and that may
also resolve the problem as well.
--------------------------------------------------

-- Server version 4.1.7-log

/*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */;
/*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */;
/*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */;
/*!40101 SET NAMES utf8 */;
/*!40014 SET @OLD_UNIQUE_CHECKS=@@UNIQUE_CHECKS, UNIQUE_CHECKS=0 */;
/*!40014 SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0 */;
/*!40101 SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE="NO_AUTO_VALUE_ON_ZERO" */;

[zinco]

MySQL returned: #1064 - You have an error in your SQL syntax; check the manual that
corresponds to your MySQL server version for the right syntax to use
near '<xxxx_iponline.MYI>' at line 1
Now I'm lost. How did this happen and how do I fix this?

That error I know what the problem is.
See these threads:
http://forum.powweb.com/showthread.php?p=264421#post264421
http://forum.powweb.com/showthread.php?t=45461
http://forum.powweb.com/showthread.php?t=45494&highlight=princess

[izan]

Thank's but I found the following answer late yesterday. It was on another webhost's board at : http://www.lunarforums.com/ (one more problem powweb and I'm gone).

Hi,

Were getting a few tickets from people with forum boards with regards to the
MYI'. (errno: 145)

Error 145 = Table was marked as crashed and should be repaired

This mainly happens with the "sessions" table.

This is the table responsible for storing who is logged in.
It's called by the script in order to display the username.

This is not a bug in the SQL.

In order to repair this:

Go into php myadmin.

Backup your Database.

Select the database in question.

check the box next to your sessions table.
(if you unsure which one this is, select them all)

Scroll down to the box that says "With selected"

Select "Repair"

This will then repair the table and you script should function again.

Please Remember to backup your database before attempting any of this .

More information on SQL table errors and how to repair them can be found at:

http://www.mysql.com/doc/en/Repair.html

If anyone has anything interesting to add to this, I'd love to hear it.

Thanks
-------------------------------------------------------------------------------
I ended up doing:
Stage 3: Difficult repair
http://dev.mysql.com/doc/mysql/en/Repair.html
Which has apparently fixed the problem - for now.

Gee, I can't wait for powweb's next little surprise. :mad: