Scribd
Upload
66 views4 pages

Merge

Full merges are used to import objects from one repository to another with no common parent, or when two derived repositories share a common parent. Patch merges apply differential changes between versions of the same repository, such as promoting development changes to production. The full merge process involves an original, modified, and current repository, while patch merges create a patch file containing differences between an original and current repository to apply to a modified repository. Decision tables are used to resolve conflicts by choosing whether to keep the current or modified object version.

Uploaded by

Dinesh V
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
66 views4 pages

Merge

Full merges are used to import objects from one repository to another with no common parent, or when two derived repositories share a common parent. Patch merges apply differential changes between versions of the same repository, such as promoting development changes to production. The full merge process involves an original, modified, and current repository, while patch merges create a patch file containing differences between an original and current repository to apply to a modified repository. Decision tables are used to resolve conflicts by choosing whether to keep the current or modified object version.

Uploaded by

Dinesh V
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

AUM:

Merge:
Full merges are typically used during development processes, when there are two different repositories that
need to be merged. Full merges can also be used to import objects from one repository into another.

Patch merges are used when you are applying the differential between two versions of the same repository. For
example, you might want to use a patch merge to apply changes from the development version of a repository
to your production repository, or to upgrade your Oracle BI Applications repository.

Full Repository Merge:

The merge process typically involves three versions of an Oracle BI Repository: the original repository,
modified repository, and current repository.

No Common Parent. This merge, also called a two-way merge, is useful when you want to import objects
from one repository to another. In this case, objects are merged from two different repositories with no
common parent
Common Parent. This merge, also called a three-way merge, is useful when you have a common parent
repository and two derived repositories. There is a parent (original) repository, and two derived repositories.
After the merge, a fourth merged repository is created.

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.
The Define Merge Strategy screen displays a decision table that shows conflicts for this merge.

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.

Patch Merge:
In a patch merge, you create a patch that contains the differences between the current repository and the
original repository.

In a development-to-production scenario, you have an original parent repository, a current repository that
contains the latest development changes, and a modified repository that is the deployed copy of the original
repository.

Original Reporitory = Modified Repository

Current Repository Contains latest Changes.

Create Patch:

Open Current RepositoryFileCompareSelect Original Repository

It is a good practice to equalize your changes to clean up underlying object IDs before generating a patch.

1. In the Compare repositories dialog, review the changes between the repositories. Then, click Create
Patch.
2. In the Create Patch dialog, enter a name for the patch file, for example,  my_patch.xml , and
click Save.

Apply Patch:
Step 1:In the Administration Tool, open the modified Oracle BI repository in offline mode. In i.e., open
the repository on which you want to apply the patch.

Step 2:Select File, then select Merge. The Merge Repository Wizard appears. For Merge Type, select
Patch Repository Merge.

Step 3: Select the original parent repository by clicking Select next to Original Master Repository.

Click Select next to Patch File. Browse to select the patch file you want to apply, 

You might also like