XML import from ERwin model

Hopefully I’m posting this in the right place. If not, please advise.

I generated the XML from and ERwin model and attempted to import it into TDM2. The ERwin model is a bit on the complex side with over 150 entities, 15 or so subject areas, a couple of dozen triggers and a handful of user domains. This is an old model that has been kept up to date through the 10 year life cycle of a software program.

It has some modelling hacks in to get ERwin to generate some SQL for Oracle that it doesn’t support. There are object oriented concepts in the model from a time when ERwin and Oracle didn’t do object oriented. The original Oracle target version was 7.3.2. The ERwin model has been migrated from version 3.5.1 to 3.5.3 to 4.0 to 4.1 with varying degrees of success. It seems like a perfect candiate for an import into TDM2.

Here are the XML import issues that I’ve found so far with TDM version 2.25.01…

  1. When I imported, it failed gracefully on the main subject area and generated an error XML file. (Kudos for not crashing altogether.) Where do I send the error.xml file???

  2. Since it wouldn’t import the main subject area, I skipped that and went on to the individual subject areas. The import loaded each subject area as a new TDM model rather than creating one model with a submodel for each ERwin subject area. I would want the entire ERwin model in one TDM model.

  3. Initial inspection of the TDM model showed that it imported physical attributes that I had marked as logical only in the ERwin model. Those attributes shouldn’t show up in the physical model or in the subsequent generated SQL code.

That’s a start. There may be more to follow as I look a little further. We can take this offline of the forum if you like.

Hello Bruce,

Here I’m with replies:

  1. Please download an updated package for ERWIN import to TDM2 from the following site:

Import the templates to the TDM2 Templates Editor.
-> Follow the instructions at the bottom of the site, or follow the ReadMe file included in the package. (See also Help file | Templates topic | Importing templates.)

Please check out the ERWIN XML file import again.

If it still doesn’t work, could you please send us your ERWIN XML file? (You can send it to: modeling@quest.com.)

  1. This problem shouldn’t occur in the updated package.
    Note: After you import the XML file to TDM2, select Model | Layout | Load (to load the .la2 file).

  2. TDM2 doesn’t have a logical model, and during the import the problem you describe can occur. We will further deal with it for TDM version 3.


BTW, in this community, only issues on TDM 3 are discussed.
TDM2 questions can be directed to the TDM2 Yahoo group at:


Vladka & TDM Team

Reposting on the Yahoo group…

OK. Thanks.


The XSD schema ERwin creates is its own internal format obviously.

We’ve created a set of tools to manipulate this into a canonical component set so you can have regular XML schema of those.

There’s a quick guide of the steps - create the dictionary - and then Export the XSD schema from the resulting template.

Here’s where you can find all this and the open source tooling.



Hi David,

thanks a lot! We will definitely check it. And I believe others will appreciate this as well.


Hi, I was able to add the Export xml from erwin but I’m getting an error: unsuppported database

Is there any recomendations to follow? I’ve exported the xml from Erwin (File-> save as -> xml)
but it seems something is wrong.
Could you advice?

Message was edited by: John2050


this thread is relatively old (started in 2007). Let me write here some general information:

  1. There is a package for importing ERwin models to TDM.
    Please note that only Oracle 10g and Oracle 9i models can be imported and format must be ERWin 7.1 XML. Newer versions of ERWin XML format are not supported.

  2. If you work with unsupported databases, the following article might be useful.




Is there a workaround for importing newer versions of ERWin XML?

Hi, the only workaround I am aware of is reverse engineering from physically existing database and updating the model metadata from XML. More info:


Good luck,