| Bug #67287 | Server crashes on INSERT into an InnoDB table | ||
|---|---|---|---|
| Submitted: | 18 Oct 2012 13:42 | Modified: | 19 Oct 2012 10:44 |
| Reporter: | Dario Kampkaspar | Email Updates: | |
| Status: | Duplicate | Impact on me: | |
| Category: | MySQL Server: General | Severity: | S2 (Serious) |
| Version: | 5.6.7 | OS: | Windows (Server 2003 (SP2)) |
| Assigned to: | CPU Architecture: | Any | |
[18 Oct 2012 13:42]
Dario Kampkaspar
[18 Oct 2012 14:34]
MySQL Verification Team
Thank you for the bug report. I can't repeat, please provide your my.ini file. Thanks.
d:\tmp\mysql-5.6.7-rc-winx64\bin>mysql -uroot
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 1
Server version: 5.6.7-rc-debug MySQL Community Server - Debug (GPL)
Copyright (c) 2000, 2012, Oracle and/or its affiliates. All rights reserved.
Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
mysql> create database katalog;
Query OK, 1 row affected (0.00 sec)
mysql> use katalog
Database changed
mysql> CREATE TABLE IF NOT EXISTS `slw` (
-> `003` bigint(20) unsigned NOT NULL AUTO_INCREMENT COMMENT 'ID',
-> `004` timestamp NOT NULL DEFAULT '0000-00-00 00:00:00' COMMENT 'Erstellungsdatum',
-> `007` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP COMMENT 'Ã"nderung',
-> `7W0` varchar(250) CHARACTER SET utf8 COLLATE utf8_german2_ci NOT NULL COMMENT 'Schlagwort / Norm FT',
-> `7W1` varchar(250) CHARACTER SET utf8 COLLATE utf8_german2_ci DEFAULT NULL COMMENT 'Schlagwort / lokal FT',
-> `7W2` text COLLATE utf8_unicode_ci COMMENT 'Beschreibung / Definition',
-> `7Wo` bigint(20) unsigned DEFAULT NULL COMMENT 'Oberbegriff',
-> `7Wc` varchar(1) COLLATE utf8_unicode_ci NOT NULL COMMENT 'Schlagwortart',
-> `7Wz` text COLLATE utf8_unicode_ci COMMENT 'allgem. Bemerkungen',
-> `z` tinyint(1) NOT NULL DEFAULT '0',
-> PRIMARY KEY (`003`),
-> KEY `7Wo` (`7Wo`),
-> FULLTEXT KEY `idx` (`7W0`,`7W1`)
-> ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci COMMENT='Schlagwort-Stammsätze' AUTO_INCREMENT=1 ;
Query OK, 0 rows affected (0.30 sec)
mysql> INSERT INTO `katalog`.`slw` (`003`, `004`, `007`, `7W0`, `7W1`, `7W2`, `7Wo`, `7Wc`, `7Wz`, `z`) VALUES (NULL, '0000-00-00 00:00:00', CURRENT_TIMEST
AMP, 'tes2', NULL, NULL, NULL, '', NULL, '0');
Query OK, 1 row affected (0.02 sec)
mysql> show variables like "%version%";
+-------------------------+--------------------------------------+
| Variable_name | Value |
+-------------------------+--------------------------------------+
| innodb_version | 1.2.7 |
| protocol_version | 10 |
| slave_type_conversions | |
| version | 5.6.7-rc-debug |
| version_comment | MySQL Community Server - Debug (GPL) |
| version_compile_machine | x86_64 |
| version_compile_os | Win64 |
+-------------------------+--------------------------------------+
7 rows in set (0.01 sec)
mysql>
[18 Oct 2012 15:06]
Dario Kampkaspar
Thank you for the quick reply! I am puzzled myself, as the same settings and DB work on my development machine. Here is my my.ini (only comments removed): [client] no-beep port=3306 [mysql] default-character-set=utf8 [mysqld] port=3306 basedir="C:\Programme\MySQL\MySQL Server 5.6\" datadir="D:\mySQL-Data\data\" character-set-server=utf8 default-storage-engine=INNODB sql-mode="STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION" log-output=FILE general-log=0 general_log_file="SERVER.log" slow-query-log=1 slow_query_log_file="SERVER-slow.log" long_query_time=5 log-bin="SERVER-bin" log-error="SERVER.err" max_connections=100 query_cache_size=0 table_open_cache=256 tmp_table_size=6M thread_cache_size=8 myisam_max_sort_file_size=100G myisam_sort_buffer_size=8M key_buffer_size=8M read_buffer_size=17K read_rnd_buffer_size=256K sort_buffer_size=243K innodb_additional_mem_pool_size=2M innodb_flush_log_at_trx_commit=1 innodb_log_buffer_size=1M innodb_buffer_pool_size=14M innodb_log_file_size=10M innodb_thread_concurrency=8 binlog-do-db=katalog --- If there is anything else you need, please let me know.
[18 Oct 2012 16:41]
MySQL Verification Team
Thank you for the feedback. I can't repeat, I did my test with a complete fresh data stuff (shipped with the package). Please test in this way. Thanks.
[18 Oct 2012 22:36]
MySQL Verification Team
iirc win2003 and xp will have a problem with this when log-bin is enabled. there's an internal bug for it, which may even be fixed in the current source.
[19 Oct 2012 10:05]
Dario Kampkaspar
Shane: You were right! After disabling binlog, everything works smoothly :) This bug should be marked as a duplicate of it, then. Thanks all for your support!
[19 Oct 2012 10:44]
MySQL Verification Team
Duplicate of internal bugs: Bug 14640486 - MISSING INITIALIZATION OF MYSQL_BIN_LOG::M_PREP_XIDS_COND Bug 14126548 - CANNOT ENABLE BINARY LOGGING ON XP OR WIN2003, CRASHES IN DEC_PREP_XIDS Fix will be available in 5.6.8.
