Bug #45443 mysql innodb error
Submitted: 11 Jun 2009 8:55 Modified: 16 Jul 2009 7:01
Reporter: Sunny Liu Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server: InnoDB storage engine Severity:S3 (Non-critical)
Version:5.0.67 OS:Linux (RedHat AS5 X64)
Assigned to: CPU Architecture:Any
Tags: innodb

[11 Jun 2009 8:55] Sunny Liu
Description:
InnoDB: Submit a detailed bug report to http://bugs.mysql.com
InnoDB: error in sec index entry update in
InnoDB: index `toId_fromId_creatorTime` of table `tximbase/receive472`
InnoDB: tuple DATA TUPLE: 4 fields;
 0: len 4; hex 81cdb5d8; asc     ;; 1: len 4; hex 80962c80; asc   , ;; 2: len 8; hex 80001245b59eef43; asc    E   C;; 3: len 4; hex 800f0744; asc    D;;

InnoDB: record PHYSICAL RECORD: n_fields 4; compact format; info bits 0
 0: len 4; hex 81cdb5d8; asc     ;; 1: len 4; hex 800003e8; asc     ;; 2: len 8; hex 80001245b580935e; asc    E   ^;; 3: len 4; hex 800ee285; asc     ;;

TRANSACTION 0 4287757491, ACTIVE 0 sec, process no 17761, OS thread id 1174124864 updating or deleting, thread declared inside InnoDB 499
mysql tables in use 1, locked 1
2 lock struct(s), heap size 368, undo log entries 1
MySQL thread id 81, query id 763933 192.168.0.104 waptx updating
delete  from receive472 where id=984900 and toId=30258648

How to repeat:
unknown
[11 Jun 2009 9:07] Sveta Smirnova
Thank you for the report.

But version 5.0.67 is old. Please try with current version 5.0.82 and if failure happens again provide output of SHOW CREATE TABLE receive472 and SHOW TABLE STATUS LIKE 'receive472'
[11 Jun 2009 9:08] Valeriy Kravchuk
Thank you for the problem report. Please, send your entire error log (compressed) and the results of:

show create table receive472\G
show table status like 'receive472'\G
[11 Jun 2009 10:24] Sunny Liu
mysql> show create table receive472\G
*************************** 1. row ***************************
       Table: receive472
Create Table: CREATE TABLE `receive472` (
  `id` int(11) NOT NULL default '0',
  `toId` int(11) NOT NULL default '0',
  `toName` varchar(32) NOT NULL default '',
  `fromId` int(11) NOT NULL default '0',
  `fromName` varchar(32) NOT NULL default '',
  `creatorTime` datetime NOT NULL,
  `msgState` tinyint(4) NOT NULL default '0',
  `msgType` int(11) NOT NULL default '0',
  `msgSubject` varchar(32) NOT NULL default '',
  `msgContent` mediumtext,
  `fromSource` varchar(32) NOT NULL default '',
  PRIMARY KEY  (`id`),
  KEY `toId_fromId_creatorTime` (`toId`,`fromId`,`creatorTime`),
  KEY `toId_creatorTime` (`toId`,`creatorTime`)
) ENGINE=InnoDB DEFAULT CHARSET=gbk
1 row in set (0.00 sec)

mysql> show table status like 'receive472'\G
*************************** 1. row ***************************
           Name: receive472
         Engine: InnoDB
        Version: 10
     Row_format: Compact
           Rows: 30549
 Avg_row_length: 292
    Data_length: 8929280
Max_data_length: 0
   Index_length: 3162112
      Data_free: 0
 Auto_increment: NULL
    Create_time: 2009-06-11 15:20:44
    Update_time: NULL
     Check_time: NULL
      Collation: gbk_chinese_ci
       Checksum: NULL
 Create_options: 
        Comment: InnoDB free: 4096 kB
1 row in set (0.05 sec)

mysql>
[12 Jun 2009 9:46] Sunny Liu
error log

Attachment: waptx124.waptx.com(1).rar (application/octet-stream, text), 56.64 KiB.

[16 Jun 2009 7:01] Sveta Smirnova
Thank you for the feedback.

Before error described you have in the error log file:

----<q>-----
090609 15:17:58  InnoDB: Error: trying to open a table, but could not
InnoDB: open the tablespace file './tximbase/receive472.ibd'!
InnoDB: Have you moved InnoDB .ibd files around without using the
InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?
----</q>----

Have you fixed this problem?
[16 Jul 2009 23:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".