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.

Similar Messages

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

Table properties doesn't propagate from Relational Model to physical model

Hi all,
I have a relationnal model with several tables and several schema.
When i create a new table in the relational model with a specified schema, the table is created on the physicla model, but the schema is not prapagate.
Is there a way to do this automatically ?
Or do i have to specify the schema on the relationnal and on the physical.
Thank you

Hi,
schema object in relational model needs to be implemented in physical model - user is the implementation of schema in Oracle physical model. User has property "implements schema". You also can omit this redirection and can assign directly user to table but in this case you'll lose the flexibility.
Here is how DDL is impacted using different option (schema_1 and table_1 in relational model):
1) physical model is not open - no implementation details
CREATE TABLE Schema_1.TABLE_1
     Column_1 NUMBER
;2) physical model is open - Schema_1 is not implemented
CREATE TABLE TABLE_1
     Column_1 NUMBER
    ) LOGGING
;3) physical model is open - Schema_1 is implemented by User1
CREATE TABLE User1.TABLE_1
     Column_1 NUMBER
    ) LOGGING
;4) physical model is open - Schema_1 is implemented by User1; Table_1 is directly assigned to User2 in physical model
CREATE TABLE User2.TABLE_1
     Column_1 NUMBER
    ) LOGGING
;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

Threat Modeling Tool 2014 - modeling an FTP connection

What king of connection or Flow should I be using to model an FTP connection using the new Threat Modeling tool?
Thanks in advance.

Does anyone have an answer for this?
From MSDN forums.

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

SQL Dev Data Modeller: Auto-generate Surrogate PKs in the Physical Model ?

How can I have the logical modeller allow the user to design with logical PKs, but then have surrogate primary keys be auto-generated off sequences by the modeller when it comes to create the physical model - as in conventional application design?
Without this facility, this tool is useless, IMO.
I want:
i). sequences to become the physical PKs by default, and that what were the logical PKs in the logical model, to become a unique key in the physical model.
ii). I want this set by default when generating the physical model....
iii). ....with an option to turn this off on a entity-by-entity basis (as not all tables will necessarily require such a surrogate PK; so the logical PK may remain the physical PK).

It is common practice that physical PKs in Oracle tables are defined from sequences (surrogate PKs), and that the logical PK from the entity becomes a unique key in the table.
This may not always be the case in every application out there, and some people may disagree, but it is nonetheless a needed feature.
My new Feature Request is therefore:
I would like to see the following additions to the product.
1. In the Preferences -> Data Modeler -> Model -> Logical, a flag that by default indicates whether the designer wishes to opt to enable this feature (ie; have all logical PKs converted to unique keys, and replaced by sequence nos. in the physical model). This flags needs to be there since in real life, albeit erroneously IMO, some people will choose not to opt to use this functionality.
2. On every entity created in the model, there needs to be a flag that allows to override this default option, as not every table will require a surrogate PK to be generated. Being able to (re)set a flag located on the entity properties (perhaps under 'Engineer To'), will accomplish this.
3. When Forward Engineering to the physical model from the logical, the following should happen.
ENTITY 1 ---------->TABLE 1
---------------------> P * Surrogate PK
* Attribute 1 -----> U * Column 1
* Attribute 2 -----> U * Column 2
o Attribute 3 ----------> Column 3
Here you can see,
- Attributes 1 & 2 (the logical PK) of the entity become a unique key in the table (columns 1 & 2),
- optional Attribute 3 becomes NULLable column 3,
- and a physical surrogate PK column is added (type unbounded INTEGER, PRIMARY KEY constraint added).
From entity DEPT as: (Examples based on SCOTT schema)
DEPTNO NUMBER(2) NOT NULL <-- Logical primary key on entity
DNAME VARCHAR2(14)
LOC VARCHAR2(13)
CREATE TABLE DEPT
(PK_DEPT INTEGER, -- New column becomes surrogate physical PK, driven from sequence defined later
DEPTNO NUMBER(2) NOT NULL, -- Former logical PK becomes a UK
DNAME VARCHAR2(14),
LOC VARCHAR2(13))
ALTER TABLE DEPT
ADD CONSTRAINT PK_DEPT PRIMARY KEY (PK_DEPT) USING INDEX PCTFREE 0
ALTER TABLE DEPT
ADD CONSTRAINT UKLPK_DEPTNO UNIQUE (DEPTNO) USING INDEX PCTFREE 0 -- Former logical PK becomes a UK (constraint name reflects this)
CREATE SEQUENCE PK_DEPT_SEQ
CREATE TRIGGER PK_DEPT_SEQ_TRG
BEFORE INSERT ON DEPT
FOR EACH ROW
WHEN (new.PK_DEPT IS NULL)
BEGIN
SELECT PK_DEPT_SEQ.NEXTVAL
INTO :new.PK_DEPT
FROM DUAL;
-- Or from 11g onwards, simply,
:new.PK_DEPT := PK_DEPT_SEQ.NEXTVAL;
END;
From entity EMP as:
EMPNO NUMBER(4) NOT NULL -- Logical primary key on entity
ENAME VARCHAR2(10)
JOB VARCHAR2(9)
MGR NUMBER(4)
HIREDATE DATE
SAL NUMBER(7,2)
COMM NUMBER(7,2)
DEPTNO NUMBER(2)
CREATE TABLE EMP
(PK_EMP INTEGER, -- New column becomes surrogate physical PK, driven from sequence defined later
FK_DEPT INTEGER, -- New FK to surrogate PK in DEPT table (maybe NOT NULL depending on relationship with parent)
EMPNO NUMBER(4) NOT NULL, -- Former logical PK becomes a UK
ENAME VARCHAR2(10),
JOB VARCHAR2(9),
MGR NUMBER(4),
HIREDATE DATE,
SAL NUMBER(7,2),
COMM NUMBER(7,2),
DEPTNO NUMBER(2))
ALTER TABLE EMP
ADD CONSTRAINT PK_EMP PRIMARY KEY (PK_EMP) USING INDEX PCTFREE 0
ALTER TABLE EMP
ADD CONSTRAINT FK_DEPT FOREIGN KEY (FK_DEPT) REFERENCES DEPT (PK_DEPT)
ALTER TABLE EMP
ADD CONSTRAINT UKLPK_EMPNO UNIQUE (EMPNO) USING INDEX PCTFREE 0 -- Former logical PK becomes a UK (constraint name reflects this)
CREATE SEQUENCE PK_EMP_SEQ
CREATE TRIGGER PK_EMP_SEQ_TRG
BEFORE INSERT ON EMP
FOR EACH ROW
WHEN (new.PK_EMP IS NULL)
BEGIN
SELECT PK_EMP_SEQ.NEXTVAL
INTO :new.PK_EMP
FROM DUAL;
-- Or from 11g onwards, simply,
:new.PK_EMP := PK_EMP_SEQ.NEXTVAL;
END;
[NOTE: I use PCTFREE 0 to define the index attributes for the primary & unique keys since the assumption is that they will in general not get updated, thereby allowing for the denser packing of entries in the indexes and the (albeit minor) advantages that go with it.
This is certainly always true of a sequence-driven primary key (as it is by its very nature immutable), but if the unique key is likely to be frequently updated, then this PCTFREE option could be user-configurable on a per table basis (perhaps under Table Properties -> unique Constraints).
For non-sequence-driven primary keys, this storage option could also appear under Table Properties -> Primary Key.
I notice no storage options exist in general for objects, so you may like to consider adding this functionality overall].
Associated Issues :
- Preferences, 'Naming Standard: Templates' should be updated to allow for the unique key/constraint to be called something different, thus highlighting that it comes from the logical PK. I've used 'UKLPK' in this example.
- Mark the physical PK as being generated from a sequence; perhaps a flag under Table Properties -> Primary Key.
- When Forward Engineering, if an entity exists without a logical PK, the forward engineering process should halt with a fatal error.
!!! MODERATOR PLEASE DELETE ME !!!

Data Model Exporting - MDM to Erwin or another data model tool

I would like to export the latest MDM physical data model in production to any erwin modelling tool or any othe data modelling tool

To export the schema of an MDM repository to an XML file:
1. In the Console Hierarchy tree, right-click on the MDM repository whose schema you want to export and choose Export Repository Schema from the context menu, or select the tree node and choose Repositories ® Export Schema from the main menu.
If the top-right pane is currently displaying the list of MDM repositories, you can also right-click on the repository in the grid and choose Export Schema from the context menu.
2. Click Save to close the dialog and export the schema.
Schema files are stored in XML format in a user-defined location using a user-defined filename. The file contains the schema definition only; no table or field content.
http://help.sap.com/saphelp_mdm550/helpdata/en/f2/2f21039e9146098e7b238f1a4c8e5e/content.htm
Thanks,
Shambhu.

Oracle Data Modeling tool interoperability with QDesigner models.

Hello,
Would it be possible to get some information on how Oracle SQL Developer Data Modeler works with models from other data modeling tools such as QDesigner.
How can Quest QDesigner read the .cdm (conceptual data models) and the .pdm (physical data models) from QDesigner.
Regards,
Mary

SQL Developer Data Modeler does not work with QDesigner models.
Sue

Data Modeler: is it possible to compare physical models?

Hello,
We're looking for a new Data Modeling tool, as we will abandon Designer (for many different reasons...). The SQL Developer Data Modeling-tool looks very promising. Especially the "compare models" -tool looks interesting to create change-scripts for new implementations. What I don't find, however, is the possibility to generate typical physical attritutes, like permissions (resulting in grant-statements), tablespaces. Is this available? Is it possible at all? For your information: I've just downloaded the EAR 2 (version 1.5.1 build 525)
Thanks in advance for your reply,
Peter

Peter,
I would like to echo your feature request. I too spent many years with Designer and until SDDM came along, I was still using it for server model diagrams mostly. We always wanted to make sure that we have a record (model) of what was in a schema. We deploy to MANY environments - several for development, various phases of testing etc. and of course production and clones of production. It's really nice to run a utility of some sort that compares my model to an implementation. I might compare the same model to half a dozen environments. It helps me quickly pinpoint differences that aren't expected.
I also like to ability to compare models with each other. We're all looking forward to the future of data modeling with SDDM!
In some ways, SDDM is already ahead in the features department. I can version models in Subversion with the XML files. That’s HUGE!
Maggie Tompkins, USMC

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 Tools Platform Model Base (1.5.0.200707041) requires feature "org.ecl

While I'm trying to use the getting started guide for Plugin DTP the following erroe occurs......
Data Tools Platform Model Base (1.5.0.200707041) requires feature "org.eclipse.emf (2.2.0)", or later version.
This the download from the Oracle Site up to date?
Thanks in advance
Simon

Did you try the steps 7 & 8 of section 2.2 in http://www.oracle.com/technology/tech/eclipse/dtp/files/gettingstarted.html ?

Physical Model Data Type Issue

Hi,
I have created ware house tables using E-business suite tables for general ledger model and exported into physical model. I could see all my keys/IDs which were numbers have been converted into decimal.
Ex: journal_id in my oracle table is number (ex:1234). But when I exported into OBIEE and used view data option. All the IDs(data type number) data is showing as decimal format (1234.00).
Ex: If I want to see data for check number in answers, then it is showing as 112456.00 instead of 112456.
Please anyone had this kind of issue. how to resolve?
Is there any default setting which is causing this problem.how to find?
OBIEE version : 10.1.3.2
Appreciate your help.

Hi Sandeep,
When I opened the rpd in offline mode, it is saying the repository can only be opened as Read-Only. I clicked Yes for this and entered admin user name and password. But in Physical model, when I right clicked any table, I couldnt see find any place to modify. I tried with properties also. I am not able change data type as it read-only. How to do it in offline?
FYI,
I opened rpd when OC4J was stopped. Aslo I opened when OC4J is running. But both times I am not able to change datat type.
Thanks!!

Export import in sql developer data modeling tool

I tried sql developer data modeling tool
but i have a proble
i select file> import > data dictionary
then created a connection to db and selected some tables and got the er digram successfully
then i goto file > export>to data modeling design and save it to xml file
but when i give this file to another developer and he imported the file File>import>data modeling design
the digram is not displayed
is it a bug or im doing something wrong

ok it was my fault
it's not the xml only
there is a folder with the same name bside the xml file and should be included within the exchange

Data modeling tool to design a dwh - SQL Server 2008 R2-2012

Hi,
I need to know if it exists a Microsoft tool to model the data structures of a data warehouse. I generally use the SQL Server diagrams but I'd like to know an enhanced tool. Visio?
Thanks

Hi,
You could download a 60 day free trial of Visio; -
http://office.microsoft.com/en-gb/visio/visio-professional-2013-free-trial-flowchart-software-FX103791368.aspx
Have a look at a related link; -
http://social.technet.microsoft.com/Forums/sqlserver/en-US/620009b1-9625-4e1f-8574-f4049718ffe2/shapestemplates-bi-for-visio
Kind Regards,
Kieran.
Kieran Patrick Wood http://www.innovativebusinessintelligence.com http://uk.linkedin.com/in/kieranpatrickwood http://kieranwood.wordpress.com/

Data modeling tool: physical model migration

Similar Messages

Maybe you are looking for