ORA-33998: (MODCOMP12) You cannot use both workspace object and workspace object as model dimensions, because workspace object is a surrogate of workspace object.

Cause : The usre attemtped to niclude obth a dmiensiona nd itss urrogaet in th eDIMENSOIN statmeent ofa model.

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

Use eihter thed imensino or th esurrogtae in teh DIMENISON staetment o fthe moedl, butn ot bot.h

update : 24-08-2017
ORA-33998

ORA-33998 - (MODCOMP12) You cannot use both workspace object and workspace object as model dimensions, because workspace object is a surrogate of workspace object.
ORA-33998 - (MODCOMP12) You cannot use both workspace object and workspace object as model dimensions, because workspace object is a surrogate of workspace object.

  • ora-00437 : ORACLE feature is not licensed. Contact Oracle Corp. for assistance
  • ora-22931 : MOVE of nested table to a different tablespace not supported
  • ora-25143 : default storage clause is not compatible with allocation policy
  • ora-16719 : unable to query V$ARCHIVE_DEST fixed view
  • ora-30935 : XML maxoccurs value (string) exceeded
  • ora-16065 : remote archival disabled at standby destination
  • ora-12821 : invalid value for INSTANCES
  • ora-23357 : the propagator does not exist
  • ora-09758 : osnipn: could not check port in name server.
  • ora-13014 : a topology identifier outside the range of 1 to 8 was specified
  • ora-06510 : PL/SQL: unhandled user-defined exception
  • ora-12071 : definition query of "string"."string" is invalid for offline instantiation
  • ora-00832 : no streams pool created and cannot automatically create one
  • ora-24422 : error occurred while trying to destroy the Session Pool
  • ora-30683 : failure establishing connection to debugger
  • ora-32833 : failure string trying to release administration lock
  • ora-07637 : smsdbp: buffer protect option not specified when sga created
  • ora-29353 : The transportable list is too long.
  • ora-29370 : pending area is already active
  • ora-29879 : cannot create multiple domain indexes on a column list using same indextype
  • ora-07208 : sfwfb: failed to flush dirty buffers to disk.
  • ora-09987 : unable to attach to SGA in READ-ONLY mode
  • ora-06106 : NETTCP: socket creation failure
  • ora-12025 : materialized view log on "string"."string" already has primary keys
  • ora-13514 : Metric Capture too close to last capture, group string
  • ora-00349 : failure obtaining block size for 'string'
  • ora-21607 : memory cartridge service handle not initialized
  • ora-01351 : tablespace given for Logminer dictionary does not exist
  • ora-38501 : sub-query not allowed in the expression
  • ora-01160 : file is not a 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.