ORA-33338: (DSSEXIST05) You cannot specify the EXPTEMP analytic workspace.

Cause : The command requires a non-temporary analytic workspace to operate on.

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

Specify an analytic workspace other than EXPTEMP.

update : 25-05-2017
ORA-33338

ORA-33338 - (DSSEXIST05) You cannot specify the EXPTEMP analytic workspace.
ORA-33338 - (DSSEXIST05) You cannot specify the EXPTEMP analytic workspace.

  • ora-13904 : The file has been dropped and recreated during the procedure call.
  • ora-32589 : unable to drop minimal supplemental logging
  • ora-32613 : not a MODEL cell
  • ora-06267 : NETNTT: bad state
  • ora-28502 : internal communication error on heterogeneous database link
  • ora-37111 : Unable to load the OLAP API sharable library: (string)
  • ora-00228 : length of alternate control file name exceeds maximum of string
  • ora-31226 : DBMS_LDAP: MOD_ARRAY size limit exceeded
  • ora-02166 : ARCHIVELOG and NOARCHIVELOG specified
  • ora-30372 : fine grain access policy conflicts with materialized view
  • ora-34346 : (MXDSS04) The string analytic workspace cannot be detached.
  • ora-15090 : handle string is not a valid descriptor
  • ora-32846 : Messaging Gateway agent cannot be started; status is string
  • ora-01973 : Missing change number
  • ora-08317 : sllfsk: Error seeking in file.
  • ora-09243 : smsget: error attaching to SGA
  • ora-29272 : initialization failed
  • ora-22293 : LOB already opened in the same transaction
  • ora-16816 : incorrect database role
  • ora-01341 : LogMiner out-of-memory
  • ora-01598 : rollback segment 'string' is not online
  • ora-40272 : apply rules prohibited for this model mode
  • ora-39148 : unable to import data into pre-existing queue table string. Table_exists_action of string being ignored for this table
  • ora-29961 : too many warnings occurred in the execution of ODCIIndex DDL routine
  • ora-36670 : (XSDPART08) workspace object is an INTEGER or NTEXT dimension, or contains an INTEGER or NTEXT dimension. INTEGER and NTEXT dimensions cannot be used as partition dimensions.
  • ora-00108 : failed to set up dispatcher to accept connection asynchronously
  • ora-32153 : Environment not specified
  • ora-30361 : unrecognized string type
  • ora-29349 : tablespace 'string' already exists
  • ora-32695 : HTI: Not enough memory
  • 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.