Author Topic: Error during data transfer (Read 5182 times)

Bokkie · « **on:** May 01, 2006, 05:31:29 am »

I am trying to transfer an .EAP file to a SQL-server database and get the following error:

Microsoft OLE DB Provider for SQL Sever [-2147217873]
INSERT statement conflicted with COLUMN FOREIGN KEY constraint 't_diagram_FK00'. The conflict ocurred in database TDS-EA, table 't_package' column 'Package_ID'.

I'm using EA build 788. With other models I was succesfull. However this one gives the same result over&over again. I have disabled the .eap user security.

Is there a fix or how do I work around this problem?

«Midnight» · « **Reply #1 on:** May 01, 2006, 05:37:11 am »

Report this as a bug Bokkie. Use the bug reporting page on the Sparx site or get there via the Help / On-line Resources / Bug Report Page menu selection from EA.

Can you send your model (zipped) to Sparx for evaluation? If so, you should probably include it with your report.

David

Bokkie · « **Reply #2 on:** May 01, 2006, 05:45:40 am »

I would like to send you the logfile but in this scenario none is created: the same error-dialog keeps pop'n-up after been clicked.

«Midnight» · « **Reply #3 on:** May 01, 2006, 06:00:14 am »

I've seen this behavior when EA runs into a database error in the repository. It often fails to write the log file and never recovers after that.

This really sounds like the kind of thing Sparx needs to know about. They'll want to replicate the problem on their site, which is why you might want to attach your project file to the bug report.

Hope this gets sorted out. I know how frustrating it can be to run into this kind of roadblock.

Just for interest, have you tried this with builds 789 or 790?

Bokkie · « **Reply #4 on:** May 01, 2006, 06:09:03 am »

Just upgraded to 790: gives the same problem....

«Midnight» · « **Reply #5 on:** May 01, 2006, 10:22:56 am »

Sorry to hear that Bokkie,

Definitely report this as a bug. Either Sparx have a work around and will let you know, or they really should know about this.

You mentioned that you are only having this problem with one model. Do you have any idea what aspect is causing the problem? For example, do you get a partial model on the receiving side? I ask this because this is the kind of thing Sparx will need to know in order to rapidly track down the root cause.

David

Bokkie · « **Reply #6 on:** May 02, 2006, 12:02:45 am »

The bug has been reported and I have contact with sparx regarding this problem. I am confident that they'll fix it.

For your question: the result is indeed a partial model in the SQLS database - unuseable. However I was succesfull transferring the data from EAP to EAP. However transferring the latter to the SQLS failed with the same error as the original.

«Midnight» · « **Reply #7 on:** May 02, 2006, 04:18:21 am »

Just out of interest have you tried this with any other back end repository? If you have Oracle 8 - 10 or ASA (I've gotten it to work with ASE and some fiddling) or one of the others on site this might provide another data point.

[Of course, where you would get the time, particularly with the original problem holding you up remains a mystery. Still, if you have the software and are having trouble filling the empty hours...]

hd · « **Reply #8 on:** May 02, 2006, 03:06:05 pm »

Quote

If you have Oracle 8 - 10 or ASA

EA is not supported on Oracle 8, only 9i and 10g.

«Midnight» · « **Reply #9 on:** May 02, 2006, 03:07:15 pm »

Oops, I stand corrected. Sorry about that.

Hopefully Bokkie, you did not try this on version 8 since I posted.

Bokkie · « **Reply #10 on:** May 03, 2006, 12:38:08 am »

I am glad to report that the guys at sparx have located the problem and provided me with a workaround.

Sparx Systems Forum

News: