ORA-16815: incorrect redo transport setting for AlternateLocation for standby database "string"

Cause : The Data Guard broker detected that the redo transport setting for the standby database regarding its AlternateLocation property value is incorrect. The incorrect setting could be 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 : 26-06-2017

ORA-16815 - incorrect redo transport setting for AlternateLocation for standby database "string"
ORA-16815 - incorrect redo transport setting for AlternateLocation for standby database "string"

  • ora-39036 : invalid metadata filter name string
  • ora-33625 : (FRASSIGN02) You cannot use the APPEND keyword with concat dimension workspace object.
  • ora-33100 : (APABBR02) Value 'number' is not valid for the workspace object option.
  • ora-24852 : protocol error during statement execution
  • ora-31500 : change source string is not a ManualLog change source
  • ora-01517 : log member: 'string'
  • ora-25407 : connection terminated
  • ora-01902 : SEGMENT keyword expected
  • ora-39137 : cannot specify a TABLE_EXISTS_ACTION of string for a job with no metadata
  • ora-02260 : table can have only one primary key
  • ora-36988 : (XSRELGID06) The related dimension of relation workspace object must be of type NUMBER.
  • ora-01206 : file is not part of this database - wrong database id
  • ora-06517 : PL/SQL: Probe error - string
  • ora-15037 : disk 'string' is smaller than mimimum of string MBs
  • ora-16150 : FINISH recovery performed on another, older standby database
  • ora-02841 : Server died on start up
  • ora-13361 : not enough sub-elements within a compound ETYPE
  • ora-14000 : only one LOCAL clause may be specified
  • ora-06533 : Subscript beyond count
  • ora-06812 : TLI Driver: could not read the ethernet driver's node address
  • ora-29846 : cannot create a local domain index on a string partitioned table
  • ora-32139 : Cannot write to the stream
  • ora-06122 : NETTCP: setup failure
  • ora-02229 : invalid SIZE option value
  • ora-00385 : cannot enable Very Large Memory with new buffer cache parameters
  • ora-31468 : cannot process DDL change record
  • ora-25232 : duplicate recipients specified for message
  • ora-27300 : OS system dependent operation:string failed with status: string
  • ora-29387 : no top-plans found in the pending area
  • ora-14251 : Specified subpartition does not exist
  • 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.