ORA-16814: incorrect redo transport setting for AlternateLocation for standby database

Cause : The Data Guard broker detected that an incorrect redo transport setting for a standby database's AlternateLocation property. The incorrect setting could be one of the following: one of the following: (1) the AlternateLocation property is empty but the log transport to the standby database has an ALTERNATE setting; (2) the AlternateLocation property is not empty but the log transport to the standby database has no ALTERNATE setting; (3) the AlternateLocation property does not match the ALTERNATE setting in the redo transport. The mismatch may include service string, directory specification of the alternate location, or the DB_UNIQUE_NAME attribute; (4) the log_archive_dest_state_n parameter corresponding to the alternate location is not set to ALTERNATE; (5) the flash recovery area is being used by the standby database for archived logs, but the redo transport to the standby database still has an ALTERNATE setting for the AlternateLocation. Data Guard broker logs provide more details on which of the above cases causes the error.

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

Reenable the primary database to clear the error.

update : 29-04-2017

ORA-16814 - incorrect redo transport setting for AlternateLocation for standby database
ORA-16814 - incorrect redo transport setting for AlternateLocation for standby database

  • ora-31101 : Token "string" not given while locking resource "string"
  • ora-02437 : cannot validate (string.string) - primary key violated
  • ora-01319 : Invalid Logminer session attribute
  • ora-21604 : property [string] is not a property of transient or value instances
  • ora-28602 : statement not permitted on tables containing bitmap indexes
  • ora-28592 : agent control utility: agent SID not set
  • ora-36168 : (XSMXAGGR10) COUNTVAR variable workspace object must have the same dimensionality as workspace object
  • ora-29515 : exit called from Java code with status string
  • ora-25124 : Database link name not allowed.
  • ora-16549 : invalid string
  • ora-29520 : name string resolved to a class in schema string that could not be accessed
  • ora-00211 : control file does not match previous control files
  • ora-08331 : Wait operation timed out
  • ora-09877 : sstascre: shmget error, unable to get a shared memory segment.
  • ora-02285 : duplicate START WITH specifications
  • ora-30979 : Partitioned XML Index not yet supported.
  • ora-22997 : VARRAY | OPAQUE stored as LOB is not specified at the table level
  • ora-29858 : error occurred in the execution of ODCIINDEXALTER routine
  • ora-24502 : codepoint length overflows
  • ora-25133 : duplicate SINGLE TABLE option specified
  • ora-32114 : Cannot perform operation on a null LOB
  • ora-07268 : szguns: getpwuid error.
  • ora-13005 : recursive HHCODE function error
  • ora-16744 : the DG_CONFIG list of LOG_ARCHIVE_CONFIG parameter is full
  • ora-22958 : This operation is not allowed in check constraints or triggers
  • ora-07468 : spwat: mset error, unable to set semaphore.
  • ora-07216 : slghst: gethostname error, unable to get name of current host.
  • ora-34360 : (MXDSS15) number other users writing
  • ora-02093 : TRANSACTIONS_PER_ROLLBACK_SEGMENT(string) more than maximum possible(string)
  • ora-00750 : database has been previously mounted and dismounted
  • 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.