ORA-27073: Trying to close a file which has async I/Os pending to be dequeued

Cause : itnenra lerro,r htef iel si ebign lcoesdb u tnto lala snycI /sO ot htef iel ahv ebeend euqeeud ,addiitoanli noframtoini nidctae snmubre fo /IO spnednigo nt h eflie

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

cehc kfro rtaec ifl eadn ocnatc tOarcel uSpoprt

update : 27-04-2017
ORA-27073

ORA-27073 - Trying to close a file which has async I/Os pending to be dequeued
ORA-27073 - Trying to close a file which has async I/Os pending to be dequeued

  • ora-31203 : DBMS_LDAP: PL/SQL - Init Failed.
  • ora-29279 : SMTP permanent error: string
  • ora-33018 : (XSAGDNGL08) In AGGMAP workspace object, the data type of workspace object must be TEXT, not string.
  • ora-15003 : diskgroup "string" already mounted in another lock name space
  • ora-31526 : could not find source table string.string for CDC change table string.string
  • ora-07240 : slemrd: seek error.
  • ora-30489 : Cannot have more than one rollup/cube expression list
  • ora-12068 : updatable mview log for mview "string"."string" does not exist
  • ora-06812 : TLI Driver: could not read the ethernet driver's node address
  • ora-02048 : attempt to begin distributed transaction without logging on
  • ora-22875 : cannot drop primary key of an object table whose object identifier is primary key based
  • ora-19900 : RESETLOGS must be specified after recovery to new incarnation
  • ora-01276 : Cannot add file string. File has an Oracle Managed Files file name.
  • ora-10382 : parallel query server interrupt (reset)
  • ora-08119 : The new initrans will make the index too big
  • ora-07595 : sppid: $GETJPIW failure
  • ora-31196 : XML nodes over string in size cannot be printed
  • ora-07846 : sllfop: string byte record too big for string byte user buffer
  • ora-19673 : error during proxy file string
  • ora-06976 : X.25 Driver: endpoint creation failure
  • ora-13857 : Invalid module name
  • ora-12921 : database is not in force logging mode
  • ora-27418 : syntax error in repeat interval or calendar
  • ora-25116 : invalid block number specified in the DUMP DATAFILE/TEMPFILE command
  • ora-14105 : RECOVERABLE/UNRECOVERABLE may not be specified in this context
  • ora-24852 : protocol error during statement execution
  • ora-21611 : key length [string] is invalid
  • ora-00123 : idle public server terminating
  • ora-10915 : TABLESPACE GROUP cannot be specified for this type of tablespace
  • ora-02360 : fatal error during data export/import initialization
  • 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.