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 : 26-06-2017

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

  • ora-01632 : max # extents (string) reached in index string.string
  • ora-24325 : this OCI operation is not currently allowed
  • ora-29283 : invalid file operation
  • ora-33290 : (DBERR17) Analytic workspace string cannot be attached in the mode you requested because another user has it attached in an incompatible mode.
  • ora-29263 : HTTP protocol error
  • ora-13024 : polygon has less than three segments
  • ora-02293 : cannot validate (string.string) - check constraint violated
  • ora-06437 : ssaio: the asynchronous write was unable to write to the database file.
  • ora-37176 : argument string is not valid for the sparsity advisor
  • ora-06929 : CMX: error when sending ORACLE_SID
  • ora-31418 : source schema string does not exist
  • ora-03238 : unable to extend LOB segment string.string subpartition string by string in tablespace string
  • ora-01113 : file string needs media recovery
  • ora-14113 : partitioned table cannot have column with LOB datatype
  • ora-31600 : invalid input value string for parameter string in function string
  • ora-39028 : cannot restart job from string state
  • ora-19001 : Invalid storage option specified
  • ora-14002 : only one GLOBAL clause may be specified
  • ora-06735 : TLI Driver: client failed to close error conn
  • ora-01672 : control file may be missing files or have extra ones
  • ora-23440 : incorrect public template value
  • ora-19682 : file string not in block media recovery context
  • ora-02844 : Invalid value for the leave open flag
  • ora-32821 : subscriber queue and exception queue must have same payload type
  • ora-02084 : database name is missing a component
  • ora-14296 : Table block size mismatch in ALTER TABLE EXCHANGE [SUB]PARTITION
  • ora-01567 : dropping log string would leave less than 2 log files for instance string (thread string)
  • ora-15192 : invalid ASM disk header [string] [string] [string] [string] [string]
  • ora-39209 : Parameter string requires privileges.
  • ora-21610 : size [string] is invalid
  • 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.