ORA-16709: standby archived log location settings in
conflict with flash recovery area
- 1 Answers
- 2915 Views
- I also Faced
- E-Mail Answers
Answer / guest
Cause: The flash recovery area was already set up on the
standby database for storing incoming archived logs from the
primary database. In this case, StandbyArchiveLocation and
AlternateLocation properties should not be used for setting
up standby archived log location. The Data Guard broker
raised this error because it detected one of the following:
(1) the user attempted to use StandbyArchiveLocation or
AlternateLocation properties to set up a standby archived
log location; (2) On the standby database, some local
destination corresponding to the StandbyArchiveLocation or
AlternateLocation properties was still set up to store
archived logs from the primary database.
Action: If you get this error when trying to set property
StandbyArchiveLocation or AlteranteLocation (case (1)
above), avoid setting these properties again. If you get
this error after a broker health check (case (2) above),
re-enable the standby database to clear the error.
Please add more information about this Error
| Is This Answer Correct ? | 0 Yes | 1 No |
LPX-00314: an internal failure occurred
ORA-29812: incorrect object name specified
ORA-14311: Expecting VALUES LESS THAN or AT clause
NPL-00417: received ASN.1 length octet count greater than maximum of string
ORA-29377: consumer group string is not part of top-plan string
ORA-29846: cannot create a local domain index on a string partitioned table
ORA-31223: DBMS_LDAP: cannot open more than string LDAP server connections
ORA-16516: The current state is invalid for the attempted operation.
imp-00038: could not convert to environment character set's handle error occurs while importing oracle 10g data into oracle 9i database.
IMG-00601: out of memory while copying image
PROC-00001: Oracle Cluster Registry cannot be initialized.
ORA-36871: (XSFTDSC01) Object string cannot be used to define a column in a LIMITMAP.
Oracle Errors 
