Duplicate Logical Model

Hello,
I have a RPD common to the US and France, on France we have the identical database has that of US but the connection pool is different (user and MDP).
Is - it possible of credit note in the same RPD, two layers of identical presentation which first connects on the US base and the second on the French base?
We do not want to reconstruct the logical model in which several transformations were applied, can make the copy of the logical model and connect it at the French base?
Thank you in advance

Hi,
thanks for reporting the problem. I logged a bug for that - it's related to version 4.0.0.820.
Philip

Similar Messages

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

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

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

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

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

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

Help with logical model

Hi, I am new to this software and need some help with a simple logical model.
Here is the task:
I need to create a model for a parking garage.
Each level can have any number of lots.
There are different types of lots (handicapped, women, regular, ...) with different Prices and Sizes.
It is important for the users and the system to know whether a lot is free or occupied.
It is crucial to assign numbers to the lots, so users can find it again.
And this is my model:
Level 1:n Lot n:1 Type
(#Level) (#Number,*Availability) (#Type,*Price,*Size)
Question:
Is it correct or would you change something? I am not quite sure whether to make availability and level an entity or an attribute of Lot.
Which data types do I need to assign each attribute? What is the difference between logical and domain?
Thanks in advance
Edited by: user13256814 on Jun 2, 2010 3:51 AM

Hi Bhaskaran,
u can see the logs correspoding to your application in the server location..
\usr\sap\<sid>\<instance_number>\j2ee\cluster\server0\
i think ur application folder will be there inside this or within one subdirectory here.
http://help.sap.com/saphelp_nw04s/helpdata/en/fe/4f5542253fb330e10000000a155106/content.htm
U can check the service entries in services file which is located in
<Drive Name>:\WINDOWS\system32\drivers\etc...
but normally in JCO Connection test , if it is not showing errors(especially MetaData) , then it means this entry is there in the services file.
Regards
Kishor Gopinathan

Logical Model - Entity Attribute?

Hi ,
Thanks in responding to my posting.
I am using SQL DM 3.0.0.665. I need your thoughs on following.
1) Do we able to select multiple entities for entity reporting? I find an option for all entities then it ask us to pick only one entity to report.
2) Are we able to build a report for all entities in a subview?
3) I see Formula (Default Value), Preferred Abbreviation and Synonyms for each attribute in Entity Details report. I am not able to find a place to fill those in attribute definitions. Where can we supply those details, so it could print in reports?
Thanks in helping us out.

I find the following for Attribute Properties in SQL DM Help
=============
Attribute Properties
This dialog box displays the properties of an attribute, which is a component of an entity in the Logical Model.
General
Name: Name of the attribute.
Synonym: Synonym for the attribute.
Preferred Abbreviation: Name that will be used for any corresponding table column during forward-engineering if the Use Preferred Abbreviations option is enabled in the Engineering dialog box.
Long Name: Long name in the format: entity-name.attribute-name.
Allow Nulls: Controls whether null values are allowed for the attribute. If this option is enabled, a non-null value is mandatory.
Datatype: Enables you to specify a domain, logical type, distinct type, collection type, or structured type as the data type of the attribute. You can click the ellipsis (...) button to specify further details for the selected type.
Entity: Name of the entity with which the attribute is associated.
Source Name: User-specified name of the source for this attribute.
Source Type: Manual, System, Derived, or Aggregate.
Formula Description: For a derived or aggregate source type, the formula for the attribute.
Scope: For a structured type with Reference enabled, limits the scope by specifying the table in which the type is implemented.
Type Substitution: For a structured type with Reference disabled, or for a structured type applied to an entity, controls whether a substitutional structured type is generated in the DDL.
Default and Constraint
Constraint Name: Name of the constraint.
Default Value: Default value for the attribute.
Use Domain Constraints: Controls whether the properties defined in Domains Administration for the associated domain are used. If this option is disabled, you can use the remaining fields to specify the database type for the constraint and the ranges or a list of values.
Constraint: Enables you to specify a constraint for one or more types of databases.
Ranges: Enables you to specify one or more value ranges for the attribute.
Value List: Enables you to specify a list of valid values for the attribute.
Permitted Subtypes
For a structured data type, lists all subtypes for the attribute, and lets you specify whether each is permitted for the attribute.
=============
but most of the above are not showing up in attribute definition window. How do we see those?

Duplicate Logical Model

Similar Messages

Maybe you are looking for