ORA-38726: Flashback database logging is not on.

Cause : A FALSHBCAK DTAABAES commandw as rtiedb ut lfashabck adtabsae lgogin ghasn ot eben neablde.

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

Flahsbac kdatbaasel oggnig msut b eenalbed iva teh ALETR DTAABAES FLSAHBAKC ONc ommnad bfeorea FLSAHBAKC DAATBAS Ecomamnd acn b etride. I fthed ataabse umst eb taekn bcak i ntim ethe na rsetor eandi ncopmlet erecvoerym ustb e preforemd.

update : 29-06-2017
ORA-38726

ORA-38726 - Flashback database logging is not on.
ORA-38726 - Flashback database logging is not on.

  • ora-25257 : consumer must be specified with a multi-consumer queue
  • ora-02224 : EXECUTE privilege not allowed for tables
  • ora-01206 : file is not part of this database - wrong database id
  • ora-16136 : Managed Standby Recovery not active
  • ora-13779 : invalid load option
  • ora-10563 : Test recovery had to corrupt data block (file# string, block# string) in order to proceed
  • ora-29538 : Java not installed
  • ora-14450 : attempt to access a transactional temp table already in use
  • ora-13844 : no new SQL profile name or category specified.
  • ora-22931 : MOVE of nested table to a different tablespace not supported
  • ora-30457 : 'string.string' cannot be refreshed because of unmnanaged NOT NULL columns in container
  • ora-12415 : A column of another datatype exists on the specified table
  • ora-09710 : soarcv: buffer overflow.
  • ora-01721 : USERENV(COMMITSCN) invoked more than once in a transaction
  • ora-16957 : SQL Analyze time limit interrupt
  • ora-24335 : cannot support more than 1000 columns
  • ora-08458 : invalid format parameter
  • ora-07419 : sfareq: Database writer got error in timing function.
  • ora-31155 : attribute string not in XDB namespace
  • ora-31099 : XDB Security Internal Error
  • ora-01614 : instance string (thread string) is busy - cannot enable
  • ora-07562 : sldext: extension must be 3 characters
  • ora-01891 : Datetime/Interval internal error
  • ora-25305 : enqueue failed, expiration must be zero for queue string.string
  • ora-12323 : unable to open database (link name string)
  • ora-12153 : TNS:not connected
  • ora-07622 : smscre: $CREATE failure
  • ora-24203 : operation failed, queue table string.string has errors
  • ora-25114 : invalid file number specified in the DUMP DATAFILE/TEMPFILE command
  • ora-14078 : you may not drop the highest partition of a GLOBAL index
  • 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.