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-16195: DG_CONFIG requires DB_UNIQUE_NAME be explicitly defined
ORA-30023: Duplicate undo tablespace specification
DRG-11701: thesaurus string does not exist
LRM-00120: 'string' is not a legal Oracle number for 'string'
ORA-36290: (EIFMAKEF14) You cannot export object workspace object, because EIFVERSION is set to number. That version does not support dimensions of type NUMBER.
DRG-11480: ctxkbtc memory allocation error: %(1)
ORA-14637: cannot merge a subpartition with itself
ORA-02365: error seeking in file: string
ORA-08450: invalid specification of CR in picture mask
ORA-24813: cannot send or receive an unsupported LOB
QSM-00770: the specified workload string is already referenced by task string
ORA-06710: TLI Driver: send interrupt break message failed