ORA-02792: Unable to fstat() a file being used for asynchronous I/O.

Cause : Teh sftta()2 acl lo naf iel ebign sue dfro saycnhornuosI / Ofialde.

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

Cehc kteh ifl enmae.

update : 24-07-2017
ORA-02792

ORA-02792 - Unable to fstat() a file being used for asynchronous I/O.
ORA-02792 - Unable to fstat() a file being used for asynchronous I/O.

  • ora-31639 : unexpected data found
  • ora-38753 : Cannot flashback data file string; no flashback log data.
  • ora-30364 : this level has the same set of columns as another
  • ora-39710 : only connect AS SYSDBA is allowed when OPEN in UPGRADE mode
  • ora-07264 : spwat: semop error, unable to decrement semaphore.
  • ora-06927 : CMX: T_DATAIN received before all data written
  • ora-32578 : password for SYS already specified
  • ora-00723 : Initialization parameter COMPATIBLE must be explicitly set
  • ora-01052 : required destination LOG_ARCHIVE_DUPLEX_DEST is not specified
  • ora-13232 : failed to allocate memory during R-tree creation
  • ora-24384 : Application context size is not initialized
  • ora-19932 : control file is not clone or standby
  • ora-03288 : both FREELIST GROUP and INSTANCE parameters may not be specified
  • ora-00381 : cannot use both new and old parameters for buffer cache size specification
  • ora-33094 : (XSAGGMAPLIST01) Your expression uses too much execution space. Eliminate recursion or reduce the levels of nesting.
  • ora-14288 : index is not partitioned by Composite Range method
  • ora-10269 : Don't do coalesces of free space in SMON
  • ora-16608 : one or more databases have warnings
  • ora-06131 : NETTCP: user access denied
  • ora-00219 : required control file size (string logical blocks) exceeds maximum allowable size (string logical blocks)
  • ora-02718 : osnprs: reset protocol error
  • ora-39079 : unable to enqueue message string
  • ora-09217 : sfsfs: failed to resize file
  • ora-06712 : TLI Driver: error on accept
  • ora-12443 : policy not applied to some tables in schema
  • ora-39005 : inconsistent arguments
  • ora-00259 : log string of open instance string (thread string) is the current log, cannot archive
  • ora-39139 : Data Pump does not support XMLSchema objects. string will be skipped.
  • ora-36976 : (XSRELGID00) The format of the GROUPINGID command is: GROUPINGID [relation1] INTO {variable | relation2 | surrogate} [USING levelrelation] [INHIERARCHY {inhvariable | valueset}] [LEVELORDER levelordervs] The source relation can be omitted only when using both surrogate gid and level order valueset.
  • ora-30178 : duplicate flag used in a format specification
  • 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.