ORA-01220: file based sort illegal before database is open

Cause : A query issued against a fixed table or view required a temporary segment for sorting before the database was open. Only in-memory sorts are supported before the database is open.

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

Re-phrase the query to avoid a large sort, increase the values of the SORT_AREA_SIZE and/or SORT_AREA_RETAINED_SIZE initialization parameters to enable the sort to be done in memory.

update : 23-09-2017
ORA-01220

ORA-01220 - file based sort illegal before database is open
ORA-01220 - file based sort illegal before database is open

  • ora-08231 : smscre: unable to attach to SGA
  • ora-00359 : logfile group string does not exist
  • ora-30936 : Maximum number (string) of 'string' XML node elements exceeded
  • ora-39082 : Object type string created with compilation warnings
  • ora-31068 : updateXML expected data format [string] instead of [string]
  • ora-25130 : cannot modify primary key - primary key not defined for table
  • ora-07573 : slkhst: could not perform host operation
  • ora-01950 : no privileges on tablespace 'string'
  • ora-28561 : unable to set date format on non-Oracle system
  • ora-12447 : policy role already exists for policy string
  • ora-31093 : null or invalid value specified for parameter : string
  • ora-14302 : only one list of added-LOB-storage-clauses can be specified in a statement
  • ora-27128 : unable to determine pagesize
  • ora-13219 : failed to create spatial index table [string]
  • ora-25282 : message id. not provided for non-repudiation
  • ora-02712 : osnpop: malloc failed
  • ora-14269 : cannot exchange partition other than a Range or Hash partition
  • ora-25020 : renaming system triggers is not allowed
  • ora-13264 : geometry identifier column string does not exist in table string
  • ora-12018 : following error encountered during code generation for "string"."string"
  • ora-15038 : disk 'string' size mismatch with diskgroup [string] [string] [string]
  • ora-33298 : (AWUPG01) Analytic Workspace string is already in the newest format allowed by the current compatibility setting
  • ora-02353 : files not from the same unload operation
  • ora-01247 : database recovery through TSPITR of tablespace string
  • ora-19559 : error sending device command: string
  • ora-30087 : Adding two datetime values is not allowed
  • ora-22303 : type "string"."string" not found
  • ora-26530 : unable to build materialized view refresh control list
  • ora-06441 : ssvwatev: Incorrect parameter passed to function call
  • ora-04077 : WHEN clause cannot be used with 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.