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-10578: Can not allow corruption for managed standby database recovery
IMP-00081: attempt to free unallocated memory
ORA-09935: Unlink of current password file failed.
RMAN-05513: cannot duplicate, controlfile is not current or backup
ORA-00353: log corruption near block string change string time string
ORA-22803: object type contains zero attributes
RMAN-03017: recursion detected in stored script string
ORA-28108: circular security policies detected
DRG-10303: could not queue given commands to be processed
ORA-13352: the coordinates do not describe a circle
ORA-00297: must specify RECOVER DATAFILE LIST before RECOVER DATAFILE START
ORA-12516: TNS:listener could not find available handler with matching protocol stack