Answer / guest

Cause: There are outstanding conflicts logged in the
DefError table at the materialized view's master.

Action: Resolve the conflicts in the master DefError table
and refresh again after the table is empty. Alternatively,
refresh with refresh_after_errors set to TRUE, which will
proceed with the refresh even if there are conflicts in the
master's DefError table. Proceeding despite conflicts can
result with an updatable materialized view's changes
appearing to be temporarily lost (until a refresh succeeds
after the conflicts are resolved).

Please add more information about this Error

IMG-00718: the same Temporary LOB cannot be used as both source and destination

1 Answers  

---

ORA-25206: enqueue failed, enqueue to exception queue string.string not permitted

1 Answers  

---

ORA-02423: schema name does not match schema authorization identifier

1 Answers  

---

ORA-31430: subscriber view exists

1 Answers  

---

ORA-12591: TNS:event signal failure

1 Answers  

---

---

PLS-00244: Multiple declarations in foreign function formal parameter list

1 Answers  

---

ORA-22132: hexadecimal string does not correspond to a valid REF

1 Answers  

---

ORA-12323: unable to open database (link name string)

1 Answers  

---

ORA-10652: Object has on-commit materialized views

1 Answers  

---

ORA-30002: SYS_CONNECT_BY_PATH function is not allowed here

1 Answers  

---

NNL-00951: Names created on lookup: number

1 Answers  

---

PLS-00484: redundant exceptions 'string' and 'string' must appear in same exception handler

1 Answers  

---