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
- 3170 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 |
NNL-00855: Slowest rename processing time: string
DRG-12513: valid stop classes are: string
ORA-12715: invalid character set specified
ORA-29502: NAMED keyword required in CREATE JAVA RESOURCE
NNL-00514: Creates a new name with a default TTL
ORA-31037: Invalid XML attribute name string
ORA-37026: (XSMLTRESYNC01) Object workspace object cannot be resynced without dimension workspace object.
ORA-32319: Cannot use direct loader log to FAST REFRESH materialized view "string"."string"
DRG-10573: index string is obsolete
ORA-00822: MMAN process terminated with error
ORA-30177: invalid flag used in a format specification
PCC-02402: Pro*C option OBJECTS=YES is required when using the object cache
Oracle Errors 
