nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Oracle Communities

Oracle Analytics and AI

Child Item

3 Way RPD Merge in 11g and 12c

2845107

Hi Experts,

I am a trying to do a 3 way rpd merge

Blank RPD

Modified RPD

Current RPD

While doing the merge in the "define merge strategy" window I got some huge conflicts around 5000 thousands.

So when I am trying to take decision on each conflict its taking lot of time. So Oracle recommends that when we have huge conflict objects we need to save the conflicts into CSV file and manually make entries on the decision by following the decision made earlier in define merge strategy window.

But in my case when I saved the file on the desktop and opened it I can not see the whole list of conflicts in the file and only can see what all I have taken decisions on the merge strategy window. I am using OBIEE 12.2.1.0.0 client to do this.Did any one else faced this issue of not getting whole list of conflicts in the file.

So for know I am trying to take decisions on the merge strategy window itself and saving the file on desktop. And next day starting again a fresh merge and using this file to continue from the point from where I have saved. Is there any other approach for this as this is taking lot of time.

In 11g also I have tried the same process.

And here I could save file on the desktop and when opened I can see the whole list of conflicts in the file along with the decisions taken on the merge strategy window. And next I have made decisions on the entire conflicts in the CSV file and when trying to upload the file. There is no change in the list of conflicts shown on the define merge strategy window.

Can any one please suggest me how to deal with this huge conflicts in 11g and 12c if you have encountered in your projects,

Thanks

Find more posts tagged with

Accepted answers

All comments

rmoff

What are the RPDs that you're actually trying to merge? Is it a genuine three-way merge, or just two RPDs with content that you want to merge together?

2845107

The modified RPD is the 7963 BI apps RPD and the Current RPD is the 11.1.1.10.1 BI apps RPD.

Thanks

2845107

Thanks for the reply Rmoff

Its a genuine 3 way merge

We are moving to new BI apps version. So we need to move our custom and out of the box custom objects to the new BI apps.

So while merging, this custom and out of the box custom will be moved and when we have same objects in both RPD but in those objects there might be changes to datatypes, description and etc then merge strategy is conflicting them asking which one to take whether current or modified.

In our case they are huge since these are BI Apps RPDs.

rmoff

I'm not so familiar with BI Apps. You might want to try

Is what you're doing a supported upgrade route?

For a three-way merge of this type you'd usually use a common parent, rather than blank, as the original RPD, so that the admin tool can establish correct lineage and commonalities.

2845107

Ya will post the same question in BI Apps forum too.

Just tried checking here.

we don't have a common parent so used blank RPD and oracle document also says using blank if you don't have a common RPD.

Srikanth Mandadi

Did you try this?

Current RPD - BI Apps 11.1.1.10.1

Original RPD - BI Apps 7963 OOTB

Modified RPD - BI Apps 7963 Customized

Regards,

Srikanth

2845107

Thanks for the reply Srikanth

We dont have the 7963 OOTB RPD. And oracle also suggests to use a blank RPD for merge.