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-07216: slghst: gethostname error, unable to get name of current host.
NNL-00961: Cache checkpoints: number
DRG-50924: PL/SQL inside PL/SQL not supported
ORA-12010: cannot create materialized view log on table owned by SYS
LPX-00268: invalid access method ~1d, must be 0 to ~2d
RMAN-06445: cannot connect to recovery catalog after NOCATALOG has been used
NNL-00046: Name string exceeds DN template depth
ORA-35071: (QFHEAD06) EIF file string cannot be imported because analytic workspace string has not been upgraded to version string.
DRG-50939: parser not set
ORA-06540: PL/SQL: compilation error
NZE-29237: the cryptographic engine could not finish the algorithm
RMAN-03012: fatal error during compilation of command