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

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

  • ora-16002 : database already open for read-write access by another instance
  • ora-09859 : sfngat: the input file name is not in the autobackup OMF format
  • ora-12826 : hung parallel query server was killed
  • ora-33313 : (DELDENT05) workspace object cannot be deleted because it is the target of an external partition of a partitioned variable.
  • ora-01594 : attempt to wrap into rollback segment (string) extent (string) which is being freed
  • ora-06926 : CMX: T_ERROR during read data
  • ora-06433 : ssaio: LSEEK error, unable to seek to requested block.
  • ora-20000 : %s
  • ora-27122 : unable to protect memory
  • ora-01481 : invalid number format model
  • ora-06927 : CMX: T_DATAIN received before all data written
  • ora-19672 : media management software returned invalid file status
  • ora-10382 : parallel query server interrupt (reset)
  • ora-01946 : DEFAULT TABLESPACE already specified
  • ora-40203 : model string does not exist
  • ora-01470 : In-list iteration does not support mixed operators
  • ora-15002 : parameter LOCK_NAME_SPACE exceeds limit of string characters
  • ora-38460 : filtering based on datatype "string" not supported for XML Tags
  • ora-24772 : Cannot mix tightly-coupled and loosely-coupled branches
  • ora-30461 : 'string.string' cannot be refreshed because it is marked DISABLED
  • ora-00405 : compatibility type "string"
  • ora-18008 : cannot find OUTLN schema
  • ora-32336 : cannot use USING NO INDEX to create materialized view "string"."string"
  • ora-04014 : descending sequences that CYCLE must specify MINVALUE
  • ora-00000 : normal, successful completion
  • ora-13198 : Spatial error: string
  • ora-25407 : connection terminated
  • ora-07552 : sftget: $GET failure
  • ora-19680 : some blocks not recovered. See trace file for details
  • ora-28332 : cannot have more than one password for the encryption key
  • 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.