Import Datastores

You must import the datastores prior to importing the customized ETL tasks.

Note:

The following steps are implemented in the DEV repository only. To migrate changes to TEST and PROD repositories, see My Oracle Support document (ID 2688437.1) titled OBIA 12c: How do you migrate configurations and/or customizations from Development to a Test or a Production Environment.
  1. Launch the ODI Studio client and connect to the ODI Repository for Oracle BI Applications 11.1.1.10.3 PS4.
  2. Click Designer, click Models, click Oracle BI Applications (folder), and select Oracle BI Applications (Model).
  3. Create original and custom versions of the model.
    1. Right-click the model, select Version and then select Create Version. Create an initial version.
    2. Perform these steps again to create the version with customizations.
    The original version reflects the ready-to-use datastores while the new version reflects the merged datastores, allowing comparison between the two.
  4. Import the customized datastores.
    1. Right-click the Oracle BI Applications model.
    2. Select the Import and the Import Datastore option.
    3. In the Import Datastore window, ensure that Import Type is Synonym Mode INSERT. The Update mode will update existing columns to reflect their pre-upgrade state while Insert/Update mode will delete columns that were introduced in the upgrade repository but do not exist in the pre-upgrade repository.
    4. Navigate to the directory where you previously exported the custom datastores.
    5. Select the check boxes for each datastore to be imported and click OK.
      If prompted to declare the repository ID and continue with the import, select Yes. You may see this prompt multiple times, click Yes each time.
      When the import completes, you should see a summary report similar to the following.

      The upgrade datastores will now be merged with the pre-upgrade customizations.

    6. Review the customized ready-to-use datastores that have been imported by navigating to the Columns tab.
      In INSERT mode, the custom columns are imported into the datastore. In the 11.1.1.10.3 repository, these are usually the last columns. In the 11.1.1.10.3 repository, Oracle may have added columns and these will have a conflicting position ID, or a column simply may have moved between 11.1.1.10.3 and 11.1.1.10.3 PS4. These columns will appear to have the same position number but this does not cause any issues. As an optional step, you can have ODI recalculate the position numbers.
    7. Double-click on any column in the datastore. Without making any changes, now select another column. ODI will automatically recalculate the position numbers. Save the datastore.