Problem maintaining cube

Question

Hi there,
I have a 2 dimensions with the following levels and hierarchies
CALENDAR_YEAR:
Levels:
YEAR
Hierarchy CALENDAR:
YEAR
LOCATION:
Levels:
ALL_LOCATIONS
CONTINENT
COUNTRY
Hierarchy PLACE:
ALL_LOCATIONS <--- CONTINENT <--- COUNTRY(default)
I created a star schema by sqlplus commandline using create table scrypts. The star schema consists of 2 dimensions as tables locations,*years* with primary keys NUMBER type ids and a fact table with primary key 2 foreign keys:
1) year pointing to primary key of years and
2) country pointing to primary key of locations.
This fact table has only 1 measure.
I already created the dimensions and the cube on awm.
I also did the mappings as they should be.
But, when i try to maintain the cube, an error occurs saying this:
An error has occurred on the server
Error class: Express Failure
Server error descriptions:
INI: Error creating a definition manager, Generic at TxsOqConnection::generic<BuildProcess>
INI: XOQ-01711: Aggregation path for hierarchies on a dimension "LOCATION" is inconsistent, Generic at TxsOqStdFormCommand::execute
at oracle.olapi.data.source.DataProvider.callGeneric(Unknown Source)
at oracle.olapi.data.source.DataProvider.callGeneric(Unknown Source)
at oracle.olapi.data.source.DataProvider.executeBuild(Unknown Source)
at oracle.olap.awm.wizard.awbuild.UBuildWizardHelper$1.construct(Unknown Source)
at oracle.olap.awm.ui.SwingWorker$2.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Any ideas on how to solve this?
Note: I don't have a Metalink and i don't need to have one!

Answer 1

i created the tables locations,years with the scrypts:
CREATE TABLE LOCATIONS
(COUNTRY_KEY varchar2(44) NOT NULL,
COUNTRY_NAME varchar2(54),
CONTINENT_KEY varchar2(20) NOT NULL,
CONTINENT_NAME varchar2(30),
COUNTRY_ID NUMBER,
CONTINENT_ID NUMBER NOT NULL,
PRIMARY KEY(COUNTRY_ID)
CREATE TABLE YEARS
(CALENDAR_YEAR_KEY NUMBER NOT NULL,
CALENDAR_YEAR_NAME varchar2(40),
CALENDAR_YEAR_TIME_SPAN NUMBER,
CALENDAR_YEAR_END_DATE DATE,
PRIMARY KEY(CALENDAR_YEAR_KEY)
I also created a name table as the fact table with this scrypt:
CREATE TABLE NAME
(SALES NUMBER,
YEAR NUMBER,
COUNTRY NUMBER,
PRIMARY KEY(YEAR,COUNTRY),
FOREIGN KEY (YEAR) REFERENCES YEARS(CALENDAR_YEAR_KEY),
FOREIGN KEY (COUNTRY) REFERENCES LOCATIONS(COUNTRY_ID)
Then i loaded my data (It is certain that they are loaded as i checked it). All these are done by sqlplus on user olaptrain(from tutorial).
After these i created on 11.1.0.7B AWM THE 2 DIMENSIONS: CALENDAR_YEAR,LOCATION
The mappings for them are:
CALENDAR_YEAR:
Member --> OLAPTRAIN.YEARS.CALENDAR_YEAR_KEY
Long Desc --> OLAPTRAIN.YEARS.CALENDAR_YEAR_NAME
Short Desc --> OLAPTRAIN.YEARS.CALENDAR_YEAR_NAME
time_span --> OLAPTRAIN.YEARS.CALENDAR_YEAR_TIME_SPAN
end_date --> OLAPTRAIN.YEARS.CALENDAR_YEAR_END_DATE
LOCATION:
ALL_LOCATIONS
Member --> 'ALL_LOCATIONS'
Long Desc --> 'All locations'
Short Desc --> 'All locations'
CONTINENT
Member --> OLAPTRAIN.LOCATIONS.CONTINENT_ID
Long Desc --> OLAPTRAIN.LOCATIONS.CONTINENT_NAME
Short Desc --> OLAPTRAIN.LOCATIONS.CONTINENT_NAME
COUNTRY
Member --> OLAPTRAIN.LOCATIONS.COUNTRY_ID
Long Desc --> OLAPTRAIN.LOCATIONS.COUNTRY_NAME
Short Desc --> OLAPTRAIN.LOCATIONS.COUNTRY_NAME
For the levels and hierarchies look on previous post. Also here are the mappings for the cube:
SALES
Sales --> OLAPTRAIN.NAME.SALES
DIMENSIONS
CALENDAR_YEAR
Year --> OLAPTRAIN.YEARS.CALENDAR_YEAR_KEY
join condition --> OLAPTRAIN.NAME.YEAR=OLAPTRAIN.YEARS.CALENDAR_YEAR_KEY
COUNTRY
ALL_LOCATIONS
CONTINENT
COUNTRY --> OLAPTRAIN.LOCATIONS.COUNTRY_ID
Join condition --> OLAPTRAIN.NAME.COUNTRY=OLAPTRAIN.LOCATIONS.COUNTRY_ID
When i press maintain cube the following error appears:
Error class: Express Failure
Server error descriptions:
INI: Error creating a definition manager, Generic at TxsOqConnection::generic<BuildProcess>
INI: XOQ-01711: Aggregation path for hierarchies on a dimension "LOCATION" is inconsistent, Generic at TxsOqStdFormCommand::execute
Could you help me solve this? I have been working on this for 3 days but still i cannot find a solution!
Edited by: spiros on 1 Ιουν 2009 4:46 πμ