Re: Can't recover a bad corrupeted table...

2001-04-03 Thread Antonio Gulli
Un update, the problem was solved thanks to Gerald Clarke and Bob Hall. They said: t(6), date date, origine varchar(16)); "The use of a reserved word as a column name probably is the reason that your table is corrupted as soon as it is created." I also declared some fields to be

Re: Can't recover a bad corrupeted table...

2001-04-02 Thread Bob Hall
>Hello Bob, first at all thank you for your support. > >Bob Hall wrote: > >>Let me see if I understand you correctly. You created a new table >>(CREATE TABLE?) and you imported data from a file that had nothing >>to do with MySQL (comma or tab delimited file?), and therefore >>couldn't be affec

Re: Can't recover a bad corrupeted table...

2001-04-02 Thread Gerald Clark
'date' is a reserved word. Try renaming your date column, and see if the problem remains. Antonio Gulli wrote: > > Hello Bob, first at all thank you for your support. > > Bob Hall wrote: > > > Let me see if I understand you correctly. You created a new table > > (CREATE TABLE?) and you importe

Re: Can't recover a bad corrupeted table...

2001-03-31 Thread Antonio Gulli
Hello Bob, first at all thank you for your support. Bob Hall wrote: > Let me see if I understand you correctly. You created a new table > (CREATE TABLE?) and you imported data from a file that had nothing to > do with MySQL (comma or tab delimited file?), and therefore couldn't > be affected

Re: Can't recover a bad corrupeted table...

2001-03-31 Thread Bob Hall
Let me see if I understand you correctly. You created a new table (CREATE TABLE?) and you imported data from a file that had nothing to do with MySQL (comma or tab delimited file?), and therefore couldn't be affected by whatever crashed your server. And this brand new table with pristine data

Re: Can't recover a bad corrupeted table...

2001-03-30 Thread Antonio Gulli
I tried -r I tried -o I tried to truncate the table and re-build the index from scratch. I tried to create ex-novo a table, import data from scratch and it result in a corrupted table. None of these seems to work Bob Hall wrote: > Sir, I looked quickly through the mass of data supplied below,

Re: Can't recover a bad corrupeted table...

2001-03-30 Thread Bob Hall
Sir, I looked quickly through the mass of data supplied below, and it looks like you only tried myisamchk with the -r -q option combination. Try it with just -r. If that doesn't work, try it with -o. If that doesn't work, restore from backup. Got backup? Bob Hall >Antonio gulli wrote: > > >

Can't recover a bad corrupeted table...

2001-03-29 Thread Antonio gulli
Antonio gulli wrote: > Any help is appreciated > > Welcome to the MySQL monitor. Commands end with ; or \g. > Your MySQL connection id is 158 to server version: 3.23.36-log > > myisamchk -V > myisamchk Ver 1.45 for pc-linux-gnu at i686 > > a) Trying a recovery. > > myisamchk -r -q -Osort_k

Can't recover a bad corrupeted table...

2001-03-29 Thread Antonio gulli
Any help is appreciated Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 158 to server version: 3.23.36-log myisamchk -V myisamchk Ver 1.45 for pc-linux-gnu at i686 a) Trying a recovery. myisamchk -r -q -Osort_key_blocks=16 keywords - check key delete