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-19334: Invalid column specification for CREATE_DBURI operator
ORA-07236: slemop: open error.
ORA-01306: dbms_logmnr.start_logmnr() must be invoked before selecting from v$logmnr_contents
PLS-01505: ALTER is non-ANSI
SQL*Loader-00700: Out of memory while performing essential allocations [number]
PLS-01711: A SELECT statement may not contain ORDER_BY, HAVING, or GROUP_BY clause
NNO-00623: setting auto-refresh retry interval to number seconds
ORA-07847: sllfop: $CONNECT failure
SQL*Loader-00943: incorrect datafile string specified for table string partition string
QSM-00505: syntax error
ORA-00356: inconsistent lengths in change description
ORA-16756: Resource guard could not open standby readonly