Even though we don't know what exact query produces this, is there a way to raise it up to the MySQL team to take a look at? It seems to be more than a random occurrence. Thanks.
Richard Gabriel Director of Technology, CoreSense Inc. (518) 306-3043 x3951 ----- Original Message ----- From: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> To: "Richard Gabriel" <[EMAIL PROTECTED]> Sent: Sunday, August 04, 2002 3:16 PM Subject: Ynt: table error 127 > *This message was transferred with a trial version of CommuniGate(tm) Pro* > i got same err (once) on winNT (sp6) when i upgraded from 3.23.47 >> > 4.0.12. everything is OK for a long time... > > > ----- Original Message ----- > From: Richard Gabriel <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]>; Jonathan Patton <[EMAIL PROTECTED]> > Cc: <[EMAIL PROTECTED]> > Sent: Monday, August 04, 2003 9:10 PM > Subject: Re: table error 127 > > > > *This message was transferred with a trial version of CommuniGate(tm) Pro* > > I have been getting this type of error ever since I upgraded from MySQL 3 > to > > 4. I actually have set up a cron to check/repair tables hourly because of > > this. The following diagnoses have been suggested, but I would bet it's > an > > obscure MySQL bug: > > > > 1. Kernel 2.4.18 IO problem > > 2. Another shared library linked to MySQL (I use RPMs) > > 3. RAID issue causing corruption > > > > Unfortunately I haven't been able to pinpoint which query causes the issue > > so I can't report a bug. It anyone else has experienced this or has > > information on it, I would really appreciate it. Thanks. > > > > Richard Gabriel > > Director of Technology, > > CoreSense Inc. > > (518) 306-3043 x3951 > > > > ----- Original Message ----- > > From: "walt" <[EMAIL PROTECTED]> > > To: "Jonathan Patton" <[EMAIL PROTECTED]> > > Cc: <[EMAIL PROTECTED]> > > Sent: Monday, August 04, 2003 12:11 PM > > Subject: Re: table error 127 > > > > > > > Jonathan Patton wrote: > > > > > > > > I have mysql setup on two computers with identical databases. When I > run > > a group of queries on the one computer I get back an error 127 which I > > checked on an it appears to be a table corruption error. On the other > > computer, the queries run fine. Since I had all the data for the table in > > question in a data file, I just dropped the table and recreated it. The > > error still appeared. Any suggestions on what to try next? The only other > > thing I can think of is to compare the mysql versions to see if I have an > > older version on the other computer. > > > > > > Jonathan, > > > Have you tried running myisamchk on the database in question before > > > running queries on it? > > > > > > walt > > > > > > -- > > > MySQL General Mailing List > > > For list archives: http://lists.mysql.com/mysql > > > To unsubscribe: > > http://lists.mysql.com/[EMAIL PROTECTED] > > > > > > > > > > > > -- > > MySQL General Mailing List > > For list archives: http://lists.mysql.com/mysql > > To unsubscribe: > http://lists.mysql.com/[EMAIL PROTECTED] > > > > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
