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

RMAN-08046: channel string: starting compressed full datafile backupset

1 Answers  

---

ORA-13762: The string ranking measure is invalid.

1 Answers  

---

PLS-01712: ANSI does not allow bind variables as INDICATORS

1 Answers  

---

NNL-00260: Server-generated requests now do not require authoritative answers

1 Answers  

---

RMAN-06430: recovery catalog userid cannot be SYS

1 Answers  

---

---

ORA-19714: length for generated name longer than string

1 Answers  

---

SQL*Loader-00566: partial record found at end of datafile

1 Answers  

---

ORA-16608: one or more sites have warnings

2 Answers  

---

PCC-01300: You are not authorized to run Pro*PL/I

1 Answers  

---

QSM-01034: materialized view, string, needs a dimension level to join table, string

1 Answers  

---

ORA-01903: EVENTS keyword expected

1 Answers  

---

ORA-12477: greatest lower bound resulted in an invalid OS label

1 Answers  

---