ORA-16709: standby archived log location settings conflict with flash recovery area

Cause : The flash recovery area was already set up on the standby database for storing incoming archived logs from the primary database. In this case, the StandbyArchiveLocation and AlternateLocation properties should not be used for setting up a standby archived log location. The Data Guard broker raised this error because it detected one of the following: (1) the user attempted to use the StandbyArchiveLocation or AlternateLocation properties to set up a standby archived log location; (2) On the standby database, a local destination corresponding to the StandbyArchiveLocation or AlternateLocation property was still set up to store archived logs from the primary database.

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

If you get this error when trying to set property StandbyArchiveLocation or AlternateLocation (case (1) above), avoid setting these properties. If you get this error after a broker health check (case (2) above), reenable the standby database to clear the error.

update : 24-05-2017
ORA-16709

ORA-16709 - standby archived log location settings conflict with flash recovery area
ORA-16709 - standby archived log location settings conflict with flash recovery area

  • ora-31448 : invalid value for change_source
  • ora-30461 : 'string.string' cannot be refreshed because it is marked DISABLED
  • ora-13501 : Cannot drop SYSAUX tablespace
  • ora-38741 : Formatted blocks value string is not valid.
  • ora-25438 : invalid variable name: string
  • ora-31055 : A null XMLType element cannot be inserted into RESOURCE_VIEW
  • ora-28602 : statement not permitted on tables containing bitmap indexes
  • ora-19109 : RETURNING keyword expected
  • ora-31094 : incompatible SQL type "string" for attribute or element "string"
  • ora-16716 : clearing parameter LOG_ARCHIVE_DEST failed
  • ora-00036 : maximum number of recursive SQL levels (string) exceeded
  • ora-07229 : slcpuc: error in getting number of CPUs.
  • ora-31224 : DBMS_LDAP: invalid LDAP session
  • ora-36847 : (XSLMGEN17) AW name is blank
  • ora-27154 : post/wait create failed
  • ora-25106 : only one of PARALLEL or NOPARALLEL clause may be specified
  • ora-22894 : cannot add constraint on existing unscoped REF columns of non-empty tables
  • ora-02449 : unique/primary keys in table referenced by foreign keys
  • ora-08120 : Need to create SYS.IND_ONLINE$ table in order to (re)build index
  • ora-15109 : conflicting protection attributes specified
  • ora-39028 : cannot restart job from string state
  • ora-19753 : error writing to change tracking file
  • ora-09743 : smscre: could not attach shared memory.
  • ora-31199 : Warning in processing file string
  • ora-12011 : execution of string jobs failed
  • ora-06135 : NETTCP: connection rejected; server is stopping
  • ora-07552 : sftget: $GET failure
  • ora-16194 : Modifying DB_UNIQUE_NAME requires SID='*' qualifier
  • ora-14001 : LOCAL clause contradicts previosly specified GLOBAL clause
  • ora-01574 : maximum number of concurrent transactions exceeded
  • 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.