Answer / guest

Cause: Supplemental logging was not turned on while there is
a logical standby database in the configuration. This could
happen either on the primary or on the logical standby that
is being switched over to be the primary.

Action: Check Data Guard broker log for more details. Issue
"ALTER DATABASE ADD SUPPLEMENTAL LOG DATA (PRIMARY KEY,
UNIQUE INDEX) COLUMNS" to add supplemental logging.

Please add more information about this Error

QSM-02129: join or filter condition(s) are complex

1 Answers  

---

NNL-00957: Name nodes created: number

1 Answers  

---

ORA-08455: syntax error in CURRENCY SIGN environment clause

1 Answers  

---

ORA-07513: sscgctl: $deq unexpected return on cancel of term. lock

1 Answers  

---

ORA-02442: Cannot drop nonexistent unique key

1 Answers  

---

ORA-32128: setDataBuffer called after fetch has started

1 Answers  

---

ORA-27071: unable to seek to desired position in file

1 Answers  

---

ORA-09847: soacon: ARCH unable to open named pipe.

1 Answers  

---

ORA-22997: VARRAY | OPAQUE stored as LOB is not specified at the table level

1 Answers  

---

RMAN-08504: input archive log thread=string sequence=string recid=string stamp=string

2 Answers  

---

ORA-36378: (XSAGTHRWEIGHT) While running AGGREGATE with multiple threads, the weight variable workspace object specified by your ARGS variable workspace object must exist in the same analytic workspace as your AGGMAP workspace object.

1 Answers  

---

ORA-10570: Test recovery complete

1 Answers  

---