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…
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???
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.
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.