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-07-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-38736 : Wrong thread number string in flashback log file header.
  • ora-40303 : invalid prior probability specification
  • ora-31615 : routine string received this error: string
  • ora-33425 : (EIFMAKEF15) CAUTION: Exporting NTEXT objects using string for the EIF file character set can cause loss of data. To preserve all NTEXT data, export using the UTF8 character set for the EIF file.
  • ora-14056 : partition number string: sum of PCTUSED and PCTFREE may not exceed 100
  • ora-13780 : SQL statement does not exist.
  • ora-26752 : Unsupported LCR received for "string"."string"
  • ora-14122 : only one REVERSE or NOREVERSE clause may be specified
  • ora-09205 : sfqio: error reading or writing to disk
  • ora-00227 : corrupt block detected in control file: (block string, # blocks string)
  • ora-06814 : TLI Driver: the SPX device file could not be opened
  • ora-16778 : redo transport error for one or more databases
  • ora-26761 : Standby Redo Logs not available for real time mining
  • ora-02830 : Segment could not be split - no free segments available
  • ora-14150 : missing SUBPARTITION keyword
  • ora-14175 : a subpartition maintenance operation may not be combined with other operations
  • ora-24909 : call in progress. Current operation cancelled
  • ora-30753 : column or table string is substitutable
  • ora-13608 : The task or object name string is invalid.
  • ora-32341 : The EXPLAIN_MVIEW facility failed to explain the materialized view "string"."string"
  • ora-39005 : inconsistent arguments
  • ora-01936 : cannot specify owner when creating users or roles
  • ora-19813 : cannot have unavailable file string in DB_RECOVERY_FILE_DEST
  • ora-39212 : installation error: XSL stylesheets not loaded correctly
  • ora-19380 : invalid plan filter
  • ora-16241 : Waiting for gap logfile (thread# string, sequence# string)
  • ora-30189 : reserved for future use
  • ora-27548 : Unable to unprepare IPC buffer
  • ora-15037 : disk 'string' is smaller than mimimum of string MBs
  • ora-39020 : invalid mode type string
  • 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.