List:General Discussion« Previous MessageNext Message »
From:Michael Widenius Date:June 3 1999 3:26am
Subject:ERROR 1030: Got error 134 from table handler - definitive
answer ?
View as plain text  
>>>>> "chas" == chas  <panda@stripped> writes:

chas> I've seen a couple of posts in the archive regarding the following error :
chas> ERROR 1030: Got error 134 from table handler

chas> but most replies explained how to fix tables and not what the problem
chas> was or how it was caused. what i have noticed though is that :
chas> a) it occurs on my tables that have chinese language characters
chas>    but not tables that don't
chas> b) some of the posters in the archive seemed to come from countries
chas>    where foreign languages are used.

chas> does anyone have the definitive answer to :
chas> 1) what causes this error ?
chas> 2) how to repair/solve it ?

chas> it seems to only affect reading the values in my table - i can still
chas> insert data or at least i hope so.  but one bad thing is :
chas> "select * from table_name"       -> ERROR 1030: Got error 134 
chas> "select count(*) from table_name -> 83 (correct)
chas> "select id from table_name"      -> hang/crash the client !

chas> thank you very much,

chas> chas

Hi!

There may be something with the chinese character handling that couses 
this.  Can you try to following test from the MySQL manual:

--------

If you get corrupted tables or if `mysqld' always fails after some
update commands, you can test if this bug is reproducible by doing the
following:

   * Stop the mysqld daemon (with `mysqladmin shutdown')

   * Check all tables with `isamchk -s database/*.ISM'.  Repair any
     wrong tables with `isamchk -r database/table.ISM'.

   * Start `mysqld' with `--log-update'

   * When you have got a crashed table, stop the `mysqld server'.

   * Restore the backup.

   * Restart the `mysqld' server *without* `--log-update'

   * Re-execute the commands with `mysql < update-log'.  The update log
     is saved in the *MySQL* database directory with the name
     `your-hostname.#'.

   * If the tables are now again corrupted, you have found reproducible
     bug in the `ISAM' code!  ftp the tables + the update log to
     `ftp://www.mysql.com/pub/mysql/secret' and we will fix this as
     soon as possible!

--------

Regards,
Monty
Thread
Sad story about MySQL RH 6.0 and DEC AlphaDim Zegebart1 Jun
  • Re: Sad story about MySQL RH 6.0 and DEC AlphaDarrell Shifflett1 Jun
    • Re: Sad story about MySQL RH 6.0 and DEC AlphaDim Zegebart1 Jun
      • Re: Sad story about MySQL RH 6.0 and DEC AlphaOrlando Andico1 Jun
        • Re: Sad story about MySQL RH 6.0 and DEC AlphaDim Zegebart1 Jun
          • Re: Sad story about MySQL RH 6.0 and DEC AlphaDarrell Shifflett1 Jun
            • Re: Sad story about MySQL RH 6.0 and DEC AlphaDim Zegebart1 Jun
              • Re: Sad story about MySQL RH 6.0 and DEC AlphaVivek Khera1 Jun
            • Re: Sad story about MySQL RH 6.0 and DEC AlphaRitschie1 Jun
              • Re: Sad story about MySQL RH 6.0 and DEC AlphaOrlando Andico1 Jun
          • Re: Sad story about MySQL RH 6.0 and DEC AlphaOrlando Andico1 Jun
Re: Sad story about MySQL RH 6.0 and DEC AlphaChristopher R. Jones1 Jun
  • My SQL on Redhat Linux 5.0Sajjad Ahmad1 Jun
    • ERROR 1030: Got error 134 from table handler - definitiveanswer ?chas1 Jun
      • ERROR 1030: Got error 134 from table handler - definitiveanswer ?Michael Widenius3 Jun
  • Re: Sad story about MySQL RH 6.0 and DEC AlphaDim Zegebart1 Jun