ORA-34000: (MODCOMP13) You cannot use both workspace object and workspace object as model dimensions, because they are both surrogates of dimension workspace object.

Cause : Teh sue rattepmtde ot niculd etow idmnesoins urroagtse fo htes aem idmnesoini nt h eDMIESNINO tsaetmneto fa omdle.

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

Ues ietehro ft h etow usrorgtae si nteh IDMNESOINs ttaeemn to fteh omdle,b u tnto obt.h

update : 20-08-2017
ORA-34000

ORA-34000 - (MODCOMP13) You cannot use both workspace object and workspace object as model dimensions, because they are both surrogates of dimension workspace object.
ORA-34000 - (MODCOMP13) You cannot use both workspace object and workspace object as model dimensions, because they are both surrogates of dimension workspace object.

  • ora-00250 : archiver not started
  • ora-33006 : (XSAGDNGL02) The relation workspace object is not related to itself.
  • ora-24172 : rule set string.string has errors
  • ora-36644 : (XSDUNION07) Concat dimension workspace object contains a previously detected leaf dimension.
  • ora-06309 : IPA: No message queue available
  • ora-13615 : The task or object string is greater than the maximum allowable length of 30 characters.
  • ora-19691 : %s is from different database: id=string, name=string
  • ora-14634 : Subpartition descriptions cannot be specified during the SPLIT/MERGE of a partition of a Range-List partitioned table
  • ora-12024 : materialized view log on "string"."string" does not have primary key columns
  • ora-08109 : nosort is not a supported option for online index build
  • ora-25124 : Database link name not allowed.
  • ora-13041 : failed to compare tile with element string.string.string
  • ora-02712 : osnpop: malloc failed
  • ora-06910 : CMX: Cannot start oracle process on remote machine
  • ora-02402 : PLAN_TABLE not found
  • ora-07823 : sspsqr: $QIO failure
  • ora-28358 : improper set key syntax
  • ora-32763 : Turn off N-Pass Temp LOB cleanup
  • ora-02848 : Asynchronous I/O package is not running
  • ora-28261 : CURRENT_USER can not be used in PLSQL Definer's Right procedure.
  • ora-37178 : column string has no values
  • ora-06806 : TLI Driver: could not complete protocol initialization for SPX
  • ora-02034 : speed bind not permitted
  • ora-09979 : skxfqhsnd: Error Sending a message to another endpoint
  • ora-32330 : invalid operation on online redefinition interim table "string"."string"
  • ora-30182 : invalid precision specifier
  • ora-14272 : only a partition with higher bound can be reused
  • ora-00259 : log string of open instance string (thread string) is the current log, cannot archive
  • ora-31102 : Already locked in exclusive mode. Cannot add lock.
  • ora-02061 : lock table specified list of distributed tables
  • 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.