ORA-36260: (XSAGHIERPART00) Aggregating from partition %J to
partition %J over hierarchy workspace object creates an
increase in sparsity.
- 1 Answers
- 2392 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 |
NZE-28872: Invalid peer certificate format
ORA-30432: summary 'string.string' is in INVALID state
ORA-09755: osngpn: port allocation failure.
give full details of this ORA-12988: cannot drop column from table owned by SYS
SQL*Loader-00278: Incorrect file specification for parallel load.
LPX-00273: failed to initialize TCP/IP
PLS-01502: Constraint name and constraint status are non-ANSI.
SQL-02114: Invalid SQL Cursor usage: trying to CLOSE a CLOSEd cursor
ORA-14266: data type or length of an index subpartitioning column may not be changed
ORA-08008: another instance is mounted with USE_ROW_ENQUEUES = string
ORA-32056: invalid number of extents
ORA-36990: (XSRELGID07) %a workspace object The level relation %1p should be dimensioned by a level dimension.
Oracle Errors 
