Compare Physical model

I am a new user here...
I just created my first model in SQL Developer data modeler .... I have been happy so far....
Question is: is there a way to compare physical model changes to Dataabase schema and generage DDL STMT?
Scenario: I created a relational schema and physical model in data modeler and generaged DDL script which I ran in to new schema... and created a working environment... for the applcation.
Now i made some Foreign key to initially defferred and saved data model. But when I compare this updated foreign key (physical model changes) changes to DB.... it doesn't show it being changed.
I just want to know if I am missing anything here.
Thank you in advance and please let me know if I need to provide any further information.
Data modeler version: 3.1.1.703 ( just got new version to see if this one fixes my problem... but still not help)
-R

Thank you Philip for clarifying the functionality.
Just wondering, is there a plan to support this functionality in near future?
I am sure there are many users like me who created their data model using Data modeler and configured initial physical model properties..... and successfully created their database .... and also want to use this too to configure further chagnes in data model and have them merged with DB.....
Thank you
-Raj

Similar Messages

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

Compare physical db with CASE model

I'm using Designer Release 6.0 for PC. I'd like to compare (diff) my Designer db server model with my physical implementation
residing on our server. We sometimes have developers change the physical db without changing the CASE tool (ERD, tables, etc.). I
remember an old version of the CASE tool that had a report available that performed this compare. You run the report, login to your
physical db, then it would compare the CASE model with the physical model and give you an output of the differences. It would report
any column size/type changes, constraint changes, index changes - everything. I don't remember the name of the report but
I can't find a report title in this CASE version that sounds like this. Anyone know of such a report?
Thanks for any help,
Kevin Sharpe

Hi,
You can run the Reconcile Report when you run the Server model generator. In the Design editor select the Relational Table Definition node and open the Server Model Generator. You must choose to generate to the livedatabase rather than generate the DDL files.
The generator does not automatically execute the DDL it creates. Once the generator has created the DDL it also creates the Reconcile Report and brings up a dialog allowing you to view the DDL, execute the DDL, examine the report or cancel. The report comapres the physical database and the table definitions.
If you examine the DDL you'll see that the generator creates ALTER statements for any tables it finds in the database.
Hope this helps
Rgds
Susan
Oracle Designer Product Management

Delete several partitions in physical model

Hi All,
I don't know if someone has the same necessity than me, if not maybe is because I don't know how to do something that is already implemented,
anyway, my question is:
How can I delete several partitions (400) at the same time from the same table in the physical model?
I can select the partitions but the contextual menu is not working, I can press delete button into the toolbar but is doing nothing,
I imported from my data dictionary a schema with several tables that have a lot of partitions and I'm not interested to save these partitions,
when I try to generate the DDL is generating all of the partitions and I don't want the DDL with thousands of partitions inside,
the number of tables with partitions is not so high but is not comfortable to go one by one selecting the partitions and deleting the object (400 times in one table),
I can modify the table to say that is not partitioned and all the partitions will disappear but I then need to modify again the tables and include the fields for the partitions and sub-partitions, not useful,
another option could be to select during the import if I want to import only one partition of each table
but I 'm not sure is at the end it's needed just because I think that only deleting the partitions with one operation should be enough, at least for me
thanks in advance

Hi David,
First of all thanks for your quick response and for your help logging the enhancement request,
I am testing more or less your suggestion but I am not sure if I understood exactly what you mean,
1)I imported from data dictionary in a new model and into the options menu on the schema select screen I un-ckecked partitions and triggers,
I guessed that the import should not get from the data dictionary the information about the partitions but the result is that the tables partitioned (by list in this case) are partitioned by range without fields into the physical model on SDDM,
2)I select one of the tables modify a NO partitioned option and propagate the option for the rest of the tables
3) I imported again from data dictionary but this time I included the partitions into the option menu on select schema screen,
into tabular view on compare models screen I can select all the tables with different partitioned option, also I can change for "list partitions" and select only the partitions that I want to import.
So I have a solution for my problem, thanks a lot for your suggestion
The second step I'm not sure is needed or maybe I can avoid the step with some configuration setting in any of the preferences screen,
if not, I think the options to not include partitions into select schema screen are not so clear, at least for me,
please, could you confirm me if a way to avoid the second step exists or if I misunderstood this option?
thanks in advance

How to specify COMPRESS FOR OLTP on a table in physical model?

Hi,
we have licensed Oracle's Advanced Compression and want to use the OLTP compression on some tables. I am looking for a way to specify COMPRESS FOR OLTP on a table in the physical model. So far, I can only set "Data Compression" to YES or NO.
Are you going to add the "new" compression modes in the next release?
Thanks,
Frank
Version of SQL Developer Data Modeler is 3.1.3.709

Hi Frank,
Are you going to add the "new" compression modes in the next release?There is support for compression type (including OLTP) in DM 3.3 EA and you can download it from OTN.
Philip

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

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

Importing logical and physical model from Sybase power designer/Erwin

Hello,
We have several models created in Sybase Power designer, logical and as a well as physical. Is there a way to directly import models into Oracle designer?
Thank you for your help.
Syed

Hi Syed,
ERwin has a facility to export to Designer 2000. Of course you're probably not using Designer 6.0 or earlier so it's of little use.
I have been looking at a couple of tools for importing from ERwin: Reischmann Informatiks TOOLBUS Interface for Oracle Designer and ALLFusion ERwin; and Meta Integration Technologys Meta Integration Model Bridge (MIMB). Neither product is free (nor inexpensive) but if you've got a number of models to convert then the tools seem cheap by comparison. Also, none of the products that I've looked at recreate the actual diagrams (not that I expected them to).
I am leaning towards TOOLBUS as it provides more complete migration of Logical and Physical models (especially the linkages between the models) using Oracle Designers API rather than a DAT file as provided by MIMB.
Hope this helps,
Wayne Lehman
Avanti Business Systems Inc.

Logical and Physical Models

Hi All,
I'm new to Designer. I need to produce a logical data model in Oracle Designer 10g. I have created a few tables in the RON and have used Design Editor to add these to a Server Model. I think this is giving me the physical model rather than the logical model.
Can you please tell me if I'm going about this the wrong way ? I need the logical model to confirm with the non-technical people before I produce the physical model for the techies.
Thanks

Billy wrote:
Hi,
John - yes I have already checked all this, all looks ok. Also, I'm only using the REPOS_MANAGER account for now so permissions should not be an issue.
Mark - when you say create an entity in the RON, I can create tables, how would I create an entity in the RON ? I can go to Diagrams in the RON and see my ERD.
When I installed the repository I do remember having to go to the SYS account to grant an execute on a package to the REPOS_MANAGER user because one of the REPOS_MANAGER packages required it.
Any direction would be appreciated ?
Thanks
BillyAh, but that IS the issue. You shouldn't use the repository owner account for your day to day work. Create another Oracle user and grant it privileges through the RAU. Then connect as that user to work in Designer. Oddly enough, the repository owner doesn't have the privileges that it needs - the privileges are stored in the repository, not database privileges.

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 ?

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

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 !!!

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

Compare Physical model

Similar Messages

Maybe you are looking for