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 : 29-06-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-25106 : only one of PARALLEL or NOPARALLEL clause may be specified
  • ora-19272 : XQ0052 - invalid atomic value in attribute or element constructor
  • ora-22919 : dangling REF error or lock object failed for no wait request
  • ora-01193 : file string is not the same file seen at start of recovery
  • ora-02375 : conversion error loading table string.string partition string
  • ora-36833 : (XSLMGEN03) View token cannot be blank
  • ora-10706 : Print out information about global enqueue manipulation
  • ora-00320 : cannot read file header from log string of thread string
  • ora-06929 : CMX: error when sending ORACLE_SID
  • ora-25311 : %s not supported for non-persistent queue
  • ora-01901 : ROLLBACK keyword expected
  • ora-23307 : replicated schema string already exists
  • ora-24911 : Cannot start listener thread at specified port
  • ora-01081 : cannot start already-running ORACLE - shut it down first
  • ora-13868 : Instance-wide SQL tracing on instance string is not enabled
  • ora-12916 : Cannot use default permanent tablespace with this release
  • ora-06815 : TLI Driver: could not link SPX and IPX streams
  • ora-24389 : Invalid scrollable fetch parameters
  • ora-30370 : set operators are not supported in this context
  • ora-29907 : found duplicate labels in primary invocations
  • ora-30331 : summary does not exist
  • ora-08187 : snapshot expression not allowed here
  • ora-28157 : Proxy user 'string' forbidden to set role 'string' for client 'string'
  • ora-09953 : scggc: unexpected return of a lock convert
  • ora-24072 : cannot execute MIGRATE_QUEUE_TABLE procedure; must own queue table
  • ora-26063 : Can not flashback to specified SCN value - Wrap: string Base: string.
  • ora-15132 : block string of file string in diskgroup string could not be written
  • ora-28164 : REVOKE already specified
  • ora-03130 : the buffer for the next piece to be fetched is required
  • ora-16590 : Data Guard configuration does not contain a primary database
  • 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.