ORA-16814: incorrect log transport setting for standby's
AlternateLocation
- 1 Answers
- 4287 Views
- I also Faced
- E-Mail Answers
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 |
LSX-00235: invalid URI "~S"
ORA-29519: name string resolved via a synonym in schema string to a class with a different name
ORA-36988: (XSRELGID06) The related dimension of relation workspace object must be of type NUMBER.
ORA-16642: db_unique_name mismatch
NNC-00404: supplied buffer of size string is smaller than minimum size string
ORA-26012: No data found while executing sql statement string for column string - check input for: string
ORA-37100: (XSUNCOMMITTED) You have one or more updated but uncommitted analytic workspaces.
NNL-00974: Name: string
ORA-31610: cannot call this function from a non-master process
TNS-00555: no directory specified for wallet resource locator
TNS-02401: gbname string too long, allowed number characters
ORA-23381: generated object for base object string.string@string does not exist
Oracle Errors 
