Bug #49155 | mysql doesn't start normaly after altering innodb table to be compressed | ||
---|---|---|---|
Submitted: | 27 Nov 2009 3:30 | Modified: | 2 Feb 2010 3:41 |
Reporter: | Goki Honjo | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Server: InnoDB Plugin storage engine | Severity: | S1 (Critical) |
Version: | 5.4.3-0 | OS: | Linux (CentOS 4.8) |
Assigned to: | CPU Architecture: | Any | |
Tags: | compression, innodb |
[27 Nov 2009 3:30]
Goki Honjo
[27 Nov 2009 4:21]
Valeriy Kravchuk
Thank you for the problem report. Please, send complete CREATE TABLE statement for the problematic table.
[27 Nov 2009 5:41]
Goki Honjo
Here's the CREATE TABLE statement executed when originally the table was created. CREATE TABLE IF NOT EXISTS `item` ( `item_id` int(10) unsigned NOT NULL AUTO_INCREMENT, `itemNumber` int(8) unsigned zerofill NOT NULL DEFAULT '00000000', `itemPrice` int(10) unsigned NOT NULL DEFAULT '0', `imageFlag` tinyint(1) NOT NULL DEFAULT '0', `shop_id` mediumint(9) unsigned NOT NULL DEFAULT '0', `genreId` int(11) NOT NULL DEFAULT '0', `get_date` int(10) NOT NULL DEFAULT '0', `get_date_micro` mediumint(6) NOT NULL DEFAULT '0', PRIMARY KEY (`item_id`), UNIQUE KEY `itemNumber` (`itemNumber`,`shop_id`), KEY `item_genreId` (`genreId`), KEY `itemPrice` (`itemPrice`), KEY `get_date` (`get_date`), KEY `shopCode` (`shop_id`) ) ENGINE=InnoDB DEFAULT CHARSET=ujis AUTO_INCREMENT=1 ;
[30 Nov 2009 10:22]
Sveta Smirnova
Thank you for the feedback. I can not repeat problem with just create/alter statements. You wrote you originally created table in version 5.1.28-0, but InnoDB Plugin is only included into MySQL releases since version 5.1.38. Did you install InnoDB Plugin with version 5.1.28 yourself? Did you use Barracuda format originally? If yes, please, indicate packages of MySQL server and InnoDB you used.
[1 Dec 2009 5:06]
Goki Honjo
When I made the table in MySQL 5.1.28, I used InnoDB not as Plugin. Installed packages were downloaded from mysql.com download page. I created the table as InnoDB in 5.1.28, inserted records into it. Then, I upgraded to MySQL 5.4.3. 5.4.3 recognized innodb data file (*.ibd, *.frm, ib_data and ib_logfile) created in 5.1.28, so the upgrading was completed without dumping the table and importing.
[1 Dec 2009 8:46]
Sveta Smirnova
Thank you for the feedback. Moving ib* files, then use another format is not recommended. Although I can not repeat described behavior with dummy data and crash is not good anyway. Please send us minimal dump of data problem is repeatable with, so we can repeat the problem on our side.
[2 Jan 2010 0: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".
[3 Feb 2010 0: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".