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?

Similar Messages

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.

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);

[BUG][4.0EA3] Invalid surrogate key is created after engineering to relation model

Repro steps:
Go to Tools -> Domain Administration. Add new domain named MyIdentifier with logical type UNIQUEIDENTIFIER. Apply and save changes.
Go to Tools -> Preferences, then Data Modeler -> Model -> Relational. Get to Surrogate Column Data Type group box and set Domain = MyIdentifier. Apply changes.
Create new Entity and enable option "Create Surrogate Key". Apply changes.
Engineer to Relational Model with default settings.
Expected result:
Entity_1_ID column's data type is UNIQUEIDENTIFIER
Actual result:
Entity_1_ID column's data type is CHAR

I've forgot to mention, that my default RDBMS Site is set to SQL Server 2008. In Types Administration UNIQUEIDENTIFIER is mapped to CHAR for Oracle, but it mapped to UNIQUEIDENTIFIER for SQL Server 2008.

Data Modeler: Super Type and Inheritance when engineered to Relational Mode

PLEASE IGNORE THIS MESSAGE, I'VE SORTED IT. MY STUPIDITY HAS BEEN RECTIFIED BY READING THE MANUAL!!
Hi
I have a logical model that I'm playing with where I want to set a super type entity that contains common columns for all sub-type entities a la java inheritance.
When I engineer this with the super type entity method set to 'Table for each entity' it creates a table for the super and sub entities and links them with a PK-FK.
That's not what I was expecting.... I would like to get :
PARENT ENTITY (Super Type)
ATTRIBUTE1
ATTRIBUTE2
and
CHILD ENTIRY (Super Type = PARENT ENTITY)
CHILD_ID PK
DESCRIPTION
when this is engineered I'd like:
TABLE = CHILD_ENTITY
Columns:
CHILD_ID PK
DESCRIPTION
ATTRIBUTE1
ATTRIBUTE2
Any ideas what I'm going wrong here????
Cheers
Chris
Edited by: chriseb on Aug 13, 2009 2:46 PM

Hi Chris,
I'm glad that you have sorted it out. Then you can mark the question as answered.
Philip

Why are tables disappearing when Engineering Logical Entity Hierarchies to Relational

Tables disappearing when Engineering Entity Hierarchies Logical to Relational
We are using 4.0.3. We have a model with imported from Designer with a number of Entity Hierarchies.
The model has a three of entity hierarchies (ORD, PLAN and STEP) each with a number of subtypes. Single tables are built for each of the entity hierarchies and are called (ORD, PLAN and STEP).
If I make a change within an entity hierarchy in the subtype (ORD_METRIC) and forward engineer the only ORD entity hierarchy as single table, the table ORD gets update but the tables STEP and PLAN disappears from the Relational table list. They only remain if I select all three entity hierarchies when engineering to relational.
Have I a missed selecting an option?

Hi,
in current implementation for entity hierarchies (only) - "engineering to" flag is used also as implementation flag for entity, i.e. if entity is not set to be engineered there will be no implementation as table for that entity in relational model. Attributes of such entity will be implemented in another entity engineered to relational model. If no one entity from hierarchy is engineered (no implementation) then existing corresponding table(s) will be removed.
We'll change it in the future to be less confusing.
Philip

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

Error engineering logical data model to relational data model -- name column hierarchies

Hello,
I have three entities, Entity1 is logical only , entity2 is a subtype of entity1, and entity3 is a subtype of entity1.
Entity1 has the abbreviation ( PRUE) and entity1 has three atributes ( PRUE_PPPPPP, PRUE_OOOOO).
when I make engineering the columns resulting in entity2 and entity3 are PRUE_PRUE_PPPPPP and PRUE_PRUE_OOOOO
I have unchecked the options apply translations of names and preferred use abbreviations in general options (engineering)
and the tree comparison is the right name (While the result in the relational model is incorrect)
¿Any help?

Hello,
version 4.0.0.820.
I checked the options (naming standard template) and they are correct, the problem is in the engineering.
Thanks

FWDEngineering.execute() nullpointerException when engineering from logical to physical model

Dear Community,
During the "engineer to relational model" from the logical model I got a long time the correct behaviour.
Now I get the following error in the log file: "ERROR FWDEngineering - FWDEngineering.execute()" NullpointerException
The model is not that large but contains a number of entities with sub-entities for which I set the way of implementation to generate a single table.
Test 1: Restart
Removing the model has not solved the problem for this ... (delete entire relational model)
Test 2: reset subtype implementation to default behaviour
So on the level of the super entity the following settings are set on the subtype property page:
- subtree do not preset
- No Discriminator column
- no 'use attribute' selected
- no column name set,
The model generates the foreign keys ... and gives no error.
Test 3 : setting discriminator.
Juglin' around with the properties I noticed that when after starting from test 2 and setting the property "generate discrimator" *and* selecting the name of the discriminator colomn the error can be reproduced. Currently I do not know fit the setting subtree together with discriminator column is logically correct ... but I get the stacktrace ;-)
Test 4 : can the subtree generation mode solve it -> Seems I'm not able to set it to an other value than "do not preset" anymore.
Version datamodeler is 4.0.0.833
Test 5 : Created a smaller model ... and tested if the foreign key generation in itself caused the problem. Removing the relationship with a subentity does not cause the problem to not occur ...
At this moment in time ... it seems to me I cannot set the mode to generate the master entity and its subs to one table anymore.
What am I doing wrong?
... and anyway ... there is a stacktrace ;-)
Has anyone some solution/experience with this?
For the completeness ... the stacktrace, which shows a processDiscriminatorColumn ....
Oh yes ... also for completeness: in the test with a subentity not having a relationship the method calling the processDescr... is a different one inheritancePostProcessingNew() ...
Thanks you all.
2014-01-30 18:35:39,795 [AWT-EventQueue-0] ERROR FWDEngineering - FWDEngineering.execute()
java.lang.NullPointerException
at oracle.dbtools.crest.model.design.engineering.FEEntityHierarchy.processDiscriminatorColumn(FEEntityHierarchy.java:592)
at oracle.dbtools.crest.model.design.engineering.FEEntityHierarchy.createFKeysNew(FEEntityHierarchy.java:921)
at oracle.dbtools.crest.model.design.engineering.FEEntityHierarchy.inheritancePostProcessingNew(FEEntityHierarchy.java:861)
at oracle.dbtools.crest.model.design.engineering.FWDEngineering.processEntities(FWDEngineering.java:275)
at oracle.dbtools.crest.model.design.engineering.FWDEngineering.execute(FWDEngineering.java:107)
at oracle.dbtools.crest.model.design.Design.forwardEngineer(Design.java:895)
at oracle.dbtools.crest.swingui.engineeringcompare.EngineeringCompareDialog.engineer(EngineeringCompareDialog.java:992)
at oracle.dbtools.crest.swingui.engineeringcompare.EngineeringCompareDialog.access$3200(EngineeringCompareDialog.java:125)
at oracle.dbtools.crest.swingui.engineeringcompare.EngineeringCompareDialog$22.actionPerformed(EngineeringCompareDialog.java:1777)
at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:2018)
at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2341)
at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:402)
at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:259)
at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:252)
at java.awt.Component.processMouseEvent(Component.java:6505)
at javax.swing.JComponent.processMouseEvent(JComponent.java:3321)
at java.awt.Component.processEvent(Component.java:6270)
at java.awt.Container.processEvent(Container.java:2229)
at java.awt.Component.dispatchEventImpl(Component.java:4861)
at java.awt.Container.dispatchEventImpl(Container.java:2287)
at java.awt.Component.dispatchEvent(Component.java:4687)
at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4832)
at java.awt.LightweightDispatcher.processMouseEvent(Container.java:4492)
at java.awt.LightweightDispatcher.dispatchEvent(Container.java:4422)
at java.awt.Container.dispatchEventImpl(Container.java:2273)
at java.awt.Window.dispatchEventImpl(Window.java:2719)
at java.awt.Component.dispatchEvent(Component.java:4687)
at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:735)
at java.awt.EventQueue.access$200(EventQueue.java:103)
at java.awt.EventQueue$3.run(EventQueue.java:694)
at java.awt.EventQueue$3.run(EventQueue.java:692)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.ProtectionDomain$1.doIntersectionPrivilege(ProtectionDomain.java:76)
at java.security.ProtectionDomain$1.doIntersectionPrivilege(ProtectionDomain.java:87)
at java.awt.EventQueue$4.run(EventQueue.java:708)
at java.awt.EventQueue$4.run(EventQueue.java:706)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.ProtectionDomain$1.doIntersectionPrivilege(ProtectionDomain.java:76)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:705)
at oracle.javatools.internal.ui.EventQueueWrapper._dispatchEvent(EventQueueWrapper.java:169)
at oracle.javatools.internal.ui.EventQueueWrapper.dispatchEvent(EventQueueWrapper.java:151)
at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:242)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:161)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:154)
at java.awt.WaitDispatchSupport$2.run(WaitDispatchSupport.java:182)
at java.awt.WaitDispatchSupport$4.run(WaitDispatchSupport.java:221)
at java.security.AccessController.doPrivileged(Native Method)
at java.awt.WaitDispatchSupport.enter(WaitDispatchSupport.java:219)
at java.awt.Dialog.show(Dialog.java:1082)
at java.awt.Component.show(Component.java:1651)
at java.awt.Component.setVisible(Component.java:1603)
at java.awt.Window.setVisible(Window.java:1014)
at java.awt.Dialog.setVisible(Dialog.java:1005)
at oracle.dbtools.crest.swingui.engineeringcompare.EngineeringCompareDialog.show(EngineeringCompareDialog.java:1766)
at oracle.dbtools.crest.swingui.browser.BrowserPanel$41.actionPerformed(BrowserPanel.java:1145)
at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:2018)
at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2341)
at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:402)
at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:259)
at javax.swing.AbstractButton.doClick(AbstractButton.java:376)
at javax.swing.plaf.basic.BasicMenuItemUI.doClick(BasicMenuItemUI.java:833)
at com.apple.laf.AquaMenuItemUI.doClick(AquaMenuItemUI.java:157)
at javax.swing.plaf.basic.BasicMenuItemUI$Handler.mouseReleased(BasicMenuItemUI.java:877)
at java.awt.Component.processMouseEvent(Component.java:6505)
at javax.swing.JComponent.processMouseEvent(JComponent.java:3321)
at java.awt.Component.processEvent(Component.java:6270)
at java.awt.Container.processEvent(Container.java:2229)
at java.awt.Component.dispatchEventImpl(Component.java:4861)
at java.awt.Container.dispatchEventImpl(Container.java:2287)
at java.awt.Component.dispatchEvent(Component.java:4687)
at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4832)
at java.awt.LightweightDispatcher.processMouseEvent(Container.java:4492)
at java.awt.LightweightDispatcher.dispatchEvent(Container.java:4422)
at java.awt.Container.dispatchEventImpl(Container.java:2273)
at java.awt.Window.dispatchEventImpl(Window.java:2719)
at java.awt.Component.dispatchEvent(Component.java:4687)
at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:735)
at java.awt.EventQueue.access$200(EventQueue.java:103)
at java.awt.EventQueue$3.run(EventQueue.java:694)
at java.awt.EventQueue$3.run(EventQueue.java:692)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.ProtectionDomain$1.doIntersectionPrivilege(ProtectionDomain.java:76)
at java.security.ProtectionDomain$1.doIntersectionPrivilege(ProtectionDomain.java:87)
at java.awt.EventQueue$4.run(EventQueue.java:708)
at java.awt.EventQueue$4.run(EventQueue.java:706)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.ProtectionDomain$1.doIntersectionPrivilege(ProtectionDomain.java:76)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:705)
at oracle.javatools.internal.ui.EventQueueWrapper._dispatchEvent(EventQueueWrapper.java:169)
at oracle.javatools.internal.ui.EventQueueWrapper.dispatchEvent(EventQueueWrapper.java:151)
at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:242)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:161)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:150)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:146)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:138)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:91)

Hi ViForEver,
thanks for detailed report. We also found the problem in engineering of entity hierarchy when existing attribute is used as discriminator column. No such problem when leave DM to create new discriminator column.
Problem is fixed and fix is included in the forthcoming patch release.
About your questions/observations:
can the subtree generation mode solve it -> Seems I'm not able to set it to an other value than "do not preset" anymore
Generation of table for given entity depends on "Engineer to" flag and it can have different value for each relational model. If the flag is checked then table will be generated for that entity
otherwise attributes will be implemented by another entity down or up in the hierarchy. So two combo boxes in "Entity and sub-tree generation preset" help you to set that flag for entity
and it's sub-tree. It's functionality behind them, not properties so they are always in initial state when you reopen dialog.
Currently I do not know fit the setting subtree together with discriminator column is logically correct
They are related - discriminator column won't be generated:
1) if you go for sub-types implementation
2)implement all entity but "References" is set to arc implementation.
Philip

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

Fwd engineering entity name changes to relational model?

I changed an entity name in my logical model after generating a relational model. But, I cannot figure out how to have SDDM (3.0.0.665) propagate this change to the relational model.
In the Engineer To Relational Model screen, if I select the changed entity from the tree view, in the Details pane there is a "Selected" check box next to the Name property (this line shows the discrepancy between logical name and relational name) but I can't check it. Under the Compare/Copy Options tab in that same dialog, the check box next to Name is checked. But, when I forward engineer the name is not changed.

BTW I just noticed that if I enable "Name Translation" then it seems to work. This is not at all intuitive or obvious, nor does it seem to be explained in the documentation.
According to the help:
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.

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

DM3.0 EA2: Filter engineering changes between logical and relational model

Hi,
when I am engineering changes between logial and relational model there are some issues at filter handling for me:
- When the filter "Show Modified Objects" is activated, the filter works only on the first level, e.g. on Entity level. On attribute level all attributes are displayed, not only the attributes which have really been modified. It is possible, to show on every level only the really modified objects?
- I think, selecting a Filter condition is circuitous. All filter conditions except "Show All Objects" keeps activated when I choose another condition. So I have to deactivate "Show Deleted Objects" when I want to see only the modified objects. It is possible to choose another control element for filtering, e.g. disjunctive radio buttons?
I am running Data Modeler on Windows XP with german localization and the JDK 1.6.0_11 from Oracle SQL Developer.

I logged bug for that.
Philip

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

Problem when updating Management Engine (ME) firmware - photo attached

Hello All:
I have encountered a perplexing problem when attempting to update the firmware in the Intel Management Engine. The firmware update is posted on the W520 driver page (it is package 83rf32ww). The problem is the error message shown in the photo below.
The update process starts when the MEUpdate.CMD file is selected within the DOS window, but after a few seconds, the error message at the bottom of the picture appears.
Any suggestions would be appreciated.
Thanks,
Michael
Solved!
Go to Solution.

Yes, except you're running it from C:\Windows\system32 rather than the expected C:\DRIVERS\WIN\ME.
Basically, you have to navigate to the folder FIRST, then run the file.
W520: i7-2720QM, Q2000M at 1080/688/1376, 21GB RAM, 500GB + 750GB HDD, FHD screen
X61T: L7500, 3GB RAM, 500GB HDD, XGA screen, Ultrabase
Y3P: 5Y70, 8GB RAM, 256GB SSD, QHD+ screen

Problem when engineering to relational model

Similar Messages

Maybe you are looking for