Categories
- All Categories
- 4 Oracle Analytics Videos
- 13.7K Oracle Analytics Forums
- 5.1K Oracle Analytics Idea Labs
- Oracle Analytics User Groups
- 57 Oracle Analytics News
- 33 Oracle Analytics Trainings
- 53 Oracle Analytics Data Visualizations
- 2 Oracle Analytics Career
- 2 Oracle Analytics Industry
- Find Partners
- For Partners
How to do RPD Incremental Refresh? Not Working? OBIEE 12c (12.2.1.2.0)
So I am trying to wrap my head around how an "incremental refresh" with patching in an RPD works and I cant quite seem to get it.
I went to my DEV environment and downloaded an offline copy of the RPD and named it
DEV_ORIG
I then made a copy of this and named it
DEV_WORK
So in total I have 2 files so far exactly the same.
I open DEV_WORK in my admin tool, begin development and complete what needs to be done. Keeping DEV_WORK open, I go and do a compare comparing
DEV_WORK to DEV_ORIG
My thinking is if I want to capture my exact development changes, I would just compare my modified RPD to the original RPD I downloaded.
I then create an XML patch file. I browse through the file and confirm that I see only my changes - So far so good.
Now I want to promote my changes from DEV_WORK into our QA environment. I download an offline copy of our QA RPD and name it
QA_ORIG
I re-open the RPD DEV_WORK and have it open. I go to Merge - Patch Repository Merge and select the following
Original Repository: QA_ORIG
Modified Repository: DEV_WORK
Patch: patch.xml
So what I thought would happen is the modified repository is my development repository, and the original master repository is basically my target enviroment, which is QA.
I would have thought OBIEE would have
1) Use the patch file to determine what needs to be migrated
2) The modified repository would have contained further details to supplement the patch file
3) Taken everything it found based on the patch file and merge it into the QA RPD.
So in the end, the QA RPD would have everything it originally had PLUS the modifications.
What I am seeing though is that it seems ANY differences between the DEV_WORK and QA_ORIG file are all put into the final patched file REGARDLESS if it was listed in the patch file or not. Therefore creating, modifying AND deleting objects.
I wasnt expecting ANY deletes, since everything in the development RPD was net new development, NO deletes.
So for example, in our QA file I found there was an extra role TESTER, and in our DEV enviroment we dont have this role.
So the final patched QA file, it now has all the development RPD changes, and it also deleted the TESTER role.
Which quite confuses me, as in my patch file - There is zero mention of anything related to the TESTER role.
I would have thought OBIEE would have only made any changes as per what is contained in the patch file, but it isnt.
So I guess few questions
- Am I missing something here? Did I not execute an incremental refresh properly?
- Based on what I am seeing, I am quite confused as to what the patch file does at all?
The patch file had ONLY the changes I made. So during the patching process, why would the RPD include any other changes outside of what is in the patch file?
I hope this makes sense, I just whirled myself around a bit in my mind and am confused.
Answers
-
Your process of testing this is flawed.
If you look at the help coming with your Admintool in the "Merge Repository Wizard" screen, you see that there are simple diagrams showing the process.
And the doc also shows (and says) that in this case the final "production" repository is now becoming like the development repository you modified.
In the case of OBIA RPD upgrade scenarios with patching it's a bit different:
In this case the patch is used to bring add to the modified RPD all the changes.
All in all, for RPD merging or patching, you better do your tests on a clean sandbox, starting with a simple (sample?) RPD. Not with your real RPD which has too many moving parts and a history already. Follow the doc (diagrams) processes and do your tests in that way, observing if you can reproduce the same behaviour as the doc and from there define what should to be need to be able to use this process in your current environment.
0 -
Couldn't agree more.
0 -
Thanks for the tip on reading through the "Help" section in the admin tool.
I actually read through most things and I think I see where I made a mistake.
I guess in my case, my DEV and QA RPD should have been the same, or equal. So my DEV_ORIG should equal my QA_ORIG basically and as you said I guess it got all confused (or I got confused) when trying to patch it as I did.
After reading through the help section I am just posting some stuff I found as well that I found helped me, as well as hopefully will help someone else if they bump into this thread below
The below is all taken from the Help section of the admin tool
0