My database experiences a similar effect, but I can't pinpoint the specific queries because it gets thousands per second. I have not noticed the problem on a machine that is only used occasionally. Is there a way to get queries out of the binlog for a specific date/time range? That might help me pinpoint the problem and ultimately get this resolved. Thanks.
Richard Gabriel Director of Technology, CoreSense Inc. (518) 306-3043 x3951 ----- Original Message ----- From: "Jonathan Patton" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Tuesday, August 05, 2003 8:58 AM Subject: RE: table error 127 Walt, Thanks for the suggestion. I ran myisamchk on the table and it said it was corrupted. So I ran myismachk on the table with the -r and it said the table was fixed. I then ran the update queries I was running before and received the same 127 error. The update queries were: update discussion_categories discussion_categories1, discussion_categories set discussion_categories1.parent_1 = discussion_categories.category_id where discussion_categories1.`parent_1_text` = discussion_categories.name; update discussion_categories discussion_categories1, discussion_categories set discussion_categories1.parent_2 = discussion_categories.category_id where discussion_categories1.`parent_2_text` = discussion_categories.name; update discussion_categories discussion_categories1, discussion_categories set discussion_categories1.parent_3 = discussion_categories.category_id where discussion_categories1.`parent_3_text` = discussion_categories.name; update discussion_categories discussion_categories1, discussion_categories set discussion_categories1.parent_4 = discussion_categories.category_id where discussion_categories1.`parent_4_text` = discussion_categories.name; So I shut the mysql server down, ran mysqlchk again and all the tables were okay. I had a backup of the database, so I just dropped the whole thing and imported from the backup. (The backup comes from another mysql server). The errors still persisted. The table in question only has 167 rows in it. I had a text file as well with the data in it, so I deleted all the data from the file and loaded the data with the load data infile command. I did get 1300 some warnings. Could the data being loaded in cause a table corruption? I'm going to go through the 169 rows being loaded to see if I can find out the problem or at least eliminate that problem from this problem. Also, could it be the backup is corrupted? Jonathan > -----Original Message----- > From: walt [mailto:[EMAIL PROTECTED] > Sent: Monday, August 04, 2003 12:12 PM > To: Jonathan Patton > Cc: [EMAIL PROTECTED] > 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]
