Oracle^® Business Intelligence Applications Upgrade Guide > Upgrading Oracle BI Applications > Process of Upgrading the Siebel Analytics Repository >

Merging the Analytics Repositories

In this procedure, you execute the main algorithm to upgrade the repository. For more information on merging the repositories, see Oracle Business Intelligence Server Administration Guide.

To merge versions of the Analytics repositories

1. Copy the three repositories (for example, SiebelAnalytics_7x.rpd, OracleBIAnalyticsApps.rpd, and Customer_SiebelAnalytics.rpd) to the AfterMerge folder.
2. Open the repository from the latest installation (for example, OracleBIAnalyticsApps.rpd) in the \OracleBIUpgrade\AfterMerge folder.
3. Save the repository with a new name, for example, Merged_Repository_OracleBIAnalyticsApps.rpd.

   This new repository will contain the final results of the upgrade.

4. From the Administration Tool menu bar, choose File > Merge.
5. In the Select Original Repository dialog box, select the original repository (for example, SiebelAnalytics_7x.rpd).
6. Enter the password, and click OK.
7. Click Select for the Modified Repository field.
8. In the Select Modified Repository dialog box, select the repository that contains the customizations you made to the previous version of the Analytics repository.
9. Click Open, type the password, and then click OK.
10. In the Decision drop-down list, select the action you want to take regarding the repository change, or accept the default action.
11. To locate subsequent rows with empty Decision fields, click the Decision header cell.

    When all rows have a value in the Decision field, the Merge button is enabled.

12. Click Merge.

    This process can take up to 40 minutes, depending on the size of the repositories you are working with. A message will alert you when the merge is complete.

13. Click Yes when asked if you want to run a consistency check.

    The number of errors returned by the consistency check is an indication of how successful the merge process was. If you receive many errors, for example, over 300, you should analyze the reason for the errors. If the merge process failed to recognize that two objects are the same, you may need to edit the rename file if the object is in the Current repository, or add your own rename file if you have renamed many of the objects and the upgrade engine failed to relate them to the original objects.

    You also may need to change the actions you selected in the Decision drop-down list before rerunning the merge. This could save you time by reducing the number of errors that you will need to fix manually.

    Once you are satisfied with the results of the merge, you should fix the remaining errors manually. It is important that you fix all errors before moving on to the next step. This repository serves as the input for the next stage.

    You should also check that all of your customized objects are present and that no duplicate physical tables were introduced. To check for duplicate tables, search for physical tables using a query such as:

    where name like '*#1'

14. Copy the repository to the folder \OracleBIUpgrade\AfterManualWork.