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

NNL-00875: Average update processing time: string

1 Answers  

---

ORA-02493: invalid file increment size in NEXT clause

1 Answers  

---

QSM-02070: PCT not supported with this type of partitioning

1 Answers  

---

ORA-25255: incorrect subscription string string

1 Answers  

---

LSX-00242: bad Boolean "~S"

1 Answers  

---

IMG-02005: 2FF05 - incorrect color specification

1 Answers  

---

DRG-51030: wildcard query expansion resulted in too many terms

1 Answers  

---

RMAN-08550: autobackup search outside recovery area not attempted because DBID was not set

1 Answers  

---

NID-00330: The following datafiles are offline immediate:

1 Answers  

---

QSM-01096: Materialized view with grouping sets contains duplicates

1 Answers  

---

ORA-36950: (XSFCAST22) The list of string values cannot have more than number members. You supplied number.

1 Answers  

---

ORA-16609: one or more resources have failed

1 Answers  

---