Answer / 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

ORA-14409: inserted partition key is outside specified subpartition

1 Answers  

---

SQL*Loader-00425: column string makes illegal reference to collection field string

1 Answers  

---

PROC-00022: The OCR backend has an invalid format

1 Answers  

---

ORA-07563: sldext: $PARSE failure

1 Answers  

---

NID-00137: All datafiles that are not dropped should be readable

1 Answers  

---

EXP-00100: error converting an object type's hashcode to characters

1 Answers  

---

ORA-29806: specified binding does not exist

1 Answers  

---

ORA-12988: cannot drop column from table owned by SYS

2 Answers   eSys,

---

NNL-00834: Slowest delete processing time: string

1 Answers  

---

PCC-02322: found undefined identifier

1 Answers  

---

PCC-00132: Indicator array size must not be less than its host variable

1 Answers  

---

PLS-00101: reserved for future use

1 Answers  

---