> -Original Message-
> From: Chris [mailto:[EMAIL PROTECTED]
> Sent: Thursday, July 27, 2006 22:42
> To: Dirk Bremer
> Cc: mysql@lists.mysql.com
> Subject: Re: Mysqlcheck issues
>
> Dirk Bremer wrote:
> > I am using MySQL server 4.1.10 on Windows 2003 Se
> -Original Message-
> From: Logan, David (SST - Adelaide) [mailto:[EMAIL PROTECTED]
> Sent: Thursday, July 27, 2006 22:40
> To: Dilipkumar; Dirk Bremer; mysql@lists.mysql.com
> Subject: RE: Mysqlcheck issues
>
> The trouble with myisamchk is that it requires the se
Dirk Bremer wrote:
I am using MySQL server 4.1.10 on Windows 2003 Server with MyISAM
tables. I have an issue where occasionally an index (MYI) file becomes
corrupted. I do not know why this occurs. To combat this issue, I tried
running the following command every half-hour:
mysqlcheck -Aamov --a
PM
To: Dirk Bremer; mysql@lists.mysql.com
Subject: Re: Mysqlcheck issues
Hi,
Instead of mysqlcheck you can use myisamckh to recover the data's.
As myisamchk -r -o *.MY*
Thanks & Regards
Dilipkumar
- Original Message -
From: "Dirk Bremer" <[EMAIL PROTECTED]>
To:
Hi,
Instead of mysqlcheck you can use myisamckh to recover the data's.
As myisamchk -r -o *.MY*
Thanks & Regards
Dilipkumar
- Original Message -
From: "Dirk Bremer" <[EMAIL PROTECTED]>
To:
Sent: Thursday, July 27, 2006 8:32 PM
Subject: Mysqlcheck issues
I am using MySQL server 4.1.10 on Windows 2003 Server with MyISAM
tables. I have an issue where occasionally an index (MYI) file becomes
corrupted. I do not know why this occurs. To combat this issue, I tried
running the following command every half-hour:
mysqlcheck -Aamov --auto-repair --use-frm
