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 : 22-08-2017

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

  • ora-25139 : invalid option for CREATE TEMPORARY TABLESPACE
  • ora-06571 : Function string does not guarantee not to update database
  • ora-13422 : invalid model coordinate parameter
  • ora-34210 : (MXCHGDCL18) You cannot change workspace object to a dimension composite because one or more surrogates has been defined for it.
  • ora-16202 : Skip procedure requested to replace statement
  • ora-22276 : invalid locator for LOB buffering
  • ora-22303 : type "string"."string" not found
  • ora-38903 : DML error logging is not supported for abstract column "string"
  • ora-12925 : tablespace string is not in force logging mode
  • ora-30199 : reserved for future use
  • ora-36694 : (XSRELTBL01) The value cannot be added to dimension workspace object.
  • ora-16016 : archived log for thread string sequence# string unavailable
  • ora-16211 : unsupported record found in the archived redo log
  • ora-01518 : CREATE DATABASE must specify more than one log file
  • ora-24044 : source string and destination string object types do not match
  • ora-31080 : type not specified for attribute or element "string"
  • ora-19333 : Invalid flags for the CREATE_DBURI operator
  • ora-10640 : Operation not permitted during SYSTEM tablespace migration
  • ora-31669 : Worker process string violated startup protocol.
  • ora-13410 : invalid layerNumbers or bandNumbers parameter
  • ora-13271 : error allocating memory for geometry object
  • ora-31432 : invalid source table
  • ora-24164 : invalid rule engine system privilege: string
  • ora-37153 : unknown exception caught: (case string)
  • ora-02402 : PLAN_TABLE not found
  • ora-01967 : invalid option for CREATE CONTROLFILE
  • ora-19664 : file type: string, file name: string
  • ora-10617 : Cannot create rollback segment in dictionary managed tablespace
  • ora-01512 : error renaming log file string - new file string not found
  • ora-23474 : definition of "string"."string" has changed since generation of replication support
  • 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.