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 : 22-09-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-19331 : Last argument to CREATE_DBURI operator must be a column
  • ora-01197 : thread string only contains one log
  • ora-28045 : SSL authentication between database and OID failed
  • ora-39782 : Direct path prepare is not allowed after another context loading the same table has ended
  • ora-31094 : incompatible SQL type "string" for attribute or element "string"
  • ora-15184 : ASMLIB error could not be determined [string] [string]
  • ora-01679 : database must be mounted EXCLUSIVE and not open to activate
  • ora-09933 : Deletion of old password file failed.
  • ora-33292 : (DBERR18) insufficient permissions to access analytic workspace string using the specified access mode.
  • ora-28274 : No ORACLE password attribute corresponding to user nickname exists.
  • ora-07460 : cannot set the RESOURCE_MANAGER_PLAN parameter
  • ora-24384 : Application context size is not initialized
  • ora-37021 : (XSMULTI02) Object workspace object is not acquired.
  • ora-36274 : (XSCGMDLAGG05) The operator used in this equation needs a weight variable.
  • ora-04080 : trigger 'string' does not exist
  • ora-01841 : (full) year must be between -4713 and +9999, and not be 0
  • ora-24413 : Invalid number of sessions specified
  • ora-26665 : STREAMS process string already exists
  • ora-30114 : error when processing from command line
  • ora-14178 : STORE IN (DEFAULT) clause is not supported for hash partitioned global indexes
  • ora-00022 : invalid session ID; access denied
  • ora-32311 : materialized view definition query selects an unsupported user-defined type
  • ora-06436 : ssaio: asynchronous I/O failed due to incorrect parameters.
  • ora-13011 : value is out of range
  • ora-29543 : Java command string not yet implemented
  • ora-00206 : error in writing (block string, # blocks string) of control file
  • ora-25225 : invalid value string, DEQUEUE_MODE should be REMOVE or BROWSE or LOCKED
  • ora-30043 : Invalid value 'string' specified for parameter 'Undo_Management'
  • ora-29399 : user string does not have privilege to switch to consumer group string
  • ora-06537 : OUT bind variable bound to an IN position
  • 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.