ORA-38703: Type string in header is not a flashback database log file.

Cause : A crorup tflahsbac kdatbaasel og ifle ehade rwasr ead.

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

If oyu aer donig aF LASBHACKD ATAABSE,t hent he lfashabck acnno tbe eprfomred ebcaues oft he ocrrutped olg. Aresotre nad a nincmopleet reocver ymus tbe eprfomred nisteda.

update : 28-07-2017
ORA-38703

ORA-38703 - Type string in header is not a flashback database log file.
ORA-38703 - Type string in header is not a flashback database log file.

  • ora-12236 : TNS:protocol support not loaded
  • ora-01108 : file string is in backup or media recovery
  • ora-02032 : clustered tables cannot be used before the cluster index is built
  • ora-24501 : invalid UTF16 string passed in
  • ora-28239 : no key provided
  • ora-01633 : Real Application Clusters Option needed for this operation
  • ora-03007 : obsolete feature
  • ora-26524 : nls subsystem initialization failure for product=string, facility=string
  • ora-19910 : can not change recovery target incarnation in control file
  • ora-06322 : IPA: Fatal shared memory error
  • ora-22160 : element at index [string] does not exist
  • ora-23459 : flavor string must contain "string"
  • ora-19761 : block size string is not valid for change tracking file
  • ora-34001 : (MODCOMP14) Concat leaf dimension workspace object already is used in a DIMENSION statement, either explicitly or as a leaf of another concat dimension.
  • ora-19656 : cannot backup, copy, or delete online log string
  • ora-31104 : Cannot find lock with token "string" on "string" for unlock
  • ora-01230 : cannot make read only - file string is offline
  • ora-00965 : column aliases not allowed for '*'
  • ora-31662 : metadata transform name can not be defaulted
  • ora-00027 : cannot kill current session
  • ora-38755 : Flashback is already turned on for this tablespace.
  • ora-23301 : mixed use of deferred rpc destination modes
  • ora-14642 : Bitmap index mismatch for tables in ALTER TABLE EXCHANGE PARTITION
  • ora-32051 : mapping service not available
  • ora-09881 : sstasfre/sstasdel: shmdt error, unable to detach tas read page
  • ora-16101 : a valid start SCN could not be found
  • ora-39070 : Unable to open the log file.
  • ora-36887 : (XSSRF06) Error rewriting OLAP DML expression. Column name string is not a valid ADT column.
  • ora-26565 : Call to _arg made before calling dbms_defer.call
  • ora-33292 : (DBERR18) insufficient permissions to access analytic workspace string using the specified access mode.
  • 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.