I need to merge my RPD content with the existing RPD in the OBIEE server.
You can't selectively deploy RPD contents - it's one great big binary object. So you need to first merge your new content into the existing RPD, and then deploy the whole thing.
There's plenty on the interwebs about RPD merging, not least in the product documentation itself : http://docs.oracle.com/cd/E28280_01/bi.1111/e10540/mngreposfiles.htm#BIEMG639
experiment on Dev instance first!!
I'll try only in the Dev instance Thanks
Can you please tell me what is minimum privilege(BI Admin?) needed to do RPD merging?
Merging's typically done offline, so you just need the RPD files and password to open them.
Thanks for the help rmoff . I found the solution.
Can a user with BI Author privilege login to the RPD and use the RPD Documentation utility? I tried to login but it is not working.
Can you please tell me the minimum privilege required to run the RPD Documentation utility?
Try to find a generic username/password for login to RPD. Mostly your admin team will provide you that. Also when you merge your rpd,
1)First select the database/connection pool
2)Find the related BMM and presentation objects and mark it
3)find the initialization blocks for your connection pool.
4)find the variables related to initialization blocks
5)Find the application roles mapped to your subject area
6)delete everything else from the source RPD
7)Delete whatever you gonna merge in target RPD
8)Merge it, Check the permissions of subject areas.
Note all these points while you do merging.
By all means, if this is a poor idea, let me know. I've always had great success with migrations between environments by migrating the entire .rpd between environments. Once development is complete, I copy the rpd from DEV and drop it into a staging location. Then I have a script run from the server that stops opmn services, makes a backup of the rpd, picks up the rpd from staging, overwrites the existing, and starts services back up.
Granted this only works if your configurations between environments are consistent, but I find it removes a lot of potential for human error.
Thanks Nathan.. But I wanted only one subject area that I've developed locally to be merged with the existing subject area in Dev.
Then from the DEV it is the question of how we are moving it to the other environment in which case your approach will help to do it faster.
If you have the script to overwrite the existing RPD attach that. It will be helpful. Thanks
Actually that is the best and easiest way to migrate RPD's. Just take a back up of higher environment RPD and deploy your Dev RPD. But it has the following disadvantages.
1)If somebody else working along with you in the same RPD , they will miss their changes.
2)There can be subject areas in UAT/Prod RPD which comes from different development environments. If you are working in an environment where you are the only developer and only one dev,uat,prod environment, it is easier to migrate entire RPD