MySql Prob

Host's stupidity and ignorance

[futureX]

Hey guys, this is the last place I can turn for help on this, I have a MySql database runing for some forums software, and my host decided to move me from one of their servers to another. However, after the move I get the following error on opening the board.

mySQL query error: DELETE FROM ibf_sessions WHERE running_time < 1074943780 or ip_address='***.***.***.***'

mySQL error: Can't open file: 'ibf_sessions.InnoDB'. (errno: 1)
mySQL error code: 1016
Date: Saturday 24th of January 2004 12:19:40 PM

Now the table in question ibf_sessions had been converted from MYISAM to INNODB on the old server to fix a table corruption problem. And when looking at the DB in phpmyadmin under table type it says "in use".

Is there any reason why the new server would not be able to read the INNODB table? I have tried repairing it, optimising it and cant even open it. I cannot restore the entire DB from a backup as the DB is huge and I timeout when I try to upload the members table.

[coopster]

Restrictions on InnoDB Tables [mysql.com]. Read bullet number 4...ouch!

If you can read from the other tables, I'm willing to bet this table is locked.

[futureX]

I think my only hope is to get the DB copied over again, as I have converted the table back to MYISAM on the old server (that DB works fine). Only thing is that my host is not exactly being helpful and they're buzzin if they think i'm going to pay them in full this month. They managed to break all my websites in different ways, and I had to run around fixing them :(

Is there no way I can unlock the table, or is that only something my host can do?

[coopster]

Depends on permissions. Here are a couple of links to get you started on troubleshooting that path...

[mysql.com...]
[mysql.com...]
[mysql.com...]

Have you ever looked into mysqldump [mysql.com]? If you have command line access to use your database, this utility is quite handy. You execute your command on the old server, FTP the dump file(s) to your new server, and run the dumped sql file. It creates the tables, inserts the records, etc. If your database is too large, you can run the command table-by-table. May be worth the read for you.

[futureX]

Thanks for the tips, I am currently restoring the database from a mysqldump, I could not do this before as the db was too big and kept timing out, but I just used a nice little php tool and its all back and running fine.