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 : 20-08-2017
ORA-16814

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

  • ora-29662 : Unable to find a field that matches one or more of the attributes
  • ora-28508 : invalid value string for Heterogeneous Services initialization parameter string
  • ora-38486 : FUNCTION/PACKAGE/TYPE already exists for the attribute set
  • ora-32403 : cannot use new values from mv log on "string"."string"
  • ora-02163 : invalid value for FREELIST GROUPS
  • ora-07400 : slemtr: translated name for the message file is too long.
  • ora-36820 : (XSLMINFO00) The LIMITMAPINFO function encountered an error while parsing the LIMITMAP.
  • ora-12574 : TNS:redirection denied
  • ora-36908 : (XSAGDNGL46) In AGGMAP workspace object, MODEL workspace object has the repeating dimension with the previous model.
  • ora-12520 : TNS:listener could not find available handler for requested type of server
  • ora-01226 : file header of log member is inconsistent with other members
  • ora-07700 : sksarch: interrupt received
  • ora-13284 : failure to copy geometry object for conversion in place
  • ora-00476 : RECO process terminated with error
  • ora-19287 : XP0017 - invalid number of arguments to function - string:string
  • ora-27025 : skgfqsbi: invalid media manager context area size
  • ora-17610 : file 'string' does not exist and no size specified
  • ora-01254 : cannot end online backup - file string in recovery manager backup
  • ora-00403 : %s (string) is not the same as other instances (string)
  • ora-22287 : invalid or modified directory occurred during string operation
  • ora-30358 : summary and materialized view are not in same schema
  • ora-32809 : foreign queue string is already registered
  • ora-07440 : WMON process terminated with error
  • ora-15068 : maximum number of diskgroups string already mounted
  • ora-24388 : Unsupported functionality in fast path mode
  • ora-25287 : Invalid value string, string should be non-negative
  • ora-10382 : parallel query server interrupt (reset)
  • ora-28239 : no key provided
  • ora-38725 : specified name "string" does not match actual "string"
  • ora-06955 : Number of database servers exceed limit
  • 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.