Re: InnoDB: a detailed bug report

[Willie D. Leiva]

On Thu, 5 Dec 2002, Heikki Tuuri wrote:

> the table definition below does not match the index records below. In the
> index records one of the datetime columns seems to appear twice.

Heikki, you are right. The old definition of that MySQl table had two
columns twice. When I REgenerated the table, with the definition sent
to you, I deleted the second insertion of those columns.

Thanks for detecting the reason of this error.

Kind regards,
Willie


-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Re: InnoDB: a detailed bug report

[Willie D. Leiva]

On Wed, 4 Dec 2002, Heikki Tuuri wrote:

> what MySQL version you are running? On what OS?

Version 3.23.53-max-nt-log on Windows Professional 2000

> What does SHOW CREATE TABLE tabdocumentoconsultado; print?

I created again all the tables of the database called "bdatena".

Now that the table is no more corrupt, it prints

Create Table: CREATE TABLE `tabdocumentoconsultado` (
  `IdDocConsultado` int(11) NOT NULL auto_increment,
  `IdAprendiz` varchar(15) NOT NULL default '',
  `codcurso` int(11) NOT NULL default '0',
  `IdP` int(11) NOT NULL default '0',
  `DiaHoraInicial` datetime NOT NULL default '-00-00 00:00:00',
  `Tipo` enum('Cur','Top','UE') NOT NULL default 'Top',
  `DiaHoraFinal` datetime default NULL,
  `EmPausa` enum('S','N') NOT NULL default 'N',
  PRIMARY KEY  (`IdDocConsultado`),
  UNIQUE KEY `umDoc` (`IdAprendiz`,`codcurso`,`IdP`,
   `DiaHoraInicial`,`Tipo`,`DiaHoraFinal`,`EmPausa`),
  KEY `DoConsInd` (`IdAprendiz`,`codcurso`),
  FOREIGN KEY (`IdAprendiz`, `codcurso`)
  REFERENCES `bdatena.cursa` (`idaluno`, `codcurso`)
) TYPE=InnoDB

> Have you used an InnoDB version <= 3.23.43 and stored characters with code >
> 127 in the table? E.g., accent characters? The ordering of such characters
> in the latin1 charset changed in 3.23.44.

In other tables, I stored accent characters.

In tabdocumentoconsultado (in English, something like
ConsultedDocumentTable), I don't store characters with code > 127.

How do I discover the InnoDB version? I don't know its version.

> What kind of operations you did to the table? INSERT, UPDATE, DELETE?

INSERT and UPDATE.

> Can you repeat the corruption starting from a fresh table?

The corruption didn't happen again with a fresh table.

> You can repair the corruption by dump + DROP + CREATE + import of the table.

Thanks for the hint!

Regards,
Willie D. Leiva



-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

InnoDB: a detailed bug report

[Willie D. Leiva]

MySQL generated the following error messages about a corrupted table:

/
021127 15:48:01  InnoDB: Started
InnoDB: error in sec index entry update in
InnoDB: index umDoc table bdatena/tabdocumentoconsultado
InnoDB: tuple  0: len 8; hex 6c616e6472616465; asc landrade;; 1: len 4;
hex 800b; asc ;; 2: len 4; hex 8014; asc ;; 3: len 8;
hex 800012358ca4940c; asc ...5;; 4: len 1; hex 02; asc .;; 5: len 8;
hex 800012358ca4d9c4; asc ...5..Ù.;; 6: len 1; hex 02; asc .;; 7: len 8;
hex 800012358ca4d9c4; asc ...5..Ù.;; 8: len 1; hex 01; asc .;; 9: len 4;
hex 802b; asc ...+;;
InnoDB: record RECORD: info bits 0 0: len 8; hex 6c616e6472616465; asc
landrade;; 1: len 4; hex 800b; asc ;; 2: len 4; hex 8014;
asc ;; 3: len 8; hex 800012358ca4940c; asc ...5;; 4: len 1; hex
02; asc .;; 5: len 8; hex 800012358ca4d9c4; asc ...5..Ù.;; 6: len 1; hex
02; asc .;; 7: len 8; hex 800012358ca49424; asc ...5...$;; 8: len 1; hex
01; asc .;; 9: len 4; hex 802b; asc ...+;;
TRANSACTION 0 672018, ACTIVE 0 sec, OS thread id 2532 updating or
deleting
3 lock struct(s), heap size 320, undo log entries 1
MySQL thread id 75, query id 17086 localhost 127.0.0.1 atena updating
UPDATE tabdocumentoconsultado SET EmPausa='N' WHERE
IdAprendiz='landrade' AND Tipo='Top' AND codcurso='11' AND
IdP='20'

InnoDB: Make a detailed bug report and send it
InnoDB: to [EMAIL PROTECTED]
InnoDB: error in sec index entry update in
InnoDB: index umDoc table bdatena/tabdocumentoconsultado
InnoDB: tuple  0: len 8; hex 6c616e6472616465; asc landrade;; 1: len 4;
hex 800b; asc ;; 2: len 4; hex 8014; asc ;; 3: len 8;
hex 800012358ca4c6fe; asc ...5;; 4: len 1; hex 02; asc .;; 5: len 8;
hex 800012358ca4d9c4; asc ...5..Ù.;; 6: len 1; hex 02; asc .;; 7: len 8;
hex 800012358ca4d9c4; asc ...5..Ù.;; 8: len 1; hex 01; asc .;; 9: len 4;
hex 802c; asc ...,;;
InnoDB: record RECORD: info bits 0 0: len 8; hex 6c616e6472616465; asc
landrade;; 1: len 4; hex 800b; asc ;; 2: len 4; hex 8014;
asc ;; 3: len 8; hex 800012358ca4c6fe; asc ...5;; 4: len 1; hex
02; asc .;; 5: len 8; hex 800012358ca4d9c4; asc ...5..Ù.;; 6: len 1; hex
02; asc .;; 7: SQL NULL; 8: len 1; hex 01; asc .;; 9: len 4; hex
802c; asc ...,;;
TRANSACTION 0 672018, ACTIVE 0 sec, OS thread id 2532 updating or
deleting
6 lock struct(s), heap size 1024, undo log entries 2
MySQL thread id 75, query id 17086 localhost 127.0.0.1 atena updating
UPDATE tabdocumentoconsultado SET EmPausa='N' WHERE
IdAprendiz='landrade' AND Tipo='Top' AND codcurso='11' AND
IdP='20'

InnoDB: Make a detailed bug report and send it
InnoDB: to [EMAIL PROTECTED]
InnoDB: error in sec index entry update in
InnoDB: index umDoc table bdatena/tabdocumentoconsultado
InnoDB: tuple  0: len 8; hex 6c616e6472616465; asc landrade;; 1: len 4;
hex 800b; asc ;; 2: len 4; hex 8014; asc ;; 3: len 8;
hex 800012358ca4c6ff; asc ...5;; 4: len 1; hex 02; asc .;; 5: len 8;
hex 800012358ca4d9c4; asc ...5..Ù.;; 6: len 1; hex 02; asc .;; 7: len 8;
hex 800012358ca4d9c4; asc ...5..Ù.;; 8: len 1; hex 01; asc .;; 9: len 4;
hex 802d; asc ...-;;
InnoDB: record RECORD: info bits 0 0: len 8; hex 6c616e6472616465; asc
landrade;; 1: len 4; hex 800b; asc ;; 2: len 4; hex 8014;
asc ;; 3: len 8; hex 800012358ca4c6ff; asc ...5;; 4: len 1; hex
02; asc .;; 5: len 8; hex 800012358ca4d9c4; asc ...5..Ù.;; 6: len 1; hex
02; asc .;; 7: SQL NULL; 8: len 1; hex 01; asc .;; 9: len 4; hex
802d; asc ...-;;
TRANSACTION 0 672018, ACTIVE 0 sec, OS thread id 2532 updating or
deleting
6 lock struct(s), heap size 1024, undo log entries 3
MySQL thread id 75, query id 17086 localhost 127.0.0.1 atena updating
UPDATE tabdocumentoconsultado SET EmPausa='N' WHERE
IdAprendiz='landrade' AND Tipo='Top' AND codcurso='11' AND
IdP='20'

InnoDB: Make a detailed bug report and send it
InnoDB: to [EMAIL PROTECTED]
InnoDB: error in sec index entry update in
InnoDB: index umDoc table bdatena/tabdocumentoconsultado
InnoDB: tuple  0: len 8; hex 6c616e6472616465; asc landrade;; 1: len 4;
hex 800b; asc ;; 2: len 4; hex 8014; asc ;; 3: len 8;
hex 800012358ca4940c; asc ...5;; 4: len 1; hex 02; asc .;; 5: len 8;
hex 800012358ca4da6e; asc ...5..Ún;; 6: len 1; hex 02; asc .;; 7: len 8;
hex 800012358ca4da6e; asc ...5..Ún;; 8: len 1; hex 01; asc .;; 9: len 4;
hex 802b; asc ...+;;
InnoDB: record RECORD: info bits 0 0: len 8; hex 6c616e6472616465; asc
landrade;; 1: len 4; hex 800b; asc ;; 2: len 4; hex 8014;
asc ;; 3: len 8; hex 800012358ca4940c; asc ...5;; 4: len 1; hex
02; asc .;; 5: len 8; hex 800012358ca4da6e; asc ...5..Ún;; 6: len 1; hex
02; asc .;; 7: len 8; hex 800012358ca4d9c4; asc ...5..Ù.;; 8: len 1; hex
01; asc .;; 9: len 4; hex 802b; asc ...+;;
TRANSACTION 0 672061, ACTIVE 0 sec, OS thread id 2324 updating or
deleting
3 lock struct(s), heap size 320, undo log entries 1
MySQL thread id 76, qu