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 : 26-04-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-13351 : two or more rings of a complex polygon overlap
  • ora-29827 : keyword USING is missing
  • ora-06720 : TLI Driver: SID lookup failure
  • ora-16006 : audit_trail destination incompatible with database open mode
  • ora-13292 : incorrect ARC_TOLERANCE specification
  • ora-09856 : smpalo: vm_allocate error while allocating pga.
  • ora-24434 : OCIStmtRelease called before OCIStmtPrepare2.
  • ora-24373 : invalid length specified for statement
  • ora-29383 : all leaves of top-plan string must be consumer groups
  • ora-12537 : TNS:connection closed
  • ora-00740 : datafile size of (string) blocks exceeds maximum file size
  • ora-25407 : connection terminated
  • ora-08235 : smsget: listener not on this node
  • ora-38416 : A stored attribute may not be longer then 300 characters.
  • ora-30932 : Reference node 'string' not contained in specified parent node 'string'
  • ora-00222 : operation would reuse name of a currently mounted control file
  • ora-13334 : LRS segments not connected
  • ora-19830 : error from target database: string
  • ora-36761 : (XSLANGDM01) Analytic workspace string already contains a dimension (%J) with the string property.
  • ora-30018 : Create Rollback Segment failed, USN string is out of range
  • ora-14155 : missing PARTITION or SUBPARTITION keyword
  • ora-01136 : specified size of file string (string blocks) is less than original size of string blocks
  • ora-02226 : invalid MAXEXTENTS value (max allowed: string)
  • ora-32743 : command cannot be executed on remote instance
  • ora-29307 : datafile string error, string
  • ora-23445 : missing template site
  • ora-38607 : FI minimum and maximum itemset length not between [1, string]
  • ora-12521 : TNS:listener does not currently know of instance requested in connect descriptor
  • ora-33304 : (DBVALID02) Note: Record number was allocated but not used. This can result in wasted space.
  • ora-33625 : (FRASSIGN02) You cannot use the APPEND keyword with concat dimension workspace object.
  • 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.