Optimize BI server query — Oracle Analytics

Oracle Analytics Cloud and Server

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

Optimize BI server query

Received Response
11
Views
4
Comments
2844292
2844292 Rank 4 - Community Specialist

Hi All,

Am having performance issues in OBIEE, in order to optimize BI server query what are the best approach i need to follow to get optimal query .

Just mention what all i need to follow.

Thank you so much for your responses

Answers

  • Kamna
    Kamna Rank 3 - Community Apprentice

    Try the below approaches:

    1. Avoid complex derived measures/attributes in BMM layer of BI RPD, rather try to use physical mappings for logical calculations.

    2. De-generate Dimensions should be developed on top of the same fact alias with which join is established.

    3. Avoid complex/cartesian joins as it affects performance.

    After these, Check latency in the server query. If the delay is more, it means your RPD design/model needs to be revisited.

    Thanks,

    Kamna

  • 2844292 wrote:
    
    Just mention what all i need to follow.
    

    Hi,

    If you mean that you are looking for which parameter to change and what setting to do stop right now as this is probably the worst thing to do when you have "generic" not better identified performance problems ....

    First (second and third) activity is to find out what does mean "performance problem", based on what do you say it's a problem, what are you comparing with, why do you say that the problem is with OBIEE?

    Have a look at this https://www.youtube.com/watch?v=0W34l2O9GMo or read the slides here No Silver Bullets - OBIEE Performance in the Real World (Oracle Open … .

    Once you identified what the real issue is you can then ask how can you improve/solve/avoid that particular issue ... But "performance problems with OBIEE" doesn't mean absolutely nothing because of the number of involved processes in a single OBIEE analysis ...

  • [Deleted User]
    [Deleted User] Rank 2 - Community Beginner
    Kamna wrote:
    
    2. De-generate Dimensions should be developed on top of the same fact alias with which join is established.
    

    Degenerate dimensions don't need joined fact aliases and can be built directly on the same physical object as the logical fact table itself. Just sayin'.

  • Kamna
    Kamna Rank 3 - Community Apprentice

    Yeah, but I have seen folks developing degenerate Dims on top of the same fact but with different Dim - Fact alias and try to treat it as Degenerate Dim. This leads to self join and hampers performance