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-02776: Value for request done signal exceeds maximum

1 Answers  

---

QSM-02081: mv log does not have all necessary columns

1 Answers  

---

ORA-12443: policy not applied to some tables in schema

1 Answers  

---

ORA-01599: failed to acquire rollback segment (string), cache space is full

1 Answers  

---

QSM-01110: a lossy join in MV, string, between tables, string, not found in query

1 Answers  

---

ORA-02307: cannot alter with REPLACE option a type that is not valid

1 Answers  

---

ORA-01924: role 'string' not granted or does not exist

1 Answers  

---

LSX-00283: referenced notation "~S" is not defined

1 Answers  

---

RMAN-06482: WARNING: proxy copy 'string' cannot be found on the storage medium

1 Answers  

---

DRG-10309: not enough job queue processes

1 Answers  

---

PLS-00232: nested packages not permitted

2 Answers  

---

ORA-03206: maximum file size of (string) blocks in AUTOEXTEND clause is out of range

2 Answers  

---