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 |
QSM-00776: the user-defined workload string is missing the following column: string
DRG-11723: phrase cannot be NULL
DRG-50949: too many SQEs
ORA-31221: DBMS_LDAP: PL/SQL - Invalid LDAP SSL wallet passwd.
TNS-12229: TNS:Interchange has no more free connections
PLS-00418: array bind type must match PL/SQL table row type
ORA-02715: osnpgetbrkmsg: message from host had incorrect message type
PCC-02203: found end of file when not expected
ORA-28109: the number of related policies has exceeded the limit of 16
NNC-00413: general failure
ORA-33456: (ESDREAD08) Discarding compiled code for workspace object because number is a(n) string, which string did not expect to find in a compiled program.
ORA-29843: indextype should support atleast one operator