Hi Reindl
I had tested your method serval months ago.
When i had a crash table, I added myisam-recover = "FORCE" to my.cnf
and restarted mysqld.
But it didn't work
So, finally, we just had to do this repairment by application code.
On Fri, Oct 19, 2012 at 4:59 PM, Reindl Harald wrote:
>
>
Am 19.10.2012 08:42, schrieb Dehua Yang:
> MyISAM storage tables also have this kind of problem.
>
> I have try serval solutions for this problem , but can't work very well.
>
> If your application isn't very import , you can let your application auto
> repair this problem.
> Just like this :
MyISAM storage tables also have this kind of problem.
I have try serval solutions for this problem , but can't work very well.
If your application isn't very import , you can let your application auto
repair this problem.
Just like this :
When your application catch this error information , run
Hi,
This table can be repaired using Repair table ; in mysql.
This should fix the corrupted index file, or if mysql is shutdown, you can
run myisamchk, also if its a myisam table.
Hope this helps.
Regards,
Akshay S
On Fri, Oct 19, 2012 at 11:52 AM, a bv wrote:
> Hi on a log management server
Looks like a MYISAM table... MYISAM is not a crash safe storage engine
and an instance crash could corrupt the tables. You should run CHECK
TABLE ; and REPAIR TABLE ; to repair this.
On 10/19/2012 11:52 AM, a bv wrote:
Hi on a log management server from the web interface i get the below
error
