MySQL Bugs: #60471: Dump import doens't work.

Bug #60471	Dump import doens't work.
Submitted:	15 Mar 2011 9:10	Modified:	1 Feb 2012 22:06
Reporter:	Frédéric MODOUX	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench: Administration	Severity:	S2 (Serious)
Version:	5.2.33CE	OS:	Windows (7 Pro 32 & 64 bit)
Assigned to:		CPU Architecture:	Any
Tags:	regression

Description:
Hi everyone,

I've downloaded the lastest version of the workbench and I can execute the export dump but when I want to import this dump to another server, the status of the import is 'finished' without error but the database / tables are not created.

I've tried the same manipulation with the version 5.2.31 and it works fine !

How to repeat:
Use 2 different servers.

Make export of server 1 database XX.
Make import on server 2 of the database XX.

Suggested fix:
it should not be something big to do cause it works in older version and the status says 'import finished'....

can you check the output of the Log pane in the lower right of the import interface (before the "import finished" line)?
also what server versions do you connect to?
thanks in advance

here is the LOG : 
09:40:18 Import of C:\Users\Fred-Bi-Xéon\Documents\dumps\groupes has finished

And the version of my servers is 5.5.9 (32 & 64 bit).

Greetings
Fred

Hi everyone,

I've done few test this week-end and the problem seems to come from distant dump.

I explain, I've installed on my 2 servers and on 1 client, the server and workbench.
If I dump on local server 1, and put with a usb key the dump and import it on local server 2, it works.

If I dump server1 by client ( a 3rd computer ), and import it with client on server2, the progressbar is filling with the right number of tables and it writes 'dump has finished' but the table doesn't appear on server2.

I've also tried to modificate in the dump, the IP Address of the server and change the one of server1 to server2 IP but nothing works.

What is strange, it's because the import is doing right, the problem is because it write 'dump is finished' and the table is not created.

And, the same operation with an older version of the workbench is working with the same users and passwords !

Thanks for your help :)

Fred

Thanks a lot Frédéric for your input.
We are working on it.

Hi Armando,

If you need some precisions, printscreen, .... don't hesitate to ask me !

Have a nice day..

Fred

Hi Frederic

I am unable to repeat this, could you please provide the following info?

- What is the connection method used for the remote server? Does it use a SSH Tunnel?
- Can you copy/paste the logs from the import operation?

Thanks!

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".

I haven't been able to reproduce this bug either trying to import the dump
folder into a local server or into a remote one. Here are the steps I
followed:

1. Opened WB 5.2.37 in Windows 7x64.
2. Opened a remote MySQL Server instance (MySQL v5.5.15 running in Ubuntu
11.10 and connected using a standard TCP/IP method).
3. Went to Admin | Data Export and exported the Actor table from the Sakila
sample database into a dump folder.
4. Opened in WB Admin a local MySQL Server instance (MySQL v5.5.15 in the
same Win7x64 box where WB is running, connected using standard TCP/IP
method).
5. Went to Admin | Data Import and imported the dump folder from step 3.
6. Opened WB's SQLIDE and issued the query SELECT * FROM sakila.actor against
the MySQL server where the dump folder was imported. All result rows were
properly shown.
7. Repeated steps 5-6 in WB 5.2.37 running in Ubuntu 11.10 and connecting via
SSH tunneling to a remote MySQL v5.1.41 instance hosted in a Ubuntu 10.04
Server box. Proper results were obtained too.