MyISAM Repair table problem
MyISAM Repair table problem
am 19.05.2011 06:00:10 von Ramesh
--0016e6db2a8fcc3b6a04a3990b4c
Content-Type: text/plain; charset=ISO-8859-1
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
--0016e6db2a8fcc3b6a04a3990b4c--
Re: MyISAM Repair table problem
am 19.05.2011 06:05:34 von sureshkumarilu
--bcaec5158ff7f4fb7d04a3991d97
Content-Type: text/plain; charset=ISO-8859-1
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 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
--bcaec5158ff7f4fb7d04a3991d97--
Re: MyISAM Repair table problem
am 19.05.2011 06:54:44 von Ramesh
--0016e6dd9771f1f83e04a399ceae
Content-Type: text/plain; charset=ISO-8859-1
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 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 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
>
--0016e6dd9771f1f83e04a399ceae--
Re: MyISAM Repair table problem
am 19.05.2011 07:00:07 von sureshkumarilu
--bcaec548a60901cb5704a399e13e
Content-Type: text/plain; charset=ISO-8859-1
Run this - repair table SystemEvents use_frm ;
On Thu, May 19, 2011 at 10:24 AM, Ramesh 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 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 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
--bcaec548a60901cb5704a399e13e--
Re: MyISAM Repair table problem
am 19.05.2011 07:41:22 von Ramesh
--001485f9a7c8b79f7a04a39a753d
Content-Type: text/plain; charset=ISO-8859-1
Lost all the records once i done the repair table with use_frm.
On 19 May 2011 10:30, Suresh Kuna wrote:
> Run this - repair table SystemEvents use_frm ;
>
>
> On Thu, May 19, 2011 at 10:24 AM, Ramesh 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 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 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
>
--001485f9a7c8b79f7a04a39a753d--
Re: MyISAM Repair table problem
am 19.05.2011 07:46:34 von sureshkumarilu
--bcaec5158ff72b3cc004a39a87f2
Content-Type: text/plain; charset=ISO-8859-1
Can you paste the table files in the datadir and the execution part of the
below query.
On Thu, May 19, 2011 at 11:11 AM, Ramesh wrote:
>
> Lost all the records once i done the repair table with use_frm.
>
> On 19 May 2011 10:30, Suresh Kuna wrote:
>
>> Run this - repair table SystemEvents use_frm ;
>>
>>
>> On Thu, May 19, 2011 at 10:24 AM, Ramesh 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 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 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
>>
>
>
--
Thanks
Suresh Kuna
MySQL DBA
--bcaec5158ff72b3cc004a39a87f2--
Re: MyISAM Repair table problem
am 19.05.2011 07:46:34 von Ramesh
--001485f9a7c850713004a39a889b
Content-Type: text/plain; charset=ISO-8859-1
Is that index and all will be fine in that table, or have to create again?
On 19 May 2011 11:11, Ramesh wrote:
>
> Lost all the records once i done the repair table with use_frm.
>
> On 19 May 2011 10:30, Suresh Kuna wrote:
>
>> Run this - repair table SystemEvents use_frm ;
>>
>>
>> On Thu, May 19, 2011 at 10:24 AM, Ramesh 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 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 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
>>
>
>
--001485f9a7c850713004a39a889b--
Re: MyISAM Repair table problem
am 19.05.2011 07:49:01 von sureshkumarilu
--bcaec547cbabe8a75504a39a8feb
Content-Type: text/plain; charset=ISO-8859-1
The index file will rebuild by using the above command.
On Thu, May 19, 2011 at 11:16 AM, Ramesh wrote:
> Is that index and all will be fine in that table, or have to create again?
>
> On 19 May 2011 11:11, Ramesh wrote:
>
>>
>> Lost all the records once i done the repair table with use_frm.
>>
>> On 19 May 2011 10:30, Suresh Kuna wrote:
>>
>>> Run this - repair table SystemEvents use_frm ;
>>>
>>>
>>> On Thu, May 19, 2011 at 10:24 AM, Ramesh 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 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 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
>>>
>>
>>
>
--
Thanks
Suresh Kuna
MySQL DBA
--bcaec547cbabe8a75504a39a8feb--