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 : 16-08-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-37021 : (XSMULTI02) Object workspace object is not acquired.
  • ora-04000 : the sum of PCTUSED and PCTFREE cannot exceed 100
  • ora-02297 : cannot disable constraint (string.string) - dependencies exist
  • ora-33018 : (XSAGDNGL08) In AGGMAP workspace object, the data type of workspace object must be TEXT, not string.
  • ora-32314 : REFRESH FAST of "string"."string" unsupported after deletes/updates
  • ora-38612 : FI item length cannot exceed half of one database block.
  • ora-27199 : skgfpst: sbtpcstatus returned error
  • ora-00822 : MMAN process terminated with error
  • ora-13126 : unable to determine class for spatial table string
  • ora-12988 : cannot drop column from table owned by SYS
  • ora-08448 : syntax error in DECIMAL-POINT environment clause
  • ora-34802 : (OCI11) OLAP OCI operation caused ROLLBACK past an UPDATE of an attached analytic workspace. Current operation canceled.
  • ora-00404 : Convert file not found: 'string'
  • ora-25203 : invalid value string, DELAY should be non-negative
  • ora-26090 : row is in partial state
  • ora-24411 : Session pool already exists.
  • ora-06700 : TLI Driver: incorrect message type from host
  • ora-31504 : cannot alter or drop predefined change source
  • ora-12590 : TNS:no I/O buffer
  • ora-03279 : invalid INSTANCE specified
  • ora-25463 : table alias not specified
  • ora-19221 : XP0001 - XQuery static context component string not initialized
  • ora-12040 : master rollback segment option not support by master site string
  • ora-12413 : labels do not belong to the same policy
  • ora-24816 : Expanded non LONG bind data supplied after actual LONG or LOB column
  • ora-07684 : sou2os: supervisor stack reset error
  • ora-13389 : unable to compute buffers or intersections in analysis function
  • ora-01529 : error closing file 'string'
  • ora-07242 : slembfn: translation error, unable to translate error file name.
  • ora-33918 : (MAKEDCL33) You cannot define a surrogate of dimension workspace object because it is a 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.