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 : 24-06-2017

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

  • ora-24809 : amount specified will not fit in the lob buffers
  • ora-13343 : a polygon geometry has fewer than four coordinates
  • ora-01954 : DEFAULT ROLE clause not valid for CREATE USER
  • ora-31218 : DBMS_LDAP: PL/SQL - Invalid LDAP deleteoldrdn.
  • ora-01908 : EXISTS keyword expected
  • ora-38489 : predicate table creation failed due to: ORAstring
  • ora-27508 : IPC error sending a message
  • ora-38714 : Instance recovery required.
  • ora-30055 : NULL snapshot expression not allowed here
  • ora-27458 : A program of type PLSQL_BLOCK cannot have any arguments.
  • ora-10269 : Don't do coalesces of free space in SMON
  • ora-14003 : GLOBAL clause contradicts previosly specified LOCAL clause
  • ora-38719 : Invalid DUMP FLASHBACK object.
  • ora-02854 : Invalid number of request buffers
  • ora-29839 : failed to validate implementation type
  • ora-32118 : Cannot perform operation on a null FILE
  • ora-39212 : installation error: XSL stylesheets not loaded correctly
  • ora-01973 : Missing change number
  • ora-31522 : could not find Streams object string for CDC change set string
  • ora-10388 : parallel query server interrupt (failure)
  • ora-36831 : (XSLMGEN01) View token cannot be NA
  • ora-36706 : (XSRELTBL07) workspace object should be dimensioned by workspace object and one level dimension.
  • ora-38747 : corrupt before image (file# string, block# string)
  • ora-10655 : Segment can be shrunk
  • ora-30088 : datetime/interval precision is out of range
  • ora-25467 : table alias not specified
  • ora-31004 : Length string of the BLOB in XDB$H_INDEX is below the minimum string
  • ora-24757 : duplicate transaction identifier
  • ora-16028 : new string causes less destinations than LOG_ARCHIVE_MIN_SUCCEED_DEST requires
  • ora-24122 : invalid block range specification
  • 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.