ORA-16815: incorrect log transport setting for
AlternateLocation of standby "string"
Answer / guest
Cause: The Data Guard broker detected that the log transport
setting for the standby 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-15198: operation string is not yet available
ORA-14015: too many partition descriptions
ORA-10579: Can not modify control file during test recovery
ORA-06571: Function string does not guarantee not to update database
ORA-32812: subscriber string does not exist
ORA-36956: (XSFCAST25) There are only number PERIODICITY values. You cannot specify more OFFSET values.
TNS-00316: Ran out of data buffers in the pump
ORA-08004: sequence string.NEXTVAL string stringVALUE and cannot be instantiated
ORA-13334: LRS segments not connected
ORA-25235: fetched all messages in current transaction
KUP-04088: data sampling is not supported by this access driver
PLS-01419: Subquery must have either '*' or exactly one column in its select list