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 : 27-05-2017

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-29816 : object being disassociated is not present
  • ora-22059 : buffer size [string] is too small - [string] is needed
  • ora-36804 : (XSTBLFUNC02) The OLAP_TABLE function encountered an error while parsing the LIMITMAP.
  • ora-24396 : invalid attribute set in server handle
  • ora-08498 : Warning: picture mask 'string' overrides picture mask option 'USAGE IS string' to 'USAGE IS DISPLAY'
  • ora-32307 : must use FROM ONLY clause when referencing an object table
  • ora-12703 : this character set conversion is not supported
  • ora-30016 : undo tablespace 'string' is already in use by this instance
  • ora-39104 : cannot call this function from a SQL parallel query slave process
  • ora-00825 : cannot set db_block_buffers if sga_target set
  • ora-07392 : sftcls: fclose error, unable to close text file.
  • ora-29379 : resource plan string is involved in a loop in top-plan string
  • ora-06005 : NETASY: dialogue file read failure
  • ora-14288 : index is not partitioned by Composite Range method
  • ora-06535 : statement string in string is NULL or 0 length
  • ora-37119 : Incompatible OLAP API library load address
  • ora-25528 : too many candidate MTTRs are specified in _DB_MTTR_SIM_TARGET
  • ora-00367 : checksum error in log file header
  • ora-27209 : syntax error in device PARMS - unknown keyword or missing =
  • ora-30029 : no active undo tablespace assigned to instance
  • ora-14629 : cannot drop the only subpartition of a partition
  • ora-24131 : table string has incorrect columns
  • ora-01622 : thread number must be specified - default not specific
  • ora-02168 : invalid value for FREELISTS
  • ora-01089 : immediate shutdown in progress - no operations are permitted
  • ora-01530 : a database already mounted by the instance
  • ora-30550 : index depends on a package/function spec/body which is not valid
  • ora-38775 : cannot disable flash recovery area - flashback database is enabled
  • ora-09961 : Unable to restore termination signal handler
  • ora-16070 : parameter string contains an invalid REGISTER attribute value
  • 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.