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

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

  • ora-16151 : Managed Standby Recovery not available
  • ora-01979 : missing or invalid password for role 'string'
  • ora-16229 : PDML child string string string for parent string string string cannot be skipped.
  • ora-22911 : duplicate storage specification for the nested table item
  • ora-27078 : unable to determine limit for open files
  • ora-15011 : failure group "string" contains no members
  • ora-38769 : FLASHBACK DATABASE failed after modifying data.
  • ora-22319 : type attribute information altered in ALTER TYPE
  • ora-16777 : unable to find the destination entry of a standby database in V$ARCHIVE_DEST
  • ora-02705 : osnpol: polling of communication channel failed
  • ora-16047 : DGID mismatch between destination setting and standby
  • ora-12157 : TNS:internal network communication error
  • ora-12625 : TNS:missing argument
  • ora-12856 : cannot run parallel query on a loopback connection
  • ora-23498 : repgroups specified must have the same masters
  • ora-13499 : %s
  • ora-15153 : cluster not in rolling upgrade
  • ora-14329 : domain index [sub]partitions cannot be renamed in this clause
  • ora-33098 : (APABBR01) A value of 'string' is not valid for the workspace object option.
  • ora-30973 : invalid Path Table option for XML Index
  • ora-38795 : warning: FLASHBACK succeeded but OPEN RESETLOGS would get error below
  • ora-26088 : scalar column "string" must be specified prior to LOB columns
  • ora-13067 : operator requires both parameters from the same topology
  • ora-13857 : Invalid module name
  • ora-36872 : (XSTFDSC02) Column type specifier cannot be used when the table function data type is specified.
  • ora-31412 : change set string is disabled and cannot be advanced
  • ora-06746 : TLI Driver: cannot alloc t_call
  • ora-02876 : smpini: Unable to attach to shared memory for PGA
  • ora-28179 : client user name not provided by proxy
  • ora-08308 : sllfop: Cannot open file
  • 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.