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 : 25-05-2017

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

  • ora-12505 : TNS:listener does not currently know of SID given in connect descriptor
  • ora-15061 : ASM operation not supported [string]
  • ora-15028 : ASM file 'string' not dropped; currently being accessed
  • ora-13509 : error encountered during updates to a AWR table
  • ora-01881 : timezone region id number is invalid
  • ora-12457 : security label exceeded maximum allowable length
  • ora-32113 : Null object passed
  • ora-30766 : cannot modify scope for a REF column with a REFERENCES constraint
  • ora-10616 : Operation not allowed on this tablespace
  • ora-08451 : invalid specification of DB in picture mask
  • ora-12158 : TNS:could not initialize parameter subsystem
  • ora-25447 : encountered errors during evaluation of rule string.string
  • ora-02738 : osnpwrtbrkmsg: incorrect number of bytes written
  • ora-01866 : the datetime class is invalid
  • ora-02792 : Unable to fstat() a file being used for asynchronous I/O.
  • ora-36970 : (XSRELTBL12) workspace object must be a self-relation.
  • ora-13914 : Threshold notification failed.
  • ora-14156 : invalid number of subpartitions specified in [SUBPARTITIONS | SUBPARTITION TEMPLATE] clause
  • ora-30768 : Cannot evaluate pipelined function
  • ora-25187 : specified exceptions table form incorrect
  • ora-39310 : call to DBMS_SCHEMA_COPY.CLEAN_FAILED_CLONE is not legal
  • ora-12324 : cannot use the ROM: link type on a private database link
  • ora-31679 : Table data object string has long columns, and longs can not be loaded/unloaded using a network link
  • ora-29927 : error in executing the ODCIStatsCollect / ODCIStatsDelete routine
  • ora-30463 : 'string' is not a detail table of any summary
  • ora-28652 : overflow segment attributes cannot be specified
  • ora-19704 : file name exceeds maximum length of string
  • ora-12074 : invalid memory address
  • ora-13381 : table:string not found in network:string
  • ora-24386 : statement/server handle is in use when being freed
  • 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.