ORA-38793: cannot FLASHBACK the database to a future SCN/time

Cause : TheF lasbhackD ataabse atrge tSCNt/imetsampi s gerate rtha nthec urrnet dtaabaes SC/Ntimsetam pandt he adtabsae icnarntaioni s nto th elas topeend icnarntaion.

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

If hte tragetS CN/itmesatmp si int he ucrretn inacrnaiton ro a hcildi ncanratino whsoe barnchp oin tis fatert he ucrretn daatbas eSCNt henR ECOEVR DTAABAES tot he atrge tSCNt/ime .If hte tragetS CN/itmesatmp si ina chlid icnarntaionw hos ebracnh piont si proir t othec urrnet dtaabaes SC Nthe nFLAHSBAC KDATBAASEt o bfeoret he rbanc hpoitn. Nxet ues RMNA tor ese tthed ataabse ot th echidl inacrnaiton.F inally, ERCOVRE DAATBAS Eto hte tragetS CN/itme.

update : 20-08-2017
ORA-38793

ORA-38793 - cannot FLASHBACK the database to a future SCN/time
ORA-38793 - cannot FLASHBACK the database to a future SCN/time

  • ora-15113 : alias name 'string' refers to a directory
  • ora-07713 : sksamtd: could not mount archival device (SYS$MOUNT failure)
  • ora-08465 : input mask contains more than 32 characters
  • ora-12951 : Attempt to change default permanent tablespace to temporary
  • ora-08189 : cannot flashback the table because row movement is not enabled
  • ora-00331 : log version string incompatible with ORACLE version string
  • ora-14257 : cannot move partition other than a Range or Hash partition
  • ora-38312 : original name is used by an existing object
  • ora-01192 : must have at least one enabled thread
  • ora-10282 : Inhibit signalling of other backgrounds when one dies
  • ora-09750 : pw_attachPorts: port_rename failed.
  • ora-30352 : inconsistent numeric precision or string length
  • ora-28577 : argument string of external procedure string has unsupported datatype string
  • ora-27417 : BYWEEKNO clause is only supported when FREQ=YEARLY
  • ora-13187 : subdivision failed
  • ora-25189 : illegal ALTER TABLE option for an index-organized table
  • ora-38465 : failed to create the privilege checking trigger due to: string
  • ora-22629 : OCIAnyData is null
  • ora-38902 : errors in array insert exceed string
  • ora-19727 : cannot plug data [string] at level string into database running Oracle string
  • ora-02769 : Setting of handler for SIGTERM failed
  • ora-28514 : heterogeneous database link initialization could not convert system date
  • ora-16128 : User initiated stop apply successfully completed
  • ora-12989 : invalid value for checkpoint interval
  • ora-31025 : Invalid document element
  • ora-09934 : Link of current password file to old failed.
  • ora-32035 : unreferenced query name defined in WITH clause
  • ora-19019 : Invalid context passed to DBMS_XMLGEN.GETXML
  • ora-01488 : invalid nibble or byte in the input data
  • ora-06721 : TLI Driver: spurious client req
  • 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.