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 : 24-06-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-12064 : invalid refresh sequence number: string
  • ora-13044 : the specified tile size is smaller than the tolerance
  • ora-29657 : class defined in EXTERNAL NAME clause is used in another subtype
  • ora-09717 : osnsui: maximum number of user interrupt handlers exceeded.
  • ora-01688 : unable to extend table string.string partition string by string in tablespace string
  • ora-13420 : the SRID of the geometry parameter was not null
  • ora-14453 : attempt to use a LOB of a temporary table, whose data has alreadybeen purged
  • ora-01270 : %s operation is not allowed if STANDBY_PRESERVES_NAMES is true
  • ora-01508 : cannot create database; error in file 'string' at line string
  • ora-13367 : wrong orientation for interior/exterior rings
  • ora-31161 : element or attribute "string" cannot be stored out of line
  • ora-06756 : TLI Driver: cannot open oratab
  • ora-14289 : cannot make local index partition of Composite Range partitioned table unusable
  • ora-37040 : (XSACQUIRE_DEP_LOCKED) Composite, concat, dimension map, or internal partition workspace object is locked by another user.
  • ora-16225 : Missing LogMiner session name for Streams
  • ora-16544 : modifying DG_BROKER_START requires SID='*' qualifier
  • ora-25255 : incorrect subscription string string
  • ora-27068 : I/O buffer is not aligned properly
  • ora-28511 : lost RPC connection to heterogeneous remote agent using SID=string
  • ora-16568 : cannot set property string
  • ora-26695 : error on call to string: return code string
  • ora-27543 : Failed to cancel outstanding IPC request
  • ora-22919 : dangling REF error or lock object failed for no wait request
  • ora-26763 : invalid file type "string"
  • ora-04055 : Aborted: "string" formed a non-REF mutually-dependent cycle with "string".
  • ora-19109 : RETURNING keyword expected
  • ora-00474 : SMON process terminated with error
  • ora-06522 : %s
  • ora-16108 : database is no longer a standby database
  • ora-16135 : Invalid LOG_ARCHIVE_CONFIG modification while in protected mode
  • 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.