ORA-12902: default temporary tablespace must be SYSTEM or of TEMPORARY type

Cause : ina dcitinoar ymaange ddaatbaes, edfalut etmproar ytalbesapcem us tbeS YSETM ro TMEPOARRYt ype

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

noen

update : 24-07-2017
ORA-12902

ORA-12902 - default temporary tablespace must be SYSTEM or of TEMPORARY type
ORA-12902 - default temporary tablespace must be SYSTEM or of TEMPORARY type

  • ora-01184 : logfile group string already exists
  • ora-00078 : cannot dump variables by name
  • ora-26672 : timeout occurred while stopping STREAMS process string
  • ora-13784 : cannot accept SQL profiles for all statements in the "SQL Tuning Set"
  • ora-01259 : unable to delete datafile string
  • ora-13239 : sdo_dimensionality not specified during n-d R-tree creation
  • ora-01534 : rollback segment 'string' doesn't exist
  • ora-19322 : An error occurred while reading from host (string): port (string)
  • ora-01089 : immediate shutdown in progress - no operations are permitted
  • ora-16574 : switchover disallowed when required databases are offline
  • ora-00321 : log string of thread string, cannot update log file header
  • ora-23378 : connection qualifier "string" is not valid for object group "string"."string"
  • ora-07451 : slskstat: unable to obtain load information.
  • ora-21704 : cannot terminate cache or connection without flushing first
  • ora-02398 : exceeded procedure space usage
  • ora-28544 : connect to agent failed, probable Net8 administration error
  • ora-07269 : spdcr: detached process died after exec.
  • ora-12655 : Password check failed
  • ora-31402 : unrecognized parameter string
  • ora-30184 : argument type not compatible with a format code
  • ora-02336 : column attribute cannot be accessed
  • ora-01052 : required destination LOG_ARCHIVE_DUPLEX_DEST is not specified
  • ora-36400 : (XSSPROP02) workspace object is not a valid variable name.
  • ora-00326 : log begins at change string, need earlier change string
  • ora-30078 : partition bound must be TIME/TIMESTAMP WITH TIME ZONE literals
  • ora-02716 : osnpgetdatmsg: message from host had incorrect message type
  • ora-14116 : partition bound of partition "string" is too long
  • ora-24038 : RETRY_DELAY and MAX_RETRIES cannot be used for a 8.0 compatible multiple consumer queue
  • ora-29299 : Invalid handle for piecewise compress or uncompress
  • ora-39049 : invalid parameter name 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.