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 : 17-08-2017

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

  • ora-37129 : (XSCCOMP04) Cannot aggregate over COMPRESSED COMPOSITE workspace object using AGGMAP workspace object. All static MODEL statements must precede all RELATION statements over the bases of the COMPRESSED COMPOSITE.
  • ora-00164 : distributed autonomous transaction disallowed within migratable distributed transaction
  • ora-38480 : creation of system trigger EXPFIL_ALTEREXPTAB_MAINT failed.
  • ora-16075 : standby database destination mismatch
  • ora-26062 : Can not continue from previous errors.
  • ora-02185 : a token other than WORK follows COMMIT
  • ora-22952 : Nested Table equality requires a map method on the element ADT
  • ora-24757 : duplicate transaction identifier
  • ora-31161 : element or attribute "string" cannot be stored out of line
  • ora-22854 : invalid option for LOB storage index
  • ora-12537 : TNS:connection closed
  • ora-31690 : Process name buffer size must be specified and must be greater than 0.
  • ora-09953 : scggc: unexpected return of a lock convert
  • ora-04052 : error occurred when looking up remote object stringstringstringstringstring
  • ora-39309 : schema sync operation failed
  • ora-23414 : materialized view log for "string"."string" does not record rowid values
  • ora-40286 : remote operations not permitted on mining models
  • ora-19687 : SPFILE not found in backup set
  • ora-12414 : internal LBAC error: string Error: string
  • ora-30116 : syntax error at 'string' following 'string'
  • ora-09714 : Two Task interface: cannot obtain puname
  • ora-22919 : dangling REF error or lock object failed for no wait request
  • ora-22882 : object creation failed
  • ora-13442 : GeoRaster metadata SRS error
  • ora-14255 : table is not partitioned by Range, Composite Range or List method
  • ora-32839 : property string is reserved, names with MGWPROP$_ prefix are not valid
  • ora-30156 : Out of disk space
  • ora-13852 : Tracing for service(module/action) string is not enabled
  • ora-15133 : instance recovery required for diskgroup string
  • ora-22291 : Open LOBs exist at transaction commit time
  • 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.