In the Select Input Files screen, for Merge Type, select Full Repository Merge. Select the original parent repository by clicking Select next to Original Master Select the modified repository by clicking Select next to the Modified Repository Optionally,

Managing Oracle BI Repository Files 16-11 Figure 16–5 Merge Repository Wizard: Select Input Files Screen Full Merge

3. In the Select Input Files screen, for Merge Type, select Full Repository Merge.

4. Select the original parent repository by clicking Select next to Original Master

Repository . Browse to select the original repository, then click Open. 5. Provide the password for the original repository in the appropriate Repository Password field.

6. Select the modified repository by clicking Select next to the Modified Repository

field. Browse to select the modified repository, then click Open. 7. Provide the password for the modified repository in the appropriate Repository Password field.

8. Optionally, you can change the default name and location of the saved merged

file by clicking Select next to the Save Merged Repository as field. Provide a new name and location, then click Save.

9. It is a good practice to equalize your changes to clean up underlying object IDs

before merging. If you have not yet equalized your changes, select Equalize during merge to equalize objects as part of the merge process. Selecting this option may affect merge performance. See Equalizing Objects for more information about equalizing.

10. Click Next. If there are any conflicts, the Define Merge Strategy screen of the

Merge Repository Wizard appears. If there are no conflicts, the Merge Repository Wizard closes. Figure 16–6 shows the Define Merge Strategy screen. 16-12 Metadata Repository Builders Guide for Oracle Business Intelligence Enterprise Edition Figure 16–6 Merge Repository Wizard: Define Merge Strategy Screen

11. The Define Merge Strategy screen displays a decision table that shows conflicts for

this merge. See Table 16–4 for details about the elements in this screen. To make decisions about whether to include or exclude objects from the merged repository, choose Current or Modified from the Decision list. Choose Current to keep the change for the selected object in the current repository, or choose Modified to keep the change for the selected object in the modified repository. When you select an object in the decision table, the read-only text box below the decision table describes what changes were made to that object in the current repository. In addition, the tree panels at the bottom of the dialog show the affected objects for the selected row. Alternatively, you can select an object in one of the tree views to automatically highlight the corresponding row in the decision table. The Modified option in the Decision list displays a suffix that indicates whether the object in question will be added to or deleted from the merged repository. Modified A indicates that the object will be added, and Modified D indicates that the object will be deleted. The type of conflict is displayed in the Description column of the Conflicts table. The decision choices you can make depend on the type of conflict shown in this column. The following list shows example results for different types of conflicts: ■ Added to Current: Choosing Current keeps the new object in the merged repository. Choosing Modified D deletes the new object from the merged repository. Managing Oracle BI Repository Files 16-13 ■ Deleted from Current: Choosing Current keeps the repository as it is without adding the object to the merged repository. Choosing Modified A adds the object back into the merged repository. ■ Changed in both different: The object was not added or deleted, but at least one of its properties was modified. Click the plus sign + to the left of the row to view the property that was changed, as well as its value in the original, current, and modified versions of the repository. Property values are only shown for small-length strings. Longer-length strings like descriptions, features, and init strings are not shown. Click the option for the value you want to retain in the merged version of the repository. For some properties, such as aliases, you can choose the Merge Choices option to merge the properties rather than choose one over the other. This option is only available if the properties can be merged. After you make a merge decision, the row for that decision in the table changes from red to black. When all rows have a value in the Decision field, the Finish button is enabled. 12. In addition to making merge decisions, you can perform other operations in the Define Merge Strategies screen. See Table 16–4 for details.

13. Click Finish.