internal erd of repository - Designer

Hi sir
I want Entity of internal table of repository how can I get this
please help me
Thank in advanced 

I believe that a model used to be shipped with Designer 2.x and
6.0, but in the Designer 6i Release 3 Release Notes, it says:
"Model diagrams and files no longer supplied
Previous releases of Oracle Designer have included printed
diagrams of the repository model, together with .DAT and .DMP
export files of the model schema. These diagrams and files are
no longer supplied. However, model element definition and API
information is available from the Start menu (Start > Programs >
Oracle Repository 6i doc > API and Model Reference Guide)."
.
Your options would therefore be to either get hold of an older
version of Designer, or capture the tables using the Design
Editor, and then run the Table to Entity Retrofit utility to
turn them into ERDs. This isn't a perfect transformation because
you cannot programmatically detect which tables are intersection
tables for many-to-many relationships, or which entities are
subtypes of others, just from the table design.

Related

Clarification on Repository and Designer

Hi
These are my understandings on the oracle repository and oracle designer.
An oracle repository consists data about data and it is stored in the database and we inturn use the oracle designer to maintain the repository.Pl confirm me whether my understanding is correct.
My other question is why should we maintain a repository.What is the necessity to maintain information on metadata?
Thanks & Regards
Suji Iyer 
Fair question, and it goes to the heart of why we Designer users prefer Designer to the design tools that are built into JDeveloper. You see, while JDeveloper can draw pretty class diagrams, database diagrams, and several of the other UML based diagrams, it has no repository behind it - only XML files. Here are my top five reasons that a metadata repository is IMPORTANT:
1. You can maintain the relationships between objects: Modules AND the tables the modules reference. Entities and the tables that are the physical implementation of the entities. Relationships that go both ways, even many to many.
2. If I change something, the change gets filtered down to everything that uses that thing. For instance, if I change a column name, all of the modules that use that column IMMEDIATELY get the change. That's because they don't have a copy of the column information with the old data, they have a reference to the column I just changed.
3. Easy reporting, cross referenced any way I need it.
4. All members of the team can immediately see the changes I've made, as soon as I commit the changes. Yes, I know that I could put the XML files on a shared file system, or in a version control system, and we could share them that way, but my experience has been that this works better.
5. I don't have a versioned repository, but I know people who do, and they love the fact that a Designer versioned repository can version table definitions. I have versioned the DDL files that create and alter tables, and it isn't the same thing. This is mostly because you use a different DDL command to change a table than you do to create it the first time. You would have to run the create command, then each alter command in the correct order to get an identical result.

Data Modeling question

Hi All,
I have a Oracle 10g database , which is fully functional and in use..
I have been asked to data modeling for the database and identify the logical data model and relationships between various objects...Could anybody suggest me how to proceed , which tool to use...any pdf's or study links from you...
Any help will be appreciated
Thank You 
While you can do this with Designer, if you aren't already a Designer user I don't recommend that you install Designer just to model an existing database.
However, if you are a Designer user already, this is done from the Design Editor. Choose Generate from the menu, and then "Capture Design of ... Server Model...". You will then be able to connect to the database that contains the objects you want to model and import the metadata into the repository, from which you will be able to draw a Server Model Diagram. Just drag tables from the navigator on the left to the gray area on the right, and Designer will start the diagrammer and draw in those tables.
If you are not already a Designer user, I recommend getting and installing JDeveloper. It has database modeling capabilities that are quite good. I'd give you a reference to a tutorial about how to use JDeveloper for this, but I can't seem to get the JDeveloper pages on OTN to come up today. You'll have to find the tutorial yourself starting from http://www.oracle.com/technology/products/jdev/index.html. 
Thank You very much for your reply
How about creating E-R diagrams about entities and a few selected tables which are most important in the database ,, rather than doing it for the entire database..
My requirement is to create a document that explains how the application works and how important messages flow from one entity to another..so that if a new comer joining an oraganization understands the application just by reading this document...
Please tell me should i go for ER Diagrams or any other way that best suits my requirement
Thanks again 
When you say "E-R diagrams", do you mean E/R Diagrams as drawn by Oracle Designer? In Designer, Entities and Relationships are logical design elements while Tables and Foreign Keys are physical design elements. So, in Designer, you draw Server Model Diagrams in the Design Editor to show tables, columns and foreign keys, but E/R Diagrams in the E/R Modeling tool to show entities, attributes and relationships. What JDeveloper can draw is a Database Diagram which is fairly close to Designer's Server Model Diagram. JDeveloper does not draw true E/R diagrams.
If you are trying to document an existing database, the physical design is probably what you want to show. You might care about the logical view, but the physical view is close enough. In fact, some people would claim that a physical database model is all you ever need. I disagree, but that can get to be something of a religious war.
However, if you really want to see Entities and Relationships, Oracle Designer has a tool called "Table to Entity Retrofit" that will transform your tables into entities, columns into attributes and foreign keys into relationships. You will find this from the Repository Object Navigator (RON), not from the Design Editor. Choose Utilities -> Designer -> Table to Entity Retrofit... After you run this tool, you will probably want to make a few changes to the resulting elements. You will especially want to rename the relationships, as the utility uses the foreign key names which are typically poor names for relationships. Then you can create an E/R diagram from the existing objects.

Tables to Entity Retrofit

I want to create an Etity-Relationship diagram from a database created manually previously. But the Table to Entity Retrofit window of course, does not show any table because I do not know where to especify the database where extract the tables from.
How can I do this? 
Hi Ulises,
Please see the following forum topic for more details on where to find information
regarding Reverse Engineering =>
Re: Strange toolbars
Basically, you capture the design of the database first using the Design Editor, then
run the Table to Entity Retrofit Utility based on your captured server DESIGN, not the
server itself.
Regards,
Dominic
Designer Product Management
Oracle Corp

Storage Clauses and using Designer

Hi there,
I am doing another OWB course and the following questions were asked:
1. How do I manage the storage clause on the DDL scripts in OWB without manually editing the scripts? (This one has been een around for a while)
2. Would it be possible to design the objects in Designer & pull in the definitions - with storage clauses?
3. If you follow this route (2), does Designer allow the creation of dimensions (I beleive the previous version did not)?
4. If you cannot create dimensions in Designer, would you be able to import the underlying table and define only the dimension (hierarchy) structure on it?
5. Previous versions of OWB could not import dimensions - is there a way around this problem?
Thanks in advance!
Marlene Raats 
Marlene,
See the answers below:
Hi there,
I am doing another OWB course and the following questions were asked:
1. How do I manage the storage clause on the DDL scripts in OWB without manually editing the scripts? (This one has been een around for a while) At the moment (version 9.0.2) there is a limited functionality on this - for example, you can define the tablespace and some other parameters but not a complex storage clause. You are limited to whatever you can define during the configuration phase of the object. If you have particularly complex storage clauses, the best way would be to deploy them separately from OWB and then import their definition into OWB. Object deployment is a one-time process.
2. Would it be possible to design the objects in Designer & pull in the definitions - with storage clauses? You can import the table definitions, but I am afraid that the storage clauses will not be imported completely (see coment above).
3. If you follow this route (2), does Designer allow the creation of dimensions (I beleive the previous version did not)? Dimensional models have to be designed in OWB, current version of designer does not support them.
4. If you cannot create dimensions in Designer, would you be able to import the underlying table and define only the dimension (hierarchy) structure on it? Yes, it is possible to import a dimension table with an already defined hierarchy structure, and then define the hierarchy inside OWB.
5. Previous versions of OWB could not import dimensions - is there a way around this problem?
Thanks in advance!As mentioned, it is possible to import dimensional tables but not dimensional objects at the moment.
Regards:
Igor
Marlene Raats 
I can provide some more information on questions 3-5:
3. In Designer you can register a table being a dimension. However, Designer does not enable you to define the levels, level attributes and hierarchies. As a result... in Designer this property is only there for documenation purposes. You create dimensions in Warehouse Builder.
4. In the current version of Warehouse Builder unfortunately you can only import the table structure in which case you get a table object inside Warehouse Builder. You cannot define a hierarchy on top of this table structure... but we are currently rebuilding the dimensional modeling area which will eventually enable you to do this. Unfortunately it will at least not be available until summer 2003 (don't have any release dates yet).
5. At the moment there is not really a way around the lack of support to import dimensions... unless you want to explore scripting to access the repository through the back end (generate a script yourself based on existing database objects).
Hope this helps,
Mark. 
I have a much better idea. Add this dimension modelling area plus the mapping modelling area to Oracle Designer and Oracle will have a far far better datawarehouse design and development tool than Oracle Warehouse Builder will ever be.
If they added the functionality of OWB to Designer two years ago, instead of developing OWB, we won't have to discuss about these kind of problems and can spent more time to actually design and develop a datawarehouse.
Maybe that somebody can tell me why Oracle still is trying to make OWB work? It isn't even capable to create datawarehouse example in the demo schema SH that comes with the Oracle 9i database.
Is it possible now to import tables (flagged as dimensions) from Oracle Designer into OWB as dimension objects?
Alternatively, is it possible to copy attributes from a table object into a dimension object? Any workarounds so I do not have to enter all of the table object information into the Dimension and Fact object editors to recreate them?
I can provide some more information on questions
3-5:
3. In Designer you can register a table being a
dimension. However, Designer does not enable you to
define the levels, level attributes and hierarchies.
As a result... in Designer this property is only
there for documenation purposes. You create
dimensions in Warehouse Builder.
4. In the current version of Warehouse Builder
unfortunately you can only import the table structure
in which case you get a table object inside Warehouse
Builder. You cannot define a hierarchy on top of this
table structure... but we are currently rebuilding
the dimensional modeling area which will eventually
enable you to do this. Unfortunately it will at least
not be available until summer 2003 (don't have any
release dates yet).
5. At the moment there is not really a way around the
lack of support to import dimensions... unless you
want to explore scripting to access the repository
through the back end (generate a script yourself
based on existing database objects).
Hope this helps,
Mark.

Incremental Server Generation

We are evaluating Server Generation technologies and trying to find out if Designer supports incremental releases of the physical database model.
We don't want to generate the complete DDL every time, only what has changed.
Also, will it create any meta data, apert from the standard Oracle meta data to define what tables and Views are supportting which ERD Entities from the Database Design Transformation.
Thanks
Pat 
1. Yes, Designer can create "alter table" etc. scripts. I don't really remember how. It's a long time ago I work with Designer.
2.What else do you want apart from the standard Oracle meta data? Designer keeps track of the entity-table and attribute-column mapping. 
Generating incremental scripts is done like this:
- in the generate dialog-box choose "database" in the "Target for Generation" section.
- enter username/password#database of the database you want incremental scripts for.
- enter "file Prefix" and directory. Remember this, because this is where you'll find the increment scripts after generation.
- click "start".
- when Designer is ready a dialog will appear with 4 options. At this point Designer has created the increment-scripts but has NOT executed them yet. In the dialog you can choose to execute them immediately... or you can click cancel: the scripts will then be available in the directory you specified before. They can then be executed at a later time using SQL*Plus.
Hope this helps.
Tim 
I need to know the transformation mapping between Entity and Tables.
We are tring to generate EJB definitions using the logical model, not the database model. To do this we need to generate against views that represent the Entities.
Does the Database Transformer store these mappings and create the logical views. 
Thanks Tim, this is just what I need.
As long as designer is kept as the master model, then this should always work.

Categories

Resources