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

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

  • ora-00386 : use_indirect_data_buffers not supported
  • ora-07709 : sksaprs: archiving to a remote host is not allowed
  • ora-09369 : Windows 3.1 Two-Task driver bad instance handle
  • ora-09775 : osnmrs: reset protocol error
  • ora-16730 : error executing dbms_logstdby.skip_txn procedure
  • ora-24323 : value not allowed
  • ora-06569 : Collection bound by bind_array contains no elements
  • ora-01953 : command no longer valid, see ALTER USER
  • ora-29523 : authorization error for unknown referenced name
  • ora-25290 : Cannot complete operation on queue string with existing messages
  • ora-16165 : LGWR failed to hear from network server
  • ora-00724 : ALTER DATABASE CONVERT command has been de-supported
  • ora-02229 : invalid SIZE option value
  • ora-31100 : XDB Locking Internal Error
  • ora-38708 : not enough space for first flashback database log file
  • ora-00267 : name of archived log file not needed
  • ora-22629 : OCIAnyData is null
  • ora-22630 : attribute [string] is null or it is not well-formed
  • ora-37038 : (XSMLTDCL04) You cannot change definitions of objects in analytic workspace string because it is attached in MULTI mode.
  • ora-37044 : (XSACQUIRE_OLDGEN) Cannot acquire object workspace object without resync.
  • ora-01549 : tablespace not empty, use INCLUDING CONTENTS option
  • ora-01233 : file string is read only - cannot recover using backup control file
  • ora-22933 : cannot change object with type or table dependents
  • ora-19752 : block change tracking is already enabled
  • ora-25183 : index-organized table top index segment is in a different tablespace
  • ora-25210 : invalid value for RELATIVE_MSGID, no message in queue with that msgid
  • ora-14003 : GLOBAL clause contradicts previosly specified LOCAL clause
  • ora-02800 : Requests timed out
  • ora-24039 : Queue string not created in queue table for multiple consumers
  • ora-28270 : Malformed user nickname for password authenticated global user.
  • 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.