Ask your WordPress questions! Pay money and get answers fast! (more info)

Import database to 1and1 using myphpadmin issue! WordPress

Hi Guys

I am trying to import a backup of an sql databse with myphpadmin at 1and1.co.uk

and I keep getting this error

http://screencast.com/t/yKBUu69KR

Any idea what i'm doing wrong.

I have dropped the old database table and am following the instructions carefully.

The back up is well within the upload limit.

Any help would be greatly appreciated.

Many thanks
Steve

Answers (3)

2013-01-17

Dbranes answers:


Hi, are you trying to import the tables

- information_schema
- mysql

also? If so, you should try to skip them in your export.

Another way, would be to edit the sql file and remove the problematic sql commands.

2013-01-17

Arnav Joy answers:

I think you db size is larger then what phpmyadmin can accept , see the attached screenshot .

to resolve this you can do one of the two things:-

1. ask your hosting provider to increase import size .

or

2 . break the db in multiple tables and then run sql query , for the table one by one


Arnav Joy comments:

I think you db size is larger then what phpmyadmin can accept , see the attached screenshot .

to resolve this you can do one of the two things:-

1. ask your hosting provider to increase import size .

or

2 . break the db in multiple tables and then run sql query , for the table one by one


Arnav Joy comments:

I think you db size is larger then what phpmyadmin can accept , see the attached screenshot .

to resolve this you can do one of the two things:-

1. ask your hosting provider to increase import size .

or

2 . break the db in multiple tables and then run sql query , for the table one by one


Arnav Joy comments:

I think you db size is larger then what phpmyadmin can accept , see the attached screenshot .

to resolve this you can do one of the two things:-

1. ask your hosting provider to increase import size .

or

2 . break the db in multiple tables and then run sql query , for the table one by one


Arnav Joy comments:

I think you db size is larger then what phpmyadmin can accept , see the attached screenshot .

to resolve this you can do one of the two things:-

1. ask your hosting provider to increase import size .

or

2 . break the db in multiple tables and then run sql query , for the table one by one


Arnav Joy comments:

I think you db size is larger then what phpmyadmin can accept , see the attached screenshot .

to resolve this you can do one of the two things:-

1. ask your hosting provider to increase import size .

or

2 . break the db in multiple tables and then run sql query , for the table one by one

2013-01-18

plovs answers:

Two most common reasons (and fixes) for the MySQL server has gone away (error 2006) are:

Server timed out and closed the connection. How to fix:

check that wait_timeout variable in your mysqld’s my.cnf configuration file is large enough. On Debian: sudo nano /etc/mysql/my.cnf, set wait_timeout = 600 seconds (you can tweak/decrease this value when error 2006 is gone), then sudo /etc/init.d/mysql restart. I didn’t check, but the default value for wait_timeout might be around 14400 seconds (4 hours).

Server dropped an incorrect or too large packet. If mysqld gets a packet that is too large or incorrect, it assumes that something has gone wrong with the client and closes the connection. You can increase the maximal packet size limit by increasing the value of max_allowed_packet in my.cnf file. On Debian: sudo nano /etc/mysql/my.cnf, set max_allowed_packet = 64M (you can tweak/decrease this value when error 2006 is gone), then sudo /etc/init.d/mysql restart.

Often it is the max_allowed_packet variable. The default is often 1 MB (you can see this by running the SHOW VARIABLES MySQL query) and the file I was importing had a few very large records. Edit the my.ini file (Windows) and set the value to this: max_allowed_packet = 64M, restarted MySQL and re-ran the import

If you cannot change the msql-server settings, and your hosting provider is not willing to, the do the export again, but break the db in smaller pieces.