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-01883: overlap was disabled during a region transition

1 Answers  

---

ORA-12539: TNS:buffer over- or under-flow

1 Answers  

---

TNS-12607: TNS: Connect timeout occurred

1 Answers  

---

ORA-22602: pickler TDS handle [string] is not well-formed

1 Answers  

---

ORA-27192: skgfcls: sbtclose2 returned error - failed to close file

1 Answers  

---

---

ORA-09284: sllfop: cannot allocate read buffer

1 Answers  

---

NNL-00814: Total query processing time: string

1 Answers  

---

ORA-27203: skgfpqb: sbtpcquerybackup returned error

1 Answers  

---

TNS-03506: Failed to create address binding

1 Answers  

---

ORA-14094: invalid ALTER TABLE EXCHANGE PARTITION option

1 Answers  

---

TNS-00228: Failure in finding pump data

1 Answers  

---

RMAN-20005: target database name is ambiguous

1 Answers  

---