Run this - repair table SystemEvents use_frm ;

On Thu, May 19, 2011 at 10:24 AM, Ramesh <rames...@gmail.com> wrote:

> mysql> repair table SystemEvents.frm;
>
> +------------------+--------+----------+----------------------------------------+
> | Table            | Op     | Msg_type |
> Msg_text                               |
>
> +------------------+--------+----------+----------------------------------------+
> | SysEvents.frm | repair | Error    | Table 'SysEvents.frm' doesn't exist |
> | SysEvents.frm | repair | error    |
> Corrupt                                |
>
> +------------------+--------+----------+----------------------------------------+
> 2 rows in set (0.00 sec)
>
> But the SysEvents.frm is there in the datadir.
>
>
>
> On 19 May 2011 09:35, Suresh Kuna <sureshkumar...@gmail.com> wrote:
>
>> use repair table table_name use_frm ;  and try it out.
>>
>> It needs to be run inside mysql.
>>
>>
>> On Thu, May 19, 2011 at 9:30 AM, Ramesh <rames...@gmail.com> wrote:
>>
>>> Hi,
>>>
>>> I am trying to repair the table and i got this error
>>>
>>> I tried with myisamchk  --rq --tmpdir=
>>> /var/lib/mysql/tablog/TabEvents.MYI
>>>
>>> [root@uidsyslog001 mysql]# myisamchk --rq --tmpdir=/var/lib/mysql
>>> /var/lib/mysql/tablog/TabEvents.MYI
>>> check record delete-chain
>>> - recovering (with sort) MyISAM-table
>>>  /var/lib/mysql/tablog/TabEvents.MYI
>>> Data records: 58354301
>>> - Fixing index 1
>>> Wrong bytesec: 0- 0- 0 at 15899573240; Skipped
>>> MyISAM-table '/var/lib/mysql/Syslog/SystemEvents.MYI' is not fixed
>>> because
>>> of errors
>>> Try fixing it by using the -safe-recover (-o), the --force (-f) option or
>>> by
>>> not using the --quick (-q) flag
>>>
>>> Then i tried the below one
>>>
>>> [root@> myisamchk  --safe-recover --force --tmpdir=/var/lib/mysql
>>> /var/lib/mysql/tablog/TabEvents.MYI
>>> - recovering (with keycache) MyISAM-table '/var/lib/mysql
>>> /var/lib/mysql/tablog/TabEvents.MYI'
>>> Data records: 78918751
>>> Wrong bytesec:   0-  0-  0 at 15899573240; Skipped
>>> Data records: 82882799
>>>
>>> What might be the problem and how to make the table repair successfully.
>>>
>>> Guidance needed
>>>
>>> Thanks
>>> Ramesh
>>>
>>
>>
>>
>> --
>> Thanks
>> Suresh Kuna
>> MySQL DBA
>>
>
>


-- 
Thanks
Suresh Kuna
MySQL DBA

Reply via email to