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

ORA-39707: compatibile parameter string too high for downgrade to string

1 Answers  

---

ORA-25961: join index prevents dml cascade constraint operation

1 Answers  

---

ORA-12072: updatable materialized view log data for "string"."string" cannot be created

1 Answers  

---

TNS-12612: TNS:connection is busy

1 Answers  

---

ORA-14038: GLOBAL partitioned index must be prefixed

1 Answers  

---

DRG-10517: index string is already valid

1 Answers  

---

DRG-11432: file error while accessing knowledge base

1 Answers  

---

ORA-24334: no descriptor for this position

2 Answers  

---

LPX-00400: an internal error has occurred in XPATH

1 Answers  

---

RMAN-02000: wrong message file version (msg number not found)

1 Answers  

---

EXP-00005: all allowable logon attempts failed

1 Answers  

---

RMAN-06197: Total System Global Area string bytes

1 Answers  

---