RE: [Krang-devel] 'history.MYI' gets clobbered

[Jesse E. <je...@er...>]

At the risk of going bling by replying to myself, I have found another
solution to the database corruption issue:

> The effect is that you get a 500 Internal Server Error=20
> whenever you try to check out anything.  The work-around is:
>=20
>   1. Shut down MySQL
>   2. Physically delete the history.* database files
>   3. Re-start MySQL
>   4. Recreate history table from DDL in sql/ directory.
>=20
> The myisamchk program reports that history.MYI isn't a MyISAM=20
> file, and I couldn't drop the table within MySQL.


Instead, use the "REPAIR TABLE xxxxx" MySQL DDL.  For example:


mysql> repair table history;

+------------------------+--------+----------+--------------------------
-----------------------------+
| Table                  | Op     | Msg_type | Msg_text
|
+------------------------+--------+----------+--------------------------
-----------------------------+
| cementamericas.history | repair | error    | 28 when fixing table
|
| cementamericas.history | repair | info     | Found block that points
outside data file at 54992864 |
| cementamericas.history | repair | warning  | Number of rows changed
from 994197 to 1249897         |
| cementamericas.history | repair | status   | OK
|
+------------------------+--------+----------+--------------------------
-----------------------------+
4 rows in set (2 min 39.14 sec)



TTYL,

-Jesse-


--
=20
Jesse Erlbaum
The Erlbaum Group
je...@er...
Phone: 212-684-6161
Fax: 212-684-6226
=20