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

Similar Messages

  • How to show relation attribute on logical model

    Hi.
    How to show child entity relation attributes on logical model?
    Entity properties attribute list contains relation attributes, LM dont show they.
    I have model with several subviews. I need to show some entity without related entities but need to save "semantic" of relations on this subview. When relation attributes does not visible - no information about invisible relations on this subview.
    I can create my own visible attribute like "reference to customer" to make sense the relation with entity "Customer". This case problem is relation attribute presents in entity implicitly and relation model have 2 attribute - my own and generated FK column.
    In logical model i can`t replace child table relation attribute to my own "visible" attribute.
    In relational model i should redefine FK manually. Transformation script is posible but very odd way.
    Any advice appreciated.

    I am confused.
    I think the legacy Oracle Designer Barker notation could show reation attributes optional or by default, int`t it?
    Thanks a lot anyway.

  • 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

  • Q:  Data Modeler - Logical Model - 0 or 1 to....relationships...

    Hi,
    I’m currently at a client where we’re using Oracle SQL Developer Data Modeler to design our Logical Data Models (as part of an overall deliverable).
    When in the Oracle SQL Developer Data Modeler (in the logical view), I’m trying to figure out if the tool has the ability to create a “zero or one to” relationship between entities.
    According to the relationship options available, it only seems to show:
    One to One,
    One to Many (*),
    Many (*) to One, or
    Many (*) to Many (*)
    In the preferences – Data Modeler – Diagram – Logical Model, the notation type is set to “Barker”.
    I don’t see anywhere else where configuration can affect the variation of these options…
    Is there a way to show either a “Zero or One to…” relationship between entities?
    I’ve also loaded version 3.1 (beta) and it appears to be behaving the same as 3.0…
    Any insights are greatly appreciated…
    Thanks,
    Patrick

    Hi Kent,
    When I looked at this option, I was expecting to see a "|" and/or "O" in front of the crow's feet. I was not expecting to see a dashed line. Now I know...
    Thanks for your reply.
    Regards,
    Patrick

  • 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

  • How to copy field comments from logical model to relational one?

    Dear gurus!
    I had a logical model without field comments. Then I made an engineering of logical model into relational one. Later I added field comments to logical model. How can I copy these values to relational model? Seems to me that when I use
    model.getTableSet().toArray()
    then I get list of relational model tables. How can I get a list of logical "tables" and to get a relations between those two lists?
    Thank you!
    Edited by: user12947051 on 12.01.2012 23:58
    Edited by: user12947051 on 12.01.2012 23:58

    You don't need to write and run script for that. Just use engineering to relational model. Use compare/copy options tab if you don't want something else to go into relational model
    Philip

  • 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.

  • 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

  • Unable to generate Logical Model Diagrams through Reverse Engineering

    Hi,
    I am currently using SQL Developer Data Modeler Version-3.0.04.
    I have generated Logical Model Diagrams from Relational Model Diagrams through Reverse Engineering (Done by pressing an" engineer to Logical Model button" on top panel of sql developer) .I saved the DMD file (source file) once i had done generating the logical diagrams.Now if i reopen the DMD and open the logical diagram again I found that most of the tables had lost their relationships.So i tried to regenerate the Logical Model Diagram again from the same Relational Diagram but it is not being generated unless i create a new Relational Diagram.Is there a way to generate multiple Logical Diagrams for the same Relational Diagram rather than creating a new one for each Logical Diagram to be created.
    Regards .
    Thanks in advance.

    Any comments on this issue?. Please let us know.

  • 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?

  • DM 3.0.0.665: How to remove arc from relational model

    When creating an arc in the logical model, "engineering to relational" will update the relational model so "DDL Preview" shows DDL for two triggers that enforce the arc.
    After removing the arc from the logical model and "engineer to relational" I still see the trigger code in "DDL Preview", as if the arc is still there.
    Where can I see the arc in the relational model, and how do I remove it from the model?
    / Marc de Oliveira
    Edited by: marc66 on 2011-03-01 06:49

    Marc,
    you can see the arc on diagram - probably it's hidden. You can move some of parent tables and probably it'll appear. If still invisible then you can create subview and put child table and two parent tables on it - arc should appear and you can delete it.
    Philip

  • DM3.0 EA2: Logical Model Relation Cardinality:Source Optional mislabeled?

    In logical model, created a 1:N non-identifying relation between 2 entities - Parent and Child. Parent is 1:N with Child. Both entities have a single column primary key - parent_id and child_id respectively. I would like to enforce RI such that a parent may exist with no children, but a child may not exist without a parent.
    In the logical model the relation properties, cardinality - I modify the Source Optional and Target Optional checkboxes to achieve my desired result. I first tried checking Target Optional and leaving Source Optional un-checked. I then engineer a physical model and generate DDL for Oracle 11g I get this constraint:
    SQL>ALTER TABLE child
      2      ADD CONSTRAINT Relation_1 FOREIGN KEY
      3      (
      4       parent_id
      5      )
      6      REFERENCES parent
      7      (
      8       parent_id
      9      )
    10      ON DELETE SET NULL
    11  ;
    Table altered.Here's a test case illustrating this isn't quite what I wanted (starting with both tables empty):
    SQL>
    SQL>
    SQL>insert into parent (parent_id) values (1);
    1 row created.
    SQL>commit;
    Commit complete.
    SQL>
    SQL>insert into child (child_id, parent_id) values (901, 1);
    1 row created.
    SQL>commit;
    Commit complete.
    SQL>
    SQL>delete from parent;
    delete from parent
    ERROR at line 1:
    ORA-01407: cannot update ("ODS_ETL_OWNER"."CHILD"."PARENT_ID") to NULLIf I have Source Optional checked, and Target Optional not checked, engineer a physical model and generate DDL for Oracle 11g I get this constraint which produces the desired results with my test case:
    SQL>ALTER TABLE child
      2      ADD CONSTRAINT Relation_1 FOREIGN KEY
      3      (
      4       parent_id
      5      )
      6      REFERENCES parent
      7      (
      8       parent_id
      9      )
    10  ;
    Table altered.
    SQL>
    SQL>insert into parent (parent_id) values (1);
    1 row created.
    SQL>commit;
    Commit complete.
    SQL>
    SQL>insert into child (child_id, parent_id) values (901, 1);
    1 row created.
    SQL>commit;
    Commit complete.
    SQL>
    SQL>delete from parent;
    delete from parent
    ERROR at line 1:
    ORA-02292: integrity constraint (ODS_ETL_OWNER.RELATION_1) violated - child
    record foundBut that seems backwards - and the documentation also reads as if it’s backwards. Am I missing something or are the Source Optional and Target Optional checkboxes mislabeled? Should they be Source Manditory and Target Manditory?

    I would like to enforce RI such that a parent may exist with no children, but a child may not exist without a parent.You need to set parent as optional and child to be mandatory.
    Am I missing something or are the Source Optional and Target Optional checkboxes mislabeled? Should they be Source Manditory and Target Manditory?There is a relationship and two ends of that relationship and you can set for each end whether it's optional or not. And that's seen directly using Barker notations. Source and target optionality place will be swapped on diagram if you use IE notation.
    I expected that cardinality part could be more confusing for you because at source end you define cardinality of the target, but it seems you have no problem with that.
    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

  • 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

  • Select schemas from relational model on import from data dictionary option

    Hi All,
    I have one relational model with 3 diferent schemas,
    I want to compare one of my schemas with the data dictionary I have in a database,
    I select the import option in the general file menu, select from data dictionary option,
    select the connection from my database,swap target model checked,select a physical model and select the objects i want to compare from the database,
    My problem is that the result is the comparison between all the objects in my model and the objects in the database that I have selected,
    what I really want is to compare a list of objects in my model to a list of objects in my database,
    this could be possible? or always need to compare all the objects of the model?
    Thanks in advance

    Hi jbellver,
    there is no any development in DM 3.1.0.691 on that problem. In production release you'll be able to compare objects in subview with database or just to select several objects and compare them with database. And of course "generate in DDl" filtering still can be used - it works at "Compare dialog" level.
    Philip

Maybe you are looking for