ORA-38731: Expected version string does not match string in log header.

Cause : The version of the flashback database log file header was corrupt.

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

If you are doing a FLASHBACK DATABASE, then the flashback cannot be performed because of the corrupted log. A restore and an incomplete recovery must be performed instead.

update : 24-06-2017

ORA-38731 - Expected version string does not match string in log header.
ORA-38731 - Expected version string does not match string in log header.

  • ora-39040 : Schema expression "string" must identify exactly one schema.
  • ora-14408 : partitioned index contains subpartitions in a different tablespace
  • ora-37122 : AW Session cache disabled
  • ora-31648 : Timeout before master process string finished initialization.
  • ora-13642 : The specified string string provided for string cannot be converted to a date. The acceptable date format is string.
  • ora-10571 : Test recovery canceled
  • ora-16563 : unable to add value, syntax error at "string"
  • ora-00369 : Current log of thread string not useable and other log being cleared
  • ora-13858 : Invalid action name
  • ora-12839 : cannot modify an object in parallel after modifying it
  • ora-31094 : incompatible SQL type "string" for attribute or element "string"
  • ora-01033 : ORACLE initialization or shutdown in progress
  • ora-03206 : maximum file size of (string) blocks in AUTOEXTEND clause is out of range
  • ora-13864 : Statistics aggregation for service (module/action) string is already enabled
  • ora-01566 : file specified more than once in ALTER DATABASE
  • ora-16589 : Data Guard Connection process detected a network transfer error
  • ora-24304 : datatype not allowed for this call
  • ora-29316 : datafile string been imported twice
  • ora-38766 : cannot flashback data file string; file resized smaller
  • ora-19212 : no key columns specified before call to DBMS_XMLSTORE.updateXML()
  • ora-30202 : NULL pointer to OCIMsgh was passed to OCIMsg function
  • ora-13627 : Setting of parameter string is disallowed until the task is reset.
  • ora-01045 : user string lacks CREATE SESSION privilege; logon denied
  • ora-08464 : input raw decimal data contains more than 42 digits
  • ora-24374 : define not done before fetch or execute and fetch
  • ora-25314 : a commit-time queue table cannot be migrated to 8.0
  • ora-15108 : missing or invalid template name
  • ora-29268 : HTTP client error string
  • ora-02363 : error reading from file: string
  • ora-08181 : specified number is not a valid system change number
  • 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.