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

ORA-02165: invalid option for CREATE DATABASE

1 Answers  

---

ORA-38702: Cannot update flashback database log file header.

1 Answers  

---

NID-00310: Control File string - reverted

1 Answers  

---

EXP-00093: Could not convert to server character set's handle

2 Answers  

---

ORA-25016: cannot specify column list for insert into nested table view column

1 Answers  

---

ORA-07242: slembfn: translation error, unable to translate error file name.

1 Answers  

---

ORA-07425: sdpri: error string in translating dump file location.

1 Answers  

---

LSX-00149: duplicated ID specified in "~S"

1 Answers  

---

SQL*Loader-00134: invalid option specified for EXTERNAL_TABLE parameter

1 Answers  

---

ORA-38739: Flashback log file is more recent than control file.

1 Answers  

---

ORA-03235: max # extents (string) reached in table string.string subpartition string

1 Answers  

---

ORA-32771: cannot add file to bigfile tablespace

2 Answers  

---