ORA-27062: could not find pending async I/Os

Cause : There should have been some async I/Os in the system but a blocking aiowait indicates that there are no more I/Os. It could be either because of an Oracle bug or the vendor OS bug or due to a NFS server not responding

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

check Oracle trace file, OS message files and contact Oracle Support

update : 28-06-2017
ORA-27062

ORA-27062 - could not find pending async I/Os
ORA-27062 - could not find pending async I/Os

  • ora-07721 : scgcm: not enough OS resource to obtain system enqueue
  • ora-00050 : operating system error occurred while obtaining an enqueue
  • ora-06532 : Subscript outside of limit
  • ora-24328 : illegal attribute value
  • ora-02437 : cannot validate (string.string) - primary key violated
  • ora-01632 : max # extents (string) reached in index string.string
  • ora-15034 : disk 'string' does not require the FORCE option
  • ora-13912 : Critical threshold value is less than warning threshold value.
  • ora-13905 : Critical or warning threshold have incorrect values
  • ora-00023 : session references process private memory; cannot detach session
  • ora-16172 : archive logs detected beyond Terminal End-Of-Redo
  • ora-33084 : (XSAGDNGL42) In AGGMAP workspace object, you cannot qualify the dimensioned valueset workspace object.
  • ora-09821 : Numeric label is not valid
  • ora-14002 : only one GLOBAL clause may be specified
  • ora-28604 : table too fragmented to build bitmap index (string,string,string)
  • ora-16195 : DG_CONFIG requires DB_UNIQUE_NAME be explicitly defined
  • ora-10576 : Give up restoring recovered datafiles to consistent state: some error occurred
  • ora-19246 : XQ0026 - validation failed - element string not found in in-scope element declarations
  • ora-01572 : rollback segment 'string' cannot be brought online, string extents exceeded
  • ora-15010 : name is already used by an existing ASM disk
  • ora-40102 : invalid input string for data mining operation string
  • ora-13332 : invalid LRS point
  • ora-12201 : TNS:encountered too small a connection buffer
  • ora-28292 : No Domain Policy registered for Kerberos based authentication
  • ora-26529 : local store callback term phase failed for 'string.string'
  • ora-06704 : TLI Driver: receive break message failed
  • ora-13125 : partition key is already set
  • ora-29703 : error occurred in global enqueue service operation
  • ora-38712 : Corrupt flashback log record header: block string, offset string.
  • ora-06442 : ssvwatev: Failed with unexpected error number.
  • 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.