10.7 About the Peer to Peer
Merge Option
This section includes the
following topics
■ Peer to Peer Merge:
High-Level Process Flow
■ Peer to Peer Merge:
Procedure for Merging
The Peer to Peer Merge
option enables you to merge DAC repositories of different instances of the
same release. For example, in a development environment you may have two
instances of a DAC Repository used with Oracle BI Applications release 7.9.5 that
you want to merge.
10.7.1 Peer to Peer Merge:
High-Level Process Flow
Figure 10–5 shows a
high-level process flow for using the Peer to Peer Merge option to merge
DAC repositories of different instances of the same release.The
term base is used to refer to a source or target container that you
have not changed or customized in any way.
Figure 10–5 Merge Process
for Peer to Peer Merge Option
In Step 1 of the high-level
process flow, you export one instance of the existing customized source
system container to the file system and then import this container into
the repository temporary tables. This repository is referred to as
the source in the
Upgrade/Merge Wizard.
In Step 2, you create a
Difference Report that compares the instance 1 container (including
customizations) with the instance 2 container (including customizations).
The instance 2 container is
referred to as the target.
In Step 3, you accept or
reject the objects that the Difference Report shows as beingpresent or changed
in the source but not the target. See Section 10.8.3, "Possible Repository
Merge Outcomes Based on Your Decisions" for a description of how
objects are merged based on the action you take.
In Step 4, after you have
resolved the differences, you then execute the merge. In Step
5, the Upgrade/Merge Wizard
references the customizations in the newly merged container with the
instance 1 base container.
10.7.2 Peer to Peer Merge:
Procedure for Merging
Follow this procedure to
use the Peer to Peer Merge option to merge DAC repositories of different
instances of the same release. Before you begin this procedure you should
review the section"Resolving Object Differences in the View
Difference Report" to gain an understanding of your options
for resolving object
differences.
To merge two DAC
repositories of different instances of the same release
1. Navigate to the
Upgrade/Merge Wizard by selecting Tools, then DAC RepositoryManagement, and
then Upgrade/Merge Wizard.
2. From the drop-down
list, select Replace Base, and then click OK.The Import Source System Container
dialog box appears.
3. Click Change
import/export folder to navigate to the directory that holds the metadata
files for instance 1 of the source system container you want to merge.
4. Select the
appropriate container from the Source System Container drop-down list and click
OK.
5. In the Importing
Tables dialog box, re-type the text in the text box to confirm you want to
proceed, and click Yes.When the import process is complete, the Importing
Tables dialog box tells you how long the process took.
6. Click OK.
The Create Difference
Report dialog box appears.
7. Create the
Difference Report to view the differences between the instance 1 container
and the instance 2 container.
a. Enter a name for
the Difference Report, or leave the default name.
b. In the Existing
Container drop-down list, select the instance 2 container.
c. (Optional) Enter a
description for the Difference Report.
d. Click OK.
When the Difference Report is complete, the Creating
Difference Report dialog box tells you how long the process took.
e. Click OK.
The View Difference Report dialog box displays the
differences between the instance 1 and instance 2 containers.
8. In the View Difference Report dialog box, resolve
the differences between the instance 1 and instance 2 DAC repositories.
The instance 1 repository is referred to as the source or existing container, and instance 2 as the
target or new container. For detailed information about the View
Difference Report, see"Resolving Object Differences in the View Difference Report". To resolve the differences, you either accept or reject the
objects that appear as new or changed in the instance 1 container but do
not appear in the instance 2 container. a. In the navigation tree, select the repository object
for which you want to view the differences between the instance 1 and
instance 2 containers. If the object selected in the navigation tree is a
hierarchical object, the subtabs for the child objects appear in the
bottom pane of the Object Differencewindow.
b. (Optional) Filter the objects that appear in the
top, right window by selecting one of the options from the drop-down list
in the toolbar.
c. For parent objects in the top pane and any child
objects in the bottom pane, accept or reject the object in the difference
list by selecting or deselecting the Accept Source check box. For
detailed information about these options and the merge outcome, see "Possible
Repository Merge Outcomes Based on Your Decisions".
Note: If a child object has been changed but not the
parent object, the parent object will still appear in the Object Difference
window even though it has not been changed.
d. (Optional) Once you have made a decision about
whether to accept or reject the difference, select the Resolved check box
to indicate you have resolved the object.
e. Repeat Steps a, b, and c, until you have resolved
all object differences.
f. Click Merge. The Merge dialog box appears and
lists the details of the merge.
9. Click Merge to begin the merge process.
10. Click OK in the Merging Repositories dialog box
when the merge process is complete.
