Oracle EAP->DBMS transfer failure

[dougj]

Hi

When I try and do a project transfer from eap to Oracle dbms it fails during the "Copying project information for: t_image" stage.

- No Logfile gets written.
- I am using the latest release of EA.
- I have the correct Oracle OLE DB drivers installed.
- The error comprises a "Microsoft Visual C++ Runtime Library" dialog box which pops up with the following text in it:

-----------------------------------

Runtime Error!

Program: C:\Program Files\Sparx Systems\EA\EA.exe

This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information.

------------------------------------

Can anyone help?

Thanks

[«Midnight»]

I'm guessing a bit here, but:

Did you use the most recent scripts from Sparx to set up the database in the first place? I recently had trouble with EA 7 and an older SQL Server script. Downloading and running a fresh version resolved the issue.

Have you got a very recent Oracle version of the Oracle client? There was a thread some months ago that dealt with a similar problem with Oracle. Updating the Oracle client made it go away.

These are just a couple of suggestions I came up with on the fly. Please keep us in the loop as you work through.

Other ideas, anyone?

David

[dougj]

I have just tried importing to a mysql database and the same error happens.
I think this points to an issue with EA or my .eap file rather than an issue with my DBMS connection.
FYI, my project integrity check passes.

Hmmm.

[dougj]

... and I've now discovered that the same error happens when I transfer an empty .eap file!

The db scripts I downloaded were from the links on the left hand side of the "registered users" section of this site. Have I inadvertently downloaded out of date versions somehow?

How can I tell?

[dougj]

ok, I've concluded that somehow I ended up with a dodgy .eap file.
If I delete every package from my .eap file so that it just has the root "Model" package and nothing else, and then try to transfer to DMBS, it throws the same error.
If I export the entire model to XMI and then import it into a new, empty .eap file, then transfer to DBMS, it works fine.

I suspect it *might* be because we have been using EAP synchronization for a while and some invisible inconsistency may have crept into the master. This inconsistency only then became apparent when we tried to transfer it to DBMS.

Anyway, if anyone else experiences a similar issue, the above steps successfully fix it.

[«Midnight»]

...
If I delete every package from my .eap file so that it just has the root "Model" package and nothing else, and then try to transfer to DMBS, it throws the same error.
If I export the entire model to XMI and then import it into a new, empty .eap file, then transfer to DBMS, it works fine....

Anyway, if anyone else experiences a similar issue, the above steps successfully fix it.

Doug,

I hope you mean that the first method (deleting everything but the root) failed, but the second method (XMI) worked. Not that deleting everything, then using XMI on the depleted model, was what worked.

That said, this deserves to be reported to Sparx, particularly if you can verify that the issue was with synchronization. In any case it would help if they knew there was a possibility. They would also be aware of the workaround if anyone else reports an 'active' problem.

If you get an issue number from Sparx in follow-up, keep track of it. If your problem recurs, you can then let Sparx know, for another data point.

If you have a copy of the original file - the one that caused the error - send it (in compressed format) to Sparx with your bug report. Perhaps you could send the depleted file, since it seems to trigger the error.

Please search my recent posts - the past couple of weeks - for a best practice we use for keeping the forum users in the loop with a bug report or feature request.

David