Interested to Buy Any Domain ? << Click Here >> for more details...
ORA-36260: (XSAGHIERPART00) Aggregating from partition %J to
partition %J over hierarchy workspace object creates an
increase in sparsity.
- 1 Answers
- 3258 Views
- I also Faced
- E-Mail Answers
Answer / guest
Cause: In the partition creation / aggmap creation a
situation developed such that when aggregating over a
particular dimension of the aggmap a partition boundery was
crossed such that the sparsity of the target partition
included dimensions that were not in the sparisty of the
source partition. Since the process of aggregation always
densifies rather than sparsifying this is an extremely
suboptimal design and it is not supported by the aggregate
system.
Action: Set up your partitioning such that for any partition
boundary the source and target partitions of the aggregation
will always move towards denser partitions. For any child
(c) and any parent (p) where (c) and (p) are in different
partitions it must be the case that the parent partition
contains no dimension in the composite that the child
partition does not contain in it's composite.
Please add more information about this Error
| Is This Answer Correct ? | 0 Yes | 0 No |
ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
ORA-38764: flashback not started; datafile string enabled threads are different
ORA-01324: cannot add file string due to DB_ID mismatch
ORA-38201: assert if pin during flush
ORA-10560: block type 'string'
DRG-12012: Proxy authentication failed - retry?
ORA-22316: input type is not a collection type
ORA-31102: Already locked in exclusive mode. Cannot add lock.
ORA-25194: invalid COMPRESS prefix length value
ORA-12519: TNS:no appropriate service handler found
ORA-15060: template "string" does not exist
ORA-12852: PARALLEL_MIN_SERVERS must be less than PROCESSES, string
Oracle Errors 
