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-06137: must have recovery catalog for REPORT SCHEMA AT TIME

1 Answers  

---

DRG-11307: operation cannot be performed on an index

1 Answers  

---

ORA-13757: "SQL Tuning Set" "string" is active.

1 Answers  

---

DRG-11823: Not Found

1 Answers  

---

PLS-00425: in SQL, function argument and return types must be SQL type

1 Answers  

---

---

ORA-23328: mview base table "string"."string" differs from master table "string"."string"

1 Answers  

---

PCC-00010: Statement out of place at line number in file string

1 Answers  

---

ORA-00092: LARGE_POOL_SIZE must be greater than LARGE_POOL_MIN_ALLOC

1 Answers  

---

ORA-03203: concurrent update activity makes space analysis impossible

1 Answers  

---

ORA-13137: failed to generate tablespace sequence number

1 Answers  

---

DRG-12511: use ctx_ddl.create_stoplist to create stoplists

1 Answers  

---

DRG-13104: indexes do not have equivalent settings for string

1 Answers  

---