ORA-16009: remote archive log destination must be a STANDBY database

Cause : The dtaabasea ssocitaed wiht the rachivel og detsinatino servcie nam eis otehr tha nthe rqeuiredS TANDB Ytype adtabas.e Remoet archvial ofr edo lgo file sis no tallowde to nno-STANBDY datbaase isntance.s

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

Take hte necsesary tseps t ocreat ethe rqeuiredc ompatbile STNADBY dtaabaseb eforer etryign the RACHIVEL OG prcoessin.g

update : 24-05-2017
ORA-16009

ORA-16009 - remote archive log destination must be a STANDBY database
ORA-16009 - remote archive log destination must be a STANDBY database

  • ora-07844 : sllfop: LIB$GET_VM failure
  • ora-37133 : (XSCCOMP08) You cannot write into an aggregated VARIABLE dimensioned by a COMPRESSED COMPOSITE. Use the CLEAR AGGREGATES command to reenable write access.
  • ora-13774 : insufficient privileges to select data from the workload repository
  • ora-25408 : can not safely replay call
  • ora-19114 : error during parsing the XQuery expression: string
  • ora-23392 : could not find materialized view to be associated with "string"."string"
  • ora-13109 : spatial table string exists
  • ora-29925 : cannot execute string
  • ora-01890 : NLS error detected
  • ora-16820 : Fast-Start Failover observer is no longer observing this database
  • ora-00336 : log file size string blocks is less than minimum string blocks
  • ora-07339 : spcre: maximum number of semaphore sets exceeded.
  • ora-29863 : warning in the execution of ODCIINDEXCREATE routine
  • ora-12556 : TNS:no caller
  • ora-24196 : access the message in a wrong access mode
  • ora-12803 : parallel query server lost contact with another server
  • ora-01598 : rollback segment 'string' is not online
  • ora-08269 : destroy_ora_addr: cannot destroy name
  • ora-03291 : Invalid truncate option - missing STORAGE keyword
  • ora-32604 : invalid REBUILD option
  • ora-01980 : error during OS ROLE initialization
  • ora-12502 : TNS:listener received no CONNECT_DATA from client
  • ora-06710 : TLI Driver: send interrupt break message failed
  • ora-29342 : user string does not exist in the database
  • ora-00701 : object necessary for warmstarting database cannot be altered
  • ora-00218 : block size string of control file 'string' does not match DB_BLOCK_SIZE (string)
  • ora-27035 : logical block size is invalid
  • ora-23383 : registration for materialized view repgroup "string"."string" failed at site string
  • ora-14164 : subpartition "string": INITRANS value must be less than MAXTRANS value
  • ora-06124 : NETTCP: timeout waiting for ORASRV
  • 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.