ORA-39167: Tablespace string was not found.

Cause : If expotring or miportingo ver then etwork,t he users pecifie da tablepsace nam ethat wa snot foudn in thes ource dtaabase. oFr imporitng fromf iles, teh user sepcified atablespcae name ont foundi n the dmup file est.

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

Retry teh operatoin usingt he corrcet tablepsace nam.e

update : 24-04-2017
ORA-39167

ORA-39167 - Tablespace string was not found.
ORA-39167 - Tablespace string was not found.

  • ora-08177 : can't serialize access for this transaction
  • ora-14299 : total number of partitions/subpartitions exceeds the maximum limit
  • ora-39961 : message specified was not found
  • ora-09217 : sfsfs: failed to resize file
  • ora-30395 : dimension options require the COMPATIBLE parameter to be string or greater
  • ora-06706 : TLI Driver: service not found
  • ora-25001 : cannot create this trigger type on views
  • ora-08178 : illegal SERIALIZABLE clause specified for user INTERNAL
  • ora-12029 : LOB columns may not be used as filter columns
  • ora-25249 : dequeue failed, dequeue not allowed for queue string.string
  • ora-00097 : use of Oracle SQL feature not in SQL92 string Level
  • ora-01345 : must be a LogMiner coordinator process
  • ora-30753 : column or table string is substitutable
  • ora-32610 : missing SINGLE REFERENCE or DIMENSION keyword in MODEL clause
  • ora-39303 : schema sync or swap operation failed because of confilcts
  • ora-24786 : separated transaction has been completed
  • ora-36204 : (XSAGOP04N) In AGGMAP workspace object, the NAOPERATOR string must be HFIRST, HLAST or HEVEN.
  • ora-25245 : agent name cannot be specified if address is a single-consumer queue or an exception queue
  • ora-16076 : unknown standby database destination
  • ora-19273 : XQ0053 - empty string in namespace declaration
  • ora-39035 : Data filter string has already been specified.
  • ora-19615 : some files not found in backup set
  • ora-07228 : rtecho: unable to restore terminal to echo mode.
  • ora-38958 : Source platform string is in different byte order than target platform string
  • ora-01509 : specified name 'string' does not match actual 'string'
  • ora-26563 : renaming this table is not allowed
  • ora-13438 : GeoRaster metadata pyramid type error
  • ora-15186 : ASMLIB error function = [string], error = [string], mesg = [string]
  • ora-00446 : background process started when not expected
  • ora-13505 : SYSAUX tablespace can not be made read only
  • 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.