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-29803: missing ANCILLARY keyword

1 Answers  

---

ORA-24814: operation not allowed for temporary LOBs

1 Answers  

---

LFI-01511: unlink() failed(OSD errno = string) in string.

1 Answers  

---

ORA-36644: (XSDUNION07) Concat dimension workspace object contains a previously detected leaf dimension.

1 Answers  

---

ORA-01264: Unable to create string file name

1 Answers  

---

ORA-37116: OLAP API table function error: (string)

1 Answers  

---

ORA-31528: could not find change set string for CDC subscription string

1 Answers  

---

DRG-50911: invalid first document number string

1 Answers  

---

NNL-01031: Name: string

1 Answers  

---

ORA-24032: object string exists, index could not be created for queue table string

1 Answers  

---

ORA-24769: cannot forget an active transaction

1 Answers  

---

ORA-16099: internal error ORA-00600 occurred at standby database

1 Answers  

---