Oracle Designer - Import
Availability-note
AWS
AWS-only features are available at any of the following URLs: us.cloud.talend.com, eu.cloud.talend.com, ap.cloud.talend.com
Bridge Requirements
This bridge:is only supported on Microsoft Windows.
Bridge Specifications
| Vendor | Oracle |
| Tool Name | Oracle Designer |
| Tool Version | 1.3.2, 2.1.2, 6.0, 6i to 10g |
| Tool Web Site | http://www.oracle.com/technology/products/designer/index.html |
| Supported Methodology | [Data Modeling] Multi-Model, Data Store (Physical Data Model, Logical Data Model) via DAT File |
| Data Profiling |  |
| Incremental Harvesting | |
| Multi-Model Harvesting |  |
| Remote Repository Browsing for Model Selection | |
SPECIFICATIONS
Tool: Oracle / Oracle Designer version 1.3.2, 2.1.2, 6.0, 6i to 10g via DAT File
See http://www.oracle.com/technology/products/designer/index.html
Metadata: [Data Modeling] Multi-Model, Data Store (Physical Data Model, Logical Data Model)
Component: OracleDesigner version 11.2.0
OVERVIEW
This bridge imports data models from an Oracle Designer .DAT file. A .DAT file may contain:
- an E/R Model with entities, attributes, domains, relationships and diagrams
- a Server Model with tables, columns, data types, PK/FK and diagrams
- one or more Database Implementation Models with table implementation specifications.
REQUIREMENTS
n/a
FREQUENTLY ASKED QUESTIONS
n/a
LIMITATIONS
Refer to the current general known limitations at MIMB Known Limitations or bundled in Documentation/ReadMe/MIMBKnownLimitations.html
This bridge does not support Database Implementation models.
SUPPORT
Provide a troubleshooting package with debug log. Debug log can be set in the UI or in conf/conf.properties with MIR_LOG_LEVEL=6
Bridge Parameters
| Parameter Name | Description | Type | Values | Default | Scope | |||||||||||||||||||||||||
| File | .DAT file produed by Oracle Designer. It is usually recommended to export a complete Application System, so that the produced DAT file is complete and does not contained references to objects not defined in the file. Alternatively, you can also select a set of individual entities or tables in the repository tree to be exported to the DAT file. However, you should not export diagram objects, since the produced DAT file will not contain the definition of the metadata objects, but only the diagram graphical information. This bridge will use the generated DAT file as input. 'Oracle Designer 10g' 1. Start the Repository Object Navigator tool by clicking on the Navigator icon. 2. Select the metadata objects to export. 'Oracle Designer 6i & 9i' 1. Select 'Export' under the 'Utilities' menu 2. Select 'Export data to a text file' and click on 'Next'. 3. Select the object you want to export (the loaded model is selected by default) and click on 'Next'. 4. Type the name of the file you want to export to or browse to select it and click on 'Finish'. 'Oracle Designer 2000' 1. Select the set of Entities you want to export from Designer 2000. 2. Choose 'Unload' from the 'File' menu (Designer 2000 1.3.2) or from the 'Utilities' menu (Designer 2000 2.1.2). 3. Browse to your file save directory and enter the file name for the model you are saving. 4. Click 'Save'. 5. Click 'Ok' when the processing is finished. |
FILE | *.dat | Mandatory | ||||||||||||||||||||||||||
| Model selection | Model to import. Only use when the import contains both an E/R Model and a Server Model. If your import only contains one or the other this parameter is ignored. 'E/R Model' Only the E/R Model is imported. 'Server Model' Only the Server Model is imported. 'E/R Model and Server Model' Both the E/R Model and Server Model are imported as separate models. |
ENUMERATED |
|
E/R Model | ||||||||||||||||||||||||||
| Import UDPs | A User Defined Property (UDP) is usually defined with a property definition object that has a default value. The objects that the property applies to may have an explicit value for this property. They may instead have no value assigned at all in which case the default value of the property definition (implicit value) applies. Control how property definitions and values are imported: 'As metadata' Import the explicit value as the property value. Implicit values are not imported. The default value is kept on the property type only. 'As metadata, migrate default values' Import the explicit or implicit values as property value. 'In description, migrate default values' Append the property name and value, even if implicit, to the object's description property. This allows you to export the UDP values to another tool which does not support the notion of UDP. 'Both, migrate default values' Import the UDP value, even if implicit, both as metadata and in the object's description. |
ENUMERATED |
|
As metadata | ||||||||||||||||||||||||||
| Insert the description in the comment field | Insert the Description in the Comment property for all objects. | BOOLEAN | False | |||||||||||||||||||||||||||
| Encoding | Specifies the character set encoding of the model to be imported. If there are multiple choices for a language, the actual encoding will be indicated between parentheses. |
ENUMERATED |
|
windows-1252 |
Bridge Mapping
| Meta Integration Repository (MIR) Metamodel (based on the OMG CWM standard) |
"Oracle Designer" Metamodel OracleDesigner |
Mapping Comments |
| Association | Relationship, Relationship Ends/Foreign Key | an association is created for each foreign key found in the model |
| Aggregation | True if one of the role is part of a unique identifier (UIE). True if the foreign key columns are part of the primary key | |
| DesignLevel | default if the model contains only logical or only physical information. If the model contains both levels, this property is set accordingly for each object. | |
| Name | Foreign key name | default for logical |
| AssociationRole | Relationship, Relationship Ends/Foreign Key | |
| Description | Description | |
| DesignLevel | default if the model contains only logical or only physical information. If the model contains both levels, this property is set accordingly for each object. | |
| Multiplicity | Minimum Cardinality, Maximum Cardinality | |
| Name | Relationship End Name | |
| Source | Based on the direction of creation, multiplicity of each role and if one end is part of a unique identifer. Set to True for the parent role (physical level) | |
| AssociationRoleNameMap | Relationship Ends/Foreign Key columns | The association between the primary key attribute and the foreign key attribute. Name mapping between a foreign key column and its associated primary key column (Physical level) |
| DesignLevel | default if the model contains only logical or only physical information. If the model contains both levels, this property is set accordingly for each object. | |
| Attribute | Attribute/Column | see DerivedType for the attribute's datatype information mapping |
| Comment | Comment | |
| Description | Description | |
| DesignLevel | default if the model contains only logical or only physical information. If the model contains both levels, this property is set accordingly for each object. | |
| InitialValue | Default Value | |
| Name | Name | |
| Optional | Optional | |
| PhysicalName | Name | |
| Position | Sequence Number | |
| BaseType | Attribute Format/Column Format | |
| DataType | Format | See datatype conversion array |
| DesignLevel | default if the model contains only logical or only physical information. If the model contains both levels, this property is set accordingly for each object. | |
| Name | Name | |
| CandidateKey | Unique Identifier/Unique Key, Primary Key | Primary UID Flag indicates a primary key |
| Description | Description | |
| DesignLevel | default if the model contains only logical or only physical information. If the model contains both levels, this property is set accordingly for each object. | |
| Name | Name | |
| PhysicalName | Name | |
| UniqueKey | set to True | |
| Class | Entity/Table | |
| CppClassType | Set to ENTITY | |
| CppPersistent | Set to True | |
| Description | Description | |
| DesignLevel | default if the model contains only logical or only physical information. If the model contains both levels, this property is set accordingly for each object. | |
| DimensionalRole | DataWarehouse Type | |
| Name | Name | |
| PhysicalName | Short Name/Name | |
| ClassDiagram | Entity Relationship Diagram/Server Model Diagram, Data Structure Diagram | |
| Description | Description | |
| DesignLevel | default if the model contains only logical or only physical information. If the model contains both levels, this property is set accordingly for each object. | |
| Name | Title | |
| PhysicalName | Name | |
| DatabaseSchema | No equivalent in Oracle Designer ER Modeling (Logical level) | |
| DerivedType | Domain, Attribute Datatype, Allowable Values | |
| Comment | Comment | |
| DataType | Format | See datatype conversion array |
| Description | Description | |
| DesignLevel | default if the model contains only logical or only physical information. If the model contains both levels, this property is set accordingly for each object. | |
| InitialValue | Default Value | |
| Length | Maximum Length | |
| LowerBound | Allowable Values : Low Value | |
| Name | Name | |
| PhysicalName | Name / Datatype | |
| Scale | Decimal Places | |
| UpperBound | Allowable Values : High Value | |
| UserDefined | True for Domain | |
| DesignPackage | Folder | Folders are not mapped into packages since this notion is only supported since version 6i. A package (Logical View) is created to contain the logical information. |
| DesignLevel | default if the model contains only logical or only physical information. If the model contains both levels, this property is set accordingly for each object. | |
| UserDefined | set to False | |
| ForeignKey | Foreign Key | Generated for associations (logical level) |
| Description | Description | default for logical level |
| DesignLevel | default if the model contains only logical or only physical information. If the model contains both levels, this property is set accordingly for each object. | |
| Name | Name | default for logical level |
| PhysicalName | Name | default for logical level |
| Generalization | Subtype | |
| DesignLevel | default if the model contains only logical or only physical information. If the model contains both levels, this property is set accordingly for each object. | |
| GeneralizationRole | Subtype | |
| Index | Index | Associated with each key for logical level |
| Comment | Comment | |
| Description | Description | default for logical level |
| DesignLevel | default if the model contains only logical or only physical information. If the model contains both levels, this property is set accordingly for each object. | |
| Name | Name | default for logical level |
| PhysicalName | Name | default for logical level |
| IndexMember | Index entries | Links each attribute in the key to the index associated to the key |
| Position | Usage sequence / Sequence in key | Computed |
| Note | Notes | |
| PropertyElementTypeScope | User Extensions | |
| Scope | Element Type the user defined property applies to | |
| PropertyType | User Defined Property, Extended Text Property | |
| DataType | set to MIR_DATATYPE_VARCHAR | |
| DesignLevel | Inferred from the Designer object Element Type the property applies to | |
| Name | Property Name | Display Name is not available in the file |
| PhysicalName | Not used | |
| Usage | set to User | |
| PropertyValue | User Defined Property Value | |
| Value | property value | |
| SQLViewAssociation | View, Table | No equivalent in Oracle Designer ER Modeling (Logical level). associations between views and tables (Physical level) |
| SQLViewAttribute | View Column | |
| Comment | Comment | |
| Description | Description | |
| Name | Prompt | |
| PhysicalName | Name | |
| Position | Sequence in Table | |
| SQLViewEntity | View, Materialized View | |
| Comment | Comment | |
| Description | Description | |
| Name | Display Title | |
| PhysicalName | Name | |
| WhereClause | Where / Validation condition | |
| StoreModel | Application Systems, ER Model | The model is built using the elements contained in the Oracle Designer DAT file |
| Comment | Comment | |
| Description | Description | |
| DesignLevel | default if the model contains only logical or only physical information. If the model contains both levels, this property is set accordingly for each object. | |
| Name | Title | The application system's title or extracted from the file name. |
| PhysicalName | Name | The application system's name or extracted from the file name. |
| Trigger | Trigger, PL/SQL Definition | |
| Description | Description | |
| FireOnDelete | Delete | |
| FireOnInsert | Insert | |
| FireOnUpdate | Update | |
| Name | Name | |
| PhysicalName | Name | |
| Semantics | PL/SQL Definition | |
| TriggerType | Execution Time | |
| TypeValue | Allowable values | |
| DesignLevel | default if the model contains only logical or only physical information. If the model contains both levels, this property is set accordingly for each object. | |
| Name | Meaning/Value | |
| Position | RadioSequence, Display Sequence | |
| Value | Value |