ORA-12950: SYSTEM tablespace specified as default permanent tablespace

Cause : SYSTEM tablespace was specified as the default permanent during database creation.

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

If default permanent tablespace is not specified,then SYSTEM will implicitly become the default permanent tablespace. Specify an alternate tablespace or omit the default tablespace clause and reissue the CREATE DATABASE statement

update : 29-04-2017
ORA-12950

ORA-12950 - SYSTEM tablespace specified as default permanent tablespace
ORA-12950 - SYSTEM tablespace specified as default permanent tablespace

  • ora-14061 : data type or length of an index partitioning column may not be changed
  • ora-29974 : Internal event for PL/SQL debugging
  • ora-12077 : temporary updatable materialized view log does not exist
  • ora-12059 : prebuilt table "string"."string" does not exist
  • ora-01640 : cannot make tablespace read only with active transactions
  • ora-32576 : missing TYPE keyword
  • ora-07243 : supplied buffer not big enough to hold entire line
  • ora-23369 : value of "string" argument cannot be null
  • ora-13295 : geometry objects are in different coordinate systems
  • ora-13370 : failure in applying 3D LRS functions
  • ora-25352 : no current transaction
  • ora-17508 : I/O request buffer ptr is not alligned
  • ora-13406 : null or invalid GeoRaster object for output
  • ora-28111 : insufficient privilege to evaluate policy predicate
  • ora-01608 : cannot bring rollback segment 'string' online, its status is (string)
  • ora-23427 : deferred purge queue argument string out of range
  • ora-19765 : mount id string does not match mount id string in control file
  • ora-31105 : User does not own lock "string"
  • ora-10701 : Dump direct loader index keys
  • ora-16533 : inconsistent Data Guard broker state
  • ora-39090 : Cannot add devices to file oriented job.
  • ora-16794 : database guard is on for primary database
  • ora-32026 : %s.string has fewer columns compared to string table.
  • ora-30741 : WITH HIERARCHY OPTION can be specified only for SELECT privilege
  • ora-19773 : must specify change tracking file name
  • ora-25958 : join index where clause predicate may only contain column references
  • ora-27374 : insufficient privileges on event source queue
  • ora-32843 : value for string is outside the valid range of string to string
  • ora-06955 : Number of database servers exceed limit
  • ora-15193 : Internal ASM tracing event number 15193
  • 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.