1. Upgrading Business Intelligence Applications
  2. In-Place Upgrade
  3. Upgrade Tasks
  4. Import Content Into the ODI Repository

Import Content Into the ODI Repository

Import content into the ODI repository of Oracle BI Applications 11.1.1.10.3 PS4.

  1. Import connection details.
    1. Launch the ODI Studio client and connect to the ODI repository of Oracle BI Applications 11.1.1.10.3 PS4.
    2. In the Topology tab, from the Connect Navigator drop-down on the top right corner, select Import.
    3. In the Import Selection dialog, select Smart Import.
    4. In the File Selection dialog, specify the export file created while exporting connections.
    5. The default behavior of Smart Import is to merge details in the target repository. Ensure that no issues are reported. If issues are reported, then resolve them to ensure that the existing details are replaced by the details being imported. Select the BIAPPS_DW and BIAPPS_BIACOMP Data Servers, and then select the Overwrite option.
    6. Select Global context, select the Reuse option, and then click Next.
  2. Verify that the physical servers have the correct details and the physical schemas have the correct Datasource Num ID value set in the DATASOURCE_NUM_ID flexfield.
    1. In ODI Studio, in the Topology tab, select Physical Architecture and open the BIAPPS_DW physical server.
    2. In the Definition tab, verify the user and password are correctly populated.
    3. In the JDBC tab, verify that the JDBC URL is correctly set. If you used the default Merge action during the Smart Import, then the user and password will be updated but the JDBC URL will remain unchanged.
    4. Repeat step 2 and its substeps for the BIAPPS_BIACOMP physical server.
    5. Verify that the physical schema for BIACOMP and DW are set as defaults using these instructions. If they are not set as defaults, then the Load Plans will fail.
      1. In ODI Studio, click Topology and select Physical Architecture.
      2. Open the physical schema under the BIAPPS_BIACOMP physical server.
      3. Verify that the Defaultoption is selected on the Definition tab and save the changes.
      4. Repeat steps ii and iii for the physical schema under the BIAPPS_DW physical server.
    6. Verify the source connection details.
      For example, if you need to extract from an instance of eBusiness Suite 12.2.0, then open the corresponding physical server ( EBS_SRC) and verify the User/Password and the JDBC.

      The physical server name is the one that you specified in the Configuration Manager user interface when you registered the source.

    7. Verify the associated physical schema. Navigate to the Flexfields tab and verify that the DATASOURCE_NUM_ID flexfield is set to the value you originally assigned. This value of DATASOURCE_NUM_ID must match the value in Configuration Manager for this source connection.
    8. Open the corresponding logical schema and verify that the DATASOURCE_NUM_ID flexfield is also set with the same value.
    9. Verify that the following logical schemas have the correct Data Source Num ID value set in the DATASOURCE_NUM_ID flexfield:

      • If you don't see 999 values for all these logical schemas, set the value to 999.

        • DW_BIAPPS11G
        • DW_BIAPPS11G_LOG_FILES
        • DW_BIAPPS11G_SHARED_FILES
        • DW_BIAPPS11G_SRCFILES

      • Navigate to the Flexfields tab and verify that the DATASOURCE_NUM_ID flexfield is set to the value you originally assigned. The value of DATASOURCE_NUM_ID must match the value in Configuration Manager for this source connection. Verify the value of DATASOURCE_NUM_ID in all the registered file technology data servers.

        • DS_TALEO15A_SRCFILES
    10. Ensure that all the registered file technology data servers have the following property in their JDBC url:
      NO_RTRIM_DEL_STRING=true

      If not , then add this property to the end of the JDBC url as shown below:jdbc:snps:dbfile?ENCODING=UTF-8&NO_RTRIM_DEL_STRING=true

    11. If the registered file technology data servers falls under the old ORACLE_HOME, update it to use the NEW_ORACLE_HOME. Repeat this task for all applicable technology data servers.
    12. Update OracleDIAgent with host name.
  3. Import the Security settings that you exported while exporting security settings. Import the Security settings using the Insert and Update options as follows:
    1. Import new security objects as follows:
      1. In the Topology tab, from the Connect Navigator (Topology icon drop- down on the top right side of the navigator pane), select Import.
      2. In the Import Selection dialog, select Import Security Settings.
      3. In the Import Security Settings dialog, select Synonym Mode INSERT for the Import Mode, select Import from a Folder, enter the directory location to which you had exported the Security settings while exporting security, and then click OK.
    2. Update the existing security objects as follows:
      1. In the Topology tab, from the Connect Navigator (Topology icon drop- down on the top right side of the navigator pane), select Import.
      2. In the Import Selection dialog, select Import Security Settings.
      3. In the Import Security Settings dialog, select Synonym Mode UPDATE for the update Mode, select Import from a Folder, enter the directory location to which you had exported the Security settings while exporting security settings, and then click OK.