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

Similar Messages

SQL Developer Data Modeler: Logical model, unable to create arc

I have a logical model in SQL Developer Data Modeler. Entity A has two 'incoming' foreign key relations to entities B and C. Both releations have the same optionality and cardinality. I want to place both relations in an arc. I see the buttons in my toolbar menu, but they are not enabled. Even when I select both relations it is not.
Bringing the logical model to the relational model creates foreign keys. These foreign keys can be selected and when I do that the 'Create new arc' button in the relational model toolbar is enabled.
What am I missing in the logical model ...? The documentation doesn't give a clue.
Erik

Thanks Sue, that worked. It is different from the way the ERD in Designer worked. Is there any reasoning behind it. As far as I know you should only put into an arc two or more relationships pointing to the same entity with the same optionality and the same cardinality. Selecting the entity with the relationships can only help in identifying at which relationship end the arc should be created but that is obvious.
And asking the question is answering it: it will help in adding an arc to two or more entities originating and ending at the same entity (and same cardinality and optionality).
Is that the reasoning behind it?
Regards
Erik

Data Modeler / Logical Model / How to display the "relationship name" ?

Hi,
Oracle SQL Developper Data Modeler 2.0.0 (build 584):
I would like to know if there is a way to display the "relationship name" in the diagram for the logical model in the GUI interface and/or to print it?
I checked in the different setup tool options and I did not find it...
Thanks for your help.
Regards,
Robin Ouellet

Hi Robin,
you cannot "show" relationship name on logical diagram - you can show "name on source" and "name on target" properties. You can set them at cardinality page of relationship dialog, And make them visible in "Tools>General options>Diagram>Logical model" settings - it's "Show Source/Target Name" option.
For printing - you can use "File>Print Diagram" to print in different format. Also "File>Print" allow diagram to be printed to printer, plotter or PDF printer if you have one installed.
Philip

SQL Modeler: Logical Model Merge

Hi all,
I'll like to consolidate and merge two (and more) logical models into one single model. We have design teams that work separately and we need to consolidate their logical models into one. Is this possible? If yes, how can I do it? If not, will be added in a future release? Is there any workaround I could use in the meantime?
Thanks.

Thanks Philip.
All the while I did not see the Apply button at the bottom of the screen and so could not complete the process.
Thanks once again.
Chiedu

SQL Data Modeler - Problem Opening Saved Logical Model

I created a logical model in the Data Modeler tool and saved it as a .dmd file.
When I try to open the .dmd file nothing pulls up. I get the following logs:
2012-11-08 11:09:45 - Building Diagrams
2012-11-08 11:11:25 - Open Design: 'CTS'
2012-11-08 11:11:25 - Open Design: 'OK'
I created a test model and saved it as a .dmdz file and I get can it to open. I tried to revise the file type of my original model to .dmdz and when I try to open, I get the following error message and nothing shows up.
"Some objects are not loaded correctly. See the log file for details." There is nothing in the log file.
Any ideas about how to get my .dmd file to open correctly?

What worked for me was going to Tools .. Preferences .. Data Modeler, and then making sure that each of the "Default <x> Directory" specifications pointed to a part of the hard drive that my operating system login user had permission to reach. (I suggest a sub-directory under your login user's "My Documents" or "Documents" folder, or whatever your operating system calls it.) Allowing the initially blank defaults produced weird behavior on my machine. YMMV.
Mark

Data Modeler Logical Data Type confusion!

I don't get it.
When defining a logical model, I want to assign data types to the attributes in my model.
I understand a logical datatype like money, and that a logical datatype might be implemented differently in different databases. The concept makes perfect sense to me.
I pick a datatype from the Logical Types.
It ignores the logical datatype that I picked and puts in another datatype instead. I'm guessing that it's a physical mapping. I would understand the logical-to-relational mapper doing that , but I don't understand it happening at this point in the model life cycle.
Let's say I pick Money. It puts Double into the logical datatype, not money.
If I pick Date or DateTime, it puts Date into the logical datatype, so what is the point of giving me two types to pick from?
Seems kind of wonky.

David,
We will publish soon a document on how the data types work.
If you go to tools, Types administration you will see that a logical type is mapped to a native type and a native type is mapped to a logical type.
The logical type MONEY is mapped to DOUBLE for Oracle.
Types and domain files can be customised.
One could argue that the logical name MONEY should show up and not the native name. Showing the native name has the benifit that you see what the logical type is mapped to. Both approaches could have their supporters, no?
Kind regards,
René De Vleeschauwer
SQL Developer Data Modeling.

Data Modeler 3.0 / Logical Model / Move relationship names

Hi,
When showing relationship names in the logical model they often appear at a not so good place
(eg two labels at the same location, lable over a table name,lable showing nowhere near his relationship line, etc...)
In the former edition, when the model was still saved as a .xml file we had the possibility to 'move' the labels around
and put them at a more proper place and as such create a solid and clear schema.
In the new version (3.0.0....) it is no longer an xml file but a .dmd file that is created and it is no longer posiible to move the labels (relationship names).
They can only be resized...
The loss of this functionality is ..... making me print the schemas whithout displaying the relationship name (if not the outprint is rather messy)
Is there a way to move the labels?
and if not , will it be re-enabled in a next edition?
reards,
E.

Hello!
I have to follow this thread too.
I use SDDM 3.3 EA2
The autorouting of FKs is great and at the same time annoying. Sometimes the endpoints of FK-Lines stick to entities and you can't move them to a correct position.
Sometimes when you position the FK-lines in a desired postion and you resize the subview the autorouting changes them. Very annoying!
Formating notes is possible but when you open the subview again the format is lost.
Positioning self joins is another 'tearing the rest of my hairs'
And you cannot set the width of borders of entities
And I'd like to have the possibiltiy to change or configure at least 2 or all fields of the legend
To offer something positiv. Thank you very much Philip, for adding the possibilty to change the grid size!
Best wishes
Guenter

Engineer to Logical Model in SQL Developer EA4 causes problems

I'm working with SQL Developer 3.0 EA4 (Build MAIN-03.97)
Unfortunately I fond out, that it would be impossible to use the function " Engineer to Logical Model" any more after I change the relational model. In datamodeler.log I got the error message line "[AWT-EventQueue-0] ERROR MDBAction - java.lang.NullPointerException" for each time I use the function "Engineer to Logical Model". I try it out with the sample model "sh_cre_all.sql" and with following steps:
1) Import via DDL File – no problem
2) Engineer to Logical Model – no problem
3) Change some attributes in the relational model – no problem
4) Again Engineer to Logical Model – no problem
5) Save, Exit an Open the sample – no problem
6) Again Step 3 and 4 – no problem
7) Add a table via drag&drop from an oracle schema – no problem
8) Save, Exit an Open the sample – no problem
9) Engineer to Logical Model no longer possible!!!
Bernd

I have experienced similar problems with 'Engineer to Logical model'.
The scenario was following:
Creating Logical model using 'Engineer to Logical model' from existing Relational model.
Modifying the Relational model and 'Engineer to Logical model' again. No exception occured but the Logical model wasn't updated accordingly.
Removing all entities from the Logical model.
Trying to 'Engineer to Logical model' again. No entities were created in the Logical model (even after few tries).
So I got to situation where I was unable to generate a Logical model, which was quite frustrating.
The workaround was to create new Data Modeller project and import to it from the original project - the 'Engineer to Logical model' worked again.

Bug regarding not filling in length of varchar field in logical model?

I successfully was able to create a logical model, engineer to relational, and generate DDL from this.
However, I found after generating the DDL and attempting to run it, I received errors in creation of some tables saying "missing left parentheses."
After going back and checking, it turned out that I was somehow able to define columns of type varchar in the logical model without putting in a length for the column. Data Modeler generated the DDL for the table looking something like this:
CREATE TABLE LIC_TYPE
    ID     INTEGER NOT NULL ,
    CODE   VARCHAR2 (1024 BYTE) NOT NULL ,
    "DESC" VARCHAR2
LOGGING ;
(for the DESC column) -- which then throws an error.
Should DDL generation should throw a warning when attempting to create CHAR or VARCHAR columns without a length instead of generating the DDL with no errors? Or is this intended functionality?
Using SQL Data Modeler/SQL Developer 4.1 EA2.

Hi,
Thanks for reporting this problem. I've logged an enhancement request.
David

How convert spaces in logical model to underscores in physical model

Hi,
in Oracle Designer we used spaces in logical model objects (entities, attributes, relations) which were automatically converted to underscores when the physical model was generated from the logical one. Is there any way how do this conversion in Data Modeler? So far I have been able to convert mixed case in logical model to uppercase in physical model (with the exception of foreign keys) but changing space to underscores still eludes me.
Why I think this is important: the logical model should use "normal" language if possible, i.e. spaces, mixed case etc. But the physical model should have uppercase only and definitely no spaces. Having objects in Oracle defined with spaces leads to many difficulties since any reference to the object must use "" around the name of the object...
Thanks
Jakub

Hi,
but the problems continues (even when the model is reduced to no entities at all!)
The error you reported (in engineering and import) cannot be reached if there are no entities and attributes - it's a specific error probably related to usage of distinct types that are removed from design.
You can use search functionality in order to find attributes/columns (logical/relational model) with incorrect data type definition based on distinct type.
And it's better to move to Data Modeler 4.0 (833).
So what to search (example is on logical model - it's the same for relational model - column):
1) Activate search window (CTRL-F when logical diagram is active, or Find icon), switch to advanced mode
2) for "Object type" Attribute:
- check "Data Type kind" line and put DT as search text
- check "Distinct type" line, don't put search text - it'll search for attributes without distinct type
- change the operand for expression from OR to AND
3) press "Find" button
If you find some attributes, then you need to decide what to do with them - to set data type or to delete them.
The same for columns in relational model.
Philip

Difference between OBIEE Logical Modelling and physical modelling

HI.
what is the difference between logical modeling (BMM) and physical modelling(Physical layer) in obiee admin tool
please narrate it in definition format
thank you
rakesh

Hi rakesh,
Administrator tool consists of 3 layers
Physcial layer:-It is typically first layer built in the repository.Contains objects representing the physical data sources to which the BI server submits queries.It may conatin multiple data sources.The common way is to import metadat from different databases.You can define joins after import if they are not defined.
Business model and mapping layer:-It is defined as business or logical models of data and specifies the mapping between the physical and business layers.This is where the physical schemas are simplified to form the basis for the end user.We can say data is seperated into facts and dimension tables
Presentation layer:-simplifies and organizes the business model to make it easy for users to understand and query
go through the user guides for all the definition and subject
Hope it helps you.my points?
By,
Kranthi
Edited by: Kranthi.K on Sep 1, 2009 10:22 PM

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

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

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.

How to resolve corruption in logical model?

Hello
I have a logical model created in SDDM 3.1.2.704. I have engineered to a relational model successfully in the past, but recently when I tried to engineer logical -> relational nothing happens. I get the following entry in the log file:
[AWT-EventQueue-0] ERROR MDBAction - java.lang.NullPointerException
Looking at some other discussions, I used the transformation script described here
3.1.3.709: How to Verify and Fix a Possibly Corrupted Design?
This didn't fix my problem, but the output file (generated when I press the Engineer to Relational model button) shows the following exception:
java.lang.NullPointerException
at oracle.dbtools.crest.model.design.engineering.EngCOPropertiesComparator.decodeDataTypeKindToString(Unknown Source)
at oracle.dbtools.crest.model.design.engineering.EngCOPropertiesComparator.processDataTypeAndUse(Unknown Source)
at oracle.dbtools.crest.model.design.engineering.EngCOPropertiesComparator.initPropertiesList(Unknown Source)
at oracle.dbtools.crest.model.design.engineering.AttributeColumnComparator.initPropertiesList(Unknown Source)
at oracle.dbtools.crest.model.design.engineering.AttributeColumnComparator.<init>(Unknown Source)
at oracle.dbtools.crest.model.design.engineering.AttributeColumnComparator.<init>(Unknown Source)
at oracle.dbtools.crest.model.design.engineering.FE_LogicalToRelational.addAttribute(Unknown Source)
at oracle.dbtools.crest.model.design.engineering.FE_LogicalToRelational.addEntityDetails(Unknown Source)
at oracle.dbtools.crest.model.design.engineering.FE_LogicalToRelational.setEditableStatus(Unknown Source)
at oracle.dbtools.crest.model.design.engineering.FE_LogicalToRelational.addEntity(Unknown Source)
at oracle.dbtools.crest.model.design.engineering.FE_LogicalToRelational.addFromLogicalModel(Unknown Source)
at oracle.dbtools.crest.model.design.engineering.FE_LogicalToRelational.<init>(Unknown Source)
at oracle.dbtools.crest.swingui.engineeringcompare.EngineeringCompareDialog.<init>(Unknown Source)
at oracle.dbtools.crest.swingui.logical.ControllerLogical$FWDEngineer.doActionPerformed(Unknown Source)
at oracle.dbtools.crest.swingui.MDBAction$ActionInvoker.run(Unknown Source)
at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209)
at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:642)
at java.awt.EventQueue.access$000(EventQueue.java:85)
at java.awt.EventQueue$1.run(EventQueue.java:603)
at java.awt.EventQueue$1.run(EventQueue.java:601)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:87)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:612)
at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:269)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:184)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:174)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:169)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:161)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:122)
I have tried SDDM 3.3.0.747, same result.
I have tried removing entities from the model, 1 at a time, but the problems continues (even when the model is reduced to no entities at all!)
I have tried exporting the model and importing it into an empty design. The import fails "Unable to generate design" and produces the following exception in the datamodeler.log file:
[Thread-19] ERROR ODExtractionController - Error Generate Design: Untitled_1
java.lang.NullPointerException
at oracle.dbtools.crest.model.design.engineering.EngCOPropertiesComparator.decodeDataTypeKindToString(Unknown Source)
at oracle.dbtools.crest.model.design.engineering.EngCOPropertiesComparator.processDataTypeAndUse(Unknown Source)
at oracle.dbtools.crest.model.design.compare.COPropertiesComparator.initPropertiesList(Unknown Source)
at oracle.dbtools.crest.model.design.compare.cwddesign.AttributeComparator.initPropertiesList(Unknown Source)
at oracle.dbtools.crest.model.design.compare.cwddesign.AttributeComparator.<init>(Unknown Source)
at oracle.dbtools.crest.model.design.compare.cwddesign.CompareCWDDesigns.addAttribute(Unknown Source)
at oracle.dbtools.crest.model.design.compare.cwddesign.CompareCWDDesigns.addEntityDetails(Unknown Source)
at oracle.dbtools.crest.model.design.compare.cwddesign.CompareCWDDesigns.addEntity(Unknown Source)
at oracle.dbtools.crest.model.design.compare.cwddesign.CompareCWDDesigns.initSourceDesign(Unknown Source)
at oracle.dbtools.crest.model.design.compare.cwddesign.CompareCWDDesigns.<init>(Unknown Source)
at oracle.dbtools.crest.swingui.compare.cwddesign.CompareCWDDesignsDialog.<init>(Unknown Source)
at oracle.dbtools.crest.imports.cwddesigner.CWDExtractionController$Runner2.run(Unknown Source)
at java.lang.Thread.run(Thread.java:662)
Any help greatly appreciated. With over 100 entities and 200 relationships I really don't want to have to recreate this.
Thanks in advance.

Hi,
but the problems continues (even when the model is reduced to no entities at all!)
The error you reported (in engineering and import) cannot be reached if there are no entities and attributes - it's a specific error probably related to usage of distinct types that are removed from design.
You can use search functionality in order to find attributes/columns (logical/relational model) with incorrect data type definition based on distinct type.
And it's better to move to Data Modeler 4.0 (833).
So what to search (example is on logical model - it's the same for relational model - column):
1) Activate search window (CTRL-F when logical diagram is active, or Find icon), switch to advanced mode
2) for "Object type" Attribute:
- check "Data Type kind" line and put DT as search text
- check "Distinct type" line, don't put search text - it'll search for attributes without distinct type
- change the operand for expression from OR to AND
3) press "Find" button
If you find some attributes, then you need to decide what to do with them - to set data type or to delete them.
The same for columns in relational model.
Philip

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

Similar Messages

Maybe you are looking for