Hi,
I am new to Oracle OLAP and I noticed something in this tool. It
doesn't aggregate the right way.
For example, if there is a customer A in the Customer dimension and
customer A has 5 records in the fact with amounts 10,20,30,40,50. When
I build the cube, the cube doesn't aggregate the amounts for customer
A. It picks one of the amounts. I have to actually aggregate in the
view and pass it to the cube.
Is this how it is in Oracle OLAP? or am i missing somehting? Help me on
this basic fact/dimension design.
Thanks in advance.

Hi PP

I believe you are talking about the data loading of the leaf data into
an Analytic Workspace(AW), and not the aggregation of that data within
the AW?

The default behaviour of the tools like AW Manager is to assume the
source does not have duplicate rows. If there ARE duplicate rows then
the default behavior is to read the last row from your source into each
cell of the cube.

Depending on the business scenario this may or may not be what you want
ofcourse...

If (as it seems from your description below) you want the SUM of all the
rows for a specific cell to be read into that cell, then there are
several approaches, probably the easiest of which is to modify the
source (eg in a view over the table which includes, say, a SUM/GROUP BY,
or for your ETL to provide you with a table which has no duplicates).

Once your leaf data is in the AW ofcourse, you have enormous control
over aggregationn, as I'm sure you have discovered.

Feel free to contact me offline if you need a pointer to more information.

Kevin (@ Oracle)

p p wrote: