Bug #79065 insert data into DB met error:"Fatal error encountered during command execution"
Submitted: 2 Nov 2015 8:27 Modified: 2 Dec 2015 9:15
Reporter: Tina Du Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server Severity:S3 (Non-critical)
Version:5.5 OS:Any
Assigned to: Assigned Account CPU Architecture:Any

[2 Nov 2015 8:27] Tina Du
Description:
met error when insert data into table by using method: ExecuteNonQuery() sometimes  with error message "Fatal error encountered during command execution". And the SQL statement can be executed successfully by using MYSQL client tools, and similar SQL statement can also executed successfully through .net program, but the error happened sometimes with no regular,please help to check the reason. thanks.
the example SQL statement is as below:
insert into location(TagType,Tagmsxxx,MapId,AreaId,CoordinateType,X,Y,Z,Time,IsOnline,Statu,OfflineReason,Orders,buildingId,CreateTime,apId,Brand,PointType,ScanType, AssocBssid, RadioMac, RadioType, Rssi, RssiType, RxChannel, TxChannel,ApSsid, SsidEncryptType, PlaceNo, DeviceNo, Identity, IdentityType, Latitude, Longitude)                                   values(6,'XXX:XXX:XXX:XX:XX:XX',2,-3,2,742,456,0,'2015/10/30 11:58:44',True,'1',0,0,2,now(),'70:65:82:8E:C9:70','',1,2,'00:00:00:00:00:00',False,False,0,-106,2,'XX:XX:XX:XX:XX:XX','b/g/n',-57,1,11,11,'air-freewifi','5','12345623654321','1','','','31.226255','121.490874') 
and the table creation script is:
CREATE TABLE `location` (
	`Id` INT(11) NOT NULL AUTO_INCREMENT,
	`TagType` INT(11) NULL DEFAULT NULL,
	`Tagmsxxx` VARCHAR(50) NULL DEFAULT NULL,
	`MapId` INT(11) NULL DEFAULT NULL ,
	`AreaId` INT(11) NULL DEFAULT NULL ,
	`CoordinateType` INT(5) NULL DEFAULT NULL ,
	`X` INT(11) NULL DEFAULT NULL ,
	`Y` INT(11) NULL DEFAULT NULL ,
	`Z` INT(11) NULL DEFAULT NULL ,
	`Time` DATETIME NOT NULL DEFAULT '0000-00-00 00:00:00' COMMENT '时间',
	`IsOnline` BIT(1) NULL DEFAULT NULL ,
	`CreateTime` DATETIME NULL DEFAULT NULL ,
	`Statu` INT(5) NULL DEFAULT NULL ,
	`OfflineReason` INT(5) NULL DEFAULT NULL ,
	`Orders` INT(5) NULL DEFAULT NULL ,
	`BuildingId` INT(11) NULL DEFAULT NULL ,
	`ApId` VARCHAR(50) NULL DEFAULT NULL ,
	`Brand` VARCHAR(20) NULL DEFAULT NULL ,
	`pointType` INT(2) NULL DEFAULT NULL ,
	`ScanType` INT(1) NULL DEFAULT NULL ,
	`AssocBssid` VARCHAR(50) NULL DEFAULT NULL ,
	`AssocFlag` BIT(1) NULL DEFAULT NULL ,
	`CurrAsscoFlag` BIT(1) NULL DEFAULT NULL ,
	`DataRate` INT(4) NULL DEFAULT NULL ,
	`Nosie` INT(4) NULL DEFAULT NULL ,
	`NosieType` INT(1) NULL DEFAULT NULL ,
	`RadioMac` VARCHAR(50) NULL DEFAULT NULL ,
	`RadioType` VARCHAR(50) NULL DEFAULT NULL ,
	`Rssi` INT(4) NULL DEFAULT NULL ,
	`RssiType` INT(1) NULL DEFAULT NULL ,
	`RxChannel` INT(4) NULL DEFAULT NULL ,
	`TxChannel` INT(4) NULL DEFAULT NULL ,
	`ApSsid` VARCHAR(50) NULL DEFAULT NULL ,
	`SsidEncryptType` VARCHAR(50) NULL DEFAULT NULL ,
	`PlaceNo` VARCHAR(50) NULL DEFAULT NULL ,
	`DeviceNo` VARCHAR(50) NULL DEFAULT NULL ,
	`Identity` VARCHAR(50) NULL DEFAULT NULL ,
	`IdentityType` VARCHAR(50) NULL DEFAULT NULL ,
	`Latitude` VARCHAR(50) NULL DEFAULT NULL ,
	`Longitude` VARCHAR(50) NULL DEFAULT NULL ,
	PRIMARY KEY (`Id`, `Time`),
	INDEX `index_time` (`Time`),
	INDEX `buildingIdIndex` (`BuildingId`),
	INDEX `xyIndex` (`X`, `Y`),
	INDEX `mapIdIndex` (`MapId`),
	INDEX `msxxxIndex` (`Tagmsxxx`)
)
COLLATE='utf8_general_ci'
AUTO_INCREMENT=1
/*!50100 PARTITION BY RANGE (TO_DAYS (`Time`))
(
 PARTITION p201511 VALUES LESS THAN (736298) ENGINE = MyISAM,
 PARTITION p201512 VALUES LESS THAN (736329) ENGINE = MyISAM)  */;

How to repeat:
using C#.net windows program to insert more than 300 records data into table one time,and the error will happen sometime but not everytime
[2 Nov 2015 9:15] Chiranjeevi Battula
Hello  Tina Du,

Thank you for the bug report.
Could you please provide us valid insert statement to confirm this issue at our end?

Thanks,
Chiranjeevi
[3 Dec 2015 1: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".