Oracle Business Intelligence Applications

Home› Oracle Analytics› Oracle Analytics Forums› More Solutions› Oracle Business Intelligence Applications

Categories

Welcome to the Oracle Analytics Community: Please complete your User Profile and upload your Profile Picture

Data Lineage objects removed from OBIA RPD

Received Response
4
Views
6
Comments
Charles M
Charles M Rank 6 - Analytics Lead
in Oracle Business Intelligence Applications

Hi All -

I recently completed the steps to configure data lineage for OBIA, per: https://docs.oracle.com/cd/E63231_01/doc/BIASA/GUID-8E9904B5-E498-40E7-88BB-6F36B309CF37.htm#BIASA24666.

The data lineage ETL completed successfully. However, I am encountering some errors when trying to view the dashboards. I opened an SR for this, and it looks look it is happening because the RPD has been "trimmed". I can see that the data lineage elements are no longer included in the current version of the RPD. And, I did confirm that these objects do appear in a very early version of the RPD:

pastedImage_3.png

We have made numerous changes/customizations since the RPD was trimmed. My question is how do we go about getting data lineage objects back into the current version of the RPD? MOS suggested that it may be possible to use the 'merge' method.

Please kindly offer any ideas on what is the best way to do this.

OBIA 11.1.1.10.1 (OBIEE 11.1.1.9.3) | DB/DW 12.1.0.2

Regards,

Charles

Answers

  • Gianni Ceresa
    Gianni Ceresa Mod

    Hi,

    Ignoring the OBIA context and just looking at your issue from an OBIEE perspective, what I don't like about merging is that it's a full merge: all you have in a RPD get into the other. So if in that older version you also have other things they will end up in the new RPD.

    If you don't have a RPD with just the data lineage part the merge sounds too risky to me (depends of course on what you did in the meantime and so what is the real delta between the current RPD and that old one).

    Personally I would go by a "do it by hand" option: it will take you 1-2h max and it will be done cleanly, copy/paste from a RPD to the other, layer by layer and checking the joins after the physical objects have been created.

  • Charles M
    Charles M Rank 6 - Analytics Lead

    Thanks Gianni. Based on your observation, I am inclined to use the "do it by hand" approach.

    (depends of course on what you did in the meantime and so what is the real delta between the current RPD and that old one)

    > It looks like the RPD was trimmed in the very beginning of the project. The delta is enormous ... basically, all of our customizations. There are like 70 versions of the RPD with incremental changes/developments since then.

    copy/paste from a RPD to the other, layer by layer and checking the joins after the physical objects have been created

    > Ok, I see. Do you recommend any particular order? For example, should I start with the Presentation layer and work back to the Physical?

    Regards,

    Charles

  • Gianni Ceresa
    Gianni Ceresa Mod

    The order is right to left, you need to have all the objects another layer will need.

    So you start with physical layer, copy/paste will give you the DB, connection pool, tables, columns etc. You need to check the physical joins (if I'm not wrong the foreign key joins are copied directly, complex join need to be recreated by hand, in your model you probably have mainly foreign key joins).

    Once physical looks identical between the 2 RPD you can copy/paste the whole business model, it's supposed to come directly with everything inside.

    And then final layer presentation.

    If you are a bit familiar to RPD work I really don't imagine this job taking more than 1-2h, even less if you are quick clicking around

  • Charles M
    Charles M Rank 6 - Analytics Lead

    Thanks very much, Gianni. I'll start working on this ...

    Regards,

    Charles

  • Gianni Ceresa
    Gianni Ceresa Mod

    Have fun

    And come back to give a feedback on how it went and close the thread (or continue it if issues happen)

  • Charles M
    Charles M Rank 6 - Analytics Lead

    Hi Gianni,

    Thanks for the guidance on this. I would have preferred to go manually with this. But, after looking over the RPD I wasn't sure I could get it right this time. So, I decided to experiment a bit.

    Here's what I did:

    I went for a 3-way full merge. Basically, I got the original RPD, then made a copy of it. I took out all of the presentation layer objects, from the copy (e.g. modified version), that we don't need/use (we use only Financials and Procurement & Spend at this time). I kept everything else in the BMM and physical layer. My thinking here was that the presentation layer was using the most space anyhow ... and, what extra stuff remained in the other layers wouldn't hurt to just keep in place for now.

    I used the original, modified, and current versions of the RPD for the merge. The downside for me with this process was that I still had to make a bunch of "decisions" on various objects. Mostly init blocks and application roles! There were several hundred of these ... maybe even more. I wasn't able to choose/highlight multiple items at once, so I ended up doing them one-at-a-time . I did take a while to finish that part. But, once I completed and uploaded the new RPD, I was able to view/use the data lineage dashboards.

    Not sure this is the best approach. But, it did server it's purpose, which was to test the data lineage dashboards. This is only a Dev instance ... so, we may be re-visiting this approach in the future.

    Regards,

    Charles