MYSQL ERROR 1160 error

  • I have received MySQL error 1160 'error writing communication packets'. I have a stored procedure that does this: step 1: compares the data from two tables and insert into a tmp table. step 2: Results from tmp table will then copied over to a table with FEDERATED engine. This Federated table is connected to another table on a different server.

    I wish to know if there is anything wrong with step 1 or 2 from above that may cause this error? The error does not always pop up. Once in a while it will pop up but is random. I also wish to know if this error will cause major data integrity issue or errors in my data

  • This is an SQL Server forum and you might not get help for MySQL. It's not that we're not willing to help, but most of us don't have experience on MySQL.

    You might get better help on a MySQL forum such as http://forums.mysql.com/ or on StackOverflow.

    Luis C.
    General Disclaimer:
    Are you seriously taking the advice and code from someone from the internet without testing it? Do you at least understand it? Or can it easily kill your server?

    How to post data/code on a forum to get the best help: Option 1 / Option 2
  • adam.mesny (5/25/2015)


    I have received MySQL error 1160 'error writing communication packets'. I have a stored procedure that does this: step 1: compares the data from two tables and insert into a tmp table. step 2: Results from tmp table will then copied over to a table with FEDERATED engine. This Federated table is connected to another table on a different server.

    I wish to know if there is anything wrong with step 1 or 2 from above that may cause this error? The error does not always pop up. Once in a while it will pop up but is random. I also wish to know if this error will cause major data integrity issue or errors in my data

    Slightly rusty on this subject but first thought is a communication/network issue interfering with the replication.

    😎

    As Luis said, you are not likely to get any better answers on this forum (not that mine is particularly good anyway).

  • Hello!

    Issue may happen even if FEDERATED tables are not actually replicated (FEDERATED turned ON, but database which contains FEDERATED tables excluded using any of the repliate* or binlog* do/ignore options).

    Did you checked the link provided its majorly timeout issue

    I would try increasing (temporarily) your net_read_timeout, net_write_timeout, and max_allowed_packet variables. When reloading a mysqldump file dies, it’s generally caused by one of those.

    Inserting too many data can even give you the error

    Try to set the max_allowed_packet to 256M, you can add it to /etc/my.cnf or my.ini

    [mysqld]

    max_allowed_packet=256M

    SET GLOBAL max_allowed_packet = 1024 * 1024 * 256;

    Also this issue is discussed on these sites below. Check them:

    https://groups.google.com/forum/?hl=en#!topic/mysql-repair/16ibF_g3dYg

    http://www.filerepairforum.com/forum/databases/databases-aa/mysql

    I hope i could help you

    Good luck!

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply