ORA-38732: Expected file size string does not match string.

Cause : The file size indicated in the control file did not match the file size contained in the flashback log file header. The flashback database log file 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-38732 - Expected file size string does not match string.
ORA-38732 - Expected file size string does not match string.

  • ora-31109 : Action failed as parent resource string is locked
  • ora-29848 : error occurred in the execution of ODCIINDEXMERGEPARTITION routine
  • ora-39134 : Cannot include "string" tablespace as a Transportable Tablespace
  • ora-00910 : specified length too long for its datatype
  • ora-38489 : predicate table creation failed due to: ORAstring
  • ora-07600 : slkmnm: $GETSYIW failure
  • ora-32838 : exceeded maximum number of properties
  • ora-14132 : table cannot be used in EXCHANGE
  • ora-30754 : column or table string stores objects of only one type
  • ora-00348 : single-process redo failure. Must abort instance
  • ora-07206 : slgtd: gettimeofday error, unable to obtain time.
  • ora-16779 : the destination parameter of a database is set incorrectly
  • ora-13919 : Cannot specify values for parameter "string" and for parameter "string"
  • ora-32834 : Messaging Gateway agent user has not been set
  • 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-30653 : reject limit reached
  • ora-38436 : attribute set used for an Expression set may not be modified.
  • ora-02174 : Missing required thread number
  • ora-06504 : PL/SQL: Return types of Result Set variables or query do not match
  • ora-32166 : Cannot get XA connection
  • ora-16148 : user requested expiration of managed recovery operation
  • ora-02704 : osndopop: fork failed
  • ora-12324 : cannot use the ROM: link type on a private database link
  • ora-07418 : sfareq: Database writer got error in timing function.
  • ora-07266 : sppst: invalid process number passed to sppst.
  • ora-01983 : invalid auditing option for DEFAULT
  • ora-32632 : incorrect subquery in MODEL FOR cell index
  • ora-02778 : Name given for the log directory is invalid
  • ora-06004 : NETASY: dialogue file open failure
  • ora-16629 : database reports a different protection level from the protection 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.