ORA-34001: (MODCOMP14) Concat leaf dimension workspace object already is used in a DIMENSION statement, either explicitly or as a leaf of another concat dimension.

Cause : Eihtert woc onact idmesniosn wihchs haer ac omomn elafd imnesino, ro ac onact nad noe fo ist laeve swhree obths peicfide i nth eDIEMNSOIN tsatmeen(ts).

Action - How to fix it : DBA Scripts :: www.high-oracle.com/scripts

Don ots peicfyo velrapipngc onact idmesniosn, ro ayn laeve sofs peicfide cnoca tdiemnsoins.

update : 28-05-2017
ORA-34001

ORA-34001 - (MODCOMP14) Concat leaf dimension workspace object already is used in a DIMENSION statement, either explicitly or as a leaf of another concat dimension.
ORA-34001 - (MODCOMP14) Concat leaf dimension workspace object already is used in a DIMENSION statement, either explicitly or as a leaf of another concat dimension.

  • ora-32304 : materialized views with user-defined types cannot use prebuilt table
  • ora-23338 : priority or value already in priority group string
  • ora-19667 : cannot do incremental restore of datafile string
  • ora-01609 : log string is the current log for thread string - cannot drop members
  • ora-22294 : cannot update a LOB opened in read-only mode
  • ora-13529 : Error occurred when flushing AWR table group
  • ora-40219 : apply result table string is incompatible with current operation
  • ora-12429 : label list range exceeded
  • ora-31472 : Importing Change Data Capture version string.string is too new
  • ora-32344 : cannot create a secondary materialized view with synonym as base table
  • ora-02253 : constraint specification not allowed here
  • ora-38908 : internal error occurred during DML Error Logging
  • ora-38408 : The ADT "string" does not exist in the current schema.
  • ora-13033 : Invalid data in the SDO_ELEM_INFO_ARRAY in SDO_GEOMETRY object
  • ora-01968 : Only specify RESETLOGS or NORESETLOGS once
  • ora-12725 : unmatched parentheses in regular expression
  • ora-09273 : szrfc: error verifying role name
  • ora-25213 : message with specified RELATIVE_MSGID has been dequeued
  • ora-25405 : transaction status unknown
  • ora-30455 : summary contains VARIANCE without corresponding SUM & COUNT
  • ora-00119 : invalid specification for system parameter string
  • ora-30478 : Specified dimension does not exist
  • ora-07534 : scginq: $getlki unexpected return on lockid string
  • ora-04020 : deadlock detected while trying to lock object stringstringstringstringstring
  • ora-28275 : Multiple mappings for user nickname to LDAP distinguished name exist.
  • ora-16061 : Log file status has changed
  • ora-25195 : invalid option for index on an index-organized table
  • ora-02200 : WITH GRANT OPTION not allowed for PUBLIC
  • ora-30120 : 'string' is not a legal oracle number for 'string'
  • ora-22877 : invalid option specified for a HASH partition or subpartition of a LOB column
  • Oracle Database Error Messages



    Oracle Database High Availability Any organization evaluating a database solution for enterprise data must also evaluate the High Availability (HA) capabilities of the database. Data is one of the most critical business assets of an organization. If this data is not available and/or not protected, companies may stand to lose millions of dollars in business downtime as well as negative publicity. Building a highly available data infrastructure is critical to the success of all organizations in today's fast moving economy.

    Well, the reason for above error is that i have taken the above script from a 11g database and running it on 10g database. 11g has bring some changes in password management. Below code is executed on 11g and user created successfully, which is expected result.