Using Comparison Filters Working with the Version Comparison Tool

19-2 Oracle Fusion Middleware Developers Guide for Oracle Data Integrator ■ Avoid any ID conflicts when exporting and importing from one repository to another ■ Understand the provenance of every object, simply by looking at its Internal ID. The 3 last digits always refer to the repository where it was created. Important ExportImport Rules and Guidelines Due to the structure of the object IDs, these guidelines should be followed: ■ Work repositories must always have different internal IDs. Work repositories with the same ID are considered to contain same objects. ■ If an exportimport operation is performed between two MasterWork repositories possessing identical internal IDs, there is a risk of overwriting objects when importing. Objects from both repositories that have same IDs are considered the same.

19.1.2 Relationships between Objects

Oracle Data Integrator stores all objects in a relational database schema the Repository with dependencies between objects. Repository tables that store these objects maintain these dependencies as references using the IDs. When you drag and drop a target datastore into an integration interface, only the reference to the ID of this datastore is stored in the interface object. If you want to export this interface, and import it in Synonym mode into another work repository, a datastore with the same ID must already exist in this other work repository otherwise the import will create a missing reference. The missing references can be resolved either by fixing the imported object directly or by importing the missing object. Solutions allow to export and import sets of dependent objects automatically. Using solutions and versioning is the recommended way of maintaining the dependencies automatically when doing exportimport. See Chapter 18, Working with Version Management . Therefore, the Model or Sub-model holding this Datastore needs to be exported and imported in Synonym mode prior to importing the integration interface. There are also dependencies between work repository objects and master repository objects. Dependencies within a work repository are ID-based. Dependencies between objects of the work and objects of the master are based on the Codes and not the IDs. This means that only the Code of the objects for example ORACLE is the code of the Oracle technology in the master of the master repository objects are referenced in the work repository. It is important to import objects in the appropriate order. You can also use Solutions to preserve these dependencies. Table 19–1 lists the dependencies of an integration interface to other objects when importing the integration interface in synonym mode. ExportingImporting 19-3

19.1.3 Import Modes

Oracle Data Integrator can import objects, the topology or repositories using several modes. Read carefully this section in order to determine the import mode you need. Table 19–1 Dependencies of an integration interface in the work and Master Repository Dependencies on other objects of Work Repository when importing in Synonym Mode Dependencies on objects of the Master Repository ■ ParentChild Folder: Folder holding this Interface needs to be imported first. ■ Reference ModelSub-Model: all ModelsSub-Models holding Datastore definitions referenced by the Interface need to be imported first. Datastore definitions including Columns, Data Types, Primary Keys, Foreign Keys references, Conditions must be exactly the same as the ones used by the exported Interface ■ Reference Global Variables, Sequences and Functions used within the Interface need to imported first ■ Reference Local Variables, Sequences and Function used within the Interface need to imported first ■ Reference Knowledge Modules referenced within the Interface need to be imported first ■ Reference Any Interface used as source in the current Interface needs to be imported first ■ Technology Codes ■ Context Codes ■ Logical Schema Names ■ Data Type Codes ■ Physical Server Names of the Optimization Contexts of Interfaces Import Mode Description Duplication This mode creates a new object with a new internal ID in the target Repository, and inserts all the elements of the export file. The ID of this new object will be based on the ID of the Repository in which it is to be created the target Repository. Dependencies between objects which are included into the export such as parentchild relationships are recalculated to match the new parent IDs. References to objects which are not included into the export are not recalculated. Note that this mode is designed to insert only new elements. The Duplication mode is used to duplicate an object into the target repository. To transfer objects from one repository to another, with the possibility to ship new versions of these objects, or to make updates, it is better to use the three Synonym modes. This import mode is not available for importing master repositories. Creating a new master repository using the export of an existing one is performed using the master repository Import wizard.