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 : 29-04-2017

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

  • ora-01372 : Insufficient processes for specified LogMiner operation
  • ora-25182 : feature not currently available for index-organized tables
  • ora-13642 : The specified string string provided for string cannot be converted to a date. The acceptable date format is string.
  • ora-02293 : cannot validate (string.string) - check constraint violated
  • ora-02774 : Invalid request list latch time out value
  • ora-01227 : log string is inconsistent with other logs
  • ora-26577 : PRESERVE TABLE can not be used when dropping old style materialized view string.string
  • ora-29558 : JAccelerator (NCOMP) not installed. Refer to Install Guide for instructions.
  • ora-33009 : (XSAGDNGLPREC) In AGGMAP workspace object, PRECOMPUTE may only be specified either for the entire AGGMAP or for individual RELATION statements.
  • ora-25304 : Cannot use priority order queues for capture LCRs
  • ora-12444 : policy already applied to table
  • ora-02822 : Invalid block offset
  • ora-13036 : Operation [string] not supported for Point Data
  • ora-25195 : invalid option for index on an index-organized table
  • ora-01353 : existing Logminer session
  • ora-19556 : required destination LOG_ARCHIVE_DUPLEX_DEST currently is deferred
  • ora-08232 : smsdes: cannot detach from SGA
  • ora-13013 : the specified topology was not INTERIOR or BOUNDARY
  • ora-13120 : invalid face_id [string]
  • ora-03007 : obsolete feature
  • ora-12434 : invalid audit type: string
  • ora-00165 : migratable distributed autonomous transaction with remote operation is not allowed
  • ora-07580 : spstp: $GETJPIW failure
  • ora-12992 : cannot drop parent key column
  • ora-23357 : the propagator does not exist
  • ora-01653 : unable to extend table string.string by string in tablespace string
  • ora-16507 : unrecognized request identifier
  • ora-24305 : bad bind or define context
  • ora-02040 : remote database string does not support two-phase commit
  • ora-06577 : output parameter not a bind variable
  • 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.