Excessive time when maintaining cube

Question

Hi there,
I have a star schema with:
a) 2 dimensions:
year with hierarchy : CALENDAR_YEAR ------------>all_years
location with hierarchy : COUNTRY -------------> CONTINENT -----------> ALL_COUNTRIES
b) 6 partitioned cubes (uncompressed)
Each cube contains measures with diffirent data types. In particular, each measure may have 1 of the following 3 data types:
varchar2 ------------> with aggregation maximum
int or dec ------------> with aggregation SUM (cube's aggregation)
date ------------> with aggregation Non additive
When i execute maintain cube (for 1 of the cubes i have) I leave my pc for 2 hours to load the data and after that it doesn't end but it continues to load data. So, data loading is never done. I have been on my pc for a week trying to solve the problem but nothing has changed. What could the problem be?
Notes:
(A)
I checked vls parameters and tha data's format and they are both compatible. See for yourself:
SQL> select value from V$NLS_Parameters;
VALUE
AMERICAN
AMERICA
$
AMERICA
GREGORIAN
DD-MON-RR
AMERICAN
WE8MSWIN1252
BINARY
HH.MI.SSXFF AM
VALUE
DD-MON-RR HH.MI.SSXFF AM
HH.MI.SSXFF AM TZR
DD-MON-RR HH.MI.SSXFF AM TZR
$
AL16UTF16
BINARY
BYTE
FALSE
19 rows selected.
(B)
Mappings are also ok. I checked them. As for each hierarchy, I gave on each attribute, values that prevent data conflict. I think `all_years` and `all_countries` levels are also ok as they include everything.
(C)
My computer is an Intel Pentiium 4 with 2x 512mb ram. I am running oracle 11g home on windows xp professional service pack 2.
Thanks in Advance

Answer 1

I need uncompressed cubes because as i said i have non-numeric data types in my data. I have dates, nums and varchar2.
Anyway.
i don't understand what you mean by saying dimensional members, but i suppose you are refering to the levels and the hierarchy of each dimension. I have already included that on my previous post. Check it! If you mean something else inform me!
As for the amount of data:
YEAR:2 RECORDS (1990 and 1991)
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)
LOCATION : 256 RECORDS (It also contains a CONTINENT_ID whose value range from 350 to 362 REPRESENTING all oceans, continents and the world. COUNTRY_ID ranges from 1 to 253)
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)
MEASURES : 498 RECORDS (249 records for 1990 and 249 records for 1991)
CREATE TABLE MEASURES
(GEOGRAPHY_total_area DEC(11,1),
GEOGRAPHY_local_area DEC(11,1),
GEOGRAPHY_arable_land DEC(5,4),
GEOGRAPHY_permanent_crops DEC(5,4),
. (various other measures)
MEASURES_YEAR NUMBER,
MEASURES_COUNTRY NUMBER,
PRIMARY KEY(MEASURES_YEAR,MEASURES_COUNTRY),
FOREIGN KEY (MEASURES_YEAR) REFERENCES YEARS(CALENDAR_YEAR_KEY),
FOREIGN KEY (MEASURES_COUNTRY) REFERENCES LOCATIONS(COUNTRY_ID)
TOTALLY : 268 measures
But to make data loading easier i created 6 cubes on Analytical Workspace Manager each one containing:
GEOGRAPHY : 51 attributes
PEOPLE : 24 attributes
ECONOMY : 40 attributes
GOVERNMENT : 113 attributes
COMMUNICATION : 28 attributes
DEFENSE FORCES : 11 attributes
(If i made any number counting error, forgive me. I only wanted to show you that there are many measures.)
So, Is there anything I can do to solve the problem?