cant open 'tablename.MYI' mysql06

[Mangus]

I cant understand.. evrybody is suffering from this... and no OFFICIAL report from powweb???

[Galax]

'cant open 'tablename.MYI' simply means that this particular table in your DB is corrupted. In most cases running a repair on the affected table corrects the issue. The problem with the database servers appears to be corrected at this point though the admins are still monitoring them for signs of further issues. In the mean time run a repair and try your site again.

[ptpghost]

fixed? Most of the database content from my site is still missing. Ive tried the repair but that doesnt help. Im on mysql02 (or was, dont know of anything has changed about the locations).

[Mangus]

Did you checked than more than XXX customers had the same problem?? I can't understand answers like this.. SIMPLY MEANS THAT... oh yeah you know... I am so dumb that couldnt figure that one.

Simply means that you ALWAYS think your customers dont know when you really F**** UP the database... for more than 2 days... and didnt replied saying that you correctly fixed the problem.

Simply means that you underestimate everybody.

Of course I personally fixed my tables.. but you know what? i still fearing that in some minutes you people will behave as you behave: messing and NEVER apologizing for what you've done. That's what running a business should be (as powweb acts)

Well.. that SIMPLY MEANS that I am angry.

[ptpghost]

ok, justed dropped all the tables in my db and ran the sql to recreate them and add in the data (all through phpmyadmin) and still nothing on the site but all is fine in phpmyadmin.

[Dagorlad]

This exact problem occurred on my database on server05, and simultaneously on the database of another site I know of located on server01.

I have spent over 15 hours trying to restore the database to a useable state from the previous night's backup, but the phpmyadmin page keeps timing out and I am left with a seriously mangled mess.

If this has been caused by the recent MySQL database upgrades then please Powweb, make some announcement about it and offer some solution. I have over a 1000 users clamouring for my blood because I can't get my website functional.

[ptpghost]

i had to split my mass backup into different sections so it wouldnt time out parsing it

[Dagorlad]

And I did that also, and have just finished doing it again, and I am still having issues. And I have repeatedly "repaired" my tables, optimized them and checked them. My backup is fully restored, but the MySQL is not working correctly.

I now get this error whenever I execute a table join on one of the two or three tables that were affected by this corruption:

#1030 - Got error 124 from storage engine

Selecting from the table directly works fine, but any joins result in this error appearing.

[Silvertiggie]

This is a nightmare, we have spent the majority of our weekend tearing our hair out over this and all we get in response from powweb is that they are looking into the situation.

[Dagorlad]

The thread at the top of this forum points us to a topic on the MySQL site, about issues to consider when upgrading from v4.0 to v4.1.

http://dev.mysql.com/doc/mysql/en/upgrading-from-4.0.html (http://dev.mysql.com/doc/mysql/en/upgrading-from-4-0.html)

Reading through this page I was staggered to see the number of Incompatible Changes listed between the two versions. And they all result in the tables being corrupted - what a funny coincidence! Just like what happened on my database (oh and is still totally crippled in case you're wondering).

Did the Powweb technical folk consider the ramifications of this upgrade before undertaking it? Did they develop a strategy to assist their customers in the event of a catastrophic failure (like this)? Did they even acknowledge that a problem occurred? And did they advise people in advance that the database was about to be upgraded?

I for one am not happy with this situation (could you tell?).

[Dagorlad]

ok, this might help people. I reindexed the tables that were corrupted and it seems to have sorted the issues out for my application.

[Galax]

Mangus: No one is denying that there was a problem with the database servers Friday and Saturday, and reported issues with mysql09 even earlier than that, but that was not what you asked, was it? Your question was in regards to the error "cant open 'tablename.MYI" and thus my answer was in regards to what you asked. If you had articulated your question in such a way as to actually ask what was on your mind, that is what my answer would have related to. :cool:

Now with the DB servers being down, alot of people are going to be getting the error you were refering to in your original question "cant open 'tablename.MYI" that is because if there is a insert going on at the same time a database server crashes, the tables will usually become corrupt. Running a repair will usually fix that. Now others will have other issues, problems importing dump files that are large and such. That will always pose an issue when trying to do it through a web-based interface, but unfortuantely that is the only way that we allow you to do it. So in cases like that you can upload the dump file to your site somewhere and call or email support with the location of the file and your DB information. We can import the files manually for you.