ORA-36389: (XSAGPARTDEP01) Can not aggregate from PARTITION
number into PARTITION number due to increasing sparsity
along DIMENSION %J.

Answer Posted / guest

Cause: The user is attempting to use partitions as a means
of sparsity control, however they have set up their
partitions in a manner that simply makes no sense. It is a
simple fact that during aggregation data becomes more dense,
not less dense, and yet thier partitions indicate the opposite.

Action: Modify the partition template add the specified
dimension into the source composite, or removing it from the
target composite.

Please add more information about this Error

Is This Answer Correct ?    0 Yes 0 No



Post New Answer       View All Answers


Please Help Members By Posting Answers For Below Questions

ORA-26094: stream format error: input column overflow

2254


if the lengths of two wires are same and the area of cross sections is 4:7 then what will be the ratio of current passing through these wires

2234


ORA-26095: unprocessed stream data exists

2805


ORA-26084: direct path context already finished

1487


ORA-26029: index string.string partition string initially in unusable state

1715






ORA-26082: load of overlapping segments on table string.string is not allowed

1378


ORA-07497: sdpri: cannot create trace file 'string'; errno = string.

2317


ORA-26079: file "string" is not part of table string.string

1524


ORA-26027: unique index string.string partition string initially in unusable state

6161


IMP-00070: Lob definitions in dump file are inconsistent with database.

1290


ORA-26076: cannot set or reset value after direct path structure is allocated

1476


In my project I am using star schema and only diimension tables are loaded and not fact tables any one can help me why it is happening? Plase guide me.

2329


NZE-28890: Entrust Login Failed

1410


ORA-26028: index string.string initially in unusable state

3403


RMAN-05017: no copy of datafile number found to recover

1889