[EMAIL PROTECTED] wrote:
Hi,
We're in the process of benchmarking/evaluating MySQL(4.1.9) on Linux for our data
warehouse. I have a group of tables (9/2004 through 2/2005) that average
about 95 million rows (215 byte rows). Using PERL and piping to mysql LOAD DATA is the way we've been loading. That all worked as advertized when single threaded. Once all the data was loaded one of the tables had several indexes created. Again, no problem. Then we tried running myisampack against one of the tables. It worked against the table, however other tables somehow
got corrupted. Running a query against the table produced the following error:
MyISAM Engine returned error 127
Ok, so we ran myisamchk --quick --recover
It ran successfully (or so we thought). Query the table for rows and the number comes back. Query the data get same error message.
Next, we ran myisamchk --force --extended-check
It ran successfully (or so we thought). Query the table for rows and the number comes back. Query the data get same error message.
Then decide to truncate the table. Same error.
Dropped the table. Same error.
Recycled MySQL then dropped the table. It worked.
Any ideas as to what may be going on here.
George
You did not state that you stopped the server before running myisamchk.
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
