Solved

'max_allowed_packet' Error With Reload of Database Dump

Posted on 2006-11-26
3
592 Views
Last Modified: 2012-06-21
"ERROR 1153 (08S01) at line 33291: Got a packet bigger than 'max_allowed_packet' bytes"

We're getting the error above when trying to restore a dump to a new database.

We have continuosly adjusted up with the following command but keep getting the error.

mysql> set max_allowed_packet = 300000000;

Is there somewhere else that we need to adjust?

I've read some about my.cnf, but am not sure if I need to change it, or what to change in it. Also, there are multiple versions of my.cnf?

Background: new to Linux!
0
Comment
Question by:runningone
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
3 Comments
 
LVL 30

Accepted Solution

by:
todd_farmer earned 500 total points
ID: 18014444
There is both a session variable and global variable for this.  Try setting the global variable:

set @@global.max_allowed_packet = 300000000;

Also, you can set this parameter in the defaults file (/etc/my.cnf):

http://dev.mysql.com/doc/refman/5.0/en/packet-too-large.html
http://dev.mysql.com/doc/refman/5.0/en/option-files.html

0

Featured Post

Back Up Your Microsoft Windows Server®

Back up all your Microsoft Windows Server – on-premises, in remote locations, in private and hybrid clouds. Your entire Windows Server will be backed up in one easy step with patented, block-level disk imaging. We achieve RTOs (recovery time objectives) as low as 15 seconds.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Does the idea of dealing with bits scare or confuse you? Does it seem like a waste of time in an age where we all have terabytes of storage? If so, you're missing out on one of the core tools in every professional programmer's toolbox. Learn how to …
When table data gets too large to manage or queries take too long to execute the solution is often to buy bigger hardware or assign more CPUs and memory resources to the machine to solve the problem. However, the best, cheapest and most effective so…

749 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question