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 : 26-06-2017

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

  • ora-37111 : Unable to load the OLAP API sharable library: (string)
  • ora-15155 : version incompatible with the cluster
  • ora-04087 : cannot change the value of ROWID reference variable
  • ora-23321 : Pipename may not be null
  • ora-01212 : MAXLOGMEMBERS may not exceed string
  • ora-24090 : at least one protocol must be enabled
  • ora-24505 : cannot change character set id on the handle
  • ora-19700 : device type exceeds maximum length of string
  • ora-19716 : error processing format string to generate name for backup
  • ora-30196 : reserved for future use
  • ora-19645 : datafile string: incremental-start SCN is prior to creation SCN string
  • ora-16161 : Cannot mix standby and online redo log file members for group string
  • ora-36222 : (XSLPDSC03) duplicate IGNORE or DENSE information for dimension workspace object
  • ora-09982 : skxfqddrg: Error Removing a page from the SDI buffer pool
  • ora-34901 : (PPWKDAYS01) Blank lines are not allowed in the DAYNAMES option.
  • ora-02095 : specified initialization parameter cannot be modified
  • ora-06920 : CMX: getbrkmsg illegal datatype
  • ora-22321 : method does not return any result
  • ora-19503 : cannot obtain information on device, name="string", type="string", parms="string"
  • ora-19958 : potential deadlock involving DIAG process
  • ora-34359 : (MXDSS11) string appears twice in the alias list.
  • ora-09826 : SCLIN: cannot initialize atomic latch.
  • ora-38468 : column "string" is not identified as a column storing expressions.
  • ora-23290 : This operation may not be combined with any other operation
  • ora-31154 : invalid XML document
  • ora-38778 : Restore point 'string' already exists.
  • ora-31011 : XML parsing failed
  • ora-10946 : trace name context forever
  • ora-00070 : command string is not valid
  • ora-26033 : column string.string encryption properties differ for source or target table
  • 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.