distal-attribute
distal-attribute
distal-attribute
distal-attribute

sql error(2007) Malformed packet

inbuffalo posted 1 year ago in Import/Export
I have HeidiSQL 8.0.0.4530 installed on both my computers.

When importing a CSV file on my laptop running Windows 7 Starter 32 bit operating system, the file did not upload into the database.

The system responded with the following message
sql error(2007) Malformed packet

I then imported the CSV file on my desktop computer running Windows XP professional Version 2002 Service Pack 3


Is there some setting that I need to make on my Windows 7 laptop computer to avoid this error?

Thanks
inbuffalo posted 1 year ago
Forgot to mention information about MySQL

Server version: 5.5.32-cll - MySQL Community Server (GPL)
Protocol version: 10
jfalch posted 1 year ago
did you (or heidisql via import) use LOAD DATA LOCAL INFILE ? if so, has your serverĀ“s my.ini, [mysql] section,
local-infile=1 ? has to be explicitly enabled)
inbuffalo posted 1 year ago
The LOAD DATA LOW_PRIORITY LOCAL INFILE was used

I made a typo on the error number- should be 2027
/* SQL Error (2027): Malformed packet */

unable to locate the my.ini file
ansgar posted 1 year ago
Is that error reproducible? Looks more like a one-time error to me.

ansgar posted 1 year ago
Just getting exactly the same error here, on a local MySQL 5.5.8 server. wtf...
ansgar posted 1 year ago
As an alternative in HeidiSQL, you can always use the "Method": "Client parser". I had introduced that alternative for users which lack the privilege to fire a LOAD DATA command. When chosing "Client parser", HeidiSQL goes through your CSV file itself, and generates extended INSERTs.
inbuffalo posted 1 year ago
Been getting the error on 5 plus attempts using the laptop with Windows 7. Have not been able to import yet

Always works with Windows XP

Will try the Client parser alternative
Thanks
ansgar posted 1 year ago
Shit... just found out the newer libmysql.dll I recently committed is causing this "malformed packet" error. See issue #3262.
ansgar posted 1 year ago
Seems to be a HeidiSQL issue, as I can fire the same LOAD command on the command line, using the same libmysql.

ansgar posted 1 year ago
* Reverting libmysql to MariaDB's v5.5.2 fixes this issue, but would break again a disconnect problem mentioned here.
* Using a libmysql from a MySQL (not MariaDB) server would most probably break pluggable authentication on MariaDB.

hmm... what code in HeidiSQL could cause this mess?
ansgar posted 1 year ago
Seems the current stable of MariaDB's libmysql (5.5.33 plus the "a" release also) does not have that "Malform packet" issue. Nothing in the changelog about that though.

r4531 exchanges the v5.5.32 to v5.5.33a .

There is a chance that pluggable authentication is broken again, so we need to wait for feedback in issue #3262. Just a gutt feeling, as HeidiSQL just reads "6.0.0" out of that libmysql now, even without "MariaDB" prefix.
ansgar posted 1 year ago
Sorry for all the mess. r4532 fixes all issues here. Using a libmysql from MariaDB 5.3.12 now. And
* it's a 32 bit version (using a 64bit .dll in a 32bit executable was quite embarrassing...)
* it supports pluggable authentication
* finally it does not have the "malformed packet" in the LOAD DATA LOCAL INFILE command
jonlegras posted 21 hours ago
Just downloaded the lastest build - 8.3.0.4851 64bit.

Our malformed packet friend when importing a csv seems to have returned.

It worked fine using Method:Client Parses File, but using Server I get the malformed packet.

Looking at the logs, v4827 included a refreshed libmysql.
ansgar posted 13 hours ago
Googling around I get the impression that both the client and server must have "enable-local-infile" activated. Is that the case on your server?

Please login to leave a reply, or register at first.