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 : 23-06-2017

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

  • ora-35587 : (SQLOUT20) The nesting of table functions and SQL commands has exceeded the maximum of number levels.
  • ora-24397 : error occured while trying to free connections
  • ora-31619 : invalid dump file "string"
  • ora-07219 : slspool: unable to allocate spooler argument buffer.
  • ora-00221 : error on write to control file
  • ora-36269 : (XSCGMDLAGG10) 'workspace object' does not exist or is not a dimension.
  • ora-13644 : The user "string" is invalid.
  • ora-36849 : (XSLMGEN19) AW owner does not match View token owner
  • ora-01672 : control file may be missing files or have extra ones
  • ora-29866 : cannot create domain index on a column of index-organized table
  • ora-39071 : Value for string is badly formed.
  • ora-01244 : unnamed datafile(s) added to control file by media recovery
  • ora-00286 : no members available, or no member contains valid data
  • ora-38433 : index "string" could not be maintained due to "string"
  • ora-36681 : (XSDPART19) Partitions string and string are out of order.
  • ora-16818 : Fast-Start Failover suspended
  • ora-02434 : cannot enable unique(string) - unique key not defined for table
  • ora-23335 : priority group string already exists
  • ora-12735 : Instant Client Light: unsupported client character set string
  • ora-02852 : Invalid critical-section time out value
  • ora-25400 : must replay fetch
  • ora-25409 : failover happened during the network operation,cannot continue
  • ora-19565 : BACKUP_TAPE_IO_SLAVES not enabled when duplexing to sequential devices
  • ora-31432 : invalid source table
  • ora-27375 : valid agent name must be specified for secure queues
  • ora-01679 : database must be mounted EXCLUSIVE and not open to activate
  • ora-24385 : Application context size or index is not valid
  • ora-03243 : destination dba overlaps with existing control information
  • ora-08453 : more than one V symbol specified in picture mask
  • ora-24788 : cannot switch to specified transaction (server type)
  • 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.