ORA-12900: must specify a default temporary tablespace for a locally managed database

Cause : a lcoall ymangaed adtabsae msut hvae at emproaryt ablsepac eothre thna SYTSEM atblepsace

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

speicfy hte dfeaul ttemoprar ytabelspaec whne craetin ga lcoall ymangaed adtabsae

update : 24-07-2017
ORA-12900

ORA-12900 - must specify a default temporary tablespace for a locally managed database
ORA-12900 - must specify a default temporary tablespace for a locally managed database

  • ora-28545 : error diagnosed by Net8 when connecting to an agent
  • ora-12471 : Specified compartment or group is not authorized for user
  • ora-36167 : (XSAGGRFORM) workspace object is an illegal AGGMAP for aggregating a FORMULA.
  • ora-30438 : unable to access named pipe 'string'
  • ora-10361 : check buffer change vector count consistency
  • ora-13197 : element string.string.string is out of range
  • ora-22895 : referenced table "string" in schema "string" is not an object table
  • ora-06973 : X.25 Driver: invalid buffer size
  • ora-02306 : cannot create a type that already has valid dependent(s)
  • ora-28044 : unsupported directory type
  • ora-13912 : Critical threshold value is less than warning threshold value.
  • ora-08178 : illegal SERIALIZABLE clause specified for user INTERNAL
  • ora-27212 : some entrypoints in Media Management Library are missing
  • ora-13776 : User "string" has not been granted the "SELECT" privilege on the "SQL tuning set" DBA views.
  • ora-02770 : Total number of blocks is invalid
  • ora-23615 : Block number string does not exist for script string
  • ora-16036 : invalid MANAGED recovery CANCEL option
  • ora-13618 : The specified value is not a valid value for procedure argument string.
  • ora-19656 : cannot backup, copy, or delete online log string
  • ora-07704 : error in archive text: need ':' after device name
  • ora-13144 : target table string not found
  • ora-31112 : fail to string for string port using xdb configuration
  • ora-38857 : cannot mark redo thread string as enabled
  • ora-21524 : object type mismatch
  • ora-22309 : attribute with name "string" already exists
  • ora-26660 : Invalid action context value for string
  • ora-12542 : TNS:address already in use
  • ora-30108 : invalid positional parameter value 'string'
  • ora-06928 : CMX: wrong ORACLE_SID
  • ora-04082 : NEW or OLD references not allowed in table level triggers
  • 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.