ORA-16709: standby archived log location settings in
conflict with flash recovery area
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 |
PLS-00594: the SELF parameter can be declared only as IN or as IN OUT
LSX-00026: unknown attribute "~S"
ORA-31022: Element not found
ORA-27212: some entrypoints in Media Management Library are missing
RMAN-10015: error compiling PL/SQL program
SQL*Loader-00290: PIECED keyword (on column string) allowed only for lob or long columns
DRG-11118: object string does not exist
ORA-39128: unexpected DbmsJava error number from statement string
TNS-01177: Log Status is OFF. Log file/directory unchanged
ORA-29825: invalid name for indextype
LPX-00228: entity reference "~S" refers to itself
ORA-04066: non-executable object, string