Answer / guest

Cause: There was an error originating from this materialized
view log. One possible cause is that schema redefinition has
occurred on the master table and one or more columns in the
log is now a different type than corresponding master
column(s). Another possible cause is that there is a problem
accessing the underlying materialized view log table.

Action: Check further error messages in stack for more
detail about the cause. If there has been schema
redefinition, drop the materialized view log and recreate it.

Please add more information about this Error

ORA-01189: file is from a different RESETLOGS than previous files

1 Answers  

---

IMG-00706: unsupported or corrupted output format

1 Answers  

---

ORA-39082: Object type string created with compilation warnings

1 Answers  

---

AMD-00103: %s "string" does not have a string

1 Answers  

---

ORA-04002: INCREMENT must be a non-zero integer

1 Answers  

---

ORA-27150: attempt to notify process of pending oradebug call failed

1 Answers  

---

RMAN-06150: auxiliary name for datafile number set to: string

1 Answers  

---

ORA-26577: PRESERVE TABLE can not be used when dropping old style materialized view string.string

1 Answers  

---

ORA-01878: specified field not found in datetime or interval

1 Answers  

---

ORA-04091: table string.string is mutating, trigger/function may not see it

1 Answers  

---

NNL-00873: Fastest update processing time: string

1 Answers  

---

ORA-02758: Allocation of internal array failed

1 Answers  

---