4.0 EA3 BUG - Physical Model Nodes Trancated

In the physical model tree, when i opened properties (unable to double click, had to right click) and assign a schema to at a table, the name is truncated to 3 to 5 characters followed by and elipsis. I closed the design and re-opened and the names are spelled out and I can now double click on tables to get properties. Only message for today in the logs is:
2013-10-31 10:12:32,496 [main] INFO ApplicationView - Oracle SQL Developer Data Modeler 4.0.0.825
I will try to reproduce it when I get time. Today I created a new logical model in a subview, saved the design, engineered to the relational model, saved the design, assigned schema to each table (tables in the Browser became blank space as before), added tables to an existing sub-view, saved the design, and then opened the Physical browser node and assigned schema to each table. The physical model is for MS SQL Server 2008.

Hi Marcus,
thanks for feedback. I was able to reproduce it and logged a bug for that.
Philip

Similar Messages

How to implement more than one physical models from the same model

Hello,
We have designed a relational model for our application and now, we would like to implement it for our 4 environments: Development, Test, User-Test and Real. Each one has the same logical schema but, different physical clauses (i.e.: in development environment we will not use partitioning clauses).
Is this possible?
Thank you,
Bernat Fabregat

Hello Bernat,
yes it's possible:
1) open your design and go to Tools>"RDBMS site administration"
2) add your sites there (Current design) - Development, Test, User-Test and Real; press ok when finish
3) go to "Physical models" node in browser and use "new" from pop-up menu - your sites will appear in list
4) after you set physical objects in one model (need to save it as well)l, you can clone those objects in other models - you can clone from lower or the same database version
You can consider usage of "name substitution" functionality during DDL generation if objects should have different name (prefix) in different environment - in this there will be no need to change the name of objects in models.
Philip

Data Modeler bug? - it keeps reporting missing physical model files

Hi,
I'm having a rather serious problem with the latest data modeler, Oracle SQL Developer Data Modeler 3.1.4.710. It keeps losing physical model files for some reason.
I started to notice that it was not generating all the tables in my small design. After hours of struggle I found multiple error messages in the log file:
2012-12-18 10:51:20,126 [Thread-71] ERROR XMLTransformationManager - Unable to load object from XML: C:\cygwin\home\Brian\codebase\models\data\Design\rel\395D160B-C7224B8EAD05\phys\D9582E4E-2ED963CB9D32\View\seg_0\A555DB9B-8864-9C0B-DCA8-BAC5231F55C6.xml
java.io.FileNotFoundException: C:\cygwin\home\Brian\codebase\models\data\Design\rel\395D160B-C7224B8EAD05\phys\D9582E4E-2ED963CB9D32\View\seg_0\A555DB9B-8864-9C0B-DCA8-BAC5231F55C6.xml (The system cannot find the path specified)
     at java.io.FileInputStream.open(Native Method)
     at java.io.FileInputStream.<init>(FileInputStream.java:138)
     at oracle.dbtools.crest.model.metadata.XMLToObjectTransformer.transformToObject(Unknown Source)
     at oracle.dbtools.crest.model.metadata.XMLToObjectTransformer.transformToObject(Unknown Source)
     at oracle.dbtools.crest.model.metadata.XMLTransformationManager.transformFromXMLToObject(Unknown Source)
     at oracle.dbtools.crest.model.metadata.XMLTransformationManager.openPhysicalModel(Unknown Source)
     at oracle.dbtools.crest.model.metadata.XMLTransformationManager.openPhysicalModel(Unknown Source)
     at oracle.dbtools.crest.swingui.browser.BrowserPanel$88.run(Unknown Source)
These messages appeared every time I opened my physical model (Oracle 10g).
After deleting and recreating the physical model the problem went away for a while. But after closing and reopening the design I started to see the errors again.
Has anyone seen something similar?
Regards,
Brian

Thanks Philip!
The workaround does the trick for the tables, primary keys and unique keys.
I have just observed that table level constraints show a slightly different behaviour.
Names show up like TCC5, TCC6, etc.
Seems the same problem as previously in SQL*Modeler forgets check constraint names
Is there a workaround for that problem too ?
I already noticed that there is no parameter NameChanged for a table constraint.
Enrico

Data modeler saving Physical model changes not saved

I am using version 2.0.0.584.
The bug fix list contains: 8722310: Save does not save physical model changes
Hovever I still see unexpected behaviour.
I created a physical model for "Oracle database 10g" and allocated a couple of tables to a different tablespace.
I saved the physical model via Physical model--> right mouse button --> save all.
I saved the model with File--> save
I close the model.
After opening, the physical model is not available anymore.
After Physical model--> right mouse button --> open (for Oracle 10g) the contents are not the same anymore.
Tablespaces with name "TableSpace3" and "TableSpace4" are added and objects belong to this tablespace.
We do not have currently a workaround for this behaviour.
Can anyone help?
Thanks
Edited by: 793016 on 06-Sep-2010 03:10
Edited by: 793016 on Sep 6, 2010 12:14 PM

Hi Philip,
default tablespaces were defined and I removed this. It did not have a positive effect.
Checking the log files was a good idea.
The log file contained errors about files which could not be found on the system.
I will do some additional tests and let you know.
Thanks.
Kind regards,
Maurice

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 ?

Physical attributes for index on temp tables (using physical model)

I need create index on temp tables.
When I generate DDL, it includes physical attributes like ‘LOGGING NOCOMPRESS NOPARALLEL’.
I get error "ORA – 14451 (unsupported feature w/temporary tables)"
I’ve to use physical model in OSDM. How do I get rid of physical attributes in DDL for index?

Hi,
Thanks for reporting this problem.
You can remove the LOGGING clause by opening the Properties dialog for the Index in the Physical model and setting its Logging property to the blank option.
However it's not possible to suppress the NOCOMPRESS and NOPARALLEL at the moment.
I've logged a bug on this.
As a workaround, you could do a global edit on the DDL file to remove all instances of NOCOMPRESS and NOPARALLEL.
David

Physical model attribute "Partition Scheme" not saved. (SS2000)

Hello,
I believe this is a bug report.
Scenario:
I have a physical model of a SQL Server database. The model contains partitioned tables, 1 partitioning function and 1 partitioning scheme. If I open the physical model properties of an index or a table, set the "Partition Scheme" attribute, save, close and re-open the model, the "Partition Scheme" attribute is lost. If I don't close out and just re-open the properties page, the attribute is retained. Some how, the attribute is lost in the persistence layer.
If there is a reason the attribute is being reset, please let me know.
Thank for your help, and all the great products you guys make,
Kurt
DataModeler v 3.1.1

Hi Kurt,
If there is a reason the attribute is being resetUnfortunately there is a bug causing the problem. Fix will be available in next patch release.
Philip

Physical model disabled

I'm trying to create a Partition using sql developer/modeler
my physical model all the options or disabled(greyed out) when it is connected to live database how do I over come this

Hi,
You need to open the Physical Model properties dialog for the Table (from the Physical model part of the Browser tree) and set the Partitioned property (on its General tab) to YES.
You will then be able to use the Partitioning tab in this dialog, to set Partitioning type and other Partitioning properties.
Also, after you've closed this dialog, you can create Partition instances by selecting New from the right-click menu for the Partitions node (subordinate to the Table's node in the Physical model part of the tree).
David

Physical Model - Propagate table property "Tablespace" doesn't seem to be working in 4.0EA2

I'm to switching from v3.3.0.747 to 4.0EA2 but experiencing some issues.
In the physical model when I try to propagate the table property "Tablespace" for the remaining tables a silent error happens and as result the value is not propagated.
The error appears in the log file:
2013-09-24 16:31:31,776 [AWT-EventQueue-0] WARN PropertyWrapper - oracle.dbtools.crest.model.design.storage.oracle.v11g.TableProxyOraclev11g.setTableSpace(oracle.dbtools.crest.model.design.storage.oracle.TableSpaceOracle)
java.lang.NoSuchMethodException: oracle.dbtools.crest.model.design.storage.oracle.v11g.TableProxyOraclev11g.setTableSpace(oracle.dbtools.crest.model.design.storage.oracle.TableSpaceOracle)
at java.lang.Class.getMethod(Class.java:1624)
at oracle.dbtools.crest.util.propertymap.PropertyWrapper.setValue(PropertyWrapper.java:65)
at oracle.dbtools.crest.swingui.editor.storage.PropertiesPropagationDialog.applyTo(PropertiesPropagationDialog.java:353)
at oracle.dbtools.crest.swingui.editor.storage.PropertiesPropagationDialog.setProperties(PropertiesPropagationDialog.java:337)
at oracle.dbtools.crest.swingui.editor.storage.PropertiesPropagationDialog.access$400(PropertiesPropagationDialog.java:46)
at oracle.dbtools.crest.swingui.editor.storage.PropertiesPropagationDialog$11.actionPerformed(PropertiesPropagationDialog.java:300)
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)
However if I try to propagate the tablespace value for indexes this works fine.
Some ideas?
Thanks.

Hi,
Thanks for reporting this. I've logged a bug.
I'm afraid you won't be able to propagate Tablespaces on Tables until it's fixed.
David

Check constraint generation in physical model in 3.1.1.

My question: Is it possible to set Use Domain Constraints ticked as default (or another way to get them in DDL) if the Domain with Check constraint is set for the column. I assume it's logical as if I bind a column to the domain then use the domain constraint as default policy. It's not a big deal if you have a few but in my case I do re-modelling just for physical model level and I have tens column in the tables based on a domain. So, I have first to set the domain as a column type and then in another screen tick Use Domain Constraints
Thank you

Hi,
Is it possible to set Use Domain Constraints ticked as default (or another way to get them in DDL) if the Domain with Check constraint is set for the column.No it's not possible I logged bug for that.
So, I have first to set the domain as a column type How do you set domain as data type? Do you have more than one columns using the same domain? In such cases you can use domain dialog (in the browser) and "Used in" page in order to assign domain to several columns/attributes at once.
You can use the script below to set use domain constraints on columns that use domain as data type
Philip
var model;
tables = model.getTableSet().toArray();
for (var t = 0; t<tables.length;t++){
table = tables[t];
columns = table.getElements();
for (var i = 0; i < columns.length; i++) {
     column = columns;
     if(column.getUse() == 0 && column.getDomain()!=null){
          if(!column.getUseDomainConstraints()){
               column.setUseDomainConstraints(true);
               table.setDirty(true);

Binding model nodes - seeming repetition?

Hello,
When creating a WD app using Adaptive RFC Model (or any model I assume), it is necessary to create a data link between the Model and Component Controller. Visually, the fields of the nodes of the Model and the fields of the model nodes of the Controller are linked. Why, then, is it necessary to again bind the model node of the Controller to the model object using the ".bind" method?
Code as shown here is a classic example:
     Bapi_Usr01Dohr_Getemployee_Input bapiInput = new Bapi_Usr01Dohr_Getemployee_Input();
     wdContext.nodeBapi_Usr01Dohr_Getemployee_Input().bind(bapiInput);
     bapiInput.setId("MY_USERID");
     try {
          bapiInput.execute();
     } catch (Exception exc) {
          IWDMessageManager msgManager = wdComponentAPI.getMessageManager();
          msgManager.raiseException(exc.getMessage(), true);
Clearly the visual binding in the diagram view of the component controller and the programmatic binding using the .bind method of the model node are doing different things. My question is, what is the difference? Why are both required?

Michael,
There are actually 3 activity types, and sadly one of them has not the best name:
1. Map at run-time / design-time model to context node (make metadata structure, that mimics model structure, possibly with renaming of target attributes / sub-nodes)
2. Map at run-time / design-time (or as you say "link") 2 nodes in different controllers (make metadata structure, that mimics structure of node's metadata in another controller, possibly with renaming of target attributes / sub-nodes)
3. "Bind" at run-time-only data to node, that was previously described as metadata either using IDE at design-time or at run-time.
So, there is no repetition: you create metadata once (ok, more logically "once" then physically), then you may assign different data to resulted node via bind several times.
Valery Silaev
EPAM Systems
http://www.NetWeaverTeam.com

Data modeling tool: physical model migration

Hi,
I have imported my relational model with a generated physical model for oracle 9i.
I'd like to migrate my DB to oracle 10g, but I don't feel like creating a new physical model for Oracle 10g from the scratch and configuring it all.
Is there any way to copy that oracle 9i physical model into an oracle 10g model? I know there could be any implementation change from 9i to 10g, but at least copy the main 99% (and warn about the 1% impossible to replicate in 10g).
Could this feature be taken into the production version?
By the way, is this a BUG? when I start the tool, my oracle 9i physical model is not shown in the tree, and I've to right-click over physical model, press open, and then select oracle 9i, to be shown in the tree. But I close the data modeling tool, and when I start again, there is no physical model shown in the tree :(
thanks a lot in advance, I'm evaluating the tool.

Thank you very much for your reply, and hearing those news makes me very happy, because I'm evaluating the product and I miss some functionality like that.
By the way, where can I find the new functionality or the fixed one that is going to be on the production release? Or could yo send it to me by email or any other way? I'm very interested in it.

Changing foreign key name in physical model

If I change foreign key name in physical model, it does not change in relational model. But when I change the name in relational model, the new name appears in physical model. This happens in Data Modeler 2 and 3EA2. Is it a bug or an intentional feature?

it's not a bug - the name in physical model "follows" the name in relational model until name in physical model is changed. It keeps the same value and changes in relational model do not affect it. original behavior can be restored if you set the same name as it is in relational model.
If I change foreign key name in physical model, it does not change in relational modelYou can look at physical model as specific implementation of relational model - changes do not go back in relational model.
Philip

Creation of new element in Model Node

Dear All,
I am facing one problem, I have two model node. I want to copy one model node to other model node.while copying its giving error saying the you can bind the element, coz target node doesn't have valid parent.
Pl don't suggest me work on Value node.
Can i create a element in model node at run time.
Thanks & Regards
Manoj Sahoo

Hi Manoj,
Model node properties :
1.A context model node makes a model object look like any other context node. I.E. it gives the model object an API that is very similar to a value node.
2. A model node is not considered valid until it is bound to a corresponding model object. Therefore, a model node always inherits its metadata from the model object to which it is bound.
3. The element collection in a model node does not hold the actual runtime data! Instead, it holds a list of references to the relevant model object instances.
If u check the 2nd property, u will find the cause of ur exception. As u have already told, don't suggest to use value nodes, i don't have any other comment.
regards
Sumit

How to populate a Value Attribute of a Value Node inside Model Node

Hello
I have my context like this.
Context
..          - ModelNode
....                      - Model Attr1
....                      - Model Attr2
....                      - Model Attr3
....                      - Model Attr4
....                      - Value Node
......                                  |
......                                   - Value Attr1
Model Node is of Cardinality 0..N
Value Node is of Cardinality 1..1
I want to create multiple records in my Model Node and one record for every Model Node in Value Node.
How to do this?
All good suggestions are welcome.
Regards,
Shubham

Hi Shubham,
With your context structure the code will be
for(int i = wdContext.nodeModelNode().size()-1 ; i>=0 ; i--)
    IPublic<comp name>.IModelNodeElement ele =   wdContext.nodeModelNode().getModelNodeElementAt(i);
    IPublic<comp name>.IValNodeElement valEle = wdContext.nodeModelNode().nodeValNode().createValNodeElement();
    valele.setValAttr("");
    ele.nodeValNode().addElement( valEle);
Your val node should be non singleton (singleton property = false)
Regards,
Jaydeep

4.0 EA3 BUG - Physical Model Nodes Trancated

Similar Messages

Maybe you are looking for