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 : 23-08-2017
ORA-38732

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

  • ora-02452 : invalid HASHKEYS option value
  • ora-12224 : TNS:no listener
  • ora-13467 : unsupported GeoRaster metadata specification: string
  • ora-02824 : Request free list is empty
  • ora-36700 : (XSRELTBL04) Dimension workspace object cannot be qualified more than once.
  • ora-01720 : grant option does not exist for 'string.string'
  • ora-24066 : invalid privilege specified
  • ora-14106 : LOGGING/NOLOGGING may not be specified for a clustered table
  • ora-16020 : less destinations available than specified by LOG_ARCHIVE_MIN_SUCCEED_DEST
  • ora-25279 : dequeue as select not supported before 8.2
  • ora-02294 : cannot enable (string.string) - constraint changed during validation
  • ora-16097 : ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY
  • ora-23515 : materialized views and/or their indices exist in the tablespace
  • ora-30064 : Test support for two phase read only optimization
  • ora-31423 : change table string does not contain column string
  • ora-37153 : unknown exception caught: (case string)
  • ora-19551 : device is busy, device type: string, device name: string
  • ora-30655 : cannot select FOR UPDATE from external organized table
  • ora-13915 : Critical byte based free space threshold value is greater than warning threshold value.
  • ora-30454 : summary contains STDDEV without corresponding SUM & COUNT
  • ora-36178 : (XSAGGR01) To be used with AGGREGATE, AGGMAP workspace object must be declared with the AGGMAP command.
  • ora-27161 : request for Oracle binary information failed
  • ora-00052 : maximum number of enqueue resources (string) exceeded
  • ora-39102 : Timeout before master process string finished initialization. Master error:
  • ora-27485 : argument string already exists at a different position
  • ora-28006 : conflicting values for parameters string and string
  • ora-09856 : smpalo: vm_allocate error while allocating pga.
  • ora-01354 : Supplemental log data must be added to run this command
  • ora-16566 : unsupported document type
  • ora-15083 : failed to communicate with ASMB background process
  • 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.