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-32338: on commit refresh grab all the detailed tables

1 Answers  

---

ORA-08196: Flashback Table operation is not allowed on AQ tables

1 Answers  

---

PCC-02332: attempted to redefine SQL identifier

1 Answers  

---

ORA-28113: policy predicate has error

1 Answers  

---

ORA-16782: some instance not open for read and write access

1 Answers  

---

NNL-00347: Save_config_on_stop is now OFF

1 Answers  

---

ORA-25279: dequeue as select not supported before 8.2

1 Answers  

---

ORA-14625: subpartition contains rows corresponding to values being dropped

1 Answers  

---

ORA-38728: Cannot FLASHBACK DATABASE to the future.

1 Answers  

---

ORA-29376: number of consumer groups string in top-plan string exceeds string

1 Answers  

---

RMAN-08587: input is copy of datafile string: string

1 Answers  

---

NNL-00955: Hash tables enlarged: number

1 Answers  

---