Answer / ram j

This would happen in an UPDATE using MERGE statement.
The cause of this that the Inner query in MERGE ( the one
after USING clause ) returns duplicate rows and Oracle
doesnt know which value to consider for UPDATE.

The only probable solution is to remove the duplicates from
the query or strengthen the join ( ON Clause ) so that the
unique values are considered for update.

Answer / guest

Cause: A stable set of rows could not be got because of
large dml activity or a non-deterministic where clause.

Action: Remove any non-deterministic where clauses and
reissue the dml.

Please add more information about this Error

ORA-19556: required destination LOG_ARCHIVE_DUPLEX_DEST currently is deferred

1 Answers  

---

ORA-09209: sftget: error reading from file

1 Answers  

---

ORA-23532: tables with different synchronization mechanisms are in the same group

1 Answers  

---

ORA-27124: unable to detach from shared memory segment

1 Answers  

---

ORA-09819: Number exceeds maximum legal value

1 Answers  

---

---

DRG-12700: seed word must be a single word

1 Answers  

---

ORA-38455: Expression Filter index should be created by the owner.

1 Answers  

---

ORA-09888: osnTXtt: txipc channel creation failed

1 Answers  

---

RMAN-06143: LIKE may only be specified with COPY

1 Answers  

---

NNL-01067: Trace level: number

1 Answers  

---

ORA-00329: archived log begins at change string, need change string

1 Answers  

---

ORA-06257: NETNTT: cannot send command line to shadow process

1 Answers  

---