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 : 24-07-2017
ORA-01220

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

  • ora-32166 : Cannot get XA connection
  • ora-22997 : VARRAY | OPAQUE stored as LOB is not specified at the table level
  • ora-22055 : unknown sign flag value [string]
  • ora-06010 : NETASY: dialogue file too long
  • ora-36644 : (XSDUNION07) Concat dimension workspace object contains a previously detected leaf dimension.
  • ora-26027 : unique index string.string partition string initially in unusable state
  • ora-24809 : amount specified will not fit in the lob buffers
  • ora-24387 : Invalid attach driver
  • ora-02026 : missing LINK keyword
  • ora-29846 : cannot create a local domain index on a string partitioned table
  • ora-33058 : (XSAGDNGL28) In AGGMAP workspace object, error code string is greater than the maximum error code of number.
  • ora-12448 : policy string not applied to schema string
  • ora-31643 : unable to close dump file "string"
  • ora-13710 : Parameter "string" must have a higher value than parameter "string". The values supplied were "string" and "string" respectively.
  • ora-01644 : tablespace 'string' is already read only
  • ora-12666 : Dedicated server: outbound transport protocol different from inbound
  • ora-25528 : too many candidate MTTRs are specified in _DB_MTTR_SIM_TARGET
  • ora-30951 : Element or attribute at Xpath string exceeds maximum length
  • ora-00255 : error archiving log string of thread string, sequence # string
  • ora-34719 : (NLSCHARSET03) Character data loss in NTEXT/TEXT conversion
  • ora-34656 : (MXSQL24) Additional WHERE clause conditions with CURRENT OF syntax
  • ora-15205 : requested mirror side unavailable
  • ora-32131 : bind data type cannot be changed
  • ora-02168 : invalid value for FREELISTS
  • ora-00001 : unique constraint (string.string) violated
  • ora-32622 : illegal multi-cell reference
  • ora-12024 : materialized view log on "string"."string" does not have primary key columns
  • ora-30445 : workload queries not found
  • ora-34514 : (MXOPERR) You cannot string string data in the expression that begins with 'string'.
  • ora-39213 : Metadata processing is not available
  • 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.