Synchronizing Solutions Working with Solutions

19-4 Oracle Fusion Middleware Developers Guide for Oracle Data Integrator Synonym Mode INSERT Tries to insert the same object with the same internal ID into the target repository. The original object ID is preserved. If an object of the same type with the same internal ID already exists then nothing is inserted. Dependencies between objects which are included into the export such as parentchild relationships are preserved. References to objects which are not included into the export are not recalculated. If any of the incoming attributes violates any referential constraints, the import operation is aborted and an error message is thrown. Note that sessions can only be imported in this mode. Synonym Mode UPDATE Tries to modify the same object with the same internal ID in the repository. This import mode updates the objects already existing in the target Repository with the content of the export file. If the object does not exist, the object is not imported. Note that this import mode does NOT delete child objects that exist in the repository but are not in the export file. For example, if the target repository contains a project with some variables and you want to replace it with one that contains no variables, this mode will update for example the project name but will not delete the variables under this project. The Synonym Mode INSERT_ UPDATE should be used for this purpose. Synonym Mode INSERT_ UPDATE If no ODI object exists in the target Repository with an identical ID, this import mode will create a new object with the content of the export file. Already existing objects with an identical ID will be updated; the new ones, inserted. Existing child objects will be updated, non-existing child objects will be inserted, and child objects existing in the repository but not in the export file will be deleted. Dependencies between objects which are included into the export such as parentchild relationships are preserved. References to objects which are not included into the export are not recalculated. This import mode is not recommended when the export was done without the child components. This will delete all sub-components of the existing object. Import Mode Description ExportingImporting 19-5

19.1.4 Tips for ImportExport

This section provides tips for the import and export operations. Repository IDs As a general rule, always use different internal IDs for your repositories in order to avoid any ID conflicts. Import Reports The import report is displayed after every import operation. It is advised to read it carefully in order to determine eventual errors of the import process. The import report gives you details on the: ■ Import Mode ■ Imported Objects . For every imported object the object type, the original object name, the object name used for the import, the original ID, and the new, recalculated ID after the import is given. ■ Deleted Objects . For every deleted object the object type, the object name, and the original ID is given. ■ Created Missing References lists the missing references detected after the import. ■ Fixed Missing References lists the missing references fixed during the import. You can save the import report as an.xml or .html file. Click Save... to save the import report. Missing References In order to avoid missing references, use solutions to manage dependencies. See Section 18.4, Working with Solutions for more information. Import Replace This import mode replaces an already existing object in the target repository by one object of the same object type specified in the import file. This import mode is only supported for scenarios, Knowledge Modules, actions, and action groups and replaces all children objects with the children objects from the imported object. Note the following when using the Import Replace mode: If your object was currently used by another ODI component like for example a KM used by an integration interface, this relationship will not be impacted by the import, the interfaces will automatically use this new KM in the project. Warnings : ■ When replacing a Knowledge module by another one, Oracle Data Integrator sets the options in the new module using option name matching with the old modules options. New options are set to the default value. It is advised to check the values of these options in the interfaces. ■ Replacing a KM by another one may lead to issues if the KMs are radically different. It is advised to check the interface’s design and execution with the new KM. Import Mode Description