Categories
- All Categories
- 15 Oracle Analytics Sharing Center
- 16 Oracle Analytics Lounge
- 216 Oracle Analytics News
- 43 Oracle Analytics Videos
- 15.7K Oracle Analytics Forums
- 6.1K Oracle Analytics Idea Labs
- Oracle Analytics User Groups
- 79 Oracle Analytics Trainings
- 15 Oracle Analytics Data Visualizations Challenge
- Find Partners
- For Partners
Parent / Child Hierarchy Issue
In Oracle Analytics Cloud 23c, I've created hierarchy table "product hierarchy" for dimension table "products". When I do the advanced consistency check, I receive the following error:
Error 38121: The parent-child hierarchy "Product Hierarchy" in "logicalTable:Territory Business Model.PRODUCTS" has invalid parent key and/or member key.
All of the member and ancestor keys in the hierarchy table are valid. I can't find any documentation for this error and I'm stuck on how to resolve it.
Can anyone offer any assistance?
Thank you
Best Answer
-
Steve,
Thank you for providing a more detailed explanation of the error. I exported the RPD from Oracle Analytics Cloud and opened it in the Model Administration Tool. The consistency check in this tool gave a much clearer error message. It specifically mentioned that the detail level did not have the parent key source assigned. Once I selected that value, the error cleared.
Ned
1
Answers
-
Hi @user7360840,
It would be helpful if you update your community profile with your name and your organization, at a minimum. It helps with creating a community.
Is your hierarchy based on relational tables? or other?
If you have not already, it may be good to review or re-review the following information.
I realize this may seem a bit basic to refer you to the documentation, but we don't have the table structure or the data model to review. There is tutorial, and there are scripts to create your tables, it may give you something for comparison.
Create and Manage Parent-Child Hierarchies
This topic provides information to help you understand and create a parent-child hierarchy.
Topics:
- About Parent-Child Hierarchies
- About Levels and Distances in Parent-Child Hierarchies
- About Parent-Child Relationship Tables
- Create Dimensions with Parent-Child Hierarchies
- Define Parent-Child Relationship Tables
- About Modeling Aggregates for Parent-Child Hierarchies
- About Storing Facts for Parent-Child Hierarchies
- About Aggregating Parent-Child Hierarchies
- Add the Parent-Child Relationship Table
- Maintain Parent-Child Hierarchies Based on Relational Tables
Other than the error that you mentioned, if you ignore the consistency check, is it actually working? If not, what is the behavior (only the parent level displaying?)
You may need to review all the way from physical to BMM layers.
Here is a prior, similar question; however, it does not include your specific error message.
Other comments welcomed.
0 -
Steve,
Thank you for the quick reply. I'm glad this is a very active group. I have a feeling I'll be posting a lot of questions. My name is Ned and I work for Pride Mobility Products in Pennsylvania. Our company is just starting to take advantage of this incredible tool. This is my first attempt at creating a hierarchy. I followed the instructions in the same topics that you listed, and I modified the template scripts to create and populate the hierarchy table. This is a simple table of our product lines, with column names "category" and "parent_category".
I am unable to determine if the hierarchy works, since I cannot deploy the semantic model because of this error. I can't find any documentation for this error number, so I don't know if the error means that the member and ancestor keys are defined incorrectly, or if the hierarchy table has invalid keys. I reviewed all of the setups, from the physical layer to the presentation layer, and don't see any obvious issues.
I had found that same question when I tried searching for this error message. I think it has more to do with errors caused by an upgrade.
I thank you in advance for any help you can offer. Do you know if there is any documentation about each consistency check error? I only found some brief points about common errors.
Ned
0 -
Hi Ned,
Welcome to the community and thanks for sharing!
The error does seem pretty generic. These are the only details, that I have for Error 38121, which you are already likely aware of from the UI.
Error Message:
Value-based dimension '@1%ls' has invalid parent key, member key, or both.
Cause:
The repository contains a definition error. Value-based dimension has invalid parent key, member key, or both.
Response:
Use the Administration Tool to correct the dimension hierarchy. If the problem persists, contact Oracle Corporation technical support for assistance.
So, as you can see, it could be multiple keys that are invalid.
I think it has more to do with errors caused by an upgrade.
Are you saying your model was working prior?
Feel free to log a service request to share the details about your tables, your model, and other pertinent, such as relationship table, member key, parent key, distance, leaf node, etc.
Someone from product support may need to recreate the issue. I believe Sample Sales data, has this example defined.
0 -
Hi @Ned Sweeney ,
Thank you for circling back and sharing your solution!
If you are able, you can mark your comment as "Answered" (the solution).
If not, a moderator will do that.
@Pravin Janardanam-Oracle ⬆️ - FYI only
0
