Oracle BI EE 10.1.3.3/2 - Merging Repositories - Substitute for Import From Repository - 2 way Merge with No Parent - Part 2
Posted by Venkatakrishnan J on March 24, 2008
If you look at the comments section of my blog entry here, there are quite a few users who have mentioned that the procedure did not work on their setup. One of the main reasons for that was that the changes being merged was not shown to the end user. Also, the procedure did not work for some of the earlier versions. So, i thought of blogging about another procedure that would basically merge only two repositories. If you had worked on the earlier releases of BI EE ( 7.8 or before versions ), you would have noticed that there was an option called Import from Repository. What this option basically did was it imported the objects from one repository into another. But this has been deprecated from 10.1.3.2 version of BI EE. Now the recommended way of getting one repository objects into another is to do a 2-way merge. Lets look at a step-by-step approach for achieving this. So basically our aim is to combine the contents of 2 repositories into a 3rd repository. The merge process would look like the one shown below
So basically, our idea is to use a blank repository as the baseline repository. Now, in our example we shall be using 2 repositories. One repository would be the default paint repository. The other would be the default bise1 repository. As the first step open up the paint repository in offline mode.
Then click on Merge. Specify a blank repository (create a repository which has no objects) as the original repository.
Once this is done, select the bise1 repository as the Modified Repository.
You would basically find the list of presentation catalogs, users, groups etc. In your case you would find either of the 2 descriptions below
Add to Current
Delete from Current
When it is Add to Current, you can choose your decision as Current or Modified(D). If you choose current, the presentation catalog would be added to the repository. Else it would be deleted from the repository. Choose Current as the decision for all the “Added to Current” descriptions.
If you have Delete from Current, you would have to decide whether to add the objects to the repository or delete them. Now, click on merge. This should merge both your repositories properly.
March 24, 2008 at 12:59 pm
[...] Posted by Venkatakrishnan J on November 22, 2007 Update: Based on the comments below, i have created a new blog post which would work in all the scenarios. You can find it here. [...]
March 28, 2008 at 11:19 am
[...] by Venkatakrishnan J on March 28, 2008 As i have said here, the supported way to combine objects in 2 repositories is to use a 2-way merge without Parent. But [...]
April 8, 2008 at 7:06 pm
Hi Venkatakrishnan,
The merge process works but unfortunately it is redemunt because we cann’t use all the functionality of decisions based on all the repository object Type. (there is no object for variables, initialization blocks, etc.)
In this case we have to manually delete the duplication after the merge, but it still the only way to mantain different version of an rpd file.
Thanks
April 8, 2008 at 9:13 pm
Hi,
If you try open paint.rpd in offline mode as the current repository, choose blank.rpd as the original repository, and then choose paintdummy.rpd ( a copy of paint.rpd) as the modified repository, the result I hope will be paint.rpd as paint.rpd = paintdummy.rpd. Actually it is not! The resulting repository
contains duplicated physical layers, duplicated BMM and duplicated
presentation layers!
Best regards,
Qinghe
April 13, 2008 at 9:40 pm
Well written article, and I agree entirely. Thank you for your fresh point of view. Keep up the good work.
April 18, 2008 at 5:30 am
[...] that we can use to automate the merging of 2 web catalogs. If you had looked at my blog entry here, i would have shown you an approach to merge 2 repositories. That concept can also be applied for [...]
April 18, 2008 at 10:15 pm
I agree with Qinghe. This method only works if I’m merging two completely different Presentation Layers. If I start with a “Global” presentation layer in my “Current” repository, and I’ve made some changes (let’s say I’ve added a couple of calculated columns), then when I go to merge my “Modified” global presentation layer into the “current” repository, the presentation layer is called “Global #1″, and all of the objects are duplicated.
So… Method #1 doesn’t show us what changes will be merged. Method 2 only works for merging the contents from two completely different repositories.
Is there a method that works every time in all circumstances?
April 22, 2008 at 10:19 am
Hi raghu,
A very interesting thought process indeed.
Very helpful.
Do you have any experience in configuring a waterfall report using bar stacked chart view in Answers?
If yes kindly shed some light on the useful approach.
Details:
I need to configure a waterfall report using bar stacked view , given the condition that the bar for the next measure should start seperately from the upper limit of the previous measure and not 0 on the x axis.
Any help in this regard is appreciated.