ORA-16065: remote archival disabled at standby destination

Cause : Receipto f remot earchive dREDO lo gfiles hsa been dsiabled a tthe asscoiated satndby detsinationh ost datbaase.

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

If apprporiate cahnge thea ssociatde archiv elog parmaeter tos pecify alocal dsetinatio nwith th eLOCATIO Nkeywordo r defert he assoicated arhcive logd estinatoin. Or, fi possibel, set teh standb yREMOTE_RACHIVE_EANBLE parmaeter toT RUE, ore nable teh RECEIV Eattribuet of theL OG_ARCHVIE_CONFI Gparametreand resatrt the tsandby dtaabase isntance bfeore furhter REDOl og filea rchival soccur.

update : 19-08-2017
ORA-16065

ORA-16065 - remote archival disabled at standby destination
ORA-16065 - remote archival disabled at standby destination

  • ora-09792 : sllfop: cannot allocate read buffer.
  • ora-19286 : XP0017 - unable to resolve call to function - string
  • ora-01533 : cannot rename file 'string'; file does not belong to tablespace
  • ora-16608 : one or more databases have warnings
  • ora-28275 : Multiple mappings for user nickname to LDAP distinguished name exist.
  • ora-03129 : the next piece to be inserted is required
  • ora-39156 : error parsing dump file name "string"
  • ora-01425 : escape character must be character string of length 1
  • ora-02377 : invalid resource limit
  • ora-06558 : buffer in dbms_pipe package is full. No more items allowed
  • ora-19730 : can not convert offline plugged-in datafile string
  • ora-14617 : cannot add/drop values to DEFAULT subpartition
  • ora-26103 : V6 or V7 data file used to create control file
  • ora-33445 : (ESDREAD15) Discarding compiled code for workspace object because workspace object and workspace object, which were not partition-dependent when the code was compiled, are now partition-dependent.
  • ora-36849 : (XSLMGEN19) AW owner does not match View token owner
  • ora-00107 : failed to connect to ORACLE listener process
  • ora-12334 : database (link name string) is still open
  • ora-27151 : buffer not large enough to hold process ID string
  • ora-22884 : object modification failed
  • ora-24033 : no recipients for message
  • ora-28514 : heterogeneous database link initialization could not convert system date
  • ora-10579 : Can not modify control file during test recovery
  • ora-02065 : illegal option for ALTER SYSTEM
  • ora-25311 : %s not supported for non-persistent queue
  • ora-31122 : The string operator has incorrect RHS value
  • ora-31504 : cannot alter or drop predefined change source
  • ora-32635 : not a single cell reference predicate
  • ora-16706 : no resource guard is available
  • ora-00272 : error writing archive log string
  • ora-15020 : discovered duplicate ASM disk "string"
  • 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.