Export & Import... Missing stuff

[marcelloh]

I wonder if this is normal:
I export an proff. edition EAP file complete into an XMI (2.1 version).
I import it into an OracleDb with a Corp. edition.
And with a check, we saw some file references missing, and some maintenance stuff missing.

So this seems not to be trusted. So, now I am in deep Sh!t.

I need a quick fix, a good advise or something. I have 14 people standing around my desk, just waiting to kill me.

HEEELLLLPPPPP!!!!!

Addition 1:
The exported XMI holds the file references and the maintenance information!
So it looks like the import isn't working. Today my trust in EA is below sealevel. How can this happen?

Addition 2:
Just filed a priority bug, with my ea_xmi_export.
The good news is, I'm still alive.

Addition 3:
Made a new local EAP-file, with the Prof.edition, imported the xmi-file, and the stuff missing, is visible. So my conclusion is, it must be something with the corporate edition, and/or with the oracleDB.

Addition 4:
Deleted the complete model in oracle, and then did a integrity check.
It mentioned 2 things, stangly enough. I let EA fix those things.
(Actually, tehy were deleted.) And imported the XMI file again.
It seems okay, but. since now my trust is very, very low. I'm gonna
export the oracleDb into another xmi-XML-dump, and use a compare tool to really check if everything is allright.
That brings up another question: Why didn't the importer mention the skipping of certain stuff? I find it scary.

Addition 5:
The XML is different of the 2 databases. Mostly because of of some EA-ID's and other stuff. So I deleted those just to compare them further. Now some localID's are different, so I deleted them too. I reordered the 2 files, to make a correct compare. (Every line is now in alphabetical order. And you know what? Still differences! This is becoming more scary. But... I'm still alive :-) and did order my collegues not to work on the corporate edition and, not to import & export ever again, until I say so. They have to retype stuff into other databases. Yes, they really love me, lucky me.....

[Geert Bellekens]

Marcel,

Yes indeed two xmi exports from the same model will always be different.
Apparently the xmi export of EA is not reproducable, (could be due to the Heisenberg uncertainty principle) no two exports will ever be the same.

Have you tried to project transfer iso the xmi import/export?
Another option is to use the compare utility to compare the exported xmi file with the model itself. That should give you a better (more sane) view on the differences between the two.

Will you ever be 100% sure you have everything? I don't think so, so you better keep a backup of the old model to be sure.

Geert

[Geert Bellekens]

Ah, and you have to use the 1.1 xmi version.
That is the version that can be trusted most. (and make sure you turn on "Enable full EA roundtrip", but you probably already did.

Geert

[marcelloh]

Eventually a collegue of mine took over (I was ill for a week). I adviced him to make to biggest report out of the 2 models and compare the output in word.

But I must say, I hate it when I can't trust a tool to do the same each time. Mr. Heisenberg was right, but since a programmer can influence the outcome of an export, I find it absolutely no excuse for messing up the endresult. It should always be a predictable result. My version of predictable is: If I import something, and export it again, to another file, the original and the second export, should exactly be the same. Not a single bit different!

[Paolo F Cantoni]

Welcome to EAUI...

"We hold that truth to be self-evident...  That doing the same thing twice yields the same outcome..."

Paolo