Import schema from ODBC stuck

[Modesto Vega]

We have been trying to import a database schema from ODBC, something I and my colleagues have done many times. However, this time Sparx EA is giving us a migraine.

A brief description of the problem is as follows:

• An attempt to import the schema associated with a given package  into our corporate repository failed/had to be aborted
• Now each time we try to run Import schema from ODBC for that package, Sparx EA does not show the corresponding dialog and the server holding the database goes into cardiac arrest
• The dialog appears for any other package
• The same behaviour happens with any machine connected to the repository

My conclusion is that there is some sort of dormant process which gets triggered by Sparx EA each time we attempt to import the schema from ODBC for that package.

Any thoughts that may ease my migraine are welcomed.


P.S.: Using Sparx EA v13

[qwerty]

No idea. But for Windoze a reboot is always the best cure.

Further: use an empty EAP for the import and turn off all MDGs.

q.

[Modesto Vega]

Thanks qwerty, already tried the old Windows trick of rebooting before posting and didn’t fix anything. There is a server side component here, there is either a blocking uncommitted database transaction or Sparx EA is being too smart.

Trouble is that we cannot see any blocking transactions in the database server.

Will try other suggestions tomorrow.

[Modesto Vega]

Oh well!!! When Sparx EA decides to be extremely annoying (please note the emphasis), it borders in the unusable.

The package, most likely the package ID, is the common thread here. Somehow, Sparx remembers there is something pending with a package. However, I have no idea of where Sparx EA stores whatever is causing the problem.

Reverse engineering into another package, deleting the old package and renaming the new package to the same name as the old package solves problem.

[qwerty]

I need to so such things all day ;-) Doesn't shock me any more :-/

q.

[Paolo F Cantoni]

Did you run an integrity check before you "creamed" the old package?

"An integrity check a day keeps the doctor away".

Paolo

[qwerty]

Ah yes. Just told that my customer. They always get scared by the messages EA pops up when starting it. Are you really, really sure?

q.

[Modesto Vega]

Did you run an integrity check before you "creamed" the old package?

"An integrity check a day keeps the doctor away".

Paolo

If you mean this, https://sparxsystems.com/enterprise_architect_user_guide/14.0/model_repository/checkingdataintegrity.html, I don’t think we did try it because it is was an import from ODBC. Good point, I’ll add it to the check list.

Another thing we noticed is that the driver makes a big difference. In this case, in terms of speed and reliability a SQL Server Native driver is the difference between trouble, a lot of it, and success.