We have replicated this crash over and over just now... Very strange.
Yet with the 2.23.30 version, we dont lose the data and dont seem to get
corruption.
Here is exactly what happened... (This also crashed it in the first
place, which lost all our data in the 2.23.28 version)
We have a table
Well, we upgraded to 2.23.30 and tried to bring it up with the same
seemingly corrupt
datafiles. It tried to do a recovery (saw this in the error log), but
died when
it was looking for database directories that had long ago been deleted.
It was like
it was making its way through the entire db tr
The MySQL team recommended upgrading to 3.23.29 gamma, especially if using
Berkeley DB.
-
/ Rick Mehalick Senior Consultant
/ Shell Services International SSI-GPAX
/ Phone: 281-544-5092(WCK)
/ Fax:281-544-2646(WCK)
/ email: [EMAIL PROTE
