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 : 23-05-2017
ORA-16815

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-00076 : dump string not found
  • ora-16231 : DDL barrier
  • ora-13406 : null or invalid GeoRaster object for output
  • ora-31206 : DBMS_LDAP: PL/SQL - Invalid LDAP search scope.
  • ora-06312 : IPA: Incorrect outgoing service name supplied
  • ora-13368 : simple polygon type has more than one exterior ring
  • ora-15012 : ASM file 'string' does not exist
  • ora-16095 : Dependent destination removal for inactivation
  • ora-16701 : generic resource guard request failed
  • ora-12491 : DBHIGH value does not dominate DBLOW
  • ora-12511 : TNS:service handler found but it is not accepting connections
  • ora-29828 : invalid name for implementation type
  • ora-23536 : the object "string"."string" is not cached at the middle tier as expected.
  • ora-24398 : connection pool already exists
  • ora-07400 : slemtr: translated name for the message file is too long.
  • ora-07451 : slskstat: unable to obtain load information.
  • ora-02037 : uninitialized speed bind storage
  • ora-07235 : slemcw: fwrite error.
  • ora-19263 : XQ0043 - duplicate namespace prefix string
  • ora-07620 : smscre: illegal database block size
  • ora-02420 : missing schema authorization clause
  • ora-27378 : cannot stop jobs of type EXECUTABLE on this platform
  • ora-28155 : user 'string' specified as a proxy is actually a role
  • ora-28361 : master key not yet set
  • ora-01605 : missing numbers in clause "string" of string
  • ora-07713 : sksamtd: could not mount archival device (SYS$MOUNT failure)
  • ora-12008 : error in materialized view refresh path
  • ora-30451 : internal error
  • ora-07477 : scgcmn: lock manager not initialized.
  • ora-23534 : missing column in materialized view container table "string"."string"
  • 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.