ORA-16814: incorrect log transport setting for standby's
AlternateLocation
Answer / guest
Cause: The Data Guard broker detected that the log transport
setting for some 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 has an ALTERNATE
setting; (2) the AlternateLocation property is not empty but
the log transport to the standby has no ALTERNATE setting;
(3) the AlternateLocation property does not match the
ALTERNATE setting in the log transport. The mismatch may
includes service string, directory specification of the
alternate location, or SP_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 for archived
logs, but the log transport to the standby still has an
ALTERNATE setting for the AlternateLocation. Data Guard
broker logs provide further details on which of the above
cases causes the error.
Action: Re-enable the primary database to clear the error.
Please add more information about this Error
| Is This Answer Correct ? | 0 Yes | 0 No |
ORA-01278: error creating file 'string'
ORA-23416: table "string"."string" does not contain a primary key constraint
ORA-14152: invalid number of partitions specified in PARTITIONS clause
RMAN-08117: channel string: the autobackup does not contain an SPFILE
RMAN-06451: proxy copy handle=string recid=string stamp=string
PCC-00014: Undeclared SQL Identifier "string" at line number in file string
ORA-26021: index string.string partition string loaded successfully with string keys
PCC-00011: Already in a declare section at line number in file string
ORA-02265: cannot derive the datatype of the referencing column
ORA-39082: Object type string created with compilation warnings
ORA-01986: OPTIMIZER_GOAL is obsolete
ORA-00203: using the wrong controlfiles