This content has been marked as final. Show 7 replies
comments and comments in RDBMS are in separate files DM_CommentsRDBMS.csv, DM_Comments.csv and DM_Notes.csv
So if I do not see those files in the output directory, does that mean there are not comments or notes in the model anywhere? I see plenty of other files (like DM_Entity.csv) that are empty (because I he no logical model), but the three you mention are missing completely.
I am running 3.3EA1.
I can confirm now that in 3.3EA1 the comment files are not being created. I just uploaded comments for 1600 columns (using the new find/export/import features) so I know they are there. Still no output.
Looks like a bug.
so I know they are there. Still no output.we can fix a bug only if we can reproduce it. So it'll be helpful for us if you can provide a test design we can use to reproduce the problem.
Looks like a bug.
Sure - how do I get a copy of the design to you? (under NDA of course)
customers data are covered by strict company rules. So for me NDA is in effect. You can create service request or zip the design and send it to me.1 person found this helpful
I don't need the whole design, just a slice of it that will allow to reproduce the problem.
How to create a slice:
- create a subview and put some objects in it;
- export to "Data Modeler Design" - select only the subview created in previous step;
- open the new design and export to CSV - if problem exists then the slice is good for testing.
Turns out I was getting an error in my log file when the export to csv was run:
2013-01-29 09:21:09,170 [Thread-23] ERROR CSVExporter - Error Exporting to CSV:
java.lang.RuntimeException: rdbmsName not known: SQL Server 2008
at oracle.dbtools.crest.model.design.LogicalDatatype.createDataType(Unknown Source)
at oracle.dbtools.crest.exports.csv.EHLogicalToNative.Export(Unknown Source)
at oracle.dbtools.crest.exports.csv.CSVExporter$Runner.run(Unknown Source)
I had forgotten that the design I was working with had actually come from reverse engineering a SQL Server database.
From that Philip was able to surmise that my Default System types directory was pointing to a directory with an old defaultRDBMSSites.xml file (pre-3.3EA) which did not have SQL Server 2008 defined. Once I pointed the directory to the current file, everything worked fine.
So not a bug, just a bad setting. User error. :-)