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 : 25-04-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-31502 : invalid number supplied for supplemental_processes
  • ora-30380 : REWRITE_TABLE does not exist
  • ora-09320 : szrfc: unable to obtain the list of valid OS roles
  • ora-31609 : error loading file "string" from file system directory "string"
  • ora-28007 : the password cannot be reused
  • ora-23463 : flavor incompatible with object "string"."string"
  • ora-31218 : DBMS_LDAP: PL/SQL - Invalid LDAP deleteoldrdn.
  • ora-19285 : FODC0002 - error retrieving resource
  • ora-13019 : coordinates out of bounds
  • ora-06011 : NETASY: dialogue too long
  • ora-30513 : cannot create system triggers of INSTEAD OF type
  • ora-36913 : (XSAGDNGL49) In AGGMAP workspace object, LOAD_STATUS object workspace object must be an undimensioned VALUESET over the relation dimension.
  • ora-06776 : TLI Driver: error sending parms
  • ora-38859 : instance string (thread string) is not ready to be disabled
  • ora-12004 : REFRESH FAST cannot be used for materialized view "string"."string"
  • ora-16651 : requirements not met for enabling Fast-Start Failover
  • ora-23453 : requested operation is not supported on top flavor
  • ora-31470 : asynchronous change tables must contain the RSID$ column
  • ora-12483 : label not in OS system accreditation range
  • ora-14177 : STORE-IN (Tablespace list) can only be specified for a LOCAL index on a Hash or Composite Range Hash table
  • ora-22132 : hexadecimal string does not correspond to a valid REF
  • ora-29972 : user does not have privilege to change/ create registration
  • ora-01928 : GRANT option not granted for all privileges
  • ora-22925 : operation would exceed maximum size allowed for a LOB value
  • ora-01208 : data file is an old version - not accessing current version
  • ora-03252 : initial extent size not enough for LOB segment
  • ora-23430 : argument "string" cannot be NULL or empty string
  • ora-16590 : Data Guard configuration does not contain a primary database
  • ora-28605 : bitmap indexes cannot be reversed
  • ora-00290 : operating system archival error occurred. See error below
  • 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.