How to Solve :
Oracle database error code ORA-36389 – (XSAGPARTDEP01) Can not aggregate from PARTITION number into PARTITION number due to increasing sparsity along DIMENSION %J.
Oracle Database Error Code ORA-36389 Description :
(XSAGPARTDEP01) Can not aggregate from PARTITION number into PARTITION number due to increasing sparsity along DIMENSION %J.
Error 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 their partitions indicate the opposite.
How to Solve :
Modify the partition template add the specified dimension into the source composite, or removing it from the target composite.
Filed under: How to Solve, Oracle 10g, Oracle 11g, Oracle 9i, Oracle Error Codes Etiketler: ora - 36389, (XSAGPARTDEP01) Can not aggregate from PARTITION number into PARTITION number due to increasing sparsity along DIMENSION %J., 36389, about oracle ORA-36389 error, help ORA-36389 about, ORA-36389 error code, ORA-36389 problem, Oracle 9i 10g 11g, Oracle Database Server Error Messages, Oracle Error Codes, oracle number 36389 error code, oracle ORA-36389 example
No Comment Yet
No Comment Yet
Recent Entries
- Oracle database error code ORA-31604 – invalid string parameter “string” for object type string in function string
- Oracle database error code ORA-29961 – too many warnings occurred in the execution of ODCIIndex DDL routine
- Oracle database error code ORA-31603 – object “string” of type string not found in schema “string”
- Oracle database error code ORA-29960 – line string, string
- Oracle database error code ORA-31602 – parameter string value “string” in function string inconsistent with string
- Oracle database error code ORA-29964 – missing ADD or DROP keyword
- Oracle database error code ORA-31606 – XML context number does not match any previously allocated context
Search Oracle Error Codes and Descriptions:
Be The First To Comment
Similar Errors
Please Leave Your Comments Below