MySQL Repository: ODBC connection fails, EA closes

[Michael Hafner]

Dear all,

v8.0: Trying to establish a connection to a MySQL repository, I encounter a problem:

1. MySQL is up an running
2. EA schema is set up in db
3. ODBC driver is installed (MySQL ODBC 5.1 Driver; TCP/IP Server, Port 3306)
4. Test of connection is succesful

5. However, when starting the project transfer, I receive the following message: "Enterprise Architect has experienced a network error and will close down". Not surprisingly, EA closes down after that...

Q #1: What may be the reason for this (and why does EA have to close down in this situation)?

Q #2: I only need to "dump" the project database into a MySQL database; is there any other way to do this (in case the network problem can't be solved)?

Thanks for any help!
Michael

[alex_b]

I have got the same problem and am in dire need for a solution.
Alex.

[qwerty]

Just the "have you plugged in the terminal"-question: is your repository initialized with EA's resource SQL script?

q.

[Michael Hafner]

Just the "have you plugged in the terminal"-question: is your repository initialized with EA's resource SQL script?

q.

Yes. I have used the script from

http://www.sparxsystems.com/downloads/corp/scripts/MySQL_MyISAM_EASchema.sql

...without any modification. No problems of any kind.

[Luis J. Lobo]

Have you uploaded an EAP file to MySQL? This is mandatory previusly to try to connect to it.

[Michael Hafner]

Have you uploaded an EAP file to MySQL? This is mandatory previusly to try to connect to it.

Hi, Luis,

thanks for the reply, but I don't get you. I have to upload an EAP file? - I want to transfer an EA project from an EAP file to a MySQL database. An EAP file is a jet database, right? Now, my documentation tells me to set up a MySQL database via Sparx's SQL script (v.s.), and to connect to it via ODBC. The transfer is (or should be) done by EA: retrieving the data from the jet db, handing them over to MySQL &c.
This is the point where the problem occurs: MySQL schema exists, ODBC driver works, EA transfer fails. Have I missed something?

Best,
Michael

[Luis J. Lobo]

The steps are:

1. Create a empty database
2. Run the SQL script
3. TRANSFER SOMETHING (maybe a empty EAP, a template from an EAP or another database...). Use the "Tools | Data Management | Project Transfer" dialog.
4. Connect to the new Repository

The step 3 is mandatory, you must transfer at least an empty model in order to be able to connect in step 4.

Look for the entire process at: (the steps could not correspond with the steps described by me, but describes the same)

http://www.sparxsystems.com/enterprise_architect_user_guide/8.0/projects_and_teams/upsizingtomysql.html

Regards,

[Michael Hafner]

The steps are:

1. Create a empty database
2. Run the SQL script
3. TRANSFER SOMETHING (maybe a empty EAP, a template from an EAP or another database...). Use the "Tools | Data Management | Project Transfer" dialog.
4. Connect to the new Repository

The step 3 is mandatory, you must transfer at least an empty model in order to be able to connect in step 4.

Look for the entire process at: (the steps could not correspond with the steps described by me, but describes the same)

http://www.sparxsystems.com/enterprise_architect_user_guide/8.0/projects_and_teams/upsizingtomysql.html

Regards,

Yup. That's precisely what I'm trying to do. Dialog Project Transfer, Transfer Type EAP to DBMS. I select a source project. I then define a target project - selecting Microsoft OLE DB Provider for ODBC drivers, selecting a data source etc. on the way -, test the connection, go back to the Project Transfer dialog, click the "Transfer" button, and bada bing, bada boom, EA crashes.

[Luis J. Lobo]

Have you checked the "Don't optimize column width" and "Return maching rows" at the MySql ODBC driver?

[Michael Hafner]

Have you checked the "Don't optimize column width" and "Return maching rows" at the MySql ODBC driver?

I don't see those options on the details panes (v5.1....

[Luis J. Lobo]

Check the point 6. here:

http://www.sparxsystems.com/enterprise_architect_user_guide/8.0/projects_and_teams/setupmysqlodbcdriver.html

The options depends on the MySQL driver version, but on every versions they are similar...

[Michael Hafner]

Check the point 6. here:

http://www.sparxsystems.com/enterprise_architect_user_guide/8.0/projects_and_teams/setupmysqlodbcdriver.html

The options depends on the MySQL driver version, but on every versions they are similar...

Thou shalt read the documentation thoroughly...

Luis, if you happen to come to Bonn, don't forget to drop by for a beer. It works.

Now there remains some collation stuff to do, and some duplicate GUIDs seem to have found their way into the project (how on earth...), but I'll deal with this.

A big thank-you to Madrid!

Best regards,
Michael

 

[alex_b]

I could solve our problem (which led to the same error message and crash of EA). I forgot to enter the db name at the msql odbc driver configuration (a small entry on bottom of dialog).
Loading a EAP onto db is NOT necessary for a valid connection (and do not mean the connection test).
Best regards,
Alex.

[Michael Hafner]

And wouldn't it be nice if EA didn't crash?
The reasons for a failed transfer may vary, but does any of them justify seppukku?