Bug #32935 Index Bug Errors
Submitted: 3 Dec 2007 15:30 Modified: 10 Dec 2007 13:52
Reporter: Melissa Dougherty Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Server: InnoDB storage engine Severity:S2 (Serious)
Version:5.0.46 OS:Any
Assigned to: Assigned Account CPU Architecture:Any

[3 Dec 2007 15:30] Melissa Dougherty
Description:
The following error was in the db error log.  I check the tables and get no errors.  Is this a real bug?

InnoDB: error in sec index entry update in
InnoDB: index `SLIDE_OBJ_INDEX` of table `vsde_2/vsde_fs_objects`
InnoDB: tuple DATA TUPLE: 2 fields;
 0: len 129; hex 2f67726f7570732f44657374696e792f44657374696e7920436f6e636570742053747564792f44657369676e20526576696577732f496e746572696d2044657369676e20526576696577202d2044656320323030372f47726f756e642053797374656d73204944522070726573656e746174696f6e202843617270656e74657229; asc /groups/Destiny/Destiny Concept Study/Design Reviews/Interim Design Review - Dec 2007/Ground Systems IDR presentation (Carpenter);; 1: len 129; hex 2f67726f7570732f44657374696e792f44657374696e7920436f6e636570742053747564792f44657369676e20526576696577732f496e746572696d2044657369676e20526576696577202d2044656320323030372f47726f756e642053797374656d73204944522070726573656e746174696f6e202843617270656e74657229; asc /groups/Destiny/Destiny Concept Study/Design Reviews/Interim Design Review - Dec 2007/Ground Systems IDR presentation (Carpenter);;

InnoDB: record PHYSICAL RECORD: n_fields 2; compact format; info bits 0
 0: len 30; hex 2f67726f7570732f44657374696e792f44657374696e7920436f6e636570; asc /groups/Destiny/Destiny Concep;...(truncated); 1: len 30; hex 2f67726f7570732f44657374696e792f44657374696e7920436f6e636570; asc /groups/Destiny/Destiny Concep;...(truncated);

TRANSACTION 0 258849917, ACTIVE 22 sec, OS thread id 12432 updating or deleting, thread declared inside InnoDB 499
mysql tables in use 1, locked 1
37 lock struct(s), heap size 2496, undo log entries 44
MySQL thread id 40, query id 101584 localhost 127.0.0.1 root updating
delete from vsde_fs_objects where uri= '/groups/Destiny/Destiny Concept Study/Design Reviews/Interim Design Review - Dec 2007/Ground Systems IDR presentation (Carpenter)'

How to repeat:
I just upgraded on Wednesday, Nov 28 and I saw these errors.  Then I repaired the tables and thought it was gone.  Then on Sunday morning the errors came again.  Not sure how the errors are happening.
[3 Dec 2007 17:40] Heikki Tuuri
Melissa,

please post SHOW CREATE TABLE for the associated table.

Please post the entire .err log, so that we can see if there are any errors or warnings before these ones.

Regards,

Heikki
[5 Dec 2007 16:51] MySQL Verification Team
Could you please answer the questions done by Heikki. Thanks in advance.
[5 Dec 2007 17:55] Melissa Dougherty
Create Table

Attachment: table.sql (application/octet-stream, text), 2.86 KiB.

[5 Dec 2007 17:55] Melissa Dougherty
Error Log

Attachment: mysql.err (application/octet-stream, text), 194.80 KiB.

[5 Dec 2007 17:56] Melissa Dougherty
The requested files have been uploaded.
[5 Dec 2007 18:18] MySQL Verification Team
melissa, heikki, I repeated this bug on 5.0.46-enterprise.
[5 Dec 2007 18:20] MySQL Verification Team
some details when i repeated assertion + corruption

Attachment: bug32935_error_log_5.0.46_stack_trace.txt (text/plain), 98.83 KiB.

[5 Dec 2007 18:28] MySQL Verification Team
maybe this is bug #28138
[5 Dec 2007 18:48] Melissa Dougherty
If this is related to bug #28138, what is the suggested solution?  I just upgraded to 5.0.46 from 5.0.24.  What Enterprise version has the fix?
[5 Dec 2007 18:57] MySQL Verification Team
Hi Melissa!
So far I cannot repeat the corruptions on 5.0.50 or 5.0.48 in 20 minutes.  I'll leave the tests running overnight.  5.0.46 failed twice in 10 minutes.  Solution for you could be to dump/reload all tables into >=5.0.48

I'll post more definitive results here tomorrow.
[5 Dec 2007 19:24] Melissa Dougherty
Where can I download 5.0.50 Enterprise from the web?  All I see is 5.0.44 and 5.0.52.
[5 Dec 2007 19:32] MySQL Verification Team
5.0.52 will be just fine. it's contains the fix too.
[5 Dec 2007 19:39] Melissa Dougherty
I found 5.0.50 under previous releases.  I've already downloaded.  I'm going to install on DEV and test a couple days before upgrading production.  What is the worst thing that could happen from the bug?  Could the table data be corrupted?

Thanks.
[6 Dec 2007 7:14] MySQL Verification Team
I cannot repeat corruptions on 5.0.48 after 8 hours.  I think this is a duplicate of that bug I mentioned earlier.  Heikki do you agree after looking at the table/logs ?
[10 Dec 2007 13:52] Heikki Tuuri
I guess this is a duplicate of:

http://bugs.mysql.com/bug.php?id=28138