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 : 17-08-2017

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-00356 : inconsistent lengths in change description
  • ora-01016 : This function can be called only after a fetch
  • ora-02255 : obsolete 7.1.5
  • ora-24083 : cannot specify remote subscribers for string QUEUE string
  • ora-01187 : cannot read from file string because it failed verification tests
  • ora-25406 : could not generate a connect address
  • ora-39046 : Metadata remap string has already been specified.
  • ora-32306 : updatable materialized views with user-defined types must use SELECT *
  • ora-10244 : make tranids in error msgs print as 0.0.0 (for testing)
  • ora-00473 : ARCH process terminated with error
  • ora-07257 : spdcr: translation error expanding program name.
  • ora-13264 : geometry identifier column string does not exist in table string
  • ora-24334 : no descriptor for this position
  • ora-30933 : Element 'string' may not appear at this point within parent 'string'
  • ora-02035 : illegal bundled operation combination
  • ora-19254 : XQ0034 - too many declarations for function string
  • ora-39154 : Objects from foreign schemas have been removed from import
  • ora-27504 : IPC error creating OSD context
  • ora-00566 : cannot request processor group - NUMA not enabled
  • ora-24402 : error occured while creating connections in the pool
  • ora-25002 : cannot create INSTEAD OF triggers on tables
  • ora-01657 : invalid SHRINK option value
  • ora-28653 : tables must both be index-organized
  • ora-00400 : invalid release value string for parameter string
  • ora-31037 : Invalid XML attribute name string
  • ora-02265 : cannot derive the datatype of the referencing column
  • ora-10584 : Can not invoke parallel recovery for test recovery
  • ora-00910 : specified length too long for its datatype
  • ora-27468 : "string.string" is locked by another process
  • ora-03250 : Cannot mark this segment corrupt
  • 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.