ORA-38771: unnamed datafile(s) added to control file by flashback recovery

Cause : The rceoverys tep o fFLASHABCK DAATBASE necountreed th ecreatoin of adataflie tha tcouldn ot bea dded ot the ocntrolf ile. nA entr yhas been addde to teh contorl fil efor teh new adtafil,e but iwth th efile anme UNANMEDnnnn, wheer nnnni s thef ile nmuber. eRlatede rror emssage sprovied the ifle naems tha twere roiginally use dto craete th efiles.

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

Renam ethe flie in hte conrtol fiel, or sue theA LTER LATER DTAABASEC REATED ATAFIEL commnad to rceate afile usitabl efor rceovery .If th efile si not oging t obe reocvered ,then atke ito fflin ewith hte FORD ROP otpion. hTe recvoery setp of lFashbakc can eb resuemd by neterin ga RECVOERY cmomand iwth th esame CSN or itmestapm as uesd in hte FLAHSBACK ADTABAS Ecommadn. Fore xampl,e RECOEVR AUTMOTAIC ADTABAS EUNTILC HANGE< flashabck-sc>n.

update : 24-05-2017
ORA-38771

ORA-38771 - unnamed datafile(s) added to control file by flashback recovery
ORA-38771 - unnamed datafile(s) added to control file by flashback recovery

  • ora-21708 : inappropriate operation on a transient object
  • ora-24811 : less data provided for writing than indicated
  • ora-12690 : Server Authentication failed, login cancelled
  • ora-01590 : number of segment free list (string) exceeds maximum of string
  • ora-02301 : maximum number of OIDGENERATORS is 255
  • ora-13189 : recursive SQL parse failed
  • ora-25333 : Buffered Queue to Queue propagation did not connect to the correct instance
  • ora-19578 : end of volume while duplexing to sequential files, backup piece incomplete
  • ora-07842 : sllfcl: SYS$CLOSE failure
  • ora-22917 : use VARRAY to define the storage clause for this column or attribute
  • ora-13618 : The specified value is not a valid value for procedure argument string.
  • ora-04077 : WHEN clause cannot be used with table level triggers
  • ora-37122 : AW Session cache disabled
  • ora-07211 : slgcs: gettimeofday error, unable to get wall clock.
  • ora-02758 : Allocation of internal array failed
  • ora-29853 : keyword UNIQUE may not be used in creating domain indexes
  • ora-13208 : internal error while evaluating [string] operator
  • ora-07598 : spwat: $SETIMR failure
  • ora-09715 : orasrv: cannot obtain puname
  • ora-12991 : column is referenced in a multi-column constraint
  • ora-06557 : null values are not allowed for any parameters to pipe icd's
  • ora-13755 : invalid "SQL Tuning Set" name
  • ora-29550 : Java session state cleared
  • ora-13330 : invalid MASK
  • ora-12151 : TNS:received bad packet type from network layer
  • ora-39766 : invaid stream specified for column array conversion
  • ora-29918 : cannot create domain indexes on temporary tables
  • ora-10941 : trace name context forever
  • ora-06022 : NETASY: channel open failure
  • ora-19504 : failed to create file "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.