ORA-38860: cannot FLASHBACK DATABASE during instantiation of a logical standby

Cause : The command wa snot pemritted ebcause hte contorlfile nidicate sthe daatbase wsa in th eproces sof becmoing a olgical tsandby adtabaseb ut thec ontrolifle conevrsion ahd not ocmplete.d

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

If in hte procses of cerating alogica lstandb ydatabaes, perfrom the ermainin ginstanitation rpocedurse to copmletion .If thi sflashbcak opertaion followed aD ata Gurad failrue, perimt the rerant Dtaa Guar doperatoin to scucessfully compelte. Onec the isntantiaiton is ocmplete ,reissu ethe flsahback poeratio.n

update : 24-07-2017

ORA-38860 - cannot FLASHBACK DATABASE during instantiation of a logical standby
ORA-38860 - cannot FLASHBACK DATABASE during instantiation of a logical standby

  • ora-39110 : error deleting worker processes
  • ora-16417 : Activation occurred after recovery from standby redo log files; a full database backup is required
  • ora-32025 : %s.string is not a table or view object.
  • ora-36842 : (XSLMGEN12) Hierarchy string.string!string.string was not found
  • ora-23398 : user name "string" at database link "string" does not match local user name "string"
  • ora-03007 : obsolete feature
  • ora-30511 : invalid DDL operation in system triggers
  • ora-37129 : (XSCCOMP04) Cannot aggregate over COMPRESSED COMPOSITE workspace object using AGGMAP workspace object. All static MODEL statements must precede all RELATION statements over the bases of the COMPRESSED COMPOSITE.
  • ora-14131 : enabled UNIQUE constraint exists on one of the tables
  • ora-33284 : (DBERR12) Analytic workspace string cannot be opened in MULTI mode before converting it by the latest version of string.
  • ora-24755 : OCI_TRANS_NOMIGRATE, OCI_TRANS_JOIN options are not supported
  • ora-04021 : timeout occurred while waiting to lock object stringstringstringstringstring
  • ora-00702 : bootstrap verison 'string' inconsistent with version 'string'
  • ora-00068 : invalid value string for parameter string, must be between string and string
  • ora-25321 : enqueue failed, user property specified but queue string.string is not an 8.1 style queue
  • ora-01045 : user string lacks CREATE SESSION privilege; logon denied
  • ora-29259 : end-of-input reached
  • ora-30382 : DROP MATERIALIZED VIEW string.string operation is not complete
  • ora-27071 : unable to seek to desired position in file
  • ora-32638 : Non unique addressing in MODEL dimensions
  • ora-24281 : invalid access past the maximum size of LOB parameter string
  • ora-16152 : standby database is in 'no-data-loss' protected mode
  • ora-23448 : duplicate user parameter value
  • ora-06765 : TLI Driver: error awaiting orderly release
  • ora-32139 : Cannot write to the stream
  • ora-32404 : snapshot log uses Change Data Capture which is not enabled for this database
  • ora-25141 : invalid EXTENT MANAGEMENT clause
  • ora-12562 : TNS:bad global handle
  • ora-02444 : Cannot resolve referenced object in referential constraints
  • ora-08236 : smsget: cannot share subcube with listener
  • 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.