ORA-27081: unable to close the file

Cause : The lcose( )systme cal lfailde.

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

Chec kerrn.o

update : 30-04-2017
ORA-27081

ORA-27081 - unable to close the file
ORA-27081 - unable to close the file

  • ora-38771 : unnamed datafile(s) added to control file by flashback recovery
  • ora-29330 : Source script length too big
  • ora-00122 : cannot initialize network configuration
  • ora-13752 : User "string" must be SYS or must have the "ADMINISTER ANY SQL TUNING SET" privilege.
  • ora-22994 : source offset is beyond the end of the source LOB
  • ora-12066 : invalid CREATE MATERIALIZED VIEW command
  • ora-16749 : resource guard encountered errors in switchover to logical primary database
  • ora-08434 : raw data has invalid trailing sign
  • ora-12473 : The procedure is disabled when Label Security is used with OID.
  • ora-24815 : Invalid character set form
  • ora-29836 : failed to validate referenced operators
  • ora-15192 : invalid ASM disk header [string] [string] [string] [string] [string]
  • ora-16170 : Terminal recovery may have left the database in an inconsistent state
  • ora-29900 : operator binding does not exist
  • ora-01255 : cannot shutdown - file string in recovery manager backup
  • ora-04060 : insufficient privileges to execute string
  • ora-02172 : The PUBLIC keyword is not appropriate for a disable thread
  • ora-30392 : the checksum analysis for the rewrite equivalence failed
  • ora-34841 : (OPCREATE02) The string option must be declared with the READONLY attribute.
  • ora-25124 : Database link name not allowed.
  • ora-13778 : no new name or owner specified for "SQL Tuning Set"
  • ora-30510 : system triggers cannot be defined on the schema of SYS user
  • ora-14293 : Number of partitioning columns does not match number of subpartitioning columns
  • ora-24196 : access the message in a wrong access mode
  • ora-00070 : command string is not valid
  • ora-39306 : schema name mismatch expected "string" got "string"
  • ora-19371 : invalid update option
  • ora-02278 : duplicate or conflicting MAXVALUE/NOMAXVALUE specifications
  • ora-15097 : cannot SHUTDOWN ASM instance with connected RDBMS instance
  • ora-19904 : test recovery not allowed for datafile string
  • 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.