Oracle Analytics Cloud and Server

Home› Oracle Analytics› Oracle Analytics Forums› Oracle Analytics Cloud and Server› Oracle Analytics Cloud and Server

Categories

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

Essbase drill down: A descendent member of the expected level is returned.

Received Response
134
Views
8
Comments
jepva
jepva Rank 5 - Community Champion
edited Aug 13, 2024 6:17PM in Oracle Analytics Cloud and Server

Having an issue where OBIEE is not picking up the end of the hierarchy.  It will show a link for the last level even though there is no further drill-down available.  If the user clicks the link, they get the error:

[nQSError: 43113] Message returned from OBIS. [nQSError: 43119] Query Failed: [nQSError: 96002] Essbase Error: A descendent member of the expected level is returned. Please check member selection in the report. (HY000)

I have researched the error and seen that it can be caused by an attribute mixed with a hierarchy column.  However, it is just attribute columns in this report, not hierarchy.  The particular dimension was imported with defaults by OBIEE into the repository.  It is currently marked as Unbalanced in the physical and ragged in the logical.

Answers

  • [Deleted User]
    [Deleted User] Rank 2 - Community Beginner 
    jepva wrote:

It is currently marked as Unbalanced in the physical and ragged in the logical.

    And what is it actually? Ragged? Unbalanced? Both? Neither?

  • jepva
    jepva Rank 5 - Community Champion

    It's unbalanced "department" dimension.  In some areas it can go 8 levels deep, other areas only 3. 

  • [Deleted User]
    [Deleted User] Rank 2 - Community Beginner

    So why is it marked ragged in the BMM?

  • jepva
    jepva Rank 5 - Community Champion

    That's how it was imported by default into the OBIEE repository.  I unchecked ragged, but it doesn't seem to have any effect.  Still the same error.

  • jepva
    jepva Rank 5 - Community Champion

    I have checked the same repository between the 11g instance (getting the descendant error) and 12c.  Instead of the error in 12c, we get the "no results" screen which is correct, since that level would have no more data under it.  However, is there a way in OBIEE to not have the link for further drill-down once it has reached the end of the analysis?  Seems silly for it to still put a link just to have users go to a "no results" screen, which is confusing for end users.

  • [Deleted User]
    [Deleted User] Rank 2 - Community Beginner

    True but there isn't really a way to stop it since disabling the interaction always happens on an attribute (representing a level) and not on a member, sorry.

    But you can always open an enhncement request!

  • jepva
    jepva Rank 5 - Community Champion

    Yes i saw where you can limit drill down to a specific level, but with an unbalanced heirarchy this wouldn't work.  We will probably have to make modifications to the cube.

    Thanks

  • [Deleted User]
    [Deleted User] Rank 2 - Community Beginner

    ...or that. If you can do this even better than to wait for an enhancement request