XMI Import DAO.Database [2004] Out of Memory Error

[tpolansk]

When importing a particular model from XMI, EA raises a DAO.Database [2004] Out of Memory error... selecting OK in the error message box, the import then successfully completes. Anyone know offhand a reason for this error (e.g., a large XMI file greater than 15 MB or...)? This error is raised during import of the same classifier every time so I will look closer into that part of the XMI file but the XMI file is actually created (through export of an EAP model) from EA, so...

To Reproduce:

Test Setup - Export a model to XMI to use for test import:

Select Export Model to XMI... from the root model node:
Export Package to XMI configuration:


No Stylesheet


Do Not Export Diagrams

Do Not Format XMI Output

Do Not Write Log file

Do Not Use DTD

Do Not Generate Diagram Images

No Diagram Image Format


Do Not Enable full EA Roundtrip

XMI Type: UML 2.1 (XMI 2.1)

Not Unisys/Rose Format

Do Not Exclude EA Tagged Values

Select Export to start the process

Test Import - Perform the test import to get the error:

Select Import Model from XMI... from a new root model node
Import Package from XMI... configuration:


Do Not Import Diagrams

Strip (recreate) GUIDs

Do Not Write Log File

No Treat Imported Datatypes as: (blank)

Select Import to start the process (delete the original root model first if an import conflict is reported; press yes to import as a root model; etc.)

The error is reported; select OK and the import successfully completes.

Thanks!

[«Midnight»]

First, make sure you are using a very recent build of EA as well. Build 816 is current.

Try running Tools | Data Management | Project Integrity Check on your project, just to see if there are any obvious issues.

Please let us know if this uncovers anything.

David

[tpolansk]

The error also occurs on the latest build (7.0 build 816). The error occurs on a brand new project or existing project so I don't believe it has anything to do with project integrity (though I did run the integrity check both before and after import and no errors were found).

Having said all that, the error occurs on the latest build during processing of the exact same classifier during the import (as reported by the import progress) as it consistently did on the previous build so there is undoubtedly something awry and/or not handled by EA with the XMI for that particular classifier (or maybe just after it, hmmm...). To expend a bit more brain damage... only obvious thing I see in the XMI file is that this particular classifier (representing an enumeration) is followed by a primitive String classifier which has -pages- (and I mean pages... the String element definition is 241 KB on its own when extracted from the file... which I could provide if it helps... don't see a file attachment button here) of the following as part of its element definition:

<extendedProperties tagged="0" package_name="Domain" ea_attsclassified="{22266DAF-0138-4bf2-B81C-D6859C0FF16D},{A33D0E14-091F-4cff-A88C-0B0C76103596},{12BAE85C-F290-4f4a-8A4B-8A8220288A70}, and on and on with these GUIDs...

No other part of the XMI file has this much GUID data repeating in the EA_ATTSCLASSIFIED (?) attribute. Please also be aware this model originates from an imported IBM RSM/RSA EMX file.

Note when the primitive String classifier is removed from the original XMI file the error goes away and all is well!  

Hmmm, thinking aloud more... What is all that data following the EA_ATTSCLASSIFIED attribute and why does that much of it cause an error... and, of course, how/why does it originate from the original IBM RSM/RSA EMX import then export to XMI... Should the export to create the XMI file toggle On the Exclude EA Tagged Values...

Again, note creating the XMI file with that toggle on removes the "lengthy" data as mentioned and the subsequent import works fine as well!  

Okay, so real question is, I don't see a setting for this (Exclude EA Tagged Values) within automation (project interface, ExportPackageXMI call) which is where I am really trying to perform an export/import for essentially copying an entire model? Is there a way to set that within automation for export to XMI? And, if I am trying to create a copy of an entire model within EA (within an add-in that needs one to work with) is this not undesirable as the EA information in the tagged values then lost (i.e., not a complete copy)?

Whew, thanks again, Tom

[Eve]

Thank you for your description of the problem XMI.  I don't know if you have also sent an email to sparx support (as you generally need to) but I have asked the relevant developer to look at the issue.

For your information, the ea_attsclassified specifies all the attributes in the model that use this type as a classifier.

[GBeutler]

Hi,

I've got the same problem. Are there any news about this problem or where do I have to look for them? Thanks in advance and

best regards,

Guido

[«Midnight»]

Has anyone tried this with build 817?