My Oracle Support Banner

OBIEE 11g: A Three-Way Merge with the OBIA SLA Patch Results in an Inconsistent RPD (Doc ID 2147208.1)

Last updated on MAY 06, 2020

Applies to:

Business Intelligence Suite Enterprise Edition - Version and later
Business Intelligence Applications Consumer - Version and later
Information in this document applies to any platform.


The OBIA Financial Analytics SLA patch is applied as per OBIA 11g: How to find SLA Patch For Financial Analytics (Doc ID 1620355.1).  The patch instructions advises to "Do a three way merge of the customer RPD and the OracleBIApps.rpd provided in the patch".

The 3-way merge is done as below, but the Merged RPD contains only the content from the SLA Patch RPD:-
     Current = Custom/Production RPD (customized from the OOTB OBIA RPD)
     Modified = SLA Patch RPD
     Original = OOTB OBIA RPD

The 3-way merge is re-done as below (as advised by the OBIA Development Team):-
     Current = SLA Patch RPD
     Modified = Custom/Production RPD (customized from the OOTB OBIA RPD)
     Original = OOTB OBIA RPD

In the merge strategy dialogue:
   1. Choose the option "Modified" for all the rows, except for objects "Added to Current".
   2. Choose the option "Current" for objects "Added to Current".

Now the Merged RPD contains the content from both the Production RPD and the SLA Patch RPD, but the Global Consistency Check throws over 150 errors that are all related to logical tables that are not joined with other logical tables.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.