Rafa, I analyzed now the latest hex dumps.
The first error looks like that the peco/lincompras index ArtPrvFec tree is broken. The child page number is 0x0000041d, but the parent has a pointer to page 045d. In the error printout below the secondary index record contains a primary key column value JA030°2217 but the closest match in the primary index is JA03005191 The character 0xb0, or ° above is probably garbage. Like the previous time a week ago, this looks like single-byte corruption. Is the same InnoDB application running ok in another Windows server? You got corruption quickly, the log sequence number is only 2.6 GB. Best regards, Heikki Tuuri Innobase Oy http://www.innodb.com Foreign keys, transactions, and row level locking for MySQL InnoDB Hot Backup - a hot backup tool for MySQL Order MySQL technical support from https://order.mysql.com/ ----- Original Message ----- From: ""Heikki Tuuri"" <[EMAIL PROTECTED]> Newsgroups: mailing.database.myodbc Sent: Tuesday, September 09, 2003 2:47 PM Subject: Re: Innodb crash under Win2000 > Rafa, > > is this the server you suspected to have some hardware problem? > > Please send me the whole .err log for analysis. > > Best regards, > > Heikki > Innobase Oy > http://www.innodb.com > InnoDB - transactions, row level locking, and foreign keys for MySQL > InnoDB Hot Backup - a hot backup tool for MySQL > Order MySQL support from http://www.mysql.com/support/index.html > > ....................... > Subject: Innodb crash under Win2000 > From: rafarife.netscape.net > Date: Tue, 09 Sep 2003 07:25:23 -0400 > > > > Description: > Hello, > > We are working with mysqld-max-nt 4.0.14 under Win2000 service-pack4. > We have a server with two Pentium-III MMX 500Mhz proccesors and 780MB > Ram. > We work with InnoDB tables. We have reserved 300MB to InnoDB and use > a RAID 5. > > We were working when Mysql/Innodb crashed. We were not able to > connect to MySql. We noticed that There wasn´t the mysqld-max-nt > service (this service is manual) So, we ran the service. Then, I > tried to check the database but I lost the connection when I was > checking a determined table, lincompras. So I run the service again, > and altered the lincompras table type to myisam and later to innodb, > checked again the database and didn´t get any error. The error log file > is: > > InnoDB: Dump of the child page: > 030909 8:43:03 InnoDB: Page dump in ascii and hex (16384 bytes): > len 16384; hex 6068cb630000041d00000425000004210000000086968aac45 .... > > > > > We have been working without problems but when I have opened the error > log file I have seen the next error: > > > MySql: preparado para conexiones > 030909 12:05:22 InnoDB: error clustered record for sec rec not found > InnoDB: index CliFecArt table peco/linventas > InnoDB: sec index record RECORD: info bits 0 0: len 6; hex 303030333839; > asc 000389;; 1: len 3; hex 8fa6ac; asc .¦¬;; 2: len 8; hex > 3030343231343130; > asc 00421410;; 3: len 10; hex 4a41303330b032323137; asc JA030°2217;; 4: len > 10; > hex 58413033303033353134; asc XA03003514;; 5: len 2; hex 8001; asc â,¬.;; > InnoDB: clust index record RECORD: info bits 0 0: len 10; hex > 4a413033303035313931; > asc JA03005191;; 1: len 0; hex ; asc ;; 2: len 2; hex 8001; asc â,¬.;; 3: > len 6; > hex 0000005acd6e; asc ...ZÃ?n;; 4: len 7; hex 8000005c010084; asc > â,¬..\..â?z;; 5: len > 0; > hex ; asc ;; 6: len 3; hex 8fa729; asc .§);; 7: len 2; hex 3030; asc 00;; > 8: len 8; > > hex 3030323731303430; asc 00271040;; 9: len 32; > hex 524f4c4c4f203530204d54532e43494e5441205445534142414e442d34363631; > asc ROLLO 50 MTS.CINTA TESABAND-4661;; 10: len 8; hex 000000000000f03f; > asc ......ð?;; 11: len 1; hex 31; asc 1;; 12: len 8; hex 0000000000004a40; > asc ......J@;; > > 13: len 4; hex 00005242; asc ..RB;; 14: len 8; hex fca9f1d24d023640; asc > ü©ñÃ'M.6@;; > 15: > len 4; hex 00008041; asc ..â,¬A;; 16: len 4; hex 00000000; asc ....;; 17: > len 2; hex > 4547; > asc EG;; 18: len 3; hex 202020; asc ;; 19: len 4; hex 00000000; asc > ....;; 20: > TRANSACTION 0 5953488, ACTIVE 1 sec, OS thread id 1864 fetching rows, thread > declared > > inside InnoDB 415 > MySQL thread id 89, query id 54296 192.168.1.210 lourdes Sending data > SELECT `LinVentas`.`Can`, `LinVentas`.`MCa`, `LinVentas`.`Pre`, > `LinVentas`.`Dto`, > `Clientes`.`Ruta_Comercial`, `Ruta_Comercial`.`Nom`, `LinVentas`.`C > > InnoDB: Make a detailed bug report and send it > InnoDB: to [EMAIL PROTECTED] > > > > Any ideas? > > Thanks in advance, > Rafa > > How-To-Repeat: > - > > Fix: > - > > Synopsis:Innodb crash under win2000 > > Submitter-Id: <submitter ID> > Originator: Rafa > Organization: Pecomark > MySQL support: none > Severity: critical > Priority: medium > Category: mysqld-max-nt > Class: sw-bug > Release: mysqld 4.0.14 > > Exectutable: mysqld-max-nt > Environment: 2 Pentium III-MMX, 500 MHZ, 780 MB > System: Windows 2000 > Compiler: - > Architecture: i > > > -- > 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]
