Logical model - 2 problems (proposal to improve)

hi,
1st problem:
New entity - Add attribute - Primary UID - Apply (Unique identifier is created)
After Primary UID unchecking the Unique identifier is still there, so after OK or Apply, an Error message (Incoplete Unique Identifier) is displayed.
Now it is necessary to modify/delete Unique identifier manually - could it be this operation automatized?
2nd problem
after duplication of Entity with Unique identifier (Copy - Paste) the new Entity is renamed right, but name of UI in new Entity is unchanged.
this cause problem after Engineer - DDL with duplicate constraint name
thank u,
mat

Quote
I recently bought 2 GB of 333Mz PC2700A DDR RAM
Please post the brand name and model/serial number of these modules. Look at the modules themselves to find that information (sticker/chip markings).
Quote
Name : Version 1.00
If you have an MS-6580 Version 2.x board you BIOS Version should not be 1.00. Please check you current BIOS Version on the POST Screen und post the full BIOS ID String:
Also, do verify you mainboard model, look at the board itself. Don't trust any software tools:
How to identify your BIOS and m/b version
Quote
OEM 230V cannot find out what Wattage it is.
For PSU details, look at the sticker on the PSU. Look for:
- brand name
- model name/model number
- amperage limits (A) on main voltage rails (12V, 5V and 3.3V)

Similar Messages

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.

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

Export logical model open all relational and physical model? -- Problem

Hello,
If I export only logical model ( file --> export --> To design Data Modeler) . Oracle Data Modeler open all relational and physical model, if I have 100 relational model open all, and this is very resource.
Can it be avoided?
Thanks.

Ok, thanks
This bug Will solved for version final Data Modeler 4.1 ?

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

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

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

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

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.

Logical model cannot refer to 'remote objects'?

Hi
Using DM 3.3.0.747.
In the relational model one can drag and drop in a table from another relational model from a separate design. This shows that table as a linked table and can be refreshed via the 'Synchronize Remote Objects' and allows that table to be referenced from your 'local' tables (i.e. used in foreign keys).
I tried the same, but for a logical model entity. This does not work/is not allowed? What is the expected behaviour?
We would like to use this for logical models as well. (So that we may develop/document the logical models separate, but use common/shared entities in the same way possible in relational models. This will help us a lot in keeping the models smaller and easier to manage and version control.)
Thank you & Regards

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

Engineering from relational model to logical model duplicated views

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

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

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.

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

What is the BDB logic model

when the Native XML DB access the xml document will thought a logic model to mapping the record.
What is the BDB logic model?? is a tree model ??
A
/ | \
B C D
or node just link first-child and other child link each other??
and when the path is A/D,will first get "A" first child, and sequence search "D"
A
B-C-D

Hi Henry,
I'm afraid I'm finding it a little difficult to understand what you're asking. I'll try to answer, but feel free to ask more specific questions.
With the 2.3 release, DB XML moved from the first model you described to the second model. That is, DB XML used to have links to all an elements children in the element itself, but now it only contains first child (and last child) pointers.
We made this change because of what we know internally as the hundred thousand child problem - which is a common pattern that we see where people have one top level element with a very large (and usually increasing) number of child elements arranged in a shallow tree. This situation resulted in a very large number of child pointers being stored in one place, causing unmarshalling to be very slow whenever that element was accessed.
How we navigate the path "A/D" depends a lot on whether there is an index present that we can use. In the case where there isn't an index, the scenario is as you described, and the child list is walked using first child/next sibling links.
I hope this helps,
John

Logical model - 2 problems (proposal to improve)

Similar Messages

Maybe you are looking for