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 |
PLS-00511: a record may not contain a PL/SQL table of records
ORA-28046: Password change for SYS disallowed
ORA-01150: cannot prevent writes - file string has online backup set
ORA-15045: ASM file name 'string' is not in reference form
ORA-28506: parse error in data dictionary translation for string stored in string
NNC-00407: alias loop in name request
ORA-12202: TNS:internal navigation error
PCC-00055: Array "string" not allowed as bind variable at line number in file string
ORA-29707: inconsistent value string for initialization parameter string with other instances
ORA-30478: Specified dimension does not exist
ORA-32131: bind data type cannot be changed
TNS-12548: TNS:incomplete read or write