Interested to Buy Any Domain ? << Click Here >> for more details...
ORA-16814: incorrect log transport setting for standby's
AlternateLocation
- 1 Answers
- 4953 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 |
ORA-26048: Scoped REF column has wrong table name.
ORA-06712: TLI Driver: error on accept
TNS-01114: LSNRCTL could not perform local OS authentication with the listener
ORA-31479: could not create LogMiner session
ORA-21708: inappropriate operation on a transient object
PCC-02112: OBJECTS option ignored. OBJECTS=YES is not allowed for DBMS=V6 or V7.
ORA-38710: Flashback log version string is incompatible with ORACLE version string.
ORA-02043: must end current transaction before executing string
RMAN-06540: tablespace string will be excluded from future whole database backups
ORA-19569: no device is allocated to this session
ORA-13339: LRS polygon clipping across multiple rings
ORA-22958: This operation is not allowed in check constraints or triggers
Oracle Errors 
