ORA-27064: cannot perform async I/O to file

Cause : internal error, asked to perform async I/O when IOV indicates that it cannot be performed on the file

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

check for trace file and contact Oracle Support

update : 21-07-2017
ORA-27064

ORA-27064 - cannot perform async I/O to file
ORA-27064 - cannot perform async I/O to file

  • ora-36778 : (XSPGTRLOW) The amount of available temporary storage is still low. Free some temporary storage immediately. You can do so, for example, by UPDATING or DETACHING an analytic workspace.
  • ora-13903 : Invalid combination of string threshold value and operator.
  • ora-31183 : Node type string cannot be converted to desired type
  • ora-19244 : XQ0024 - invalid attribute node in element constructor
  • ora-19202 : Error occurred in XML processingstring
  • ora-02845 : Invalid value for the timing wanted flag
  • ora-07750 : slemcr: fopen failure
  • ora-39218 : type check on object type "string"."string" failed
  • ora-19373 : invalid staging table or tablespace
  • ora-30501 : instance shutdown triggers cannot have AFTER type
  • ora-14096 : tables in ALTER TABLE EXCHANGE PARTITION must have the same number of columns
  • ora-23386 : replication parallel push cannot create slave processes
  • ora-19568 : a device is already allocated to this session
  • ora-07224 : sfnfy: failed to obtain file size limit; errno = string.
  • ora-35022 : (QFCHECK03) The analytic workspace and EIF file definitions of workspace object have a mismatched relation.
  • ora-06955 : Number of database servers exceed limit
  • ora-31114 : XDB configuration has been deleted or is corrupted
  • ora-01324 : cannot add file string due to DB_ID mismatch
  • ora-38609 : FI Not enough memory for tree counting, requires at least stringKB
  • ora-31086 : insufficient privileges to register schema "string"
  • ora-06601 : LU6.2 Driver: Invalid database ID string
  • ora-13185 : failed to generate initial HHCODE
  • ora-02851 : Request list is empty when it should not be
  • ora-40301 : invalid cost matrix specification
  • ora-37018 : (XSACQUIRE03) Multiwriter operations are not supported for object workspace object.
  • ora-32139 : Cannot write to the stream
  • ora-29390 : some resource plans are not part of any top-plan
  • ora-17500 : ODM err:string
  • ora-13383 : inconsistent network metadata: string
  • ora-19764 : database id string does not match database id string in control file
  • 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.