List:General Discussion« Previous MessageNext Message »
From:Harry Brueckner Date:December 4 1999 4:12pm
Subject:Re: Problem with 3.23.6a
View as plain text  
Hi Sinisa,

-- On 30.11.99 18:36 +0200 sinisa@stripped wrote:
>  > since I upgraded from MySQL 3.22.25 to 3.23.6a on my Linux 2.0.36 box
>  and > converted all databases to the MyISAM format, I regularly get those
>  > messages for alot of my databases and tables. I run a database check
>  every > night which verifies the databases with "myisamchk -s ..."
>  > 
>  > /home/mysql/bin/myisamchk: ISAM file cthv/customer.MYI
>  > /home/mysql/bin/myisamchk: error: Key 1 doesn't point at all records
>  > MyISAM-table 'cthv/customer.MYI' is corrupted
>  > Fix it using switch "-r" or "-o"
>  > 
>  > /home/mysql/bin/myisamchk: MyISAM file fnet/bericht.MYI
>  > /home/mysql/bin/myisamchk: warning: 2 clients is using or hasn't
>  closed the > table properly
>  > MyISAM-table 'fnet/bericht.MYI' is usable but should be fixed
>  > 
>  > After I repair it it takes 1 or 2 days until I get the very same
>  problems > again. :-(
>  > I access the databases with PHP3 and C programs which up to now all
>  use the > old 3.22.25 libraries. With the old 3.22.25 database I didnt
>  have any > problems with corrupted index files and things like the above
>  messages. :-( > 
>  > What could be wrong and what can I do against these problems so I do
>  not > have to repair the tables every day?

> Are you using glibc ??? Install glibc 2.1.2, use binary from MySQL
> pages or re-build MySQL yourself.

I am running on an old libc system - it's libc 5.4.46.

Is this the reason for tmy problems?

Harry

Thread
Problem with 3.23.6aHarry Brueckner30 Nov
  • Re: Problem with 3.23.6asinisa30 Nov
    • Re: Problem with 3.23.6aHarry Brueckner4 Dec
      • Re: Problem with 3.23.6asinisa5 Dec