DataModeler: Cannot engineer from logical model to relational model

Hello,
I have been trying for a couple of (very frustrating) hours to engineer a very simple logical model to its relational model. The toolbar button (and also menu option) that should do this just does nothing. No errors, no feedback, absolutely nothing!!! However I could engineer a relational model back to its logical model.
I am using SQL Modeler version 1.5.1 build 525 on Windows Vista. I have closed and restarted the program many times but to no avail. Are there other factors (e.g. anti-virus, JDK etc) that could be responsible? But then why are other parts of the software working but not this one?
Please kindly send your advice asap so I can proceed. I really like the Modeler and will not want to discard it.
Thanks,
Chiedu

Hi Folks,
I was able to figure out the likely cause of the problem. The version of Modeler (datamodeling-1.5.1-525-no-jre.zip) I used was downloaded without JRE. The current version of JRE installed on my computer is Java 6 Update 12 (build 1.6.0_12-b04). I suppose the two don't quite work very well together.
I have now downloaded and installed another version (datamodeling-1.5.1-525.zip) with its own JRE and the problem was resolved.
My guess is that the problem was due to the incompatibilities that may exist between Data Modeler and the various versions of JRE.
Thanks.

Similar Messages

Strange mapping of Boolean from Logical to DB2 Relational model

Hi guys,
Using most recent version of Data Modeler (3.3.0.747) I notice strange behavior:
Attribute, declared as Boolean in Logical model is engineered to a column, with type CHAR(1) in Relational Model, when "RDBMS Type" is Oracle, but when "RDBMS Type" is "DB2", column type is CHAR(254)
Is this a bug or a feature?
Is there any way, where I can control type mapping between logical and relational model?
Well, I can just go and change CHAR(254) to CHAR(1) all over my Relational Model, but this is pretty frustrating.
MfG,
Stoyan Tsonev

Hi Stoyan,
Is there any way, where I can control type mapping between logical and relational model?In fact mapping is between logical data type and database native types - Tools>Types Administration.
You need to change mapping for Boolean logical data type - check "size" check box and put value in text field to define default size. Default size will be used when there is no explicitly defined size in column/domain definition.
Philip

Engineer between Logical Model and Relational Model

I am trying to update changes from one model to the other but there are dublicate entries generated instead of updates.
The Logical Model was imported from Oracle Designer, the Relational Model was imported from data dictionary.
Our rule is, that the name of Entities/Tables and Attribute/Columns are identical.
So I changed the Naming Standard of the Logical Model in Preferences
from Separator = Space to Separator = Character with char = Underline.
If the entity is not existing, it is created with the correct name.
If the entity exists, a new entity is created with Namev1.
The same happens when I try to update changes in the other direction.
How can I achieve that the existing entity (or table) is updated and not a new one is created?
Or in other words, is there a way to link entities to corresponding tables?
Walter

Hi Walter,
The Logical Model was imported from Oracle Designer, the Relational Model was imported from data dictionaryit's good to import entities and related tables from Designer repository together. Data Modeler will import the link between them and use that link in synchronization between logical and relational model. After that you can import details for physical model from database.
If you don't have tables in Designer repository and keep the same names for entities, attributes, tables and columns then you can engineer logical model to relational and import details from database.
Philip

Engineering logical subtypes to Relational model

I have a logical model with subtype (box in box). When I forward engineer to a relational model there is nothing in the model to represent the subtypes. I was expecting (as in old Designer) to see a differentiator "type" column to be generated with a column check constraint based on my subtypes. In the logical model I selected "single table" as the implementation strategy.
Note I also have these entities tagged as Dimensions and did notice the engineering dialog showed the substypes as hierarchies too.
Am I missing a a preference setting somewhere?

Hi Kent,
I was expecting (as in old Designer) to see a differentiator "type" column to be generated support for that will be added later.
Note I also have these entities tagged as Dimensionswhat do you expect - if you change implementation from "single table" to something else you'll get tables also classified as dimension, no other magic will be involved
and did notice the engineering dialog showed the substypes as hierarchies tooI don't see your point here.
Philip

Delete Rules between Logical Model and Relational Model are different

Relation Properties in Logical model has three Delete Rules: "RESTRICT", "NO_ACTION", "SET NULL".
1. "RESTRICT" and "NO_ACTION" are same
2. "CASCADE" is missing.
However, Foreign Key Properties in Physical model has three Delete Rules: "RESTRICT", "NO_ACTION", "CASCADE".
1. "RESTRICT" and "NO_ACTION" are same
2. "SET NULL" is missing in this case.
They are supposed to have "NO_ACTION or RESTRICT", "SET NULL", and "CASCADE".
Please fix this ASAP. It is really annoying in Engineering process. Modeler creates duplicate wrong relationships while it engineers.
Thanks.
Edited by: hayangae on Oct 9, 2012 1:01 PM
Edited by: hayangae on Apr 3, 2013 4:08 PM

Hi,
it seems you are not using the latest version 3.3. In earlier versions - delete rule set on relationship was used only in some cases to set delete rule on related foreign key. Now delete rule is transferred to FK as it's defined on relationship.
I assume you are using Oracle database - "Restrict" doesn't appear anymore for Oracle.
2. "SET NULL" is missing in this case.Most likely the foreign key is set as mandatory thus you cannot use "set null" as option.
Modeler creates duplicate wrong relationships while it engineers.Can you elaborate on that - example?
Philip

Design - Engineer to Logical Model: Nullpointer Exception

Hi
I imported in my physical data model as relation model using Import -> Data Dictionary. Craeted a subview (in relational model) and reverse engineered to logical model. Worked fine.
Now I created more subviews(ard 10) in relational model and when try to reverse engineer, get nothing on screen.
In <datamodeler>\datamodeler\log\datamodeler.log find the following exception:
2011-10-25 12:22:39,588 [main] INFO DataModelerAddin - Oracle SQL Developer Data Modeler 3.0.0.665
2011-10-25 12:25:20,344 [AWT-EventQueue-0] ERROR MDBAction - java.lang.NullPointerException
Any help would be appreciated.
Regards
P.S have approx 90 tables in relational model where I created subviews. Also have 2 more relational model with in same design with just tables import in them.

Philip
Thanks for your answer. I downloaded and installed 3.1 EA1 and for some weird reason I dont see Design menu as it was in DM3.0.
I have uploaded a snapshot (No Design Menu in DM 3.1) with menu and about. I tried uninstalling and reinstalling the 3.1 too with out any success.
Any pointers?
Regards

Views always appear as different when engineering from Logical to Relational

I created some views in my logical model. After I engineer them to relational model, they appear in relational with an exclamation mark near the upper left corner. If I try to generate ddl for them, I get an error (-- ERROR: Invalid View VwTest). I realized that I have to "validate selected views", in order for the eclamation mark to disappear, and then I am able to generate ddl for them. After that, when I engineer from logical to relational again, it always shows me that my views are different. The difference is that in logical, my entities are shown between double quotes ("), while in relational, after the validation, the tables are not between double quotes. Is there a way to overcome this?
Thanks

Hi,
Thanks for reporting this problem. It appears that this is happening when the Entity name contains lower-case letters.
David

Problem when engineering to relational model

I have modeled everything in Logical model and then engineered it to the relational model. Now I have to make some changes, and I'm doing them in Logical model. When I'm engineering it to Relational, although I just altered one single item, I see that it's also bringing some other entities as altered. Inpecting these I see that all of them relate to identifying foreign keys with more than one column. For examplo, I have an entity with 2 columns as primary key, and a second entity with an identifying foreign key to the first, and a third column, based on a sequence, which, all three of them, are the second tables primary key. Everything is OK, I haven't changed anything on any of these entities, but when I'm engineering to relational, it creates a duplicate of one of the columns on the relational model, and alters it's name appendig a number 1 after it. If I try engineering again, it is going to create another column appending a number 2 and so on.... I think this is a bug.... am I right?
My alternate solution is to drop the foreign key on the relational model, thus dropping both columns, and then engineering from Logical again. Everything keeps working fine, until I close my model. When I open it again, the same problem reappears....

Philip,
Sorry for my too late reply, as I forgot to flag this discussion to notify me via e-mail. Thanks for your response, but I was actually using DM 4.0.1.836 and this issue still persisted.
I just downloaded DM 4.0.2.840, and the issue still persists. I just opened my original model and, without making any changes, tried to forward engineer from logical to relational, and it brings up differences on exactly the same tables.
Wolf
P.S.: I've gone through the motions of dropping the FKs on the relational model, dropping any orphaned columns (from these FKs) and re-engineering. Afterwards, I saved and closed all models, closed the application, opened it again and opened my model and the issue persists.
I also created a new model, with some tables using the same principles, and no error occurred, although in this new model I didn't create a physical model.
Is it possible that something is wrong with my original model?

Problem with naming of FK attribute when generating the relational model

I'm usign Data Modeler 4.0 and I have a problem when I engineer from Logical model to Relational model.
I have a table SUBJECTS with an unique identifier called ID (pk) and a table BOOKS related to SUBJECTS with a relation named FK_SUBJECT_BOOK and FK attribute named ID_SUBJECT.
When I engineer to Relational Model, it transforms the original FK attribute ID_SUBJECT of the Logical model into an attribute called SUBJECTS_ID in the Relational model.
How can I mantain the name defined in the Logical model also in the Relational model, without using abbrevation and without applying name translation when generating the relational model?
Thank you

I have already tried it. The problem is that if I check the option you mention, then it uses the pk as it is in the related table creating attributes like ID1, ID2, ID3 and so on for all the relations you have.

Logical model fwd engineer to relational model. Missing FK relationships

We are experiencing missing relationships in the relational model when engineering from logical model to the relational model. The logical model objects have properly defined primary keys defined. We are using SQL Data Modeler v3.1.700. Any suggestions on how to engineering these relationships without deleting the objects from the relational model.
Thanks,
Ed

Hi Ed,
I presume you had some relationships in the Logical Model that you were expecting to be engineered to Foreign Key relationships in the Relational Model.
Please can you provide more detail to help resolve your problem. For example:
Was the problem on an initial engineer from the logical model? Or on a re-engineer?
Are you using Entity subtyping in your Logical Model?
Are there any relevant error messages in the log file? (This is normally file datamodeler.log in folder datamodeler\datamodeler\log.)
David

Engineering from relational model to logical model duplicated views

Hi all,
Several times, also in different projects, when I engineer from relational model to the logical model, the comparator tool show me de differences.
In these differences there are no view differences, but when I finish the process everything goes right except that in the logical model under views, I see all the views duplicated with [view_name]v1.
I've tried not selecting the view checkbox, in the compare dialog,but I get duplicated views also.
I don't know fir sue if this happens with table also.
What can I do to solve this problem? Is this a bug?
Edited by: morfeo8marc on 04-abr-2012 2:02

The problem is fixed in DM 3.1.1.703 and it's published. You can run following script and save design in order to get mappings for views recovered.
Philip
lmodel = model.getDesign().getLogicalDesign();
rmodels = model.getDesign().getRelationalDesigns().toArray();
for (var i = 0; i < rmodels.length; i++) {
rm = rmodels;
eviews = lmodel.getEntityViewSet().toArray();
for (var k = 0; k < eviews.length; k++) {
ev = eviews[k];
tv = rm.getTableViewSet().getObjectByID(ev.getGeneratorID());
if(tv == null){
tv = rm.getTableViewSet().getObjectGeneratedBy(ev);
if(tv != null){
rm.getRMExtendedMap().createMapping(ev,tv);

Engineering to and from logical and relational models

I have tried to modify a logical model entity by adding an attribute or two, tried to engineer to the associated relational model, only to have the engineering process create a brand new table rather than adding the new column or two to the existing table.
Creating the column in the table first and engineering back to the logical model didn't appear to do anything, although I might have missed a new logical entity.
Is this how the product is supposed to work?

Hello,
I'm sorry but your steps are not evident for me.How it works - you can start from table or entity, it doesn't matter which one is first you should be able to synchronize changes.
Let's assume you have two relational models RM1 and RM2 and table TABLE_1 in RM1. if you engineer RM1 to logical model then entity will be created that corresponds to TABLE_1 in RM1 (and it will be named TABLE_1 if you don't use glossary that provides replacement of TABLE with something else).
You can add attribute to entity and engineer logical model to other relational model (RM2) - new table will be created in RM2.
Add one more attribute to entity and engineer to RM1 - two attributes will appear showing that two new columns can be created - they are not selected and you have to select them if you want columns to be created.
You'll get only one new attribute (column) if you engineer to RM2 - the first added attributed is already there as column.
Of course you can add columns in tables and can synchronize them with entity in logical model.
Philip

Sql datamodeler: Engineer to relational model: General Options

Hello
When you engineer your logical model to a relational model you get a wizard. In lower part of this wizard byou have several tabs, one of the tabs is called general.
On this general tab you have check box: Apply Name Translation
The corresponding help text:
Apply Name Translation: Controls whether formal names are translated to abbreviated names when the logical model is forward engineered to a relational model, and whether abbreviated names are translated to format names when a relational model is reverse engineered to the logical model. Name translation is applied only for valid names. In addition, translations between the words entity/attribute/key and table/column/index are performed.
Does anybody have a clue what is meant here?
Regards Erik

Erik,
you have to create glossary (tools>Glossary editor) with words permitted for usage in names in logical model. For each word you can define abbreviation that will be used in transformation process.
Example:
Employee - EMP
Salary - SAL
Attribute "Employee Salary" will be transformed to column "EMP_SAL".
You can define preferred abbreviation for entities and attributes and it can be used instead of glossary definitions.
You also have to set your glossary in "Tools>General Options>Naming standards>Glossary"
Best regards,
Philip

SQL Datamodeler: engineer to relational model: column names

Hello
Suppose I have an attribute called DAY OF BIRTH. Is there a way I can forward engineer this attribute to a column name DAY_OF_BIRTH?
(I know you could have a coulmn name "day of birth" but thats not what I want)
Regards Erik

Hi Erik,
1) you should check separator settings in General options>Naming Standard -it should be "space" for Logical model and "underscore" for Relational model;
2) "Apply name translation" should be selected in engineering dialog
Best regards,
Philip

Column Prefix from Logical to Relational Model

Hi,
is there any option, that data modeler append an prefix (table short name) to a column, when the logical model will be transformed to relational model? (Same behavior as Oracle Designer)
Example:
Logical Model
TABLE: PERSON
TABLE-SHORT: PERS
COLUMN-1: ID
COLUMN-1: NAME
Relational-Model
TABLE: PERSON
COLUMN-1: PERS_ID
COLUMN-2: PERS_NAME
Kind Regards,
Stefan

Thanks for your answer!
This Script is not really working for me, because of our foreign keys.
All our Foreign-Keys are named "ID" (for nummeric column) or "INDEX" (for a varchar column). After the transformation form logical to relational all the foreign-keys are named like "ID1", "ID2", "ID3", "INDEX1", "INDEX2" etc.
There is no way to apply this script before the foreign-keys where added in the tables?
The Second Way is to create a new script for this task.
am i the only one with this problem? :-/

DataModeler: Cannot engineer from logical model to relational model

Similar Messages

Maybe you are looking for