Repeated mysql corruption

[Mr. Natural]

I'd like to know how many folks are having repeated problems with your mysql database becoming corrupted?
From what I've read on many bbs support forums there is a problem with MySQL version 4.0.12. A good example is the vbulletin message posted here (http://www.vbulletin.com/forum/showthread.php?t=69803) .
I've also read similar posts on the ib/ikonboard forums.
I've tried both bbs programs and a couple of times a week a database corruption occurs and I find myself having to fix a table in mysql. Sometimes data loss occurs as a result.

Also I'd appreaciate if powweb folks could advise us on this matter. Are bug reports being reported to the mysql folks? Is there a patch in the works? Basically any status information would be greatly appreciated.

[Xinil]

Happens all the time for me. Not a damn thing anyone can do about it though.

mySQL.com states that TEXT columns are more susceptible to cause corruptions than VARCHAR columns are. This is obviously because of the enormous difference in space each column can hold.

mySQL.com also states that inefficient code will not cause table corruptions. It's a server problem.

Basically, this just means that Powweb can't control the corruptions that occur. I run a Apache / PHP / mySQL server on my home computer and it also gets corrupted on a weekly basis.

However, I have noticied that if you maintain your database on a one to two day span, corruptions are much less likely to occur. Each day I run "repair table <tablename>" (using mysql Front) on all of my tables. Ever since I've been doing this (started doing it about 3 weeks ago), not one of my tables have crashed.

[Gaim Mastr]

Thanks for the reply, Xinil.

It's unfortunate that such steps would need to be taken to resolve a problem that causes corruption every 2 or 3 days.

I also have read several threads regarding MySQL on different message board support forums.

One solution that web hosts seem to have been taking is that they are going back to the MySQL v3 until the MySQL company can correct this seemingly widespread problem.

Does anyone know if PowWeb has or is considering doing something similar in an effort to stem this problem for their clients ??

Or has MySQL acknowledged the problem and are working on a patch or updated version to fix this any time soon ??


I notice that these PowWeb Customer forums are run with the same version of vBulletin as my own. Perhaps those responsible for keeping these forums up and running smoothly have some advice for how we can combat these MySQL problems.

[Xinil]

It doesn't look like Powweb will be going back to v3 of mySQL. Three weeks ago, my members table with over 200 members crashed because of this "problem". Unfortunately, the crash was so dramatic that I was unable to repair the table. Being my idiot self, I never made any back-ups, so I had to restart from square 1.

Anyway, Powweb has known about this error for quite some time now. Problems aren't widespread enough for them to go back to v3.

Hopefully mySQL.com will come out with a patch to fix this annoying bug.

[RocketJeff]

Originally posted by Xinil
Hopefully mySQL.com will come out with a patch to fix this annoying bug.
I doubt it. mySQL version 4.1.0 is already in Alpha testing so that'll probably be the version with the fix.