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

ORA-24142: invalid ruleset name

1 Answers  

---

ORA-12094: error during online redefinition

1 Answers  

---

ORA-12923: tablespace string is in force logging mode

1 Answers  

---

ORA-19653: cannot switch to older file incarnation

1 Answers  

---

ORA-01138: database must either be open in this instance or not at all

2 Answers  

---

TNS-01052: The command completed successfully

1 Answers  

---

PLS-00536: Navigation through REF variables is not supported in PL/SQL.

1 Answers  

---

ORA-15069: ASM file 'string' not accessible; timed out waiting for lock

1 Answers  

---

DRG-11867: Method Not Suited For Automatic Redirection

1 Answers  

---

PLS-00221: 'string' is not a procedure or is undefined

1 Answers  

---

ORA-26017: global indexes not allowed for direct path load of table partition string

1 Answers  

---

ORA-13331: invalid LRS segment

1 Answers  

---