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 : 20-08-2017
ORA-38731

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-29375 : sum of values string for level string, plan string exceeds string
  • ora-33427 : (EIFMAKEF16) CAUTION: NTEXT object workspace object will be exported with type TEXT.
  • ora-29378 : invalid consumer group mapping priorities
  • ora-31530 : could not find published column string for CDC subscriber view string.string
  • ora-31043 : Element 'string' not globally defined in schema 'string'
  • ora-13918 : Updating system alert with reason_id string failed; previous alert not found
  • ora-28262 : global_context_pool_size has invalid value.
  • ora-00270 : error creating archive log string
  • ora-16741 : the destination parameter of standby database "string" has incorrect syntax
  • ora-33274 : (DBERR07) Timed out while trying to lock analytic workspace string for string.
  • ora-02031 : no ROWID for fixed tables or for external-organized tables
  • ora-30388 : name of the rewrite equivalence is not specified
  • ora-26725 : cannot downgrade apply handlers
  • ora-07260 : spdcr: wait error.
  • ora-01556 : MINEXTENTS for rollback segment must be greater than 1
  • ora-00268 : specified log file does not exist 'string'
  • ora-19811 : cannot have files in DB_RECOVERY_FILE_DEST with keep attributes
  • ora-12076 : invalid threshold value
  • ora-01876 : year must be at least -4713
  • ora-36208 : (XSAGOP05N) In AGGMAP workspace object, you can only specify NAOPERATOR string with the PROPORTIONAL or EVEN operators, not string.
  • ora-38749 : A media recovery has been started.
  • ora-31621 : error creating master process
  • ora-24433 : This statement has already been prepared using OCIStmtPrepare2.
  • ora-06312 : IPA: Incorrect outgoing service name supplied
  • ora-02194 : event specification syntax error string (minor error string) near 'string'
  • ora-02299 : cannot validate (string.string) - duplicate keys found
  • ora-29550 : Java session state cleared
  • ora-29381 : plan/consumer_group string referred to by another plan and cannot be deleted
  • ora-13785 : missing target object for tuning task "string"
  • ora-09921 : Unable to get information label from connection
  • 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.