Discussions
Categories
- 197K All Categories
- 2.5K Data
- 546 Big Data Appliance
- 1.9K Data Science
- 450.8K Databases
- 221.9K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 31 Multilingual Engine
- 552 MySQL Community Space
- 479 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3.1K ORDS, SODA & JSON in the Database
- 556 SQLcl
- 4K SQL Developer Data Modeler
- 187.2K SQL & PL/SQL
- 21.4K SQL Developer
- 296.3K Development
- 17 Developer Projects
- 139 Programming Languages
- 293K Development Tools
- 110 DevOps
- 3.1K QA/Testing
- 646.1K Java
- 28 Java Learning Subscription
- 37K Database Connectivity
- 158 Java Community Process
- 105 Java 25
- 22.1K Java APIs
- 138.2K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 19 Java Essentials
- 162 Java 8 Questions
- 86K Java Programming
- 81 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.3K Java SE
- 13.8K Java Security
- 205 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 468 LiveLabs
- 39 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.7K Other Languages
- 2.3K Chinese
- 175 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 233 Portuguese
Compiling an Analytic View, I get "ORA-18298: The REFERENCES clause ...

When compiling an Analytic View, I sometimes get the error "ORA-18298: The REFERENCES clause for the analytic view dimension " <attr dim name>" does not determine the lowest level of every hierarchy."
What does this mean?
What should I be looking for?
I suspect it has to do wit the quality of the data in the base AV table or that in the attribute dimension, but the error message is not giving me much to go on.
I cannot find a clear description of this error. Any help or recommendations are welcome.
Answers
-
Wow, apparently no one else can figure this one out either
-
I've had this today. The livesql tutorial stated: "The REFERENCES property identifies the key attribute in the attribute dimension that the fact table joins to. This should be the key attribute that is derived from the primary key of the dimension table."
So I also thought it was related to my data somehow. But, I've fixed it by changing my attribute dimension definition statement to always define the levels in order from children to parents. Even though I had placed the determines clause within the correct level, the fact that I'd specified the parent level before the child caused ORA-18298 to appear when defining the OAV. (And there were no errors during the dimension definition).
-
Just seeing this, but wow, this is awesome! Will try it.