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

DRG-11875: Access Scheme Is Not Allowed

1 Answers  

---

NNL-00834: Slowest delete processing time: string

1 Answers  

---

RMAN-03032: this option of set command needs to be used outside of a run block

1 Answers  

---

QSM-01060: illegal subquery in the HAVING clause

1 Answers  

---

NNL-00292: Scheduled statistic counters to be reset in string

1 Answers  

---

ORA-30340: illegal dimension name

1 Answers  

---

IMP-00041: Warning: object created with compilation warnings

1 Answers  

---

ORA-01422: exact fetch returns more than requested number of rows

1 Answers  

---

ORA-02185: a token other than WORK follows COMMIT

1 Answers   IBM,

---

ORA-06916: CMX: error in data read (t_datain)

1 Answers  

---

RMAN-04021: target database DBID string does not match channel's DBID string

1 Answers  

---

DRG-11708: too many thesauri

1 Answers  

---