ORA-27037: unable to obtain file status

Cause : stat system call returned an error, additional information indicates which function encountered the error

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

check errno

update : 17-08-2017

ORA-27037 - unable to obtain file status
ORA-27037 - unable to obtain file status

  • ora-01291 : missing logfile
  • ora-14014 : maximum number of partitioning columns is 16
  • ora-10265 : Keep random system generated output out of error messages
  • ora-39775 : direct path API commit not allowed due to previous fatal error
  • ora-24079 : invalid name string, names with AQ$_ prefix are not valid for string
  • ora-16804 : one or more configuration properties in metadata have invalid values
  • ora-00065 : initialization of FIXED_DATE failed
  • ora-01135 : file string accessed for DML/query is offline
  • ora-04014 : descending sequences that CYCLE must specify MINVALUE
  • ora-16125 : large transaction string string string is waiting for more data
  • ora-09913 : Malloc of dummy name failed.
  • ora-03219 : Tablespace 'string' is dictionary-managed, offline or temporary
  • ora-27103 : internal error
  • ora-27040 : file create error, unable to create file
  • ora-00270 : error creating archive log string
  • ora-00108 : failed to set up dispatcher to accept connection asynchronously
  • ora-00281 : media recovery may not be performed using dispatcher
  • ora-19881 : Corrupted space bitmap for datafile string, block string backup aborted
  • ora-06600 : LU6.2 Driver: SNA software is not loaded
  • ora-23313 : object group "string"."string" is not mastered at string
  • ora-00322 : log string of thread string is not current copy
  • ora-38419 : invalid identifier in attribute : string
  • ora-06974 : X.25 Driver: SID lookup failure
  • ora-31459 : system triggers for DBMS_CDC_PUBLISH package are not installed
  • ora-31624 : A job cannot be modified after it has started.
  • ora-10946 : trace name context forever
  • ora-12823 : default degree of parallelism may not be specified here
  • ora-01943 : IDENTIFIED BY already specified
  • ora-02084 : database name is missing a component
  • ora-06035 : NETDNT: connect failed, insufficient resources
  • 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.