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 |
TNS-01099: %s * string * string * string * number
ORA-15037: disk 'string' is smaller than mimimum of string MBs
ORA-30199: reserved for future use
ORA-14261: partition bound may not be specified when adding this Hash partition
ORA-31635: unable to establish job resource synchronization
ORA-29295: invalid mime header tag
ORA-27087: unable to get share lock - file not readable
ORA-25209: invalid value string, EXPIRATION should be non-negative or NEVER
LFI-01516: read() failed (OSD return value = string) in string.
PLS-01714: ANSI expects a column name not a literal value here
ORA-14523: Cannot co-locate [sub]partition of string string with table [sub]partition because string block size [string] does not match table block size [string]
ORA-27212: some entrypoints in Media Management Library are missing